Wikibooks enwikibooks https://en.wikibooks.org/wiki/Main_Page MediaWiki 1.46.0-wmf.26 first-letter Media Special Talk User User talk Wikibooks Wikibooks talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Cookbook Cookbook talk Transwiki Transwiki talk Wikijunior Wikijunior talk Subject Subject talk TimedText TimedText talk Module Module talk Event Event talk 4 385 4634174 4634022 2026-05-04T19:15:10Z Kittycataclysm 3371989 /* History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23 */ Reply 4634174 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == Algebra/Chapter 10/Symmetric Polynomials == I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC) :'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC) :{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC) ::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) == [[Template:Qr-twwp]] == This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC) == [[Ghouls of the Miskatonic]] == I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC) :{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC) ::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC) :::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC) ::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC) == [[Annotations to The Joy of Music]] == Abandoned with minimal content. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:48, 24 August 2025 (UTC) :Author of the book/page here. I wouldn't call it "abandoned": it's still a start, but I'm here and do plan to fill out the rest (most of the annotations are for the early part of the book though). :I'm an experience editor at Wikipedia and Wiktionary, but am not very familiar with Wikibooks standards. When reading this book, I found myself looking up unfamiliar terms and quotes and thought some annotations would be helpful when reading or especially studying the text. It's a notable book by a notable author (extensive Wikipedia page). Here the source text is not freely available, but annotations are easy to add separately. I looked at [[WB:AT]] and existing examples of annotations and tried to follow them. Per [[WB:WIW]], the scope is instructional texts (including annotated texts), and minor works are in scope. :I'll grant that this is not large and not likely to become very long – many books only need minor annotations – but the content would certainly have been helpful to me when reading this book. :Are there specific changes you'd suggest or general guidelines to follow in this kind of book? ::—Nils von Barth ([[User:Nbarth|nbarth]]) ([[User talk:Nbarth|talk]]) 02:42, 3 September 2025 (UTC) ::: Pinging @[[User:Kittycataclysm|Kittycataclysm]] and @[[User:Nbarth|Nbarth]]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:15, 21 April 2026 (UTC) ::::I think I stand by my original reasoning given that no work has been done on it, and I don't think it contains enough content to hang around in main space for so long. What about moving it to user space? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:16, 23 April 2026 (UTC) == [[Template:Deleted page]] == Per [[Wikibooks:Reading room/Proposals#Retiring Template:Deleted page]], this is because the template is unnecessary given that creation protection (salting) is used instead. I am also proposing the deletion of the following categories used by this template: * [[:Category:Protected deleted categories]] * [[:Category:Protected deleted pages]] Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:36, 29 January 2026 (UTC) :This seems premature - [[:Category:Protected deleted pages]] is still in use for pages with generic names. Is there a plan to transition those pages to create protection; if so, can that be implemented before deleting the templates/categories? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:28, 30 January 2026 (UTC) ::JJPMaster proposed that the pages listed in that category should be moved to the [[MediaWiki:Titleblacklist|title blacklist]], and that {{tlx|naming policy notice}} shall be fully protected and used as an interface (title blacklist) message. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:18, 30 January 2026 (UTC) :::@[[User:Omphalographer|Omphalographer]]: Have you seen this reply? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 15:28, 11 February 2026 (UTC) ::::I have, but I'm not sure I follow. These templates, and the categories which they populate, are currently in use. Once that's no longer the case, I have no objection to deleting them - but they need to be delinked first. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:20, 12 February 2026 (UTC) :::::I deleted the categories mentioned above, moved all the generic titles to the title blacklist, and for those pages that used {{tlx|Deleted page}}, I deleted then applied creation protection. An uninvolved admin can delete {{tlx|Deleted page}} and then close this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:39, 30 March 2026 (UTC) == [[Cereal Grains Through History]] == Abandoned with no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:18, 30 March 2026 (UTC) :[[User:Kittycataclysm|Kittycataclysm]]: The author (Karosent) objects to the deletion per their talk page: {{quote|:Yes, please do not delete this wiki book. It is a work in progress. It is just taking some time to make progress on it. Thank you.}} :{{courtesy ping}} to @[[User:Karosent|Karosent]] as the author of the book for their input. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:42, 30 March 2026 (UTC) ::If the user does intend to work on it, I think the best course of action would be moving it to user space until more progress is made. Having abandoned works around the main space is a bit messy. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 28 April 2026 (UTC) ::: {{courtesy ping}} to [[User:Karosent|Karosent]] again. Do you agree with the pages being moved to your userspace? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:23, 3 May 2026 (UTC) == [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23]] == Transcribed from a magazine copy that cannot be traced via the URL provided. Generally archival of primary source works is undertaken on Wikisource (not Wikibooks), backed by a suitable page scan. This isn't at present. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 16:32, 27 April 2026 (UTC) :This doesn't need an RfD since it is obviously out of scope. You can instead put a CSD tag on the page. Additionally, it seems that the entire /Publications section contains only source works here, so it might require a mass deletion. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:32, 27 April 2026 (UTC) ::@[[User:Samuel.dellit|Samuel.dellit]] looping you in here so you're aware. I don't think any pages like this (i.e. source text) can be kept here, since we are explicitly and unambiguously not a text repository per [[WB:SOURCE]]. I am inclined to speedily delete for that reason, but I want to hear from the primary editor. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:40, 27 April 2026 (UTC) :::Thanks for looping me in. :::This is not simply a transcription of the magazine. :::It includes new formatting to make the content better reachable. :::It includes commentary to place the transcribed material in context. :::It permits related material to be placed in chronological order. :::The version here is not complete (as per banner included), hence the URL link not working (National Library of Australia's Trove has been updated). :::There is no point in placing this material on Wikisource as the Trove website is functionally similar and now provides for text correction (a fairly recent development). :::I have not be editing Wikibooks for the last six month's following a personal matter but now slowly returning to the task. :::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:08, 27 April 2026 (UTC) ::::I'm still not sure whether this makes it in-scope at Wikibooks and suitable for the book-like scope of this work, so I'm looping in other admins to weigh in on scope and consensus @[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:SHB2000|SHB2000]]. For material that is planned but not yet enacted after a significant period, I'm wondering if user space is more suitable than main space. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:48, 3 May 2026 (UTC) :::::This is just one page of a book, right? It's not like the entire wikibook is a transcription. I'm inclined to keep it unless there is something I am missing. "For material that is planned but not yet enacted after a significant period" - that's a draft and can generally stay in article space. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:09, 4 May 2026 (UTC) ::::::My thoughts are similar to Leaderboard's. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 05:47, 4 May 2026 (UTC) ::::::@[[User:Leaderboard|Leaderboard]] @[[User:SHB2000|SHB2000]] Thank you, and good to know. Unless I am misunderstanding, the plan is actually to host many source texts in this book's namespace (see other subpages in [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications]]) and not limited to this one page. Additionally, do we have anything in policy regarding how long drafts can stay in mainspace? I couldn't find anything, and it strikes me as unconstructive to the project if pages with significant issues (e.g. scope, quality, etc) are left in the mainspace for months to years. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 4 May 2026 (UTC) : As an admin who was involved in deleting this (and related subpages) and ''only'' undeleting it later per the author's request, I therefore '''recuse''' (will not do) on taking any administrative actions for this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:33, 27 April 2026 (UTC) :{{vd}} - including other similar pages - per nom. Transcriptions of previously published works, like these magazines, belong on Wikisource. I don't see any evidence of substantial commentary in any of the pages I've looked at. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:47, 28 April 2026 (UTC) :'''Retain''' - including other similar pages - annotated texts WB:AT are a clear exception to Wikibooks "Not a text repository" policy; these are subpages of a very large body of work (I understand the largest Wikibook in Wikibooks) and integral to its overall development; yes, the pages are a work in progress and the annotations are as yet limited, but I will now prioritise their development[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:28, 3 May 2026 (UTC) == [[History Books]] == Minimal existing content is editorialized, book scope unclear, no sourcing —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:47, 27 April 2026 (UTC) :{{comment}} - there is one unlinked subpage of this book, [[History Books/Who Was Alexander the Great/Introduction]]. I'm not impressed by the content (it's basically historical fiction written for a young child), but it's not hopeless. I'd encourage the author to create an account to allow us to communicate with them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:34, 28 April 2026 (UTC) ::If it is really aimed at children, shouldn't it be moved to the Wikijunior: namespace? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:55, 28 April 2026 (UTC) == [[Music Production Guide by Taskin Ahmed Kayum]] == no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:50, 27 April 2026 (UTC) :{{vd}} - this is not a useful guide. It fails to provide any actionable directions to the reader. :As some advice to the author: you may want to try writing a guide on a narrower topic which you are personally familiar with, like how to produce a particular type of music, or how to use a particular piece of software to produce music. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 03:44, 28 April 2026 (UTC) :{{vd}}, no useful content. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:17, 28 April 2026 (UTC) :{{done}} [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:10, 4 May 2026 (UTC) == [[FORTRAN program for calculating representative parameters and operating conditions of AC overhead transmission lines]] == As the title suggests, this page is primarily code for a computer program, not a book. Wikibooks is not a code hosting web site; this code might be more appropriate as a repository on a code hosting site such as Codeberg or GitHub. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:30, 28 April 2026 (UTC) :{{Del}}, the book seems to be out of scope in its current state, especially considering that most of it is just code and it has no subpages. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:35, 28 April 2026 (UTC) :I agree that this is not a book in its current form. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:26, 28 April 2026 (UTC) == Various Transwiki Namespace Pages == *[[Transwiki:Digging trees and shrubs for transplanting]] *[[Transwiki:Create bit mask algorithm]] *[[Transwiki:CRFL (CaReFuL mnemonic)]] *[[Transwiki:Developing a library websites]] *<s>[[Transwiki:Fischer's Lovebird]]</s> *[[Transwiki:Float (breakdancing move)]] *[[Transwiki:Front door method]] *[[Transwiki:Hair Color Tips and Tricks]] *[[Transwiki:Horse grooming]] *[[Transwiki:How to distinguish a monocot from a dicot]] *[[Transwiki:Humminbird PC connection cable wiring diagramm. (AS PC2)]] *[[Transwiki:Inbound connectivity under 3G Datacard]] *[[Transwiki:Common Test Cases]] *[[Transwiki:Comparison of EHR solution providers]] *[[Transwiki:Computer forensics]] *[[Transwiki:Barter]] *[[Transwiki:Career domains in computer science]] *[[Transwiki:Buying snowboards]] *[[Transwiki:Common chemicals]] *[[Transwiki:B+ Tree Java Implementation]] *[[Transwiki:Cattle judging]] *[[Transwiki:Two-handed manual alphabet]] *<s>[[Transwiki:Silver-copper nitrate]]</s> *[[Transwiki:Slating procedure]] *<s>[[Transwiki:Rhodesia's Unilateral Declaration of Independence]]</s> *[[Transwiki:Technical writing for the Web]] *[[Transwiki:Technology roadmap]] *[[Transwiki:Special product and factoring]] *[[Transwiki:Researching Japanese names]] *[[Transwiki:Job-seeking expense tax deductions]] *[[Transwiki:Labeling family photos]] *[[Transwiki:List of mnemonics for the cranial nerves]] *<s>[[Transwiki:Maude system]]</s> *[[Transwiki:Model rocket]] *[[Transwiki:NIS Configuration on Debian]] *<s>[[Transwiki:Paper model tutorials]]</s> *[[Transwiki:Photosynthesis misconceptions]] *[[Transwiki:Project Schedule Development]] This list includes pages in the Transwiki namespaces that have mostly been imported from enwiki, which makes them unusable in a book. If there are any pages here that can be turned into a book, let me know and I can strike them out. I believe that all of these pages should be deleted as we do not allow encyclopedic material on Wikibooks, and these are mostly articles that were imported from English Wikipedia. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 13:25, 1 May 2026 (UTC) :[[Transwiki:Cattle judging]], [[Transwiki:Horse grooming]], and [[Transwiki:Hair Color Tips and Tricks]] could be viable book content. None of the others obviously looked usable to me. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 16:39, 1 May 2026 (UTC) ::I excluded Transwikis that could be added to books here, but the pages you mentioned do not seem usable to me (unless a specific book where they could be added is created). Additionally, in [[Transwiki:Hair Color Tips and Tricks]], the tone is unfit for Wikibooks. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:39, 1 May 2026 (UTC) :I deleted a few of these that seemed unambiguously out of scope. I agree that most of them are not sufficiently book-like in scope on their own, and I think they warrant deletion unless anyone can identify specific books that can host them. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:01, 3 May 2026 (UTC) == [[A second course to linear algebra - Matrix algebra]] == Abandoned, with several unresolved quality issues as outlined at [[User talk:Akira tanzivana]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:04, 3 May 2026 (UTC) == [[Bengali–Assamese script]] == Abandoned for three years with minimal content that is seemingly redundant to [[Bengali]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:08, 3 May 2026 (UTC) hu1gae7mzl8wxat8sadxn2zmsuvyre8 4634186 4634174 2026-05-04T19:59:46Z Samuel.dellit 1387936 /* History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23 */ Reply 4634186 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == Algebra/Chapter 10/Symmetric Polynomials == I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC) :'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC) :{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC) ::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) == [[Template:Qr-twwp]] == This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC) == [[Ghouls of the Miskatonic]] == I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC) :{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC) ::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC) :::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC) ::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC) == [[Annotations to The Joy of Music]] == Abandoned with minimal content. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:48, 24 August 2025 (UTC) :Author of the book/page here. I wouldn't call it "abandoned": it's still a start, but I'm here and do plan to fill out the rest (most of the annotations are for the early part of the book though). :I'm an experience editor at Wikipedia and Wiktionary, but am not very familiar with Wikibooks standards. When reading this book, I found myself looking up unfamiliar terms and quotes and thought some annotations would be helpful when reading or especially studying the text. It's a notable book by a notable author (extensive Wikipedia page). Here the source text is not freely available, but annotations are easy to add separately. I looked at [[WB:AT]] and existing examples of annotations and tried to follow them. Per [[WB:WIW]], the scope is instructional texts (including annotated texts), and minor works are in scope. :I'll grant that this is not large and not likely to become very long – many books only need minor annotations – but the content would certainly have been helpful to me when reading this book. :Are there specific changes you'd suggest or general guidelines to follow in this kind of book? ::—Nils von Barth ([[User:Nbarth|nbarth]]) ([[User talk:Nbarth|talk]]) 02:42, 3 September 2025 (UTC) ::: Pinging @[[User:Kittycataclysm|Kittycataclysm]] and @[[User:Nbarth|Nbarth]]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:15, 21 April 2026 (UTC) ::::I think I stand by my original reasoning given that no work has been done on it, and I don't think it contains enough content to hang around in main space for so long. What about moving it to user space? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:16, 23 April 2026 (UTC) == [[Template:Deleted page]] == Per [[Wikibooks:Reading room/Proposals#Retiring Template:Deleted page]], this is because the template is unnecessary given that creation protection (salting) is used instead. I am also proposing the deletion of the following categories used by this template: * [[:Category:Protected deleted categories]] * [[:Category:Protected deleted pages]] Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:36, 29 January 2026 (UTC) :This seems premature - [[:Category:Protected deleted pages]] is still in use for pages with generic names. Is there a plan to transition those pages to create protection; if so, can that be implemented before deleting the templates/categories? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:28, 30 January 2026 (UTC) ::JJPMaster proposed that the pages listed in that category should be moved to the [[MediaWiki:Titleblacklist|title blacklist]], and that {{tlx|naming policy notice}} shall be fully protected and used as an interface (title blacklist) message. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:18, 30 January 2026 (UTC) :::@[[User:Omphalographer|Omphalographer]]: Have you seen this reply? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 15:28, 11 February 2026 (UTC) ::::I have, but I'm not sure I follow. These templates, and the categories which they populate, are currently in use. Once that's no longer the case, I have no objection to deleting them - but they need to be delinked first. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:20, 12 February 2026 (UTC) :::::I deleted the categories mentioned above, moved all the generic titles to the title blacklist, and for those pages that used {{tlx|Deleted page}}, I deleted then applied creation protection. An uninvolved admin can delete {{tlx|Deleted page}} and then close this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:39, 30 March 2026 (UTC) == [[Cereal Grains Through History]] == Abandoned with no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:18, 30 March 2026 (UTC) :[[User:Kittycataclysm|Kittycataclysm]]: The author (Karosent) objects to the deletion per their talk page: {{quote|:Yes, please do not delete this wiki book. It is a work in progress. It is just taking some time to make progress on it. Thank you.}} :{{courtesy ping}} to @[[User:Karosent|Karosent]] as the author of the book for their input. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:42, 30 March 2026 (UTC) ::If the user does intend to work on it, I think the best course of action would be moving it to user space until more progress is made. Having abandoned works around the main space is a bit messy. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 28 April 2026 (UTC) ::: {{courtesy ping}} to [[User:Karosent|Karosent]] again. Do you agree with the pages being moved to your userspace? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:23, 3 May 2026 (UTC) == [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23]] == Transcribed from a magazine copy that cannot be traced via the URL provided. Generally archival of primary source works is undertaken on Wikisource (not Wikibooks), backed by a suitable page scan. This isn't at present. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 16:32, 27 April 2026 (UTC) :This doesn't need an RfD since it is obviously out of scope. You can instead put a CSD tag on the page. Additionally, it seems that the entire /Publications section contains only source works here, so it might require a mass deletion. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:32, 27 April 2026 (UTC) ::@[[User:Samuel.dellit|Samuel.dellit]] looping you in here so you're aware. I don't think any pages like this (i.e. source text) can be kept here, since we are explicitly and unambiguously not a text repository per [[WB:SOURCE]]. I am inclined to speedily delete for that reason, but I want to hear from the primary editor. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:40, 27 April 2026 (UTC) :::Thanks for looping me in. :::This is not simply a transcription of the magazine. :::It includes new formatting to make the content better reachable. :::It includes commentary to place the transcribed material in context. :::It permits related material to be placed in chronological order. :::The version here is not complete (as per banner included), hence the URL link not working (National Library of Australia's Trove has been updated). :::There is no point in placing this material on Wikisource as the Trove website is functionally similar and now provides for text correction (a fairly recent development). :::I have not be editing Wikibooks for the last six month's following a personal matter but now slowly returning to the task. :::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:08, 27 April 2026 (UTC) ::::I'm still not sure whether this makes it in-scope at Wikibooks and suitable for the book-like scope of this work, so I'm looping in other admins to weigh in on scope and consensus @[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:SHB2000|SHB2000]]. For material that is planned but not yet enacted after a significant period, I'm wondering if user space is more suitable than main space. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:48, 3 May 2026 (UTC) :::::This is just one page of a book, right? It's not like the entire wikibook is a transcription. I'm inclined to keep it unless there is something I am missing. "For material that is planned but not yet enacted after a significant period" - that's a draft and can generally stay in article space. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:09, 4 May 2026 (UTC) ::::::My thoughts are similar to Leaderboard's. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 05:47, 4 May 2026 (UTC) ::::::@[[User:Leaderboard|Leaderboard]] @[[User:SHB2000|SHB2000]] Thank you, and good to know. Unless I am misunderstanding, the plan is actually to host many source texts in this book's namespace (see other subpages in [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications]]) and not limited to this one page. Additionally, do we have anything in policy regarding how long drafts can stay in mainspace? I couldn't find anything, and it strikes me as unconstructive to the project if pages with significant issues (e.g. scope, quality, etc) are left in the mainspace for months to years. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 4 May 2026 (UTC) :::::::@[[User:Kittycataclysm|Kittycataclysm]] Thank you for your considered responses, the following is provided as background summary. :::::::(1) I should mention that all of these pages were speedily deleted six months ago on the basis of breach of copyright, despite the fact that they are in the public domain (yes I was remiss in not making this clear in the relevant discussion pages, and yes I was aware of the need for copyright explanation, but was overly focussed on content creation). I was hit by about 20 simultaneous speedily delete notifications, responded to 2 or 3 thinking that would be sufficient, but later found they had all been deleted (I was not active on Wikibooks at the time). My intention is to provide clear public domain information for each page in the coming months, but I am only one person and need time to give effect. Copyright worldwide is quite complex. :::::::(2) I was hit by this RfD about 2 weeks ago, nominally a single subpage, but with the threat of dozens of subpages being similarly treated. This time the basis of the RfD was breach of the "Not a text repository" policy, of which I was not previously aware. I see in the policy that there is a clear exception for annotated texts and I will further develop content in support of that exception (you will see that is my general practice in any event). There are literally hundreds of articles in this Wikibook already heavily annotated, simply on the basis of good authorship e.g. :::::::https://en.wikibooks.org/wiki/History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Biographies/Clement_Edgar_Ames/Notes :::::::https://en.wikibooks.org/wiki/History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Stations/7BU_Burnie/Notes :::::::But, again, I am only one person and need time to give effect. [[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:59, 4 May 2026 (UTC) : As an admin who was involved in deleting this (and related subpages) and ''only'' undeleting it later per the author's request, I therefore '''recuse''' (will not do) on taking any administrative actions for this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:33, 27 April 2026 (UTC) :{{vd}} - including other similar pages - per nom. Transcriptions of previously published works, like these magazines, belong on Wikisource. I don't see any evidence of substantial commentary in any of the pages I've looked at. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:47, 28 April 2026 (UTC) :'''Retain''' - including other similar pages - annotated texts WB:AT are a clear exception to Wikibooks "Not a text repository" policy; these are subpages of a very large body of work (I understand the largest Wikibook in Wikibooks) and integral to its overall development; yes, the pages are a work in progress and the annotations are as yet limited, but I will now prioritise their development[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:28, 3 May 2026 (UTC) == [[History Books]] == Minimal existing content is editorialized, book scope unclear, no sourcing —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:47, 27 April 2026 (UTC) :{{comment}} - there is one unlinked subpage of this book, [[History Books/Who Was Alexander the Great/Introduction]]. I'm not impressed by the content (it's basically historical fiction written for a young child), but it's not hopeless. I'd encourage the author to create an account to allow us to communicate with them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:34, 28 April 2026 (UTC) ::If it is really aimed at children, shouldn't it be moved to the Wikijunior: namespace? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:55, 28 April 2026 (UTC) == [[Music Production Guide by Taskin Ahmed Kayum]] == no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:50, 27 April 2026 (UTC) :{{vd}} - this is not a useful guide. It fails to provide any actionable directions to the reader. :As some advice to the author: you may want to try writing a guide on a narrower topic which you are personally familiar with, like how to produce a particular type of music, or how to use a particular piece of software to produce music. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 03:44, 28 April 2026 (UTC) :{{vd}}, no useful content. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:17, 28 April 2026 (UTC) :{{done}} [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:10, 4 May 2026 (UTC) == [[FORTRAN program for calculating representative parameters and operating conditions of AC overhead transmission lines]] == As the title suggests, this page is primarily code for a computer program, not a book. Wikibooks is not a code hosting web site; this code might be more appropriate as a repository on a code hosting site such as Codeberg or GitHub. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:30, 28 April 2026 (UTC) :{{Del}}, the book seems to be out of scope in its current state, especially considering that most of it is just code and it has no subpages. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:35, 28 April 2026 (UTC) :I agree that this is not a book in its current form. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:26, 28 April 2026 (UTC) == Various Transwiki Namespace Pages == *[[Transwiki:Digging trees and shrubs for transplanting]] *[[Transwiki:Create bit mask algorithm]] *[[Transwiki:CRFL (CaReFuL mnemonic)]] *[[Transwiki:Developing a library websites]] *<s>[[Transwiki:Fischer's Lovebird]]</s> *[[Transwiki:Float (breakdancing move)]] *[[Transwiki:Front door method]] *[[Transwiki:Hair Color Tips and Tricks]] *[[Transwiki:Horse grooming]] *[[Transwiki:How to distinguish a monocot from a dicot]] *[[Transwiki:Humminbird PC connection cable wiring diagramm. (AS PC2)]] *[[Transwiki:Inbound connectivity under 3G Datacard]] *[[Transwiki:Common Test Cases]] *[[Transwiki:Comparison of EHR solution providers]] *[[Transwiki:Computer forensics]] *[[Transwiki:Barter]] *[[Transwiki:Career domains in computer science]] *[[Transwiki:Buying snowboards]] *[[Transwiki:Common chemicals]] *[[Transwiki:B+ Tree Java Implementation]] *[[Transwiki:Cattle judging]] *[[Transwiki:Two-handed manual alphabet]] *<s>[[Transwiki:Silver-copper nitrate]]</s> *[[Transwiki:Slating procedure]] *<s>[[Transwiki:Rhodesia's Unilateral Declaration of Independence]]</s> *[[Transwiki:Technical writing for the Web]] *[[Transwiki:Technology roadmap]] *[[Transwiki:Special product and factoring]] *[[Transwiki:Researching Japanese names]] *[[Transwiki:Job-seeking expense tax deductions]] *[[Transwiki:Labeling family photos]] *[[Transwiki:List of mnemonics for the cranial nerves]] *<s>[[Transwiki:Maude system]]</s> *[[Transwiki:Model rocket]] *[[Transwiki:NIS Configuration on Debian]] *<s>[[Transwiki:Paper model tutorials]]</s> *[[Transwiki:Photosynthesis misconceptions]] *[[Transwiki:Project Schedule Development]] This list includes pages in the Transwiki namespaces that have mostly been imported from enwiki, which makes them unusable in a book. If there are any pages here that can be turned into a book, let me know and I can strike them out. I believe that all of these pages should be deleted as we do not allow encyclopedic material on Wikibooks, and these are mostly articles that were imported from English Wikipedia. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 13:25, 1 May 2026 (UTC) :[[Transwiki:Cattle judging]], [[Transwiki:Horse grooming]], and [[Transwiki:Hair Color Tips and Tricks]] could be viable book content. None of the others obviously looked usable to me. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 16:39, 1 May 2026 (UTC) ::I excluded Transwikis that could be added to books here, but the pages you mentioned do not seem usable to me (unless a specific book where they could be added is created). Additionally, in [[Transwiki:Hair Color Tips and Tricks]], the tone is unfit for Wikibooks. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:39, 1 May 2026 (UTC) :I deleted a few of these that seemed unambiguously out of scope. I agree that most of them are not sufficiently book-like in scope on their own, and I think they warrant deletion unless anyone can identify specific books that can host them. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:01, 3 May 2026 (UTC) == [[A second course to linear algebra - Matrix algebra]] == Abandoned, with several unresolved quality issues as outlined at [[User talk:Akira tanzivana]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:04, 3 May 2026 (UTC) == [[Bengali–Assamese script]] == Abandoned for three years with minimal content that is seemingly redundant to [[Bengali]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:08, 3 May 2026 (UTC) mjw2bp5l70z4ym0z7op1zpx9tkwk7o6 4634219 4634186 2026-05-05T04:49:32Z Leaderboard 1176064 /* History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23 */ Reply 4634219 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == Algebra/Chapter 10/Symmetric Polynomials == I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC) :'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC) :{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC) ::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) == [[Template:Qr-twwp]] == This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC) == [[Ghouls of the Miskatonic]] == I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC) :{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC) ::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC) :::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC) ::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC) == [[Annotations to The Joy of Music]] == Abandoned with minimal content. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:48, 24 August 2025 (UTC) :Author of the book/page here. I wouldn't call it "abandoned": it's still a start, but I'm here and do plan to fill out the rest (most of the annotations are for the early part of the book though). :I'm an experience editor at Wikipedia and Wiktionary, but am not very familiar with Wikibooks standards. When reading this book, I found myself looking up unfamiliar terms and quotes and thought some annotations would be helpful when reading or especially studying the text. It's a notable book by a notable author (extensive Wikipedia page). Here the source text is not freely available, but annotations are easy to add separately. I looked at [[WB:AT]] and existing examples of annotations and tried to follow them. Per [[WB:WIW]], the scope is instructional texts (including annotated texts), and minor works are in scope. :I'll grant that this is not large and not likely to become very long – many books only need minor annotations – but the content would certainly have been helpful to me when reading this book. :Are there specific changes you'd suggest or general guidelines to follow in this kind of book? ::—Nils von Barth ([[User:Nbarth|nbarth]]) ([[User talk:Nbarth|talk]]) 02:42, 3 September 2025 (UTC) ::: Pinging @[[User:Kittycataclysm|Kittycataclysm]] and @[[User:Nbarth|Nbarth]]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:15, 21 April 2026 (UTC) ::::I think I stand by my original reasoning given that no work has been done on it, and I don't think it contains enough content to hang around in main space for so long. What about moving it to user space? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:16, 23 April 2026 (UTC) == [[Template:Deleted page]] == Per [[Wikibooks:Reading room/Proposals#Retiring Template:Deleted page]], this is because the template is unnecessary given that creation protection (salting) is used instead. I am also proposing the deletion of the following categories used by this template: * [[:Category:Protected deleted categories]] * [[:Category:Protected deleted pages]] Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:36, 29 January 2026 (UTC) :This seems premature - [[:Category:Protected deleted pages]] is still in use for pages with generic names. Is there a plan to transition those pages to create protection; if so, can that be implemented before deleting the templates/categories? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:28, 30 January 2026 (UTC) ::JJPMaster proposed that the pages listed in that category should be moved to the [[MediaWiki:Titleblacklist|title blacklist]], and that {{tlx|naming policy notice}} shall be fully protected and used as an interface (title blacklist) message. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:18, 30 January 2026 (UTC) :::@[[User:Omphalographer|Omphalographer]]: Have you seen this reply? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 15:28, 11 February 2026 (UTC) ::::I have, but I'm not sure I follow. These templates, and the categories which they populate, are currently in use. Once that's no longer the case, I have no objection to deleting them - but they need to be delinked first. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:20, 12 February 2026 (UTC) :::::I deleted the categories mentioned above, moved all the generic titles to the title blacklist, and for those pages that used {{tlx|Deleted page}}, I deleted then applied creation protection. An uninvolved admin can delete {{tlx|Deleted page}} and then close this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:39, 30 March 2026 (UTC) == [[Cereal Grains Through History]] == Abandoned with no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:18, 30 March 2026 (UTC) :[[User:Kittycataclysm|Kittycataclysm]]: The author (Karosent) objects to the deletion per their talk page: {{quote|:Yes, please do not delete this wiki book. It is a work in progress. It is just taking some time to make progress on it. Thank you.}} :{{courtesy ping}} to @[[User:Karosent|Karosent]] as the author of the book for their input. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:42, 30 March 2026 (UTC) ::If the user does intend to work on it, I think the best course of action would be moving it to user space until more progress is made. Having abandoned works around the main space is a bit messy. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 28 April 2026 (UTC) ::: {{courtesy ping}} to [[User:Karosent|Karosent]] again. Do you agree with the pages being moved to your userspace? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:23, 3 May 2026 (UTC) == [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23]] == Transcribed from a magazine copy that cannot be traced via the URL provided. Generally archival of primary source works is undertaken on Wikisource (not Wikibooks), backed by a suitable page scan. This isn't at present. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 16:32, 27 April 2026 (UTC) :This doesn't need an RfD since it is obviously out of scope. You can instead put a CSD tag on the page. Additionally, it seems that the entire /Publications section contains only source works here, so it might require a mass deletion. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:32, 27 April 2026 (UTC) ::@[[User:Samuel.dellit|Samuel.dellit]] looping you in here so you're aware. I don't think any pages like this (i.e. source text) can be kept here, since we are explicitly and unambiguously not a text repository per [[WB:SOURCE]]. I am inclined to speedily delete for that reason, but I want to hear from the primary editor. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:40, 27 April 2026 (UTC) :::Thanks for looping me in. :::This is not simply a transcription of the magazine. :::It includes new formatting to make the content better reachable. :::It includes commentary to place the transcribed material in context. :::It permits related material to be placed in chronological order. :::The version here is not complete (as per banner included), hence the URL link not working (National Library of Australia's Trove has been updated). :::There is no point in placing this material on Wikisource as the Trove website is functionally similar and now provides for text correction (a fairly recent development). :::I have not be editing Wikibooks for the last six month's following a personal matter but now slowly returning to the task. :::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:08, 27 April 2026 (UTC) ::::I'm still not sure whether this makes it in-scope at Wikibooks and suitable for the book-like scope of this work, so I'm looping in other admins to weigh in on scope and consensus @[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:SHB2000|SHB2000]]. For material that is planned but not yet enacted after a significant period, I'm wondering if user space is more suitable than main space. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:48, 3 May 2026 (UTC) :::::This is just one page of a book, right? It's not like the entire wikibook is a transcription. I'm inclined to keep it unless there is something I am missing. "For material that is planned but not yet enacted after a significant period" - that's a draft and can generally stay in article space. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:09, 4 May 2026 (UTC) ::::::My thoughts are similar to Leaderboard's. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 05:47, 4 May 2026 (UTC) ::::::@[[User:Leaderboard|Leaderboard]] @[[User:SHB2000|SHB2000]] Thank you, and good to know. Unless I am misunderstanding, the plan is actually to host many source texts in this book's namespace (see other subpages in [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications]]) and not limited to this one page. Additionally, do we have anything in policy regarding how long drafts can stay in mainspace? I couldn't find anything, and it strikes me as unconstructive to the project if pages with significant issues (e.g. scope, quality, etc) are left in the mainspace for months to years. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 4 May 2026 (UTC) :::::::@[[User:Kittycataclysm|Kittycataclysm]] Thank you for your considered responses, the following is provided as background summary. :::::::(1) I should mention that all of these pages were speedily deleted six months ago on the basis of breach of copyright, despite the fact that they are in the public domain (yes I was remiss in not making this clear in the relevant discussion pages, and yes I was aware of the need for copyright explanation, but was overly focussed on content creation). I was hit by about 20 simultaneous speedily delete notifications, responded to 2 or 3 thinking that would be sufficient, but later found they had all been deleted (I was not active on Wikibooks at the time). My intention is to provide clear public domain information for each page in the coming months, but I am only one person and need time to give effect. Copyright worldwide is quite complex. :::::::(2) I was hit by this RfD about 2 weeks ago, nominally a single subpage, but with the threat of dozens of subpages being similarly treated. This time the basis of the RfD was breach of the "Not a text repository" policy, of which I was not previously aware. I see in the policy that there is a clear exception for annotated texts and I will further develop content in support of that exception (you will see that is my general practice in any event). There are literally hundreds of articles in this Wikibook already heavily annotated, simply on the basis of good authorship e.g. :::::::https://en.wikibooks.org/wiki/History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Biographies/Clement_Edgar_Ames/Notes :::::::https://en.wikibooks.org/wiki/History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Stations/7BU_Burnie/Notes :::::::But, again, I am only one person and need time to give effect. [[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:59, 4 May 2026 (UTC) :::::::@[[User:Kittycataclysm|Kittycataclysm]] As far as I can see, isn't the goal to annotate most of those pages? And there is no set limit for a draft. The main reason we'd delete a draft is if the book ''itself'' has nothing of value, which is not the case here. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 04:49, 5 May 2026 (UTC) : As an admin who was involved in deleting this (and related subpages) and ''only'' undeleting it later per the author's request, I therefore '''recuse''' (will not do) on taking any administrative actions for this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:33, 27 April 2026 (UTC) :{{vd}} - including other similar pages - per nom. Transcriptions of previously published works, like these magazines, belong on Wikisource. I don't see any evidence of substantial commentary in any of the pages I've looked at. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:47, 28 April 2026 (UTC) :'''Retain''' - including other similar pages - annotated texts WB:AT are a clear exception to Wikibooks "Not a text repository" policy; these are subpages of a very large body of work (I understand the largest Wikibook in Wikibooks) and integral to its overall development; yes, the pages are a work in progress and the annotations are as yet limited, but I will now prioritise their development[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:28, 3 May 2026 (UTC) == [[History Books]] == Minimal existing content is editorialized, book scope unclear, no sourcing —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:47, 27 April 2026 (UTC) :{{comment}} - there is one unlinked subpage of this book, [[History Books/Who Was Alexander the Great/Introduction]]. I'm not impressed by the content (it's basically historical fiction written for a young child), but it's not hopeless. I'd encourage the author to create an account to allow us to communicate with them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:34, 28 April 2026 (UTC) ::If it is really aimed at children, shouldn't it be moved to the Wikijunior: namespace? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:55, 28 April 2026 (UTC) == [[Music Production Guide by Taskin Ahmed Kayum]] == no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:50, 27 April 2026 (UTC) :{{vd}} - this is not a useful guide. It fails to provide any actionable directions to the reader. :As some advice to the author: you may want to try writing a guide on a narrower topic which you are personally familiar with, like how to produce a particular type of music, or how to use a particular piece of software to produce music. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 03:44, 28 April 2026 (UTC) :{{vd}}, no useful content. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:17, 28 April 2026 (UTC) :{{done}} [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:10, 4 May 2026 (UTC) == [[FORTRAN program for calculating representative parameters and operating conditions of AC overhead transmission lines]] == As the title suggests, this page is primarily code for a computer program, not a book. Wikibooks is not a code hosting web site; this code might be more appropriate as a repository on a code hosting site such as Codeberg or GitHub. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:30, 28 April 2026 (UTC) :{{Del}}, the book seems to be out of scope in its current state, especially considering that most of it is just code and it has no subpages. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:35, 28 April 2026 (UTC) :I agree that this is not a book in its current form. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:26, 28 April 2026 (UTC) == Various Transwiki Namespace Pages == *[[Transwiki:Digging trees and shrubs for transplanting]] *[[Transwiki:Create bit mask algorithm]] *[[Transwiki:CRFL (CaReFuL mnemonic)]] *[[Transwiki:Developing a library websites]] *<s>[[Transwiki:Fischer's Lovebird]]</s> *[[Transwiki:Float (breakdancing move)]] *[[Transwiki:Front door method]] *[[Transwiki:Hair Color Tips and Tricks]] *[[Transwiki:Horse grooming]] *[[Transwiki:How to distinguish a monocot from a dicot]] *[[Transwiki:Humminbird PC connection cable wiring diagramm. (AS PC2)]] *[[Transwiki:Inbound connectivity under 3G Datacard]] *[[Transwiki:Common Test Cases]] *[[Transwiki:Comparison of EHR solution providers]] *[[Transwiki:Computer forensics]] *[[Transwiki:Barter]] *[[Transwiki:Career domains in computer science]] *[[Transwiki:Buying snowboards]] *[[Transwiki:Common chemicals]] *[[Transwiki:B+ Tree Java Implementation]] *[[Transwiki:Cattle judging]] *[[Transwiki:Two-handed manual alphabet]] *<s>[[Transwiki:Silver-copper nitrate]]</s> *[[Transwiki:Slating procedure]] *<s>[[Transwiki:Rhodesia's Unilateral Declaration of Independence]]</s> *[[Transwiki:Technical writing for the Web]] *[[Transwiki:Technology roadmap]] *[[Transwiki:Special product and factoring]] *[[Transwiki:Researching Japanese names]] *[[Transwiki:Job-seeking expense tax deductions]] *[[Transwiki:Labeling family photos]] *[[Transwiki:List of mnemonics for the cranial nerves]] *<s>[[Transwiki:Maude system]]</s> *[[Transwiki:Model rocket]] *[[Transwiki:NIS Configuration on Debian]] *<s>[[Transwiki:Paper model tutorials]]</s> *[[Transwiki:Photosynthesis misconceptions]] *[[Transwiki:Project Schedule Development]] This list includes pages in the Transwiki namespaces that have mostly been imported from enwiki, which makes them unusable in a book. If there are any pages here that can be turned into a book, let me know and I can strike them out. I believe that all of these pages should be deleted as we do not allow encyclopedic material on Wikibooks, and these are mostly articles that were imported from English Wikipedia. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 13:25, 1 May 2026 (UTC) :[[Transwiki:Cattle judging]], [[Transwiki:Horse grooming]], and [[Transwiki:Hair Color Tips and Tricks]] could be viable book content. None of the others obviously looked usable to me. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 16:39, 1 May 2026 (UTC) ::I excluded Transwikis that could be added to books here, but the pages you mentioned do not seem usable to me (unless a specific book where they could be added is created). Additionally, in [[Transwiki:Hair Color Tips and Tricks]], the tone is unfit for Wikibooks. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:39, 1 May 2026 (UTC) :I deleted a few of these that seemed unambiguously out of scope. I agree that most of them are not sufficiently book-like in scope on their own, and I think they warrant deletion unless anyone can identify specific books that can host them. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:01, 3 May 2026 (UTC) == [[A second course to linear algebra - Matrix algebra]] == Abandoned, with several unresolved quality issues as outlined at [[User talk:Akira tanzivana]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:04, 3 May 2026 (UTC) == [[Bengali–Assamese script]] == Abandoned for three years with minimal content that is seemingly redundant to [[Bengali]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:08, 3 May 2026 (UTC) g7naymq4kamuffgqmnpnnfe5gwvi49c 4634254 4634219 2026-05-05T11:06:17Z Samuel.dellit 1387936 /* History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23 */ 4634254 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == Algebra/Chapter 10/Symmetric Polynomials == I personally believe that [[Algebra/Chapter 10/Symmetric Polynomials|this]], and all of the sections should be deleted for the fact that this goes WAY beyond the scope of what was intended for the Chapter (Algebra II level polynomials). [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 15:07, 6 February 2025 (UTC) :'''Split''': Deletion here is not the best solution (see [[w:WP:ATD]]). Instead, this page and its subpages should be moved to another book, most likely [[Abstract Algebra]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:35, 6 February 2025 (UTC) :{{keep}} since there is a good amount of content. If [[Abstract Algebra]] is appropriate, it seems like a fine idea to move there. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:59, 7 February 2025 (UTC) ::Eh, yeah, I supposed moving it is better. I just don't think it's suitable for where it appears. [[User:GoreyCat|GoreyCat]] ([[User talk:GoreyCat|discuss]] • [[Special:Contributions/GoreyCat|contribs]]) 01:40, 8 February 2025 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) == [[Template:Qr-twwp]] == This isn't exactly a request to delete the template, but rather to merge it with {{tlx|Copypaste}}. The {{tlx|Qr-twwp}} template serves the same purpose as {{tlx|Copypaste}}, but without the seven-day period after which the page is deleted. This leads to confusion, as well as a perpetually full [[:Category:Queried pages]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:37, 30 March 2025 (UTC) == [[Ghouls of the Miskatonic]] == I don't think that a plot summary of a book is in-scope here. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:43, 20 August 2025 (UTC) :{{vd}} - at least, not a summary of ''this'' book. A summary and/or study guide to a notable work of literature might be in scope, but this is certainly not one. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:23, 25 August 2025 (UTC) ::Hi. I am the creator of the pages of this book. If I understand correctly, it has to be a summary of a notable work of literature? So what exactly is defined as such? I only started this as I thought it would be fun, interesting and encouraging to others who read the Arkham Horror novels, and I thought it was permitted as I've seen other summaries of books on wikibooks. [[User:Dayne90|Dayne90]] ([[User talk:Dayne90|discuss]] • [[Special:Contributions/Dayne90|contribs]]) 13:27, 26 August 2025 (UTC) :::Your problem is it is just the plot... it needs to include an educational textual analysis to be in scope [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:47, 28 August 2025 (UTC) ::::And ideally it'd be a text which has ''already'' been the subject of literary analysis, such that the analysis on Wikibooks isn't original research. A notable work of literature like ''Frankenstein'' or ''Moby-Dick'' would easily meet that requirement; a tie-in novel for a tabletop RPG probably does not. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:08, 29 August 2025 (UTC) == [[Annotations to The Joy of Music]] == Abandoned with minimal content. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:48, 24 August 2025 (UTC) :Author of the book/page here. I wouldn't call it "abandoned": it's still a start, but I'm here and do plan to fill out the rest (most of the annotations are for the early part of the book though). :I'm an experience editor at Wikipedia and Wiktionary, but am not very familiar with Wikibooks standards. When reading this book, I found myself looking up unfamiliar terms and quotes and thought some annotations would be helpful when reading or especially studying the text. It's a notable book by a notable author (extensive Wikipedia page). Here the source text is not freely available, but annotations are easy to add separately. I looked at [[WB:AT]] and existing examples of annotations and tried to follow them. Per [[WB:WIW]], the scope is instructional texts (including annotated texts), and minor works are in scope. :I'll grant that this is not large and not likely to become very long – many books only need minor annotations – but the content would certainly have been helpful to me when reading this book. :Are there specific changes you'd suggest or general guidelines to follow in this kind of book? ::—Nils von Barth ([[User:Nbarth|nbarth]]) ([[User talk:Nbarth|talk]]) 02:42, 3 September 2025 (UTC) ::: Pinging @[[User:Kittycataclysm|Kittycataclysm]] and @[[User:Nbarth|Nbarth]]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:15, 21 April 2026 (UTC) ::::I think I stand by my original reasoning given that no work has been done on it, and I don't think it contains enough content to hang around in main space for so long. What about moving it to user space? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:16, 23 April 2026 (UTC) == [[Template:Deleted page]] == Per [[Wikibooks:Reading room/Proposals#Retiring Template:Deleted page]], this is because the template is unnecessary given that creation protection (salting) is used instead. I am also proposing the deletion of the following categories used by this template: * [[:Category:Protected deleted categories]] * [[:Category:Protected deleted pages]] Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:36, 29 January 2026 (UTC) :This seems premature - [[:Category:Protected deleted pages]] is still in use for pages with generic names. Is there a plan to transition those pages to create protection; if so, can that be implemented before deleting the templates/categories? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:28, 30 January 2026 (UTC) ::JJPMaster proposed that the pages listed in that category should be moved to the [[MediaWiki:Titleblacklist|title blacklist]], and that {{tlx|naming policy notice}} shall be fully protected and used as an interface (title blacklist) message. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:18, 30 January 2026 (UTC) :::@[[User:Omphalographer|Omphalographer]]: Have you seen this reply? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 15:28, 11 February 2026 (UTC) ::::I have, but I'm not sure I follow. These templates, and the categories which they populate, are currently in use. Once that's no longer the case, I have no objection to deleting them - but they need to be delinked first. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:20, 12 February 2026 (UTC) :::::I deleted the categories mentioned above, moved all the generic titles to the title blacklist, and for those pages that used {{tlx|Deleted page}}, I deleted then applied creation protection. An uninvolved admin can delete {{tlx|Deleted page}} and then close this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:39, 30 March 2026 (UTC) == [[Cereal Grains Through History]] == Abandoned with no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:18, 30 March 2026 (UTC) :[[User:Kittycataclysm|Kittycataclysm]]: The author (Karosent) objects to the deletion per their talk page: {{quote|:Yes, please do not delete this wiki book. It is a work in progress. It is just taking some time to make progress on it. Thank you.}} :{{courtesy ping}} to @[[User:Karosent|Karosent]] as the author of the book for their input. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:42, 30 March 2026 (UTC) ::If the user does intend to work on it, I think the best course of action would be moving it to user space until more progress is made. Having abandoned works around the main space is a bit messy. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 28 April 2026 (UTC) ::: {{courtesy ping}} to [[User:Karosent|Karosent]] again. Do you agree with the pages being moved to your userspace? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:23, 3 May 2026 (UTC) == [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Wireless Weekly/Issues/1928 03 23]] == Transcribed from a magazine copy that cannot be traced via the URL provided. Generally archival of primary source works is undertaken on Wikisource (not Wikibooks), backed by a suitable page scan. This isn't at present. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 16:32, 27 April 2026 (UTC) :This doesn't need an RfD since it is obviously out of scope. You can instead put a CSD tag on the page. Additionally, it seems that the entire /Publications section contains only source works here, so it might require a mass deletion. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:32, 27 April 2026 (UTC) ::@[[User:Samuel.dellit|Samuel.dellit]] looping you in here so you're aware. I don't think any pages like this (i.e. source text) can be kept here, since we are explicitly and unambiguously not a text repository per [[WB:SOURCE]]. I am inclined to speedily delete for that reason, but I want to hear from the primary editor. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:40, 27 April 2026 (UTC) :::Thanks for looping me in. :::This is not simply a transcription of the magazine. :::It includes new formatting to make the content better reachable. :::It includes commentary to place the transcribed material in context. :::It permits related material to be placed in chronological order. :::The version here is not complete (as per banner included), hence the URL link not working (National Library of Australia's Trove has been updated). :::There is no point in placing this material on Wikisource as the Trove website is functionally similar and now provides for text correction (a fairly recent development). :::I have not be editing Wikibooks for the last six month's following a personal matter but now slowly returning to the task. :::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:08, 27 April 2026 (UTC) ::::I'm still not sure whether this makes it in-scope at Wikibooks and suitable for the book-like scope of this work, so I'm looping in other admins to weigh in on scope and consensus @[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:SHB2000|SHB2000]]. For material that is planned but not yet enacted after a significant period, I'm wondering if user space is more suitable than main space. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:48, 3 May 2026 (UTC) :::::This is just one page of a book, right? It's not like the entire wikibook is a transcription. I'm inclined to keep it unless there is something I am missing. "For material that is planned but not yet enacted after a significant period" - that's a draft and can generally stay in article space. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:09, 4 May 2026 (UTC) ::::::My thoughts are similar to Leaderboard's. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 05:47, 4 May 2026 (UTC) ::::::@[[User:Leaderboard|Leaderboard]] @[[User:SHB2000|SHB2000]] Thank you, and good to know. Unless I am misunderstanding, the plan is actually to host many source texts in this book's namespace (see other subpages in [[History of wireless telegraphy and broadcasting in Australia/Topical/Publications]]) and not limited to this one page. Additionally, do we have anything in policy regarding how long drafts can stay in mainspace? I couldn't find anything, and it strikes me as unconstructive to the project if pages with significant issues (e.g. scope, quality, etc) are left in the mainspace for months to years. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 4 May 2026 (UTC) :::::::@[[User:Kittycataclysm|Kittycataclysm]] Thank you for your considered responses, the following is provided as background summary. :::::::(1) I should mention that all of these pages were speedily deleted six months ago on the basis of breach of copyright, despite the fact that they are in the public domain (yes I was remiss in not making this clear in the relevant discussion pages, and yes I was aware of the need for copyright explanation, but was overly focussed on content creation). I was hit by about 20 simultaneous speedily delete notifications, responded to 2 or 3 thinking that would be sufficient, but later found they had all been deleted (I was not active on Wikibooks at the time). My intention is to provide clear public domain information for each page in the coming months, but I am only one person and need time to give effect. Copyright worldwide is quite complex. :::::::(2) I was hit by this RfD about 2 weeks ago, nominally a single subpage, but with the threat of dozens of subpages being similarly treated. This time the basis of the RfD was breach of the "Not a text repository" policy, of which I was not previously aware. I see in the policy that there is a clear exception for annotated texts and I will further develop content in support of that exception (you will see that is my general practice in any event). There are literally hundreds of articles in this Wikibook already heavily annotated, simply on the basis of good authorship e.g. :::::::https://en.wikibooks.org/wiki/History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Biographies/Clement_Edgar_Ames/Notes :::::::https://en.wikibooks.org/wiki/History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Stations/7BU_Burnie/Notes :::::::But, again, I am only one person and need time to give effect. [[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:59, 4 May 2026 (UTC) :::::::@[[User:Kittycataclysm|Kittycataclysm]] As far as I can see, isn't the goal to annotate most of those pages? And there is no set limit for a draft. The main reason we'd delete a draft is if the book ''itself'' has nothing of value, which is not the case here. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 04:49, 5 May 2026 (UTC) : As an admin who was involved in deleting this (and related subpages) and ''only'' undeleting it later per the author's request, I therefore '''recuse''' (will not do) on taking any administrative actions for this request. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:33, 27 April 2026 (UTC) :{{vd}} - including other similar pages - per nom. Transcriptions of previously published works, like these magazines, belong on Wikisource. I don't see any evidence of substantial commentary in any of the pages I've looked at. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:47, 28 April 2026 (UTC) :{{keep}} - including other similar pages - annotated texts WB:AT are a clear exception to Wikibooks "Not a text repository" policy; these are subpages of a very large body of work (I understand the largest Wikibook in Wikibooks) and integral to its overall development; yes, the pages are a work in progress and the annotations are as yet limited, but I will now prioritise their development[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 19:28, 3 May 2026 (UTC) == [[History Books]] == Minimal existing content is editorialized, book scope unclear, no sourcing —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:47, 27 April 2026 (UTC) :{{comment}} - there is one unlinked subpage of this book, [[History Books/Who Was Alexander the Great/Introduction]]. I'm not impressed by the content (it's basically historical fiction written for a young child), but it's not hopeless. I'd encourage the author to create an account to allow us to communicate with them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:34, 28 April 2026 (UTC) ::If it is really aimed at children, shouldn't it be moved to the Wikijunior: namespace? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:55, 28 April 2026 (UTC) == [[Music Production Guide by Taskin Ahmed Kayum]] == no meaningful content —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:50, 27 April 2026 (UTC) :{{vd}} - this is not a useful guide. It fails to provide any actionable directions to the reader. :As some advice to the author: you may want to try writing a guide on a narrower topic which you are personally familiar with, like how to produce a particular type of music, or how to use a particular piece of software to produce music. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 03:44, 28 April 2026 (UTC) :{{vd}}, no useful content. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:17, 28 April 2026 (UTC) :{{done}} [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 05:10, 4 May 2026 (UTC) == [[FORTRAN program for calculating representative parameters and operating conditions of AC overhead transmission lines]] == As the title suggests, this page is primarily code for a computer program, not a book. Wikibooks is not a code hosting web site; this code might be more appropriate as a repository on a code hosting site such as Codeberg or GitHub. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:30, 28 April 2026 (UTC) :{{Del}}, the book seems to be out of scope in its current state, especially considering that most of it is just code and it has no subpages. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:35, 28 April 2026 (UTC) :I agree that this is not a book in its current form. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:26, 28 April 2026 (UTC) == Various Transwiki Namespace Pages == *[[Transwiki:Digging trees and shrubs for transplanting]] *[[Transwiki:Create bit mask algorithm]] *[[Transwiki:CRFL (CaReFuL mnemonic)]] *[[Transwiki:Developing a library websites]] *<s>[[Transwiki:Fischer's Lovebird]]</s> *[[Transwiki:Float (breakdancing move)]] *[[Transwiki:Front door method]] *[[Transwiki:Hair Color Tips and Tricks]] *[[Transwiki:Horse grooming]] *[[Transwiki:How to distinguish a monocot from a dicot]] *[[Transwiki:Humminbird PC connection cable wiring diagramm. (AS PC2)]] *[[Transwiki:Inbound connectivity under 3G Datacard]] *[[Transwiki:Common Test Cases]] *[[Transwiki:Comparison of EHR solution providers]] *[[Transwiki:Computer forensics]] *[[Transwiki:Barter]] *[[Transwiki:Career domains in computer science]] *[[Transwiki:Buying snowboards]] *[[Transwiki:Common chemicals]] *[[Transwiki:B+ Tree Java Implementation]] *[[Transwiki:Cattle judging]] *[[Transwiki:Two-handed manual alphabet]] *<s>[[Transwiki:Silver-copper nitrate]]</s> *[[Transwiki:Slating procedure]] *<s>[[Transwiki:Rhodesia's Unilateral Declaration of Independence]]</s> *[[Transwiki:Technical writing for the Web]] *[[Transwiki:Technology roadmap]] *[[Transwiki:Special product and factoring]] *[[Transwiki:Researching Japanese names]] *[[Transwiki:Job-seeking expense tax deductions]] *[[Transwiki:Labeling family photos]] *[[Transwiki:List of mnemonics for the cranial nerves]] *<s>[[Transwiki:Maude system]]</s> *[[Transwiki:Model rocket]] *[[Transwiki:NIS Configuration on Debian]] *<s>[[Transwiki:Paper model tutorials]]</s> *[[Transwiki:Photosynthesis misconceptions]] *[[Transwiki:Project Schedule Development]] This list includes pages in the Transwiki namespaces that have mostly been imported from enwiki, which makes them unusable in a book. If there are any pages here that can be turned into a book, let me know and I can strike them out. I believe that all of these pages should be deleted as we do not allow encyclopedic material on Wikibooks, and these are mostly articles that were imported from English Wikipedia. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 13:25, 1 May 2026 (UTC) :[[Transwiki:Cattle judging]], [[Transwiki:Horse grooming]], and [[Transwiki:Hair Color Tips and Tricks]] could be viable book content. None of the others obviously looked usable to me. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 16:39, 1 May 2026 (UTC) ::I excluded Transwikis that could be added to books here, but the pages you mentioned do not seem usable to me (unless a specific book where they could be added is created). Additionally, in [[Transwiki:Hair Color Tips and Tricks]], the tone is unfit for Wikibooks. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:39, 1 May 2026 (UTC) :I deleted a few of these that seemed unambiguously out of scope. I agree that most of them are not sufficiently book-like in scope on their own, and I think they warrant deletion unless anyone can identify specific books that can host them. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:01, 3 May 2026 (UTC) == [[A second course to linear algebra - Matrix algebra]] == Abandoned, with several unresolved quality issues as outlined at [[User talk:Akira tanzivana]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:04, 3 May 2026 (UTC) == [[Bengali–Assamese script]] == Abandoned for three years with minimal content that is seemingly redundant to [[Bengali]]. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:08, 3 May 2026 (UTC) hs4caqul68g22l6qpl1jpdsj57kv4t1 102 3548 4634146 4610437 2026-05-04T18:23:56Z ~2026-27081-28 3581241 /* Ingredients */ 4634146 wikitext text/x-wiki __NOTOC__ {{recipesummary|category=Recipes for dessert|servings=8|time=60 minutes + cooling|difficulty=2|Image=[[File:Pumpkin Pie.jpg|300px]]}} {{recipe}} | [[Cookbook:Dessert|Dessert]] | [[Cookbook:Cuisine of the United States|American cuisine]] | [[Cookbook:Holiday Recipes|Holiday]] '''Pumpkin pie''' is a traditional American and Canadian holiday [[Cookbook:Dessert|dessert]]. It consists of a pumpkin-based custard baked in a single pie shell. The pie is traditionally served with [[Cookbook:Whipped Cream|whipped cream]]. ==Ingredients== *2 [[Cookbook:Cup|cups]] (480 [[Cookbook:Milliliter|ml]]) [[Cookbook:Milk|milk]], scalded *2 cups (450 g) cooked and puréed [[Cookbook:Pumpkin|pumpkin]] (or plain canned pumpkin) *1 [[Cookbook:Tablespoon|tbsp]] [[Cookbook:Flour|flour]] *&frac12; [[Cookbook:Teaspoon|tsp]] [[Cookbook:Salt|salt]] *1 tsp [[Cookbook:Ginger|ginger]] *1 tsp [[Cookbook:Cinnamon|cinnamon]] *¼ tsp [[Cookbook:Nutmeg|nutmeg]] (optional) *2 large [[Cookbook:Egg|eggs]], beaten *1 unbaked 9-inch [[Cookbook:Pie Crust|pie shell]] ==Procedure== #Preheat [[Cookbook:Oven|oven]] to 350°F (180°C). #Blend all ingredients except the pie shell together to make the filling. #Pour the filling into the unbaked pie shell. #[[Cookbook:Baking|Bake]] in the preheated oven for 45 minutes. #Let cool and serve. ==Notes, tips, and variations== *This recipe replaces much of the [[Cookbook:Sugar|sugar]] normally found in a [[Cookbook:Pumpkin|pumpkin]] [[Cookbook:Pie|pie]] recipe with [[Cookbook:Maple Syrup|maple syrup]]. Use only real 100% maple syrup, not maple-flavored pancake syrup, as their sugar content is different. You can also substitute ⅔ cup [[Cookbook:Brown Sugar|brown sugar]] mixed with ⅓ cup [[Cookbook:Milk|milk]] for the maple syrup. *Prepare the raw pumpkin by skinning and cutting into 1 [[Cookbook:Inch|inch]] cubes. Bake at 350°F (180°C) for 1 hour and then turn off the heat. Leave the pumpkin in the oven for another hour or two, which will reduce the moisture content. The pumpkin may also be steamed but may end up with too much moisture, resulting in a runny pie. A 10 inch (25 cm)-diameter pumpkin will make 4–6 pies. The pumpkin may also be baked whole and skinned afterwards. *Pumpkin pie has no top crust, which makes most forms of decoration impossible; however, for a more aesthetically-pleasing pie, put dollops of real [[Cookbook:Whipped Cream|whipped cream]] on each slice, or add a decorative rim to the side crust with artfully layered dough cut-outs in the shape of fall leaves, squash, or pumpkins. *Use a smaller 'sugar pumpkin' instead of the big 'Jack O Lantern' pumpkin. Sugar pumpkins have a firm and smooth texture while the larger 'Jack O Lantern' pumpkin has a more stringy or fibrous texture and more watery flesh. === Variations === * '''Chocolate-covered pumpkin pie:''' After the pie has cooled, melt 2 oz (55 g) of sweetened [[Cookbook:Chocolate|chocolate]] (milk or dark) and pour over the top of the pie. Be sure to completely cover the pumpkin. Refrigerate to set the chocolate. * '''Pumpkin Pastries:''' Roll pie crust pastry thin and cut into circles approx 4" in diameter. Put a spoonful of the cool pumpkin mixture towards one side of the center of the circle. Fold over the crust into a half-circle and firmly crimp the edges closed. Slice three small slits in the top for venting. Place on a greased cookie sheet. Bake only until crust is a light golden-brown, approx 10 minutes. ===Substitutions=== * 14 [[Cookbook:Ounce|oz]] (1 can) [[Cookbook:Sweetened Condensed Milk|sweetened condensed milk]] can replace the scalded milk and maple syrup. * 2 cups of plain canned pumpkin can replace the cooked and strained pumpkin. Do not use "pumpkin pie filling", which has added spices. For a discussion on the use of canned pumpkin and the recipes attached, please see [[Cookbook Talk:Pumpkin Pie|the talk page]]. [[Category:Recipes for pies and tarts]] [[Category:Recipes using pumpkin]] [[Category:Recipes using maple syrup]] [[Category:Thanksgiving recipes]] [[Category:Vegetarian recipes]] [[Category:Featured recipes]] [[Category:Recipes_with_metric_units]] [[Category:Kid-friendly recipes]] [[Category:Halloween recipes]] [[Category:Recipes using egg]] [[Category:Recipes for dessert]] [[Category:Recipes using ground cinnamon]] [[Category:Recipes using wheat flour]] [[Category:Recipes using ground ginger]] [[de:Kochbuch/ Kürbiskuchen]] [[Category:Recipes using sugar]] [[Category:Recipes using milk]] e8vxgc6jdltpbmkuiqh156nlizin21g 4634152 4634146 2026-05-04T18:41:46Z Kittycataclysm 3371989 Rollback 1 edit by [[Special:Contributions/~2026-27081-28|~2026-27081-28]]: Vandalism 4608525 wikitext text/x-wiki __NOTOC__ {{recipesummary|category=Recipes for dessert|servings=8|time=60 minutes + cooling|difficulty=2|Image=[[File:Pumpkin Pie.jpg|300px]]}} {{recipe}} | [[Cookbook:Dessert|Dessert]] | [[Cookbook:Cuisine of the United States|American cuisine]] | [[Cookbook:Holiday Recipes|Holiday]] '''Pumpkin pie''' is a traditional American and Canadian holiday [[Cookbook:Dessert|dessert]]. It consists of a pumpkin-based custard baked in a single pie shell. The pie is traditionally served with [[Cookbook:Whipped Cream|whipped cream]]. ==Ingredients== *2 [[Cookbook:Cup|cups]] (480 [[Cookbook:Milliliter|ml]]) [[Cookbook:Milk|milk]], scalded *2 cups (450 g) cooked and puréed [[Cookbook:Pumpkin|pumpkin]] (or plain canned pumpkin) *1 cup (240 ml) [[Cookbook:Maple Syrup|maple syrup]] *⅛ cup (30 g) [[Cookbook:Sugar|sugar]] *1 [[Cookbook:Tablespoon|tbsp]] [[Cookbook:Flour|flour]] *&frac12; [[Cookbook:Teaspoon|tsp]] [[Cookbook:Salt|salt]] *1 tsp [[Cookbook:Ginger|ginger]] *1 tsp [[Cookbook:Cinnamon|cinnamon]] *¼ tsp [[Cookbook:Nutmeg|nutmeg]] (optional) *2 large [[Cookbook:Egg|eggs]], beaten *1 unbaked 9-inch [[Cookbook:Pie Crust|pie shell]] ==Procedure== #Preheat [[Cookbook:Oven|oven]] to 350°F (180°C). #Blend all ingredients except the pie shell together to make the filling. #Pour the filling into the unbaked pie shell. #[[Cookbook:Baking|Bake]] in the preheated oven for 45 minutes. #Let cool and serve. ==Notes, tips, and variations== *This recipe replaces much of the [[Cookbook:Sugar|sugar]] normally found in a [[Cookbook:Pumpkin|pumpkin]] [[Cookbook:Pie|pie]] recipe with [[Cookbook:Maple Syrup|maple syrup]]. Use only real 100% maple syrup, not maple-flavored pancake syrup, as their sugar content is different. You can also substitute ⅔ cup [[Cookbook:Brown Sugar|brown sugar]] mixed with ⅓ cup [[Cookbook:Milk|milk]] for the maple syrup. *Prepare the raw pumpkin by skinning and cutting into 1 [[Cookbook:Inch|inch]] cubes. Bake at 350°F (180°C) for 1 hour and then turn off the heat. Leave the pumpkin in the oven for another hour or two, which will reduce the moisture content. The pumpkin may also be steamed but may end up with too much moisture, resulting in a runny pie. A 10 inch (25 cm)-diameter pumpkin will make 4–6 pies. The pumpkin may also be baked whole and skinned afterwards. *Pumpkin pie has no top crust, which makes most forms of decoration impossible; however, for a more aesthetically-pleasing pie, put dollops of real [[Cookbook:Whipped Cream|whipped cream]] on each slice, or add a decorative rim to the side crust with artfully layered dough cut-outs in the shape of fall leaves, squash, or pumpkins. *Use a smaller 'sugar pumpkin' instead of the big 'Jack O Lantern' pumpkin. Sugar pumpkins have a firm and smooth texture while the larger 'Jack O Lantern' pumpkin has a more stringy or fibrous texture and more watery flesh. === Variations === * '''Chocolate-covered pumpkin pie:''' After the pie has cooled, melt 2 oz (55 g) of sweetened [[Cookbook:Chocolate|chocolate]] (milk or dark) and pour over the top of the pie. Be sure to completely cover the pumpkin. Refrigerate to set the chocolate. * '''Pumpkin Pastries:''' Roll pie crust pastry thin and cut into circles approx 4" in diameter. Put a spoonful of the cool pumpkin mixture towards one side of the center of the circle. Fold over the crust into a half-circle and firmly crimp the edges closed. Slice three small slits in the top for venting. Place on a greased cookie sheet. Bake only until crust is a light golden-brown, approx 10 minutes. ===Substitutions=== * 14 [[Cookbook:Ounce|oz]] (1 can) [[Cookbook:Sweetened Condensed Milk|sweetened condensed milk]] can replace the scalded milk and maple syrup. * 2 cups of plain canned pumpkin can replace the cooked and strained pumpkin. Do not use "pumpkin pie filling", which has added spices. For a discussion on the use of canned pumpkin and the recipes attached, please see [[Cookbook Talk:Pumpkin Pie|the talk page]]. [[Category:Recipes for pies and tarts]] [[Category:Recipes using pumpkin]] [[Category:Recipes using maple syrup]] [[Category:Thanksgiving recipes]] [[Category:Vegetarian recipes]] [[Category:Featured recipes]] [[Category:Recipes_with_metric_units]] [[Category:Kid-friendly recipes]] [[Category:Halloween recipes]] [[Category:Recipes using egg]] [[Category:Recipes for dessert]] [[Category:Recipes using ground cinnamon]] [[Category:Recipes using wheat flour]] [[Category:Recipes using ground ginger]] [[de:Kochbuch/ Kürbiskuchen]] [[Category:Recipes using sugar]] [[Category:Recipes using milk]] rpx3l384bp7rtn0ff7ovftuosbliu4h 0 38308 4634070 2059620 2026-05-04T12:29:00Z Jcb 90773 4634070 wikitext text/x-wiki {{Radiation Oncology:TOC}} *Global cancer statistics: [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?CMD=search&DB=pubmed&term=15761078 2002] [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?CMD=search&DB=pubmed&term=10200776 1999] ==Resources for statistics== *'''Global Cancer Statistics''' - published in Ca Cancer J Clin **[http://www.ncbi.nlm.nih.gov/pubmed?term=ca%20cancer%20j%20clin%20global%20cancer%20statistics Search for publications] **GLOBOCAN data, produced by IARC (International Agency for Research on Cancer) **Latest: {{PMID|21296855}} published 2011 (2008 data) *'''Global Cancer Facts & Figures''' - American Cancer Society **[http://www.cancer.org/Research/CancerFactsFigures/GlobalCancerFactsFigures/index Website] **Latest: [http://www.cancer.org/Research/CancerFactsFigures/GlobalCancerFactsFigures/global-facts-figures-2nd-ed 2nd edition] (2008 data) ==Summary== *In 2002, there were estimated to be 10.9 million new cases of cancer, 6.7 million deaths, and 24.6 million persons living with cancer. ==Incidence== *1st - Lung - 1.35 million (in 2002) *2nd - Breast - 1.15 million (in 2002) *3rd - Colon and rectum - 1.02 million cases (in 2002) *4th - Stomach - 934,000 cases (in 2002) *5th - Liver - 626,000 (in 2002) *9th - Bladder - 357,000 (in 2002) ===Incidence - Women=== *1st - Breast - 1.15 million (in 2002) *2nd - Cervix ==Deaths== *1st - Lung - 1.18 million (in 2002) *2nd - Stomach - 700,000 (in 2002) *3rd - Liver - 598,000 (in 2002) *4th - Colon and rectum - 529,000 (in 2002) *5th - Breast - 411,000 (in 2002) *-?- - Bladder - 145,000 (in 2002) ===Deaths - Women=== *1st - Breast - 411,000 (in 2002) *2nd - Cervix kpq882c5kcrykgm6iln2gdwvs13l5wo 0 38309 4634067 3932480 2026-05-04T12:26:03Z Jcb 90773 4634067 wikitext text/x-wiki {{Radiation Oncology:TOC}} <big>'''Cancer Epidemiology and Survival'''</big> ==Cancer Epidemiology== *[[Radiation Oncology/Epidemiology/USA|USA]] *[[Radiation Oncology/Epidemiology/Worldwide|Worldwide]] *[[Radiation Oncology/China|China]] *[[/Taiwan Cancer Registry/|Taiwan]] *[[Radiation Oncology/Cancer epidemiology|Cancer epidemiology]] *[[Radiation Oncology/Epidemiology/By cancer site|By cancer site]] *[[Radiation Oncology/Epidemiology/Most commons|List of most commons]] *[[Radiation_Oncology/Epidemiology/Survival|Survival data]] *[[Radiation Oncology/Epidemiology/Cancer screening|Cancer screening]] *[[Radiation Oncology/Epidemiology/Cancer prevention|Cancer prevention]] ==Known/Probable Human Carcinogens== '''[https://monographs.iarc.fr/list-of-classifications/ IARC MONOGRAPHS ON THE IDENTIFICATION OF CARCINOGENIC HAZARDS TO HUMANS]''' * [[/Group 1: Carcinogenic to humans (120 agents)]] * [[/Group 2A: Probably carcinogenic to humans (88 agents)]] * [[/Group 2B: Possibly carcinogenic to humans (313 agents)]] * [[/Group 3: Not classifiable as to its carcinogenicity to humans (499 agents)]] ==Radiotherapy Epidemiology== *'''Sweden; 2003''' {{PMID|14596502}} -- "A prospective survey of radiotherapy practice 2001 in Sweden." (Moller TR, Acta Oncol. 2003;42(5-6):387-410.) ==Global Oncology== *[https://globalonc.org/ JCO Global Oncology - ASCO Journals] *[https://jamanetwork.com/journals/jama/fullarticle/2737536 Global Oncology | Global Health | JAMA | JAMA Network] * dz2tgmfrbb3ecjevit65xg62nvp65dy 0 38313 4634069 1711304 2026-05-04T12:28:00Z Jcb 90773 4634069 wikitext text/x-wiki {{Radiation Oncology:TOC}} *'''American Cancer Society''' **'''2009''' {{PMID|19474385}} -- "Cancer statistics, 2009." (Jemal A, CA Cancer J Clin. 2009 Jul-Aug;59(4):225-49. Epub 2009 May 27.) {| border="1" ! Cancer Site !! width="140" | Incidence !!width="140" | Deaths |- ! Lung | align="center" | 219 K || align="center" | 159 K |- ! Breast | align="center" | 194 K || align="center" | 41 K |- ! Prostate | align="center" | 192 K || align="center" | 27 K |- ! Colon | align="center" | 106 K || align="center" | 50 K <br>(combined with rectum) |- ! Bladder | align="center" | 71 K || align="center" | 14 K |- ! Melanoma | align="center" | 69 K || align="center" | 9 K |- ! NHL | align="center" | 66 K || align="center" | 19 K |- ! Kidney | align="center" | 58 K || align="center" | 13 K |- ! Endometrial | align="center" | 42 K || align="center" | 8 K |- ! Pancreas | align="center" | 42 K || align="center" | 35 K |- ! Rectum | align="center" | 41 K || align="center" | (grouped with colon) |} **'''2008''' {{PMID|18287387}} -- "Cancer statistics, 2008." (Jemal A, CA Cancer J Clin. 2008 Mar-Apr;58(2):71-96. Epub 2008 Feb 20.) **'''2007''' {{PMID|17237035}} -- "Cancer statistics, 2007." (Jemal A, CA Cancer J Clin. 2007 Jan-Feb;57(1):43-66.) **'''2006''' {{PMID|16514137}} -- "Cancer statistics, 2006" (Jemal A, CA Cancer J Clin. 2006 Mar-Apr;56(2):106-30.) **'''2005''' {{PMID|16514137}} -- "Cancer statistics, 2005" (Jemal A, CA Cancer J Clin. 2005 Jan-Feb;55(1):10-30.) ==Survival== *'''SEER data, 2007''' (1998-2003) {{PMID|17664474}} -- "Recent major progress in long-term cancer patient survival disclosed by modeled period analysis." (Brenner H, J Clin Oncol. 2007 Aug 1;25(22):3274-80.) **5- and 10-year relative survival evaluated, as a ratio of survival with disease over expected survival in population without disease {| border="1" |+ '''2003 U.S. Relative Survival Figures''' ! Cancer Site !! Incidence !! 5-year RS !! 10-year RS |- ! Prostate | 256 K || 99.8% || 98% |- ! Breast | 232 K || 91% || 86% |- ! Lung | 200 K || 16% || 11% |- ! Colon | 120 K || 66% || 62% |- ! Bladder | 62 K || 80% || 74% |- ! NHL | 61 K || 65% || 55% |- ! Melanoma | 53 K || 93% || 91% |- ! Rectum | 48 K || 67% || 60% |- ! Uterus | 44 K || 85% || 83% |- ! Leukemias | 37 K || 46% || 35% |- ! Oral cavity | 36 K || 61% || 50% |- ! Pancreas | 34 K || 7% || 5% |- ! Kidney | 33 K || 67% || 60% |- ! Stomach | 27 K || 26% || 12% |- ! Ovary | 26 K || 44% || 35% |- ! Thyroid | 24 K || 97% || 96% |- ! Brain | 21 K || 30% || 24% |- ! Multiple myeloma | 18 K || 32% || 15% |- ! Cervix | 17 K || 72% || 67% |- ! Liver | 15 K || 12% || 9% |- ! Esophagus | 14 K || 18% || 13% |- ! Larynx | 14 K || 62% || 49% |- ! Testis | 11 K || 97% || 96% |- ! Hodgkin's Disease | 11 K || 85% || 80% |} ==Pediatric== *[http://seer.cancer.gov/csr/1975_2006/results_single/sect_29_table.01_2pgs.pdf SEER Incidence Rates (2002-2006)] ==References== *[http://www.cancer.org/docroot/STT/stt_0.asp American Cancer Society: Cancer Facts & Figures 2006] *[http://www.cdc.gov/cancer/npcr/uscs/2002/facts_major_findings.htm U.S. Cancer Statistics 2002] fpkt7c3rakvysr17ibsbwsqy57hmic3 0 38719 4634234 4609258 2026-05-05T08:47:41Z ~2026-26995-93 3581107 Added 3...Qb6. 4634234 wikitext text/x-wiki {{Chess Opening Theory/Position |Modern variation |eco=[[Chess/ECOB|B12]] |parent=[[Chess Opening Theory/1. e4/1...c6|Caro-Kann]] → [[../|2...d5]] }} == 3. Nd2 · Modern variation == White prepares to recapture on e4 with their knight while keeping the option of c3. This move is intended to avoid the Gurgenidze system, [[../3. Nc3|3. Nc3]] [[../3. Nc3/3...g6|g6]], where Black will fianchetto their king's side bishop. Here, [[/3...g6|'''3...g6''']] may be answered 4. c3, mitigating the pressure Black's bishop will be able to impose on the long diagonal. This encourages the main move, [[/3...dxe4|'''3...dxe4''']], and after 4. Nxe4 this [[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Nc3/3...dxe4/4. Nxe4|transposes into the same line]] as if 3. Nc3 dxe4 4. Nxe4 had been played. A minor sideline is '''[[/3...Qb6/]]''', the Edinburgh Variation. Black develops their queen and attacks the undefended d4 pawn, though this can be answered with 4. c3. == Theory table == {{Chess Opening Theory/Table}} '''1.e4 c6 2.d4 d5 3.Nd2''' <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">3</th> <th align="left">4</th> <th align="left">5</th> <th align="left">6</th> </tr> <tr> <th align="right">Main Line</th> <td>...<br>[[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Nd2/3...dxe4|dxe4]] </td> <td>[[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Nc3/3...dxe4/4. Nxe4|Nxe4]]<br>Bf5</td> <td>Ng3<br>Bg6</td> <td>h4<br>h6</td> <td>=</td> </tr> </table> {{ChessMid}} ==References== {{reflist}} === See also === {{Wikipedia|Caro-Kann}} {{NCO}} {{MCO14}} {{BCO2}} {{Chess Opening Theory/Footer}} 0vppar6oq6rfvxd4vejoqdgjwnje2j1 0 42436 4634246 4628743 2026-05-05T10:10:45Z Nbrouard 60611 Use of multicolumn with only one column \multicolumn{1}{r|}{David Batty} (authorization of the new multicolumn.svg is pending 4634246 wikitext text/x-wiki <noinclude>{{LaTeX/Top}} </noinclude> Tables are a common feature in academic writing, often used to summarize research results. Mastering the art of table construction in LaTeX is therefore necessary to produce quality papers and with sufficient practice one can print beautiful tables of any kind. Keeping in mind that LaTeX is not a spreadsheet; it makes sense to use a dedicated tool to build tables and then to export these tables into the document. Basic tables are not too taxing, but anything more advanced can take a fair bit of construction; in these cases, more advanced packages can be very useful. However, first it is important to know the basics. Once you are comfortable with basic LaTeX tables, you might have a look at more advanced packages or the [[#Using spreadsheets and data analysis tools|export options of your favorite spreadsheet]]. Thanks to the modular nature of LaTeX, the whole process can be automated in a fairly comfortable way. == Introduction == LaTeX has built-in support to typeset tables and provides two environments: {{LaTeX/Environment|tabular}} and {{LaTeX/Environment|table}}. To typeset material in rows and columns, the {{LaTeX/Environment|tabular}} environment is needed; the optional {{LaTeX/Environment|table}} environment is a container for floating material similar to {{LaTeX/Environment|figure}}, into which a {{LaTeX/Environment|tabular}} environment may be included. The {{LaTeX/Environment|table}} environment contains the caption and defines the float for the table, i.e., where in the document the table should be positioned and whether we want it to be displayed centered. The {{LaTeX/Inline|code=\caption}} and {{LaTeX/Inline|code=\label}} commands can be used in the same way as for pictures. For more information about the {{LaTeX/Environment|table}} environment, see the [[#Floating with table|Floating with ''table'']] section. In any case, the actual content of the table is contained within the {{LaTeX/Environment|tabular}} environment. == The ''tabular'' environment == The {{LaTeX/Environment|tabular}} environment can be used to typeset tables with optional horizontal and vertical lines. LaTeX determines the width of the columns automatically. The first line of the environment has the form: {{LaTeX/Usage|code= \begin{tabular}[pos]{table spec} }} The {{LaTeX/Parameter|table spec}} argument tells LaTeX the alignment to be used in each column and the vertical lines to insert. The number of columns does not need to be specified as it is inferred by looking at the number of arguments provided. It is also possible to add vertical lines between the columns here. The following symbols are available to describe the table columns (some of them require that the package {{LaTeX/Package|array}} has been loaded): {| class="wikitable" | {{LaTeX/Parameter|l}} | left-justified column |- | {{LaTeX/Parameter|c}} | centered column |- | {{LaTeX/Parameter|r}} | right-justified column |- | {{LaTeX/Parameter|p{'width'}<!---->}} | paragraph column with text vertically aligned at the top |- | {{LaTeX/Parameter|m{'width'}<!---->}} | paragraph column with text vertically aligned in the middle (requires array package) |- | {{LaTeX/Parameter|b{'width'}<!---->}} | paragraph column with text vertically aligned at the bottom (requires array package) |- | <code><nowiki>|</nowiki></code> | vertical line |- | <code><nowiki>||</nowiki></code> | double vertical line |} By default, if the text in a column is too wide for the page, LaTeX won’t automatically wrap it. Using {{LaTeX/Parameter|p{'width'}<!---->}} you can define a special type of column which will wrap-around the text as in a normal paragraph. You can pass the width using any unit supported by LaTeX, such as 'pt' and 'cm', or ''command lengths'', such as {{LaTeX/LaTeX|code=\textwidth<!---->}}. You can find a list in chapter [[LaTeX/Lengths|Lengths]]. The optional parameter {{LaTeX/Parameter|pos}} can be used to specify the vertical position of the table relative to the baseline of the surrounding text. In most cases, you will not need this option. It becomes relevant only if your table is not in a paragraph of its own. You can use the following letters: {| class="wikitable" |- | {{LaTeX/Parameter|b}} | bottom |- | {{LaTeX/Parameter|c}} | center (default) |- | {{LaTeX/Parameter|t}} | top |- |} To specify a font format (such as bold, italic, etc.) for an entire column, you can add {{LaTeX/LaTeX|code=>{\format}<!---->}} before you declare the alignment. For example {{LaTeX/LaTeX|code=\begin{tabular}{ >{\bfseries}l c >{\itshape}r }<!---->}} will indicate a three column table with the first one aligned to the left and in bold font, the second one aligned in the center and with normal font, and the third aligned to the right and in italic. The "array" package needs to be activated in the preamble for this to work. In the first line you have pointed out how many columns you want, their alignment and the vertical lines to separate them. Once in the environment, you have to introduce the text you want, separating between cells and introducing new lines. The commands you have to use are the following: {| class="wikitable" | {{LaTeX/LaTeX|code=&<!---->}} | column separator |- | {{LaTeX/LaTeX|code=\\<!---->}} | start new row (additional space may be specified after {{LaTeX/LaTeX|code=\\<!---->}} using square brackets, such as {{LaTeX/Parameter|\\[6pt]}}) |- | {{LaTeX/LaTeX|code=\hline<!---->}} | horizontal line |- | {{LaTeX/LaTeX|code=\newline<!---->}} | start a new line within a cell (in a paragraph column) |- | {{LaTeX/LaTeX|code=\cline{i-j}<!---->}} | partial horizontal line beginning in column ''i'' and ending in column ''j'' |} Note, any white space inserted between these commands is purely down to one's preferences. I personally add spaces between to make it easier to read. === Basic examples === This example shows how to create a simple table in LaTeX. It is a three-by-three table, but without any lines. {{LaTeX/Example|code= \begin{tabular}{ l c r } 1 & 2 & 3 \\ 4 & 5 & 6 \\ 7 & 8 & 9 \\ \end{tabular} |render= <math>\begin{array}{lcr} 1 & 2 & 3 \\ 4 & 5 & 6 \\ 7 & 8 & 9 \\ \end{array}</math> }} Expanding upon that by including some vertical lines: {{LaTeX/Example|code= \begin{tabular}{ l {{!}} c {{!}} r } 1 & 2 & 3 \\ 4 & 5 & 6 \\ 7 & 8 & 9 \\ \end{tabular} |render= <math>\begin{array}{l|c||r} 1 & 2 & 3 \\ 4 & 5 & 6 \\ 7 & 8 & 9 \\ \end{array}</math> }} To add horizontal lines to the very top and bottom edges of the table: {{LaTeX/Example|code= \begin{tabular}{ l {{!}} c {{!}} r } \hline 1 & 2 & 3 \\ 4 & 5 & 6 \\ 7 & 8 & 9 \\ \hline \end{tabular} |render= <math>\begin{array}{l|c||r}\hline 1 & 2 & 3 \\ 4 & 5 & 6 \\ 7 & 8 & 9 \\ \hline \end{array}</math> }} And finally, to add lines between all rows, as well as centering (notice the use of the center environment - of course, the result of this is not obvious from the preview on this web page): {{LaTeX/Example|code= \begin{center} \begin{tabular}{ l {{!}} c {{!}} r } \hline 1 & 2 & 3 \\ \hline 4 & 5 & 6 \\ \hline 7 & 8 & 9 \\ \hline \end{tabular} \end{center} |render= <math>\begin{array}{l|c||r}\hline 1 & 2 & 3 \\ \hline 4 & 5 & 6 \\ \hline 7 & 8 & 9 \\ \hline \end{array}</math> }} {{LaTeX/Example|code= \begin{center} \begin{tabular}{ {{!}} l {{!}} c {{!}} r } \hline 1 & 2 & 3 \\ \hline 4 & 5 & 6 \\ \hline 7 & 8 & 9 \\ \hline \end{tabular} \end{center} |render= <math>\begin{array}{|l||c|||r}\hline 1 & 2 & 3 \\ \hline 4 & 5 & 6 \\ \hline \hline 7 & 8 & 9 \\ \hline \end{array}</math> }} {{LaTeX/Example|code= \begin{tabular}{{{!}}r{{!}}l{{!}}} \hline 7C0 & hexadecimal \\ 3700 & octal \\ \cline{2-2} 11111000000 & binary \\ \hline \hline 1984 & decimal \\ \hline \end{tabular} |render= {{Dark mode invert|[[Image:Latex example tabular cline.svg|250px]]}} }} === Text wrapping in tables === LaTeX's algorithms for formatting tables have a few shortcomings. One is that it will not automatically wrap text in cells, even if it overruns the width of the page. For columns that will contain text whose length exceeds the column's desired width, it is recommended that you use the {{LaTeX/Parameter|p}} attribute and specify the desired width of the column (although it may take some trial-and-error to get the result you want). For a more convenient method, have a look at [[#The tabularx package|The tabularx package]], or [[#The tabulary package|The tabulary package]]. Instead of {{LaTeX/Parameter|p}}, use the {{LaTeX/Parameter|m}} attribute to have the lines aligned toward the middle of the box or the {{LaTeX/Parameter|b}} attribute to align along the bottom of the box. Here is a simple example. The following code creates two tables with the same code; the only difference is that the last column of the second one has a defined width of 5 centimeters, while in the first one we didn't specify any width. Compiling this code: {{LaTeX/Usage|code= \documentclass{article} \usepackage[english]{babel} \begin{document} Without specifying width for last column: \begin{center} \begin{tabular}{{{!}} l {{!}} l {{!}} l {{!}} l {{!}}} \hline Day & Min Temp & Max Temp & Summary \\ \hline Monday & 11C & 22C & A clear day with lots of sunshine. However, the strong breeze will bring down the temperatures. \\ \hline Tuesday & 9C & 19C & Cloudy with rain, across many northern regions. Clear spells across most of Scotland and Northern Ireland, but rain reaching the far northwest. \\ \hline Wednesday & 10C & 21C & Rain will still linger for the morning. Conditions will improve by early afternoon and continue throughout the evening. \\ \hline \end{tabular} \end{center} With width specified: \begin{center} \begin{tabular}{ {{!}} l {{!}} l {{!}} l {{!}} p{5cm} {{!}}} \hline Day & Min Temp & Max Temp & Summary \\ \hline Monday & 11C & 22C & A clear day with lots of sunshine. However, the strong breeze will bring down the temperatures. \\ \hline Tuesday & 9C & 19C & Cloudy with rain, across many northern regions. Clear spells across most of Scotland and Northern Ireland, but rain reaching the far northwest. \\ \hline Wednesday & 10C & 21C & Rain will still linger for the morning. Conditions will improve by early afternoon and continue throughout the evening. \\ \hline \end{tabular} \end{center} \end{document} }} You get the following output: {{Dark mode invert|[[Image:Latex example wrapped table.svg|800px|center]]}} Note that the first table has been cropped, since the output is wider than the page width. === Manually broken paragraphs in table cells === Sometimes it is necessary to not rely on the breaking algorithm when using the {{LaTeX/Parameter|p}} specifier, but rather specify the line breaks by hand. In this case it is easiest to use a {{LaTeX/LaTeX|code=\parbox<!---->}}: {{LaTeX/Usage|code= \begin{tabular}{cc} boring cell content & \parbox[t]{5cm}{rather long par\\new par} \end{tabular} }} Here the {{LaTeX/Parameter|t}} argument controls the placement of the text inside the box. Other allowed values are {{LaTeX/Parameter|c}} for center and {{LaTeX/Parameter|b}} for bottom. === Space between columns === To tweak the space between columns (LaTeX will by default choose very tight columns), one can alter the column separation: {{LaTeX/LaTeX|code=\setlength{\tabcolsep}{5pt}<!---->}}. The default value is 6pt. One can also introduce a horizontal space with hspace like this: {{LaTeX/LaTeX|code=\begin{tabular}{r@{\hspace{1in}<!---->}<!---->rr}<!---->}} There are different options for the hspace [[LaTeX/Lengths|length]]. === Space between rows === Re-define the {{LaTeX/LaTeX|code=\arraystretch<!---->}} command to set the space between rows: {{LaTeX/Usage|code= \renewcommand{\arraystretch}{1.5} }} Default value is 1.0. An alternative way to adjust the rule spacing is to add {{LaTeX/LaTeX|code=\noalign{\smallskip}<!---->}} before or after the {{LaTeX/LaTeX|code=\hline<!---->}} and {{LaTeX/LaTeX|code=\cline{i-j}<!---->}} commands: {{LaTeX/Usage|code= \begin{tabular}{ {{!}} l {{!}} l {{!}} r {{!}} } \hline\noalign{\smallskip} \multicolumn{2}{c}{Item} \\ \cline{1-2}\noalign{\smallskip} Animal & Description & Price (\$) \\ \noalign{\smallskip}\hline\noalign{\smallskip} Gnat & per gram & 13.65 \\ & each & 0.01 \\ Gnu & stuffed & 92.50 \\ Emu & stuffed & 33.33 \\ Armadillo & frozen & 8.99 \\ \noalign{\smallskip}\hline \end{tabular} }} You may also specify the skip after a line explicitly using glue after the line terminator {{LaTeX/Usage|code= \begin{tabular}{ll} \hline Mineral & Color \\[1cm] Ruby & red \\ Sapphire & blue \\ \hline \end{tabular} }} === Other environments inside tables === If you use some LaTeX environments inside table cells, like {{LaTeX/Environment|verbatim}} or {{LaTeX/Environment|enumerate}}: {{LaTeX/Usage|code= \begin{tabular}{c c} \hline \begin{verbatim} code \end{verbatim} & description \\ \hline \end{tabular} }} you might encounter errors similar to <syntaxhighlight lang="output"> ! LaTeX Error: Something's wrong--perhaps a missing \item. </syntaxhighlight> To solve this problem, change [[#The tabular environment|column specifier]] to "paragraph" ({{LaTeX/Parameter|p}}, {{LaTeX/Parameter|m}} or {{LaTeX/Parameter|b}}). {{LaTeX/Usage|code= \begin{tabular}{m{5cm} c} }} === Defining multiple columns === It is possible to define many identically aligned columns at once using the {{LaTeX/LaTeX|code=*{num}{str}<!---->}} syntax. This is particularly useful when your table has many columns. Here is a table with six centered columns flanked by a single column on each side: {{LaTeX/Example|code= \begin{tabular}{l*{6}{c}r} Team & P & W & D & L & F & A & Pts \\ \hline Manchester United & 6 & 4 & 0 & 2 & 10 & 5 & 12 \\ Celtic & 6 & 3 & 0 & 3 & 8 & 9 & 9 \\ Benfica & 6 & 2 & 1 & 3 & 7 & 8 & 7 \\ FC Copenhagen & 6 & 2 & 1 & 3 & 5 & 8 & 7 \\ \end{tabular} |render= {{Dark mode invert|[[Image:Latex example defining multiple columns.svg|450px]]}} }} === Column specification using <code>>{\cmd}</code> and <code><{\cmd}</code> === The column specification can be altered using the {{LaTeX/Package|array}} package. This is done in the argument of the tabular environment using {{LaTeX/LaTeX|code=>{\command}}} for commands executed right ''before'' each column element and {{LaTeX/LaTeX|code=<{\command}}} for commands to be executed right ''after'' each column element. As an example: to get a column in math mode enter: <syntaxhighlight lang="tex" inline>\begin{tabular}{>{$}c<{$}}</syntaxhighlight>. Another example is changing the font: {{LaTeX/LaTeX|code=\begin{tabular}{>{\small}c}|}} to print the column in a small font. The argument of the {{LaTeX/LaTeX|code=>|}} and {{LaTeX/LaTeX|code=<|}} specifications must be correctly balanced when it comes to {{LaTeX/LaTeX|code={|}} and {{LaTeX/LaTeX|code=}|}} characters. This means that {{LaTeX/LaTeX|code=>{\bfseries}|}} is valid, while {{LaTeX/LaTeX|code=>{\textbf}|}} will not work and <code>{\textbf{}}</code> is not valid. If there is the need to use the text of the table as an argument (for instance, using the {{LaTeX/LaTeX|code=\textbf|}} to produce bold text), one should use the {{LaTeX/LaTeX|code=\bgroup|}} and {{LaTeX/LaTeX|code=\egroup|}} commands: {{LaTeX/LaTeX|code=>{\textbf\bgroup}c<{\egroup}|}} produces the intended effect. This works only for some basic LaTeX commands. For other commands, such as {{LaTeX/LaTeX|code=\underline|}} to underline text, it is necessary to temporarily store the column text in a box using {{LaTeX/LaTeX|code=lrbox|}}. First, you must define such a box with {{LaTeX/LaTeX|code=\newsavebox{\boxname}|}} and then you can define: {{LaTeX/Usage|code= >{\begin{lrbox}{\boxname} }% l% <{\end{lrbox}% \underline{\unhbox\boxname} }% } }} This stores the text in a box and afterwards, takes the text out of the box with {{LaTeX/LaTeX|code=\unhbox|}} (this destroys the box, if the box is needed again one should use {{LaTeX/LaTeX|code=\unhcopy|}} instead) and passing it to {{LaTeX/LaTeX|code=\underline|}}. (For LaTeX2e, you may want to use {{LaTeX/LaTeX|code=\usebox{\boxname}|}} instead of {{LaTeX/LaTeX|code=\unhbox\boxname|}}.) This same trick done with {{LaTeX/LaTeX|code=\raisebox|}} instead of {{LaTeX/LaTeX|code=\underline|}} can force all lines in a table to have equal height, instead of the natural varying height that can occur when e.g. math terms or superscripts occur in the text. Here is an example showing the use of both {{LaTeX/LaTeX|code=p{...}|}} and {{LaTeX/LaTeX|code=>{\centering}|}} : <syntaxhighlight lang="tex"> \begin{tabular}{>{\centering}p{3.5cm}>{\centering}p{3.5cm} } Geometry & Algebra \tabularnewline \hline Points & Addition \tabularnewline Spheres & Multiplication \end{tabular} </syntaxhighlight> Note the use of {{LaTeX/LaTeX|code=\tabularnewline|}} instead of {{LaTeX/LaTeX|code=\\|}} to avoid a <samp>Misplaced \noalign</samp> error. === @ and ! expressions === The column separator can be specified with the {{LaTeX/LaTeX|code=@{...}<!---->}} or {{LaTeX/LaTeX|code=!{...}<!---->}} constructs. It typically takes some text as its argument, and when appended to a column, it will automatically insert that text into each cell in that column before the actual data for that cell. The {{LaTeX/LaTeX|code=@{...}<!---->}} command kills the inter-column space and replaces it with whatever is between the curly braces. To keep the initial space, use {{LaTeX/LaTeX|code=!{...}<!---->}}. To add space, use {{LaTeX/LaTeX|code=@{\hspace{''width''}<!---->}<!---->}}. Admittedly, this is not that clear, and so will require a few examples to clarify. Sometimes, it is desirable in scientific tables to have the numbers aligned on the decimal point. This can be achieved by doing the following: {{LaTeX/Example|code= \begin{tabular}{r@{.}l} 3 & 14159 \\ 16 & 2 \\ 123 & 456 \\ \end{tabular} |render= <math>\begin{align}3&.14159\\16&.2\\123&.456\end{align}</math> }} The space-suppressing qualities of the @-expression actually make it quite useful for manipulating the horizontal spacing between columns. Given a basic table, and varying the column descriptions: {{LaTeX/Usage|code= \begin{tabular}{ {{!}}l{{!}}l{{!}} } \hline stuff & stuff \\ \hline stuff & stuff \\ \hline \end{tabular} }} {| | style="vertical-align: middle;" | <code><nowiki>{|l|l|}</nowiki></code> | style="vertical-align: middle;" | {{Dark mode invert|[[Image:specifier1.svg]]}} |- | style="vertical-align: middle;" | <code><nowiki>{|@{}l|l@{}|}</nowiki></code> | style="vertical-align: middle;" | {{Dark mode invert|[[Image:specifier2.svg]]}} |- | style="vertical-align: middle;" | <code><nowiki>{|@{}l@{}|l@{}|}</nowiki></code> | style="vertical-align: middle;" | {{Dark mode invert|[[Image:specifier3.svg]]}} |- | style="vertical-align: middle;" | <code><nowiki>{|@{}l@{}|@{}l@{}|}</nowiki></code> | style="vertical-align: middle;" | {{Dark mode invert|[[Image:specifier4.svg]]}} |} === Aligning columns at decimal points using dcolumn === Instead of using @-expressions to build columns of decimals aligned to the decimal point (or equivalent symbol), it is possible to center a column on the decimal separator using the {{LaTeX/Package|dcolumn}} package, which provides a new column specifier for floating point data. See the [http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/latex/required/tools/dcolumn.pdf dcolumn package documentation] for more information, but a simple way to use {{LaTeX/Package|dcolumn}} is as follows. {{LaTeX/Example|code= \usepackage{dcolumn} \ldots \newcolumntype{d}[1]{D{.}{\cdot}{#1} } %the argument for d specifies the maximum number of decimal places \begin{tabular}{l r c d{1} } Left&Right&Center&\mathrm{Decimal}\\ 1&2&3&4\\ 11&22&33&44\\ 1.1&2.2&3.3&4.4\\ \end{tabular} |render={{Dark mode invert|[[File:LaTeX_example_dcolumn.png|200px]]}} }} A negative argument provided for the number of decimal places in the new column type allows unlimited decimal places, but may result in rather wide columns. Rounding is not applied, so the data to be tabulated should be adjusted to the number of decimal places specified. Note that a decimal aligned column is typeset in math mode, hence the use of \mathrm for the column heading in the example above. Also, text in a decimal aligned column (for example the header) will be right-aligned before the decimal separator (assuming there's no decimal separator in the text). While this may be fine for very short text, or numeric column headings, it looks cumbersome in the example above. A solution to this is to use the {{LaTeX/LaTeX|code=\multicolumn}} command described below, specifying a single column and its alignment. For example to center the header ''Decimal'' over its column in the above example, the first line of the table itself would be {{LaTeX/LaTeX|code=Left&Right&Center&\multicolumn{1}{c}{Decimal}\\}} ====Bold text and dcolumn==== To draw attention to particular entries in a table, it may be nice to use bold text. Ordinarily this is easy, but as dcolumn needs to ''see'' the decimal point it is rather harder to do. In addition, the usual bold characters are wider than their normal counterparts, meaning that although the decimals may align nicely, the figures (for more than 2--3 digits on one side of the decimal point) will be visibly misaligned. It is however possible to use normal width bold characters and define a new bold column type, as shown below.<ref>{{cite web|url=http://tex.stackexchange.com/questions/118458/decimals-in-table-dont-align-with-dcolumn-when-bolded|title=Decimals in table don't align with dcolumn when bolded|author=D Carlisle|publisher=Stackexchange}}</ref> {{LaTeX/Example|code= \usepackage{dcolumn} %here we're setting up a version of the math fonts with normal x-width \DeclareMathVersion{nxbold} \SetSymbolFont{operators}{nxbold}{OT1}{cmr} {b}{n} \SetSymbolFont{letters} {nxbold}{OML}{cmm} {b}{it} \SetSymbolFont{symbols} {nxbold}{OMS}{cmsy}{b}{n} \begin{document} \makeatletter \newcolumntype{d}{D{.}{.}{-1} } %decimal column as before %wide bold decimal column \newcolumntype{B}[3]{>{\boldmath\DC@{#1}{#2}{#3} }c<{\DC@end} } %normal width bold decimal column \newcolumntype{Z}[3]{>{\mathversion{nxbold}\DC@{#1}{#2}{#3} }c<{\DC@end} } \makeatother \begin{tabular}{l l d} Type &M & \multicolumn{1}{c}{N} \\ Normal & 1 & 22222.222 \\ Bold (standard)&10 & \multicolumn{1}{B{.}{.}{-1} }{22222.222}\\ Bold (nxbold)&100 & \multicolumn{1}{Z{.}{.}{-1} }{22222.222}\\ \end{tabular} \end{document} |render={{Dark mode invert|[[file:LaTeX example dcolumn bold.png|200px]]}} }} == Row specification == It might be convenient to apply the same command over every cell of a row, just as for column. Unfortunately the {{LaTeX/Environment|tabular}} environment cannot do that by default. We will need {{LaTeX/Package|tabu}} instead, which provides the {{LaTeX/LaTeX|code=\rowfont<!---->}} option. {{LaTeX/Usage|code= \begin{tabu}{XX} \rowfont{\bfseries\itshape\large} Header1 & Header2 \\ \hline Cell2 & Cell2 \end{tabu} }} == Spanning == To complete this tutorial, we take a quick look at how to generate slightly more complex tables. Unsurprisingly, the commands necessary have to be embedded within the table data itself. === Rows spanning multiple columns === The command for this looks like this: {{LaTeX/LaTeX|code=\multicolumn{num_cols}{alignment}{contents}<!---->}}. {{LaTeX/Parameter|num_cols}} is the number of subsequent columns to merge; {{LaTeX/Parameter|alignment}} is either {{LaTeX/Parameter|l}}, {{LaTeX/Parameter|c}}, {{LaTeX/Parameter|r}}, or to have text wrapping specify a width {{LaTeX/LaTeX|code=p{5.0cm}<!---->}} . And {{LaTeX/Parameter|contents}} is simply the actual data you want to be contained within that cell. You can also use {{LaTeX/LaTeX|code=\multicolumn{1}{alignment}{contents}<!---->}} for a single column. In this simple example, the name David Batty is an exception, shifted to the right: {{LaTeX/Example|code= \begin{tabular}{ {{!}}l{{!}}l{{!}} } \hline \multicolumn{2}{{{!}}c{{!}}}{Team sheet} \\ \hline GK & Paul Robinson \\ LB & Lucas Radebe \\ DC & Michael Duberry \\ DC & Dominic Matteo \\ RB & Dider Domi \\ MC & \multicolumn{1}{r{{!}}}{David Batty} \\ MC & Eirik Bakke \\ MC & Jody Morris \\ FW & Jamie McMaster \\ ST & Alan Smith \\ ST & Mark Viduka \\ \hline \end{tabular} |render= {{Dark mode invert|[[Image:multicolumn.svg]]}} }} === Columns spanning multiple rows === The first thing you need to do is add {{LaTeX/LaTeX|code=\usepackage{multirow}}} to the preamble<ref name="multirow">Package multirow [http://www.ctan.org/tex-archive/macros/latex/contrib/multirow/ on CTAN]</ref>. This then provides the command needed for spanning rows: <code>\multirow{''num_rows''}{''width''}{''contents''}</code>. The arguments are pretty simple to deduce ({{LaTeX/LaTeX|code=*<!---->}} for the ''width'' means the content's natural width). {{LaTeX/Example|code= ... \usepackage{multirow} ... \begin{tabular}{ {{!}}l{{!}}l{{!}}l{{!}} } \hline \multicolumn{3}{ {{!}}c{{!}} }{Team sheet} \\ \hline Goalkeeper & GK & Paul Robinson \\ \hline \multirow{4}{*}{Defenders} & LB & Lucas Radebe \\ & DC & Michael Duburry \\ & DC & Dominic Matteo \\ & RB & Didier Domi \\ \hline \multirow{3}{*}{Midfielders} & MC & David Batty \\ & MC & Eirik Bakke \\ & MC & Jody Morris \\ \hline Forward & FW & Jamie McMaster \\ \hline \multirow{2}{*}{Strikers} & ST & Alan Smith \\ & ST & Mark Viduka \\ \hline \end{tabular} |render= {{Dark mode invert|[[Image:multirow.svg]]}} }} The main thing to note when using {{LaTeX/LaTeX|code=\multirow<!---->}} is that a blank entry must be inserted for each appropriate cell in each subsequent row to be spanned. If there is no data for a cell, just don't type anything, but you still need the "&" separating it from the next column's data. The astute reader will already have deduced that for a table of <math>n</math> columns, there must always be <math>n-1</math> ampersands in each row (unless {{LaTeX/LaTeX|code=\multicolumn<!---->}} is also used). === Spanning in both directions simultaneously === Here is a nontrivial example of how to use spanning in both directions simultaneously and have the borders of the cells drawn correctly: {{LaTeX/Example|code= \usepackage{multirow} \begin{tabular}{cc{{!}}c{{!}}c{{!}}c{{!}}c{{!}}l} \cline{3-6} & & \multicolumn{4}{ c{{!}} }{Primes} \\ \cline{3-6} & & 2 & 3 & 5 & 7 \\ \cline{1-6} \multicolumn{1}{ {{!}}c }{\multirow{2}{*}{Powers} } & \multicolumn{1}{ {{!}}c{{!}} }{504} & 3 & 2 & 0 & 1 & \\ \cline{2-6} \multicolumn{1}{ {{!}}c }{} & \multicolumn{1}{ {{!}}c{{!}} }{540} & 2 & 3 & 1 & 0 & \\ \cline{1-6} \multicolumn{1}{ {{!}}c }{\multirow{2}{*}{Powers} } & \multicolumn{1}{ {{!}}c{{!}} }{gcd} & 2 & 2 & 0 & 0 & min \\ \cline{2-6} \multicolumn{1}{ {{!}}c }{} & \multicolumn{1}{ {{!}}c{{!}} }{lcm} & 3 & 3 & 1 & 1 & max \\ \cline{1-6} \end{tabular} |render= {{Dark mode invert|[[Image:multirowandcolumnexample.svg|300px]]}} }} The command {{LaTeX/LaTeX|code=\multicolumn{1}{|c|}{...}<!---->}} is just used to draw vertical borders both on the left and on the right of the cell. Even when combined with {{LaTeX/LaTeX|code=\multirow{2}{*}{...}<!---->}}, it still draws vertical borders that only span the first row. To compensate for that, we add {{LaTeX/LaTeX|code=\multicolumn{1}{|c|}{...}<!---->}} in the following rows spanned by the multirow. Note that we cannot just use {{LaTeX/LaTeX|code=\hline<!---->}} to draw horizontal lines, since we do not want the line to be drawn over the text that spans several rows. Instead we use the command {{LaTeX/LaTeX|code=\cline{2-6}<!---->}} and opt out the first column that contains the text "Powers". Here is another example exploiting the same ideas to make the familiar and popular "2x2" or double dichotomy: {{LaTeX/Example|code= \begin{tabular}{ r{{!}}c{{!}}c{{!}} } \multicolumn{1}{r}{} & \multicolumn{1}{c}{noninteractive} & \multicolumn{1}{c}{interactive} \\ \cline{2-3} massively multiple & Library & University \\ \cline{2-3} one-to-one & Book & Tutor \\ \cline{2-3} \end{tabular} |render= {{Dark mode invert|[[Image:Latex-tables-double-dichotomy-example.svg|400px]]}} }} ==Controlling table size== === Resize tables === The {{LaTeX/Package|graphicx}} packages features the command {{LaTeX/LaTeX|code=\resizebox{width}{height}{object}<!---->}} which can be used with {{LaTeX/Environment|tabular}} to specify the height and width of a table. The following example shows how to resize a table to 8cm width while maintaining the original width/height ratio. {{LaTeX/Usage|code= \usepackage{graphicx} % ... \resizebox{8cm}{!} { \begin{tabular}... \end{tabular} } }} Resizing table including the caption {{LaTeX/Usage|code= \begin{table}[h] \resizebox{1.4\textwidth}{!}{\begin{minipage}{\textwidth} \begin{tabular}{r{{!}}c{{!}}c{{!}}} & \multicolumn{1}{c}{noninteractive} & \multicolumn{1}{c}{interactive} \\ \cline{2-3} massively multiple & Library & University \\ \cline{2-3} one-to-one & Book & Tutor \\ \cline{2-3} \end{tabular} \caption[Table caption text]{Table taken from \cite[p.10]{refid} } \label{table:name} \end{minipage} } \end{table} }} Alternatively you can use {{LaTeX/LaTeX|code=\scalebox{ratio}{object}<!---->}} in the same way but with ratios rather than fixed sizes: {{LaTeX/Usage|code= \usepackage{graphicx} % ... \scalebox{0.7}{ \begin{tabular}... \end{tabular} } }} === Changing font size === A table can be globally switched to a different font size by simply adding the desired size command (here: {{LaTeX/LaTeX|code=\footnotesize<!---->}}) in the table scope, which may be after the {{LaTeX/LaTeX|code=\begin{table}<!---->}} statement if you use floats, otherwise you need to add a group delimiter. {{LaTeX/Usage|code= {\footnotesize \begin{tabular}{{{!}} r {{!}} r {{!}}{{!}} c {{!}} c {{!}} c {{!}}} % ... \end{tabular} } }} {{LaTeX/Usage|code= \begin{table}[h]\footnotesize \caption{Performance at peak F-measure} \begin{tabular}{{{!}} r {{!}} r {{!}}{{!}} c {{!}} c {{!}} c {{!}}} % ... \end{tabular} \end{table} }} Alternatively, you can change the default font for all the tables in your document by placing the following code in the preamble: {{LaTeX/Usage|code= \let\oldtabular\tabular \renewcommand{\tabular}{\footnotesize\oldtabular} }} See [[LaTeX/Fonts#Sizing_text|Fonts]] for named font sizes. The table caption font size is not affected. To control the caption font size, see [[LaTeX/Floats,_Figures_and_Captions#Caption_Styles|Caption Styles]]. It is also possible to change the vertical space between rows using {{LaTeX/LaTeX|code=\renewcommand{\arraystretch}{0.8}<!---->}} before {{LaTeX/LaTeX|code=\begin{tabular}<!---->}}. == Colors == === Alternate row colors in tables === The {{LaTeX/Package|xcolor}} package provides the necessary commands to produce tables with alternate row colors, when loaded with the {{LaTeX/Parameter|table}} option. The command <code>\rowcolors{<''starting row''>}{<''odd color''>}{<''even color''>}</code> has to be specified right before the {{LaTeX/Environment|tabular}} environment starts. {{LaTeX/Example|code= \documentclass{article} \usepackage[table]{xcolor} \begin{document} \begin{center} \rowcolors{1}{green}{pink} \begin{tabular}{lll} odd & odd & odd \\ even & even & even\\ odd & odd & odd \\ even & even & even\\ \end{tabular} \end{center} \end{document} |render= [[File:LaTeXAlternateRowTable.svg|right]] }} The command {{LaTeX/LaTeX|code=\hiderowcolors<!---->}} is available to deactivate highlighting from a specified row until the end of the table. Highlighting can be reactivated within the table via the {{LaTeX/LaTeX|code=\showrowcolors<!---->}} command. If while using these commands you experience <samp>misplaced \noalign errors</samp> then use the commands at the very beginning or end of a row in your tabular. {{LaTeX/Usage|code=\hiderowcolors odd & odd & odd \\<!---->}} or {{LaTeX/Usage|code=odd & odd & odd \\ \showrowcolors<!---->}} === Colors of individual cells === As above this uses the {{LaTeX/Package|xcolor<!---->}} package. {{LaTeX/Usage|code= % Include this somewhere in your document \usepackage[table]{xcolor} % Enter this in the cell you wish to color a light grey. % NB: the word 'gray' here denotes the grayscale color scheme, not the color grey. '0.9' denotes how dark the grey is. \cellcolor[gray]{0.9} % The following will color the cell red. \cellcolor{red} }} == Width and stretching == We keep providing documentation for {{LaTeX/Environment|tabular*}} and {{LaTeX/Environment|tabularx}}. === The ''tabular*'' environment=== This is basically a slight extension on the original tabular version, although it requires an extra argument (before the column descriptions) to specify the preferred width of the table. {{LaTeX/Example|code= \begin{tabular*}{0.75\textwidth}{ {{!}} c {{!}} c {{!}} c {{!}} r {{!}} } \hline label 1 & label 2 & label 3 & label 4 \\ \hline item 1 & item 2 & item 3 & item 4 \\ \hline \end{tabular*} |render= {{Dark mode invert|[[Image:LaTeX TabWidth1.svg|right]]}} }} However, that may not look quite as intended. The columns are still at their natural width (just wide enough to fit their contents) while the rows are as wide as the table width specified. If you do not like this default, you must also explicitly insert extra column space. LaTeX has ''rubber lengths'', which, unlike others, are not fixed. LaTeX can dynamically decide how long the lengths should be. So, an example of this is the following. {{LaTeX/Example|code= \begin{tabular*}{0.75\textwidth}{@{\extracolsep{\fill} } {{!}} c {{!}} c {{!}} c {{!}} r {{!}} } \hline label 1 & label 2 & label 3 & label 4 \\ \hline item 1 & item 2 & item 3 & item 4 \\ \hline \end{tabular*} |render= {{Dark mode invert|[[Image:LaTeX TabWidth2.svg|right]]}} }} You will notice the {{LaTeX/LaTeX|code=@{...}<!---->}} construct added at the beginning of the column description. Within it is the {{LaTeX/LaTeX|code=\extracolsep<!---->}} command, which requires a width. A fixed width could have been used. However, by using a rubber length, such as {{LaTeX/LaTeX|code=\fill<!---->}}, the columns are automatically spaced evenly. === The ''tabularx'' package === This package provides a table environment called {{LaTeX/Environment|tabularx}}, which is similar to the {{LaTeX/Environment|tabular*}} environment except that it has a new column specifier {{LaTeX/Parameter|X}} (in uppercase). The column(s) specified with this specifier will be stretched to make the table as wide as specified, greatly simplifying the creation of tables. {{LaTeX/Example|code= \usepackage{tabularx} % ... \begin{tabularx}{\textwidth}{ {{!}}X{{!}}X{{!}}X{{!}}X{{!}} } \hline label 1 & label 2 & label 3 & label 4 \\ \hline item 1 & item 2 & item 3 & item 4 \\ \hline \end{tabularx} |render= {{Dark mode invert|[[Image:LaTeX TabXWidth1.svg|450px|right]]}} }} The content provided for the boxes is treated as for a {{LaTeX/Parameter|p}} column, except that the width is calculated automatically. If you use the package {{LaTeX/Package|array}}, you may also apply any {{LaTeX/LaTeX|code=>{\cmd}|}} or {{LaTeX/LaTeX|code=<{\cmd}|}} command to achieve specific behavior (like {{LaTeX/LaTeX|code=\centering<!---->}}, or {{LaTeX/LaTeX|code=\raggedright\arraybackslash<!---->}}) as described previously. Another option is to use {{LaTeX/LaTeX|code=\newcolumntype<!---->}} to format selected columns in a different way. It defines a new column specifier, e.g. {{LaTeX/Parameter|R}} (in uppercase). In this example, the second and fourth column is adjusted in a different way ({{LaTeX/LaTeX|code=\raggedleft<!---->}}): {{LaTeX/Example|code= \usepackage{tabularx} % ... \newcolumntype{R}{>{\raggedleft\arraybackslash}X}% \begin{tabularx}{\textwidth}{ {{!}}l{{!}}R{{!}}l{{!}}R{{!}} } \hline label 1 & label 2 & label 3 & label 4 \\ \hline item 1 & item 2 & item 3 & item 4 \\ \hline \end{tabularx} |render= {{Dark mode invert|[[Image:LaTeX TabXWidth2.svg|450px|right]]}} }} Tabularx with rows spanning multiple columns using {{LaTeX/LaTeX|code=\multicolumn<!---->}}. The two central columns are posing as one by using the {{LaTeX/Parameter|X@{}}} option. Note that the {{LaTeX/LaTeX|code=\multicolumn<!---->}} width (which in this example is 2) should equal the (in this example 1+1) width of the spanned columns: {{LaTeX/Example|code= \usepackage{tabularx} % ... \begin{tabularx}{1\textwidth}{ {{!}}>{\setlength\hsize{1\hsize}\centering}X{{!}}>{\setlength\hsize{1\hsize}\raggedleft}X@{} >{\setlength\hsize{1\hsize}\raggedright}X{{!}}>{\setlength\hsize{1\hsize}\centering}X{{!}} } \hline Label 1 & \multicolumn{2}{>{\centering\setlength\hsize{2\hsize} }X{{!}}}{Label 2} & Label 3\tabularnewline \hline 123 & 123 & 456 & 123 \tabularnewline \hline 123 & 123 & 456 & 123 \tabularnewline \hline \end{tabularx} |render= {{Dark mode invert|[[Image:LaTeX tabularx_multi.svg|450px|right]]}} }} In a way analogous to how new commands with arguments can be created with {{code|\newcommand}}, new column types with arguments can be created with {{code|\newcolumntype}} as follows: {{LaTeX/Usage|code= \usepackage{tabularx} \usepackage[table]{xcolor} %Used to color the last column % ... \newcolumntype{L}[1]{>{\hsize=#1\hsize\raggedright\arraybackslash}X}% \newcolumntype{R}[1]{>{\hsize=#1\hsize\raggedleft\arraybackslash}X}% \newcolumntype{C}[2]{>{\hsize=#1\hsize\columncolor{#2}\centering\arraybackslash}X}% \begin{tabularx}{\textwidth}{ {{!}} L{1} {{!}} R{0.5} {{!}} R{0.5} {{!}} C{2}{gray} {{!}} } \hline label 1 & label 2 & label 3 & label 4 \\ \hline item 1 & item 2 & item 3 & item 4 \\ \hline \end{tabularx} }} where since there are 4 columns, the sum of the {{code|\hsize}}'s (1 + 0.5 + 0.5 + 2) must be equal to 4. The default value used by tabularx for {{code|\hsize}} is 1. === The ''tabulary'' package === [http://www.ctan.org/pkg/tabulary <code>tabulary</code>] is a modified {{LaTeX/Package|tabular*}} allowing width of columns set for equal heights. {{LaTeX/Package|tabulary}} allows easy and convenient writing of well balanced tables. The problem with {{LaTeX/Package|tabularx}} is that it leaves much blank if your cells are almost empty. Besides, it is not easy to have different column sizes. {{LaTeX/Package|tabulary}} tries to balance the column widths so that each column has at least its natural width, without exceeding the maximum length. {{LaTeX/Usage|code= \usepackage{tabulary} ... \begin{center} \begin{tabulary}{0.7\textwidth}{LCL} Short sentences & \# & Long sentences \\ \hline This is short. & 173 & This is much loooooooonger, because there are many more words. \\ This is not shorter. & 317 & This is still loooooooonger, because there are many more words. \\ \end{tabulary} \end{center} }} The first parameter is the maximum width. {{LaTeX/Package|tabulary}} will try not to exceed it, but it will not stretch to it if there is not enough content, contrary to {{LaTeX/Package|tabularx}}. The second parameter is the column disposition. Possible values are those from the {{LaTeX/Environment|tabular}} environment, plus {| class="wikitable" | {{LaTeX/Parameter|L}} | left-justified balanced column |- | {{LaTeX/Parameter|C}} | centered balanced column |- | {{LaTeX/Parameter|R}} | right-justified balanced column |- | {{LaTeX/Parameter|J}} | left-right-justified balanced column |} These are all capitals. === The ''tabu'' environment === It works pretty much like {{LaTeX/Environment|tabularx}}. Note: ''tabu'' is currently [https://github.com/tabu-issues-for-future-maintainer/tabu/blob/master/README.md broken and unmaintained] {{LaTeX/Usage|code= \begin{tabu} to \linewidth {llX[2]lllXl} % ... \end{tabu} }} {{LaTeX/LaTeX|code=to \linewidth<!---->}} specifies the target width. The {{LaTeX/Parameter|X}} parameter can have an optional span factor. == Table across several pages == Long tables are natively supported by LaTeX thanks to the {{LaTeX/Environment|longtable}} environment, which replaces both the {{LaTeX/Environment|tabular}} and {{LaTeX/Environment|table}} environments or rather combines them into a single environment. Unfortunately, this environment does not support stretching (X columns). The {{LaTeX/Package|tabu}} package (which is [https://github.com/tabu-issues-for-future-maintainer/tabu/blob/main/README.md no longer maintained]) provides the {{LaTeX/Environment|longtabu}} environment. It has most of the features of {{LaTeX/Environment|tabu}}, with the additional capability to span multiple pages. LaTeX can do well with long tables: you can specify a header that will repeat on every page, a header for the first page only, and the same for the footer. {{LaTeX/Usage|code= \begin{longtabu} to \linewidth {lX[2]lXl} \rowfont\bfseries H1 & H2 & H3 & H4 & H5 \\ \hline \endhead \\ \hline \multicolumn{5}{r}{There is more to come} \\ \endfoot \\ \hline \endlastfoot % Content ... }} It uses syntax similar to {{LaTeX/Environment|longtable}}, so you should have a look at its documentation if you want to know more. Alternatively you can try one of the following packages [http://www.ctan.org/pkg/supertabular <code>supertabular</code>] or [http://www.ctan.org/pkg/xtab <code>xtab</code>], an extended and somewhat improved version of {{LaTeX/Package|supertabular}}. == Partial vertical lines == Adding a partial vertical line to an individual cell: {{LaTeX/Example|code= \begin{tabular}{ l c r } \hline 1 & 2 & 3 \\ \hline 4 & 5 & \multicolumn{1}{r{{!}}}{6} \\ \hline 7 & 8 & 9 \\ \hline \end{tabular} |render= {{Dark mode invert|[[Image:Partial-vertical-line-add.svg]]}} }} Removing part of a vertical line in a particular cell: {{LaTeX/Example|code= \begin{tabular}{ {{!}} l {{!}} c {{!}} r {{!}} } \hline 1 & 2 & 3 \\ \hline 4 & 5 & \multicolumn{1}{r}{6} \\ \hline 7 & 8 & 9 \\ \hline \end{tabular} |render= {{Dark mode invert|[[Image:Partial-vertical-line-remove.svg]]}} }} == Vertically centered images == Inserting images into a table row will align it at the top of the cell. By using the {{LaTeX/Package|array}} package this problem can be solved. Defining a new columntype will keep the image vertically centered. {{LaTeX/Usage|code= \newcolumntype{V}{>{\centering\arraybackslash} m{.4\linewidth} } }} Or use a parbox to center the image. {{LaTeX/Usage|code= \parbox[c]{1em}{\includegraphics{image.png} } }} A raisebox works as well, also allowing to manually fine-tune the alignment with its first parameter. {{LaTeX/Usage|code= \raisebox{-.5\height}{\includegraphics{image.png} } }} == Footnotes in tables == The {{LaTeX/Environment|tabular}} environment does not handle footnotes properly. The {{LaTeX/Environment|longtable}} fixes that. == Professional tables == Many professionally typeset books and journals feature simple tables, which have appropriate spacing above and below lines, and almost ''never'' use vertical rules. Many examples of LaTeX tables (including this Wikibook) showcase the use of vertical rules (using "|"), and double-rules (using {{LaTeX/LaTeX|code=\hline\hline<!---->}} or "||"), which are regarded as unnecessary and distracting in a professionally published form. The [http://www.ctan.org/tex-archive/macros/latex/contrib/booktabs/ booktabs] package is useful for easily providing this professionalism in LaTeX tables, and the [http://mirrors.ctan.org/macros/latex/contrib/booktabs/booktabs.pdf documentation] also provides guidelines on what constitutes a "good" table. In brief, the package uses {{LaTeX/LaTeX|code=\toprule<!---->}} for the uppermost rule (or line), {{LaTeX/LaTeX|code=\midrule<!---->}} for the rules appearing in the middle of the table (such as under the header), and {{LaTeX/LaTeX|code=\bottomrule<!---->}} for the lowermost rule. This ensures that the rule weight and spacing are acceptable. In addition, {{LaTeX/LaTeX|code=\cmidrule<!---->}} can be used for mid-rules that span specified columns. The following example contrasts the use of booktabs and two equivalent normal LaTeX implementations (the second example requires {{LaTeX/LaTeX|code=\usepackage{array}<!---->}} or {{LaTeX/LaTeX|code=\usepackage{dcolumn}<!---->}}, and the third example requires {{LaTeX/LaTeX|code=\usepackage{booktabs}<!---->}} in the preamble). === Normal LaTeX === {{LaTeX/Example|code= \begin{tabular}{llr} \hline \multicolumn{2}{c}{Item} \\ \cline{1-2} Animal & Description & Price (\$) \\ \hline Gnat & per gram & 13.65 \\ & each & 0.01 \\ Gnu & stuffed & 92.50 \\ Emu & stuffed & 33.33 \\ Armadillo & frozen & 8.99 \\ \hline \end{tabular} |render={{Dark mode invert|[[Image:LaTeX animal table.svg]]}}}} === Using {{LaTeX/Package|array}} === {{LaTeX/Example|code= \usepackage{array} %or \usepackage{dcolumn} ... \begin{tabular}{llr} \firsthline \multicolumn{2}{c}{Item} \\ \cline{1-2} Animal & Description & Price (\$) \\ \hline Gnat & per gram & 13.65 \\ & each & 0.01 \\ Gnu & stuffed & 92.50 \\ Emu & stuffed & 33.33 \\ Armadillo & frozen & 8.99 \\ \lasthline \end{tabular} |render={{Dark mode invert|[[Image:LaTeX animal table with array.svg]]}}}} === Using {{LaTeX/Package|booktabs}} === {{LaTeX/Example|code= \usepackage{booktabs} \begin{tabular}{llr} \toprule \multicolumn{2}{c}{Item} \\ \cmidrule(r){1-2} Animal & Description & Price (\$) \\ \midrule Gnat & per gram & 13.65 \\ & each & 0.01 \\ Gnu & stuffed & 92.50 \\ Emu & stuffed & 33.33 \\ Armadillo & frozen & 8.99 \\ \bottomrule \end{tabular} |render={{Dark mode invert|[[Image:LaTeX animal table with booktabs.svg]]}}}} Usually the need arises for footnotes under a table (and not at the bottom of the page), with a caption properly spaced above the table. These are addressed by the [http://www.ctan.org/tex-archive/macros/latex/contrib/ctable/ ctable] package. It provides the option of a short caption given to be inserted in the list of tables, instead of the actual caption (which may be quite long and inappropriate for the list of tables). The {{LaTeX/Package|ctable}} uses the {{LaTeX/Package|booktabs}} package. == Sideways tables == Tables can also be put on their side within a document using the {{LaTeX/Package|rotating}} or the {{LaTeX/Package|rotfloat}} package. See the [[LaTeX/Rotations|Rotations]] chapter. == Table with legend == To add a legend to a table the [http://www.ctan.org/tex-archive/macros/latex/contrib/caption/ caption] package can be used. With the caption package a {{LaTeX/LaTeX|code=\caption*{...}<!---->}} statement can be added besides the normal {{LaTeX/LaTeX|code=\caption{...}<!---->}}. Example: {{LaTeX/Usage|code= \begin{table} \begin{tabular}{{{!}} r {{!}} r {{!}}{{!}} c {{!}} c {{!}} c {{!}}} ... \end{tabular} \caption{A normal caption} \caption*{ A legend, even a table can be used \begin{tabular}{l l} item 1 & explanation 1 \\ \end{tabular} } \end{table} }} The normal caption is needed for labels and references. == The ''eqparbox'' package == On rare occasions, it might be necessary to stretch every row in a table to the natural width of its longest line, for instance when one has the same text in two languages and wishes to present these next to each other with lines synching up. A tabular environment helps control where lines should break, but cannot justify the text, which leads to ragged right edges. The {{LaTeX/Package|eqparbox}} package provides the command {{LaTeX/LaTeX|code=\eqmakebox<!---->}} which is like {{LaTeX/LaTeX|code=\makebox<!---->}} but instead of a {{LaTeX/Parameter|width}} argument, it takes a tag. During compilation it bookkeeps which {{LaTeX/LaTeX|code=\eqmakebox<!---->}} with a certain tag contains the widest text and can stretch all {{LaTeX/LaTeX|code=\eqmakebox<!---->}}es with the same tag to that width. Combined with the {{LaTeX/Package|array}} package, one can define a column specifier that justifies the text in all lines:comand {{LaTeX/Usage|code= \newsavebox{\tstretchbox} \newcolumntype{S}[1]{% >{\begin{lrbox}{\tstretchbox} }% l% <{\end{lrbox}% \eqmakebox[#1][s]{\unhcopy\tstretchbox} }% } }} See the documentation of the {{LaTeX/Package|eqparbox}} package for more details. == The ''paracol'' package == The various tabular environments available for LaTeX are feature rich; however, they lack the ability to '''automatically page break large rows'''. The paracol package provides automatic page breaks in between rows and in certain cases can replace the tabular environment. Such situations could be common in documents that require translations and definitions, which may also includes lists. For further detail see the documentation of the {{LaTeX/Package|paracol}} package. == Floating with ''table'' == In WYSIWYG document processors, it is common to put tables in the middle of the text. This is what we have been doing until now. Professional documents, however, often make it a point to print tables on a dedicated page so that they do not disrupt the flow. From the point of view of the source code, one has no idea on which page the current text is going to lie, so it is hardly possible to guess which page may be appropriate for our table. LaTeX can automate this task by abstracting objects such as tables, pictures, etc., and deciding for us where they might fit best. This abstraction is called a ''float''. Generally, an object that is floated will appear in the vicinity of its introduction in the source file, but one can choose to control its position also. To tell LaTeX we want to use our table as a float, we need to put a {{LaTeX/Environment|table}} environment around the {{LaTeX/Environment|tabular}} environment, which is able to float and add a label and caption. {{Warning| Please understand: you do not ''have to'' use floating tables. If you want to place your tables where they lie in your source code and you do not need any label, do not use {{LaTeX/Environment|table}} at all! This is a very common misunderstanding among newcomers. }} The {{LaTeX/Environment|table}} environment initiates a type of float just as the environment {{LaTeX/Environment|figure}}. In fact, the two bear a lot of similarities (positioning, captions, etc.). More information about floating environments, captions etc. can be found in [[LaTeX/Floats,_Figures_and_Captions|Floats, Figures and Captions]]. The environment names may now seem quite confusing. Let's sum it up: * {{LaTeX/Environment|tabular}} is for the content itself (columns, lines, etc.). * {{LaTeX/Environment|table}} is for the location of the table on the document, plus caption and label support. {{LaTeX/Usage|code= \begin{table}[position specifier] \centering \begin{tabular}{{{!}}l{{!}}} ... your table ... \end{tabular} \caption{This table shows some data} \label{tab:myfirsttable} \end{table} }} In the table, we used a label, so now we can refer to it just like any other reference: {{LaTeX/Usage|code= \ref{tab:myfirsttable} }} The {{LaTeX/Environment|table}} environment is also useful when you want to have a list of tables at the beginning or end of your document with the command {{LaTeX/Usage|code= \listoftables }} The captions now show up in the list of tables, if displayed. You can set the optional parameter {{LaTeX/Parameter|position specifier}} to define the position of the table, where it should be placed. The following characters are all possible placements. Using sequences of it define your "wishlist" to LaTeX. {| class="wikitable" |- | {{LaTeX/Parameter|h}} | where the table is declared ('''h'''ere) |- | {{LaTeX/Parameter|t}} | at the '''t'''op of the page |- | {{LaTeX/Parameter|b}} | at the '''b'''ottom of the page |- | {{LaTeX/Parameter|p}} | on a dedicated '''p'''age of floats |- | {{LaTeX/Parameter|!}} |override the default float restrictions. E.g., the maximum size allowed of a {{LaTeX/Parameter|b}} float is normally quite small; if you want a large one, you need this {{LaTeX/Parameter|!}} parameter as well. |- |} Default is {{LaTeX/Parameter|tbp}}, which means that it is by default placed on the top of the page. If that's not possible, it's placed at the bottom if possible, or finally with other floating environments on an extra page. You can force LaTeX to use one given position. E.g. {{LaTeX/Parameter|[!h]}} forces LaTeX to place it exactly where you place it (Except when it's really impossible, e.g you place a table ''here'' and this place would be the last line on a page). Again, understand it correctly: it urges LaTeX to put the table at a specific place, but it will not be placed there if LaTeX thinks it will not look great. If you really want to place your table manually, do not use the {{LaTeX/Environment|table}} environment. Centering the table horizontally works like everything else, using the {{LaTeX/LaTeX|code=\centering<!---->}} command just after opening the {{LaTeX/Environment|table}} environment, or by enclosing it with a {{LaTeX/Environment|center}} environment. == Using spreadsheets and data analysis tools == For complex or dynamic tables, you may want to use a spreadsheet. You might save lots of time by building tables using specialized software and exporting them in LaTeX format. The following plugins and libraries are available for some popular software: * [http://calc2latex.sourceforge.net/ calc2latex]: for LibreOffice and OpenOffice.org Calc spreadsheets, * [http://www.ctan.org/tex-archive/support/excel2latex/ excel2latex]: for Microsoft Office Excel, * [https://github.com/TheChymera/matrix2latex matrix2latex]: for Python and MATLAB, * [http://pandas.pydata.org/pandas-docs/stable/generated/pandas.DataFrame.to_latex.html pandas]: pandas DataFrame's have a method to convert data they contain to latex, * [http://rubygems.org/gems/latex-tools latex-tools]: a Ruby library, * [http://cran.r-project.org/web/packages/xtable/index.html xtable]: a library for R, * [http://orgmode.org/ org-mode]: for Emacs users, org-mode tables can be used inline in LaTeX documents, see [https://www.gnu.org/software/emacs/manual/html_node/org/A-LaTeX-example.html] for a tutorial. * [http://emacswiki.org/emacs/AlignCommands Emacs align commands]: the align commands can clean up a messy LaTeX table. * [http://truben.no/latex/table/ Online Table generator for LATeX]: An online tool for creating simple tables within the browser. LaTeX format is directly generated as you type. * [http://www.tablesgenerator.com/ Create LaTeX tables online ]: Online tool. However, copying the generated source code to your document is not convenient at all. For maximum flexibility, generate the source code to a separate file which you can input from your main document file with the {{LaTeX/LaTeX|code=\input<!---->}} command. If your spreadsheet supports command-line, you can generate your complete document (table included) in one command, using a Makefile for example. See [[LaTeX/Modular Documents|Modular Documents]] for more details. == Need more features? == Have a look at one of the following packages: * [http://www.ctan.org/pkg/hhline <code>hhline</code>]: do whatever you want with horizontal lines * [http://www.ctan.org/pkg/array <code>array</code>]: gives you more freedom on how to define columns * [http://www.ctan.org/pkg/colortbl <code>colortbl</code>]: make your table more colorful * <code>[https://ctan.org/pkg/threeparttable threeparttable]</code> makes it possible to put footnotes both within the table and its caption * [http://www.ctan.org/pkg/arydshln <code>arydshln</code>]: creates dashed horizontal and vertical lines * [http://www.ctan.org/pkg/ctable <code>ctable</code>]: allows for footnotes under table and properly spaced caption above (incorporates booktabs package) * [http://www.ctan.org/pkg/slashbox <code>slashbox</code>]: create 2D tables with the first cell containing a description for both axes. Not available in Tex Live 2011 or later. * <code>[https://ctan.org/pkg/diagbox diagbox]</code>: compatible to <code>slashbox</code>, come with Tex Live 2011 or later * [http://www.ctan.org/pkg/dcolumn <code>dcolumn</code>]: decimal point alignment of numeric cells * [http://www.ctan.org/pkg/rccol <code>rccol</code>]: advanced decimal point alignment of numeric cells with rounding * [http://www.ctan.org/pkg/numprint <code>numprint</code>]: print numbers, in the current mode (text or math) in order to use the correct font, with separators, exponent and/or rounded to a given number of digits. tabular(*), array, tabularx, and longtable environments are supported using all features of numprint * [http://www.ctan.org/pkg/spreadtab <code>spreadtab</code>]: spread sheets allowing the use of formulae * [http://ctan.org/tex-archive/macros/latex/contrib/siunitx <code>siunitx</code>]: alignment of tabular entries * <code>[https://www.ctan.org/pkg/pgfplotstable pgfplotstable]</code>: loads, rounds, formats and postprocesses numerical tables, e.g. by importing the data directly from .csv (comma-separated value) files instead of manually writing the whole tables in LaTeX code. Programs such as Excel, LibreOffice Calc etc. can export data sheets as .csv files. == References == {{reflist|2}} <noinclude> {{LaTeX/Bottom|Rotations|Title Creation}} </noinclude> [[fr:LaTeX/Faire_des_tableaux]] [[nl:LaTeX/Tabellen]] [[pl:LaTeX/Tabele]] 6l23hxfqblpawp6t01qibui7l6kxgp5 0 55788 4634247 4490966 2026-05-05T10:17:10Z Darrelljon 45960 File:Venus and I at the park.jpg 4634247 wikitext text/x-wiki {{npov}} == Introduction == [[File:Venus and I at the park.jpg|thumb|Zak George, a dog trainer and content creator]] The proper training of the canine companion is essential to the coexistence of human and dog. While the task of training a dog or any other pet can seem daunting, the processes for training both everyday behavior and tricks are well established. Many people unfamiliar with dog training believe that it must be difficult, since so few dogs have any modicum of training. In fact, training a dog to be a well-adjusted member of a family is well within the reach of most people. Dog owners normally train their dogs to be [[Dog Care/Training/Obedience|obedient]] and loving, to do tricks, and sometimes to compete in dog sports. There are multiple schools of thought on dog training, which run the gamut from training based on escape/avoidance to so-called "positive reinforcement" training in which no correction is used. While positive-only methods such as clicker training are currently in vogue, much if not most dog training is still accomplished using some sort of correction at some point in the training process. The single most important factor in dog training is that whatever method is applied is done so consistently. Dogs can be trained by amateur enthusiasts to compete in obedience trials, various dog sports, for use in hunting, and to serve e.g. on volunteer search and rescue teams or as therapy dogs. Moving to the professional side, dogs are trained for personal protection, security, police patrol, drug and bomb detection, evidence identification, etc. == Meta == There are several schools of thought on how to train dogs, ranging from what are often termed "Traditional" methods, based largely on avoidance or escape, to "Positive-Only" methods, such as Clicker Training. All of these methods when properly applied can be used to train most dogs to be tractable companions. This project is aimed at '''novice''' and '''intermediately''' experienced dog owners. This book is about the basic training all dogs will need to have, for example to pass a Canine Good Citizen (CGC) or other similar certification. The training methods recommended in this book should be safe enough that a novice dog owner won't be in danger of harming a dog by following the instructions (or vice versa). Additional topics in dog training include * [[Dog Care/Training/Gun Training|Gun training]] * General dog care * Electrical, prong, choke collars, gentle leaders * [[Dog Care/Training/Clicker training|Clicker training]] Please, if you can contribute to this book, do so. I'm also not sure what the best way to organize the chapters is yet. Please feel free to rearrange the sections if it makes more sense to you. <gallery> File:dog.png|Training requires practice and patience </gallery> {{stages}} == Choosing Commands == Voice Commands Hand signals Looks == What is dog training? == The key to successful dog training is communication. Dogs don't speak our language so we have to use a language they do understand. == Set your dog up to succeed... or to fail?== There are three stages to dog training. Motivational, correction and distraction (or 'proofing'). In the motivational stage, you will set your dog up to succeed, giving it short training sessions and big rewards in a quiet environment and with plenty of encouragement. For example, Sit. You will lure your dog, click, treat, big smile, excitement and if your dog slips, you shrug it off and do it all over again. Come the correction stage. Positive Reinforcement trainers view not getting the reward as a correction. They also teach a "no reward marker", a word or sound such as "oops" or "uh uh" to signal the dog that no reward is coming and pick a new behavior. You're sure your dog knows Sit already. It does it even before the lure comes and you're very pleased. Now you try a 2 second stay without a lure. Your dog does it. You're pretty excited and the dog can feel it too as you dump a big reward on it. Next is a 5 second stay. Your dog slips. You give your no reward marker and help the dog figure out what is expected. Your dog learns to choose, correctly = reward, wrongly = correction, or no reward. The dog might get another correction but then it learns, a lightbulb goes up in its head, it has chosen the right path and gets the reward it has been waiting for all along. Using common sense, it is better if you are told what's wrong rather than be given little hints that aren't straight-forward. Training should be done in increments. The biggest mistake novice trainers make is to move too fast. The dog has the mental capacity of the average 2 year old human child. They are sponges, but can only absorb so much at a sitting. Distractions should also be increased slowly. At first, you teach your dog a command, such as "Sit", in its own house. As the dog masters this, you start moving the dog to places with more distractions, the back yard, the front yard, the sidewalk in front of the house, etc. There are certain common sense rules: when teaching stays, "with time comes distance". Teach your dog to stay while you are close to your dog and can keep him/her in the stay position, before you disappear around the corner. Once your dog learns to stay with you there for 5 minutes, putting that leash down and walking away is a piece of cake. Also, never call your dog to you and punish him/her. If your dog escapes, after you have panicked, chased him around, screamed yourself senseless, etc. When your dog is finally back to you, YOU CANNOT PUNISH HER. She is incapable of understanding she is being punished for running away. She only knows when she got back to you, bad things happened to her and next time, she won't come back at all. This indicates a huge problem with your relationship with your dog, and says your dog is not interested in being with you. Perhaps the dog hasn't been trained, or has fear issues, but you need to go back to square one and train your dog. == Food Lures == Luring with food is a very natural way to show the dog what you'd like it to do. Dogs generally will follow your hand with food. This can be used to teach many commands such as "sit" or "down". If you've ever wanted to create a cool treat for your doggie, with style AND flavor then try "Doggie Popsicles" <!--This content merged from [[Transwiki:Doggie popsicles]] --> ===Doggie Popsicles=== '''Ingredients''' * 2 bouillon cubes (beef, chicken, any flavor works0 * 2 cups of water * an ice cube tray * a pot '''Preparation''' # Start by boiling the water in the pot. # After the water is boiling, put the boullion cubes into the water. # Let them cook until they dissolve, gently stirring them occasionally. # After they are completely dissolved, take them off the stove. Let them cool for 5-10 minutes. # Pour the broth into the ice cube tray. Put it in the freezer. # Once frozen, give to your doggie. Watch him play with and eat his new treat!! Cook time: approx. 15 min. Freeze time: approx. 2 hrs. <!--End merge --> == Discouraging Bad Behavior == There are many things dogs do that humans find unacceptable: Jumping up, mouthing, running away, urinating in the house, chewing, etc. The human has the big brain and should be able to manage the dog's environment so the dog doesn't get a chance to practice objectionable behavior. Don't leave shoes where the puppy can find them, teach the dog to "sit" when greeting people, yell "OUCH!!!" loudly when the puppy puts his teeth on you, go out with the puppy to be sure he potties outside and reward him instantly when he potties appropriately. Teach your dog to do something that make the objectionable behavior impossible: teaching your dog to touch the palm of your hand with its nose, makes it impossible for the dog to mouth your hand at the same time. So instead of constantly correcting bad behavior, or just yelling "NO!" to your dog, you will learn to be proactive and not give it a chance to misbehave. Everyone is happier that way. Redirect your dog when the behavior is inappropriate. If your dog is loose at the dog park, for example, and is starting to be rude to other dogs, call your dog and start walking briskly away. Your dog should want to be with you and will come. === Ignoring Bad Behavior === Sometimes it is best to ignore the bad behavior. Many times people inadvertently reinforce the bad behavior by giving the dog attention. For example, letting a dog inside while it is outside barking teaches the dog to bark to get inside. You are better off to wait until the dog has stopped barking for several minutes before letting it inside. === Distracting === Distracting the dog can be a useful tool to reduce the frequency of an undesirable behavior. A small rattle made from a plastic soda bottle, or a can with pennies placed inside can be shaken to distract the dog from repeating the behavior. Most dogs however only require your voice. A well timed 'Hey, quit it!' is very effective. Then ask the dog to do something that is incompatible with the undesired behavior. Instead of jumping up to Counter surf, call the dog to you and play some tug. Be very careful using sound distractions, many dogs are sound sensitive and the shaking of the penny can may make your dog skittish. If your dog is sound sensitive, you can create a situation when your dog will learn to mistrust you. Using Equipment to get control of your dog while you are training. If you have a dog that pulls or lunges at other dogs barking, it is imperative that you not give your dog the opportunity to practice that behavior. ''''''Pulling'''''' If your dog just pulls, using something like the Sense-ation or other No pull harness. In this style of harness, the leash is connected in front of the dog's chest, so when the dog pulls, it inhibits should action and stops the pulling. If your dog pulls and bark/lunges at other dogs, you need a head halter. There are several types of head halters available and all fit a bit differently from each other. Some of the most popular brands are the Gentle Leader, the Halti, the Comfort Trainer, the Snoot Loop. The basic idea is like the halters used on horses. A person can control a beast weighing over a ton by controlling the head. The same is true for dogs. The strap over the nose is the control. It hits a pressure point that both controls and helps calm the dog. Another piece of equipment that can help with control is a prong, or pinch collar. Contrary to some myths, this is not designed to dig into the dog's neck or puncture the dog. If there is blood, the human is not only using the equipment wrong, but is guilty of abusing the dog. The prong should only be used as a last resort, after other alternatives have been exhausted. It can be an effective tool for dedicated pullers, but it is not recommended for dogs that lunge/bark. The tightening of the prongs on the dog's neck as it is looking at the dog it is lungeing at, can increase aggression. === Boobie-traps === Boobie-traps are items that will surprise a dog by making a loud noise when tripped or knocked over. They have a big advantage in that you don't have to be right there in order to correct the dog. This prevents the dog from associating you with the correction and allow for consistent correction even when you are out of the dogs sight. The effectiveness of these traps depends on the dog; some dogs are very calm and won't care that something fell, while others will learn on the first try and never trip the trap again. As always, use good judgment when formulating a trap. Do not cause harm to the dog, or cause an overconfident dog to get too scared. Again, this can cause a lot of sound sensitivity. Management is the first defense. Pick up the shoes, keep food of off the counters, put the trash under the sink, etc. '''Boobie-traps for use while training dogs can be made from various items:''' Some traps can easily be produced from items found around the house. An object balanced on the edge of a counter may fall and frighten the dog when the dog sniffs at it. This is useful to deter a dog from patrolling the counter for food. *A 12 oz. soda can with several coins inside will make a lot of noise when it falls. {{TODO|todonote=add picture of can on windowsill}} *A small tuna can with water will splash the dog when it is tipped. (Of course, this is only useful if getting some water on the floor is acceptable.) {{TODO|todonote=add picture of tuna can with water on it on edge of counter}} Some alarm systems to deter a dog from unwanted behavior can be purchased at your local pet store. *Motion alarms *trash can lid alarms {{TODO|todonote=add pictures of alarms}} == Walking on a Leash == Walking a dog gives it exercise to help it remain healthy. It is also an easy way for the person walking the dog to get a little exercise. A dog will enjoy being walked because it will be able to explore and see new things. A dog being walked can often be distracted by things like cars, strange noises, objects, plants, other people, or other dogs, so the person walking the dog will want to keep a good hold on the leash. Walking on a leash requires a collar and a leash, which may be purchased at a pet store. It is important to teach a dog "loose leash walking". This involves teaching the dog not to pull and to walk with you regardless of distractions. Treats/clicker can be helpful in this task. On of the most effective techniques is 'be a tree'. Dogs pull because they want to go somewhere. If you hold the leash tightly against your body, plant your feet and refuse to move forward when the dog pulls, the dog isn't getting what it wants. At some point, the dog will turn to look at you. When the dog looks back, the leash will get slack, you immediately reward the dog by moving in the direction the dog originally wanted to go. If the dog pulls again, stop moving until the dog looks at you. This is effective because the dog learns that by not pulling, he gets what he wants. The dog is also learning to pay attention to where you are in relation to the end of the leash. This can build your bond and relationship. Let's work together instead of away from each other. Another technique is reversing direction immediately when the dog begins to pull. This technique is not effective on a determined dog and will often result in the owner being rather dizzy. It works best on young pups as it is virtually painless. People often use 'Prong collars' or other devices such as 'Haltis' to discourage and teach the dog how to walk nicely. Never ever use a traditional halter as it only encourages the dog to pull more (think sled dog). However, the Sense-ation, Sense-ible and Easy Walk harnesses are designed to lessen pulling and work very well. == House Training == {{sectstub}} == Crating == Crating is the practice of keeping a puppy or dog in a kennel when you are not at home and at night. This provides a safe place for the dog and keeps them from being destructive when unsupervised. This is an excellent way to housebreak a new dog. ==Basic Commands== Here are a few commands that almost every dog should respond to: *'''Come''': This command, also referred to as the '''recall''', is crucial. If the dog won't come when called, it is not an obedient dog. One method for training begins by allowing the dog to wander out on a long leash or line, then calling it by name and the command '''Come'''. This method might require a quick, light tug on the leash to get the dog moving when first teaching this command. Like all commands, it is successful only if the dog is rewarded when it completes the command and only if the practice is repeated&mdash;under different circumstances and distances and gradually removing the controls; until the dog performs flawlessly. Another good way to train them without reinforcement is to praise them while afar. They will hear this and come to you. Then, grant them more "good dog!" and such. *'''Sit''': This command is also crucial. Sitting dogs are under the handler's direct control. It is common to precede other commands, such as the '''Stay''' command, with a sit command. One method for training uses a treat held in front of the dog's nose and passed back over its head, forcing the dog to sit. '''Sit''' and '''Stay''' are used in conjunction with many other commands. *'''Stay''': This command gives peace of mind. An owner can park her dog while doing something else. One method of training involves placing the dog in a sit or a down position, then telling it to stay while stepping away from the dog. If the dog stays, the handler rewards it while it is still in the position. Indoors, use this command to park your dog under a favorite table or bench. *'''Lie down''' or '''down''': this command allows even greater control than sitting. One training method uses a treat drawn forward and down across the dog's face, forcing it to lie down to get at it. Since even people without dogs are familiar with this command and use it when dogs are bothering them, the better the dog is at it, the better it can get along with strangers and visitors. But don't get discouraged if the dog refuses or is reluctant to drop into position. The Down is a submissive position and often a dominant dog will refuse to give in. *'''Go to bed''' or '''get in''': Directs the dog to go to its bed or its crate and to remain there until released. The dog has freedom of movement in that location to stand up, turn around, or lie down, unlike when placed in a '''Stay'''. Useful to keep a dog out from underfoot and safe in a busy or complicated situation. Not a necessary command as the dog is taught to 'stay' already while in Down or Sit. Useful for Stand stays though. *'''Drop''' or '''drop it''': Dogs pick up all sorts of things, some of which they shouldn't have. A dog that drops anything on command, no matter how attractive (which to a dog can be rotten and smelly), is a dog under control that the owner can prevent from eating dangerous items or from destroying valued personal property. *'''Leave it''': An adjunct to '''Drop''', directing the dog to not touch an item. Also useful before the dog has picked anything up. One method of training involves leaving a treat on the ground and walking the dog past it without allowing the dog to pick it up. '''Leave it''' is also used in conjunction with '''Take it'''. *'''Take it''': The dog leaves a desired object, such as a toy or treat, untouched until given this command. This can protect an owner's, visitor's, or child's fingers. *'''Heel''', '''Close''', '''By me''': The dog walks with its head directly next to the handler's leg and does not deviate until released. One method of training accompanies the command with a slap to the thigh indicating where the handler wants the dog's head. *'''Okay''', '''Free''', '''Break''', or '''Release''': Releases the dog from '''Stay''', '''Heel''', '''Sit''', and so forth. Also a general release to play. A clicker acts as a release. The specific command word is not important, although the preceding list covers some of the more common words. Short, clear words that are easily understood by other humans are generally recommended; that way, people will understand what a handler is telling his dog to do and other handlers have a good chance of controlling someone else's dog if necessary. In fact, dogs can learn commands in any language or other communications medium, including whistles, mouth sounds, hand gestures, and so forth. == Less Common Commands == While dogs can be trained far beyond these rudiments, a dog that obeys these commands will be a pleasure to keep and take out. Off-leash obedience is the hallmark of a well-trained dog. There are a few commands that many domestic dogs learn, but that are not part of the basic repertoire. *'''Stop''' – a dog that will simply stop whatever it is doing and lie down on command no matter how far it is from its keeper is a dog that can be taken anywhere. Some handlers use the German word '''''Platz''''' (related to "place", i.e. stay in position) for this action. (Useful if your dog is in danger, or headed for some trouble. I.e., your dog is about to get run over by a car. He/she hears "Stop!" and drops and you can be sure it will not be hit. Much faster response than a "Come" command.) *'''Back up''' – keepers of large dogs or dogs with a reputation for aggressiveness can make strangers more comfortable by teaching the dog to back up on command. (Also useful if you are carrying a large box or something and the dog's in your way.) *'''Growl''' – the inverse of backing up. Some owners teach non-aggressive dogs to growl on a subtle command – not the word ''growl'', usually a small hand gesture – as a way of letting strangers know that you and your dog value being left alone. *'''Steady''' – keep near by. The dog can walk free, but not dash off. Train to this command with a long leash, calling out '''Steady''' when the leash is taut. Continue off leash. *'''Stand''' – dog stands still. Train from lying-down position by lifting under belly while repeating command. Useful for grooming. Many dogs are groomed frequently and need to stand quietly during the process. *'''Speak''' – for amusement or showing off, a dog may be trained to bark on command. *'''Chase Recall''' – *'''Paw, or Give Paw''' – Pretty much for showing off, a dog may be trained to give you a "handshake". (Though it's also very useful if the dog needs to get their nails clipped or they have an injury.) *'''Shake''' – Very useful after baths, or walks in snow or rain. *'''Roll Over''' – *'''Jump''' – *'''Calm''' – tells the dog to stop growling and/or playing roughly. Similar to '''Back Up'''. == Games == Games can be fun for both the dog and the owner. Here are some games that can be played with a dog: *'''Fetch''' – This is a game where the owner throws out an object and the dog retrieves it and gives it back to the owner. It can be played with a small ball like a tennis ball, a frisbee, a stick, or any small light object that is easy to throw and easy for the dog to pick up and carry. Large balls can also be used. *'''Hide and Seek''' – You hide and your dog seeks. It is more difficult but worth attempting to make your dog hide while you seek. *'''Tug-of-War''' – It should first be noted, that some (perhaps most) experts state that this game can teach or instil aggressive behavior in your dog. However, most dogs love playing 'Tug-of-War,' and if vigorously participated in by the owner, will allow the dog, especially a younger dog, to use a lot of its extra energy. One rule of the thumb is that you decide when the game ends and you always win. Never let your dog win even if it means pinching your dog's lips against it's teeth to get it to let go. A 'drop it' command is very useful for this. == Problem Behavior == ====Chewing==== One of the causes of destructive chewing behavior in younger dogs, as with children, is 'teething.' A good suggestion, that will allow your dog to relieve it's discomfort, without destroying your home, uses only a used, but clean hand, dish, or other small towel. Soak the towel in clean drinking water. Wring out the excess, until the towel no longer drips. Tie the towel in a knot, and place in the freezer (you may want to place the towel in a freezer bag to protect other items). Once frozen it can be given to the dog as a chew toy. A more expensive but better way is to purchase toys for your dog. The most popular amongst chewers is the Kong toy. Stuffable and challenging to even the most seasoned of veterans. Squeaky toys are noisy but fun to the dog as it mimics an animal that the dog has attacked. Dogs are often observed 'pouncing' on these. ====Jumping up==== First you have to decide if you want to allow your dog to jump up on people or not. Then you need to be consistent in enforcing the rules. Being consistent is the important thing to help your dog learn what is acceptable behavior. Even if you decide it's okay, you may encounter other people who don't like it at all. NOT jumping on people is generally considered good doggie manners. Once you've made the decision that it will not be allowed you have to train your dog to understand what the rules are. To teach a dog not to jump up on you, simply turn your back on the dog when he jumps up. The dog wants your attention. When you turn away from him, you give him the message that jumping up on you will not earn your attention. After a short time (a few seconds) of having you back to the dog, turn back to him and give him another chance to keep his feet on the ground. If he does stay down, praise or reward him for it. He may well try to jump up again then, because he hasn't yet learned what is getting him the praise and what is making you go away. But the dog will figure it out. Most dogs catch on quickly, after just a few times of ignoring him. But remember, it will take a while for your dog to really learn what is expected. So, don't be surprised if the next time he greets you he jumps up. Just be consistent in letting him know it's not acceptable. Keep the emotion out of it. You don't need to scold the dog or correct him. The fact that he is not getting the desired result from jumping on you will be self correcting to him. You should also ask your visitors not to encourage jumping up on people. You can explain to them that they should turn their back on your dog if he attempts to jump up on them. A good alternative to permitting a dog to jump up on people is to teach him to sit when greeting people. Only praise and reward your dog when he is sitting. Turn away if he jumps up, as described above. He will learn to offer sitting to get the attention he seeks. ====Barking==== ====Scratching on doors==== ====Begging==== Don't reward your dog for begging. Dogs learn to beg quickly if you drop food even just a few times and even if you dropped the food by accident. Teach it to lay down out of the way while you are eating or cooking. Crating or a stuffed Kong is also recommended. If you can't prevent the dog from getting the food (this is usually the case when small children have the food) it is best to remove the dog from the room while eating. A well timed correction is also another way to deter Begging forever. ====Chasing Other Small Animals==== Everyone has heard stories about the dog who ate the gerbil, hamster, or even human baby. Try not to let this happen. Correct the dog (via training collar or voice) for attempting to even sniff the animal. It will soon learn to ignore it. ====Aggression==== ====Submissiveness==== ====Stealing Food==== Once the dog learns it can steal food, it's hard to break it out of the habit. A good way is also corrections, teaching the Leave It and anticipating the dog's action and reacting (verbal correction, taking the food away and turning the dog away, etc.). ====Getting in the Trash==== There are two situations to consider 1) dog gets into trash when you are present (supervising) It will be helpful to teach your dog a "Leave It" command. But start by teaching the command in a more controlled situation with a single piece of food. 2) dog gets into trash when you are NOT there to supervise Dogs are dogs, they get into trash if it's left out for them when they are unsupervised. Put the trash somewhere where your dog cannot get to it. Or get a trash can that your dog cannot get open. ====Digging==== Best way to avoid this is to occupy the dog's time. Training, toys and walks are excellent ways. You can also use [[Cookbook:Chili Powder|chili powder]]<ref>[http://www.djournal.com/lifestyle/home-gardening/master-gardener-dogs-can-create-challenges-in-landscape/article_fcae52d0-9474-5586-bbca-c8f1b2b6c29e.html "The Chili Powder Method" ''Mississippi Street Journal'']</ref> to cover up the digging spot. ==External Links== {{BookCat}} <references /> 5up1y9vlpomsr5uuurxdfao7rkjzdrj 4634249 4634247 2026-05-05T10:20:25Z Darrelljon 45960 /* Meta */ File:Cesar Millan 285.jpg 4634249 wikitext text/x-wiki {{npov}} == Introduction == [[File:Venus and I at the park.jpg|thumb|Zak George, a dog trainer and content creator]] The proper training of the canine companion is essential to the coexistence of human and dog. While the task of training a dog or any other pet can seem daunting, the processes for training both everyday behavior and tricks are well established. Many people unfamiliar with dog training believe that it must be difficult, since so few dogs have any modicum of training. In fact, training a dog to be a well-adjusted member of a family is well within the reach of most people. Dog owners normally train their dogs to be [[Dog Care/Training/Obedience|obedient]] and loving, to do tricks, and sometimes to compete in dog sports. There are multiple schools of thought on dog training, which run the gamut from training based on escape/avoidance to so-called "positive reinforcement" training in which no correction is used. While positive-only methods such as clicker training are currently in vogue, much if not most dog training is still accomplished using some sort of correction at some point in the training process. The single most important factor in dog training is that whatever method is applied is done so consistently. Dogs can be trained by amateur enthusiasts to compete in obedience trials, various dog sports, for use in hunting, and to serve e.g. on volunteer search and rescue teams or as therapy dogs. Moving to the professional side, dogs are trained for personal protection, security, police patrol, drug and bomb detection, evidence identification, etc. == Meta == [[File:Cesar Millan 285.jpg|thumb|Cesar Millan]] There are several schools of thought on how to train dogs, ranging from what are often termed "Traditional" methods, based largely on avoidance or escape, to "Positive-Only" methods, such as Clicker Training. All of these methods when properly applied can be used to train most dogs to be tractable companions. This project is aimed at '''novice''' and '''intermediately''' experienced dog owners. This book is about the basic training all dogs will need to have, for example to pass a Canine Good Citizen (CGC) or other similar certification. The training methods recommended in this book should be safe enough that a novice dog owner won't be in danger of harming a dog by following the instructions (or vice versa). Additional topics in dog training include * [[Dog Care/Training/Gun Training|Gun training]] * General dog care * Electrical, prong, choke collars, gentle leaders * [[Dog Care/Training/Clicker training|Clicker training]] Please, if you can contribute to this book, do so. I'm also not sure what the best way to organize the chapters is yet. Please feel free to rearrange the sections if it makes more sense to you. <gallery> File:dog.png|Training requires practice and patience </gallery> {{stages}} == Choosing Commands == Voice Commands Hand signals Looks == What is dog training? == The key to successful dog training is communication. Dogs don't speak our language so we have to use a language they do understand. == Set your dog up to succeed... or to fail?== There are three stages to dog training. Motivational, correction and distraction (or 'proofing'). In the motivational stage, you will set your dog up to succeed, giving it short training sessions and big rewards in a quiet environment and with plenty of encouragement. For example, Sit. You will lure your dog, click, treat, big smile, excitement and if your dog slips, you shrug it off and do it all over again. Come the correction stage. Positive Reinforcement trainers view not getting the reward as a correction. They also teach a "no reward marker", a word or sound such as "oops" or "uh uh" to signal the dog that no reward is coming and pick a new behavior. You're sure your dog knows Sit already. It does it even before the lure comes and you're very pleased. Now you try a 2 second stay without a lure. Your dog does it. You're pretty excited and the dog can feel it too as you dump a big reward on it. Next is a 5 second stay. Your dog slips. You give your no reward marker and help the dog figure out what is expected. Your dog learns to choose, correctly = reward, wrongly = correction, or no reward. The dog might get another correction but then it learns, a lightbulb goes up in its head, it has chosen the right path and gets the reward it has been waiting for all along. Using common sense, it is better if you are told what's wrong rather than be given little hints that aren't straight-forward. Training should be done in increments. The biggest mistake novice trainers make is to move too fast. The dog has the mental capacity of the average 2 year old human child. They are sponges, but can only absorb so much at a sitting. Distractions should also be increased slowly. At first, you teach your dog a command, such as "Sit", in its own house. As the dog masters this, you start moving the dog to places with more distractions, the back yard, the front yard, the sidewalk in front of the house, etc. There are certain common sense rules: when teaching stays, "with time comes distance". Teach your dog to stay while you are close to your dog and can keep him/her in the stay position, before you disappear around the corner. Once your dog learns to stay with you there for 5 minutes, putting that leash down and walking away is a piece of cake. Also, never call your dog to you and punish him/her. If your dog escapes, after you have panicked, chased him around, screamed yourself senseless, etc. When your dog is finally back to you, YOU CANNOT PUNISH HER. She is incapable of understanding she is being punished for running away. She only knows when she got back to you, bad things happened to her and next time, she won't come back at all. This indicates a huge problem with your relationship with your dog, and says your dog is not interested in being with you. Perhaps the dog hasn't been trained, or has fear issues, but you need to go back to square one and train your dog. == Food Lures == Luring with food is a very natural way to show the dog what you'd like it to do. Dogs generally will follow your hand with food. This can be used to teach many commands such as "sit" or "down". If you've ever wanted to create a cool treat for your doggie, with style AND flavor then try "Doggie Popsicles" <!--This content merged from [[Transwiki:Doggie popsicles]] --> ===Doggie Popsicles=== '''Ingredients''' * 2 bouillon cubes (beef, chicken, any flavor works0 * 2 cups of water * an ice cube tray * a pot '''Preparation''' # Start by boiling the water in the pot. # After the water is boiling, put the boullion cubes into the water. # Let them cook until they dissolve, gently stirring them occasionally. # After they are completely dissolved, take them off the stove. Let them cool for 5-10 minutes. # Pour the broth into the ice cube tray. Put it in the freezer. # Once frozen, give to your doggie. Watch him play with and eat his new treat!! Cook time: approx. 15 min. Freeze time: approx. 2 hrs. <!--End merge --> == Discouraging Bad Behavior == There are many things dogs do that humans find unacceptable: Jumping up, mouthing, running away, urinating in the house, chewing, etc. The human has the big brain and should be able to manage the dog's environment so the dog doesn't get a chance to practice objectionable behavior. Don't leave shoes where the puppy can find them, teach the dog to "sit" when greeting people, yell "OUCH!!!" loudly when the puppy puts his teeth on you, go out with the puppy to be sure he potties outside and reward him instantly when he potties appropriately. Teach your dog to do something that make the objectionable behavior impossible: teaching your dog to touch the palm of your hand with its nose, makes it impossible for the dog to mouth your hand at the same time. So instead of constantly correcting bad behavior, or just yelling "NO!" to your dog, you will learn to be proactive and not give it a chance to misbehave. Everyone is happier that way. Redirect your dog when the behavior is inappropriate. If your dog is loose at the dog park, for example, and is starting to be rude to other dogs, call your dog and start walking briskly away. Your dog should want to be with you and will come. === Ignoring Bad Behavior === Sometimes it is best to ignore the bad behavior. Many times people inadvertently reinforce the bad behavior by giving the dog attention. For example, letting a dog inside while it is outside barking teaches the dog to bark to get inside. You are better off to wait until the dog has stopped barking for several minutes before letting it inside. === Distracting === Distracting the dog can be a useful tool to reduce the frequency of an undesirable behavior. A small rattle made from a plastic soda bottle, or a can with pennies placed inside can be shaken to distract the dog from repeating the behavior. Most dogs however only require your voice. A well timed 'Hey, quit it!' is very effective. Then ask the dog to do something that is incompatible with the undesired behavior. Instead of jumping up to Counter surf, call the dog to you and play some tug. Be very careful using sound distractions, many dogs are sound sensitive and the shaking of the penny can may make your dog skittish. If your dog is sound sensitive, you can create a situation when your dog will learn to mistrust you. Using Equipment to get control of your dog while you are training. If you have a dog that pulls or lunges at other dogs barking, it is imperative that you not give your dog the opportunity to practice that behavior. ''''''Pulling'''''' If your dog just pulls, using something like the Sense-ation or other No pull harness. In this style of harness, the leash is connected in front of the dog's chest, so when the dog pulls, it inhibits should action and stops the pulling. If your dog pulls and bark/lunges at other dogs, you need a head halter. There are several types of head halters available and all fit a bit differently from each other. Some of the most popular brands are the Gentle Leader, the Halti, the Comfort Trainer, the Snoot Loop. The basic idea is like the halters used on horses. A person can control a beast weighing over a ton by controlling the head. The same is true for dogs. The strap over the nose is the control. It hits a pressure point that both controls and helps calm the dog. Another piece of equipment that can help with control is a prong, or pinch collar. Contrary to some myths, this is not designed to dig into the dog's neck or puncture the dog. If there is blood, the human is not only using the equipment wrong, but is guilty of abusing the dog. The prong should only be used as a last resort, after other alternatives have been exhausted. It can be an effective tool for dedicated pullers, but it is not recommended for dogs that lunge/bark. The tightening of the prongs on the dog's neck as it is looking at the dog it is lungeing at, can increase aggression. === Boobie-traps === Boobie-traps are items that will surprise a dog by making a loud noise when tripped or knocked over. They have a big advantage in that you don't have to be right there in order to correct the dog. This prevents the dog from associating you with the correction and allow for consistent correction even when you are out of the dogs sight. The effectiveness of these traps depends on the dog; some dogs are very calm and won't care that something fell, while others will learn on the first try and never trip the trap again. As always, use good judgment when formulating a trap. Do not cause harm to the dog, or cause an overconfident dog to get too scared. Again, this can cause a lot of sound sensitivity. Management is the first defense. Pick up the shoes, keep food of off the counters, put the trash under the sink, etc. '''Boobie-traps for use while training dogs can be made from various items:''' Some traps can easily be produced from items found around the house. An object balanced on the edge of a counter may fall and frighten the dog when the dog sniffs at it. This is useful to deter a dog from patrolling the counter for food. *A 12 oz. soda can with several coins inside will make a lot of noise when it falls. {{TODO|todonote=add picture of can on windowsill}} *A small tuna can with water will splash the dog when it is tipped. (Of course, this is only useful if getting some water on the floor is acceptable.) {{TODO|todonote=add picture of tuna can with water on it on edge of counter}} Some alarm systems to deter a dog from unwanted behavior can be purchased at your local pet store. *Motion alarms *trash can lid alarms {{TODO|todonote=add pictures of alarms}} == Walking on a Leash == Walking a dog gives it exercise to help it remain healthy. It is also an easy way for the person walking the dog to get a little exercise. A dog will enjoy being walked because it will be able to explore and see new things. A dog being walked can often be distracted by things like cars, strange noises, objects, plants, other people, or other dogs, so the person walking the dog will want to keep a good hold on the leash. Walking on a leash requires a collar and a leash, which may be purchased at a pet store. It is important to teach a dog "loose leash walking". This involves teaching the dog not to pull and to walk with you regardless of distractions. Treats/clicker can be helpful in this task. On of the most effective techniques is 'be a tree'. Dogs pull because they want to go somewhere. If you hold the leash tightly against your body, plant your feet and refuse to move forward when the dog pulls, the dog isn't getting what it wants. At some point, the dog will turn to look at you. When the dog looks back, the leash will get slack, you immediately reward the dog by moving in the direction the dog originally wanted to go. If the dog pulls again, stop moving until the dog looks at you. This is effective because the dog learns that by not pulling, he gets what he wants. The dog is also learning to pay attention to where you are in relation to the end of the leash. This can build your bond and relationship. Let's work together instead of away from each other. Another technique is reversing direction immediately when the dog begins to pull. This technique is not effective on a determined dog and will often result in the owner being rather dizzy. It works best on young pups as it is virtually painless. People often use 'Prong collars' or other devices such as 'Haltis' to discourage and teach the dog how to walk nicely. Never ever use a traditional halter as it only encourages the dog to pull more (think sled dog). However, the Sense-ation, Sense-ible and Easy Walk harnesses are designed to lessen pulling and work very well. == House Training == {{sectstub}} == Crating == Crating is the practice of keeping a puppy or dog in a kennel when you are not at home and at night. This provides a safe place for the dog and keeps them from being destructive when unsupervised. This is an excellent way to housebreak a new dog. ==Basic Commands== Here are a few commands that almost every dog should respond to: *'''Come''': This command, also referred to as the '''recall''', is crucial. If the dog won't come when called, it is not an obedient dog. One method for training begins by allowing the dog to wander out on a long leash or line, then calling it by name and the command '''Come'''. This method might require a quick, light tug on the leash to get the dog moving when first teaching this command. Like all commands, it is successful only if the dog is rewarded when it completes the command and only if the practice is repeated&mdash;under different circumstances and distances and gradually removing the controls; until the dog performs flawlessly. Another good way to train them without reinforcement is to praise them while afar. They will hear this and come to you. Then, grant them more "good dog!" and such. *'''Sit''': This command is also crucial. Sitting dogs are under the handler's direct control. It is common to precede other commands, such as the '''Stay''' command, with a sit command. One method for training uses a treat held in front of the dog's nose and passed back over its head, forcing the dog to sit. '''Sit''' and '''Stay''' are used in conjunction with many other commands. *'''Stay''': This command gives peace of mind. An owner can park her dog while doing something else. One method of training involves placing the dog in a sit or a down position, then telling it to stay while stepping away from the dog. If the dog stays, the handler rewards it while it is still in the position. Indoors, use this command to park your dog under a favorite table or bench. *'''Lie down''' or '''down''': this command allows even greater control than sitting. One training method uses a treat drawn forward and down across the dog's face, forcing it to lie down to get at it. Since even people without dogs are familiar with this command and use it when dogs are bothering them, the better the dog is at it, the better it can get along with strangers and visitors. But don't get discouraged if the dog refuses or is reluctant to drop into position. The Down is a submissive position and often a dominant dog will refuse to give in. *'''Go to bed''' or '''get in''': Directs the dog to go to its bed or its crate and to remain there until released. The dog has freedom of movement in that location to stand up, turn around, or lie down, unlike when placed in a '''Stay'''. Useful to keep a dog out from underfoot and safe in a busy or complicated situation. Not a necessary command as the dog is taught to 'stay' already while in Down or Sit. Useful for Stand stays though. *'''Drop''' or '''drop it''': Dogs pick up all sorts of things, some of which they shouldn't have. A dog that drops anything on command, no matter how attractive (which to a dog can be rotten and smelly), is a dog under control that the owner can prevent from eating dangerous items or from destroying valued personal property. *'''Leave it''': An adjunct to '''Drop''', directing the dog to not touch an item. Also useful before the dog has picked anything up. One method of training involves leaving a treat on the ground and walking the dog past it without allowing the dog to pick it up. '''Leave it''' is also used in conjunction with '''Take it'''. *'''Take it''': The dog leaves a desired object, such as a toy or treat, untouched until given this command. This can protect an owner's, visitor's, or child's fingers. *'''Heel''', '''Close''', '''By me''': The dog walks with its head directly next to the handler's leg and does not deviate until released. One method of training accompanies the command with a slap to the thigh indicating where the handler wants the dog's head. *'''Okay''', '''Free''', '''Break''', or '''Release''': Releases the dog from '''Stay''', '''Heel''', '''Sit''', and so forth. Also a general release to play. A clicker acts as a release. The specific command word is not important, although the preceding list covers some of the more common words. Short, clear words that are easily understood by other humans are generally recommended; that way, people will understand what a handler is telling his dog to do and other handlers have a good chance of controlling someone else's dog if necessary. In fact, dogs can learn commands in any language or other communications medium, including whistles, mouth sounds, hand gestures, and so forth. == Less Common Commands == While dogs can be trained far beyond these rudiments, a dog that obeys these commands will be a pleasure to keep and take out. Off-leash obedience is the hallmark of a well-trained dog. There are a few commands that many domestic dogs learn, but that are not part of the basic repertoire. *'''Stop''' – a dog that will simply stop whatever it is doing and lie down on command no matter how far it is from its keeper is a dog that can be taken anywhere. Some handlers use the German word '''''Platz''''' (related to "place", i.e. stay in position) for this action. (Useful if your dog is in danger, or headed for some trouble. I.e., your dog is about to get run over by a car. He/she hears "Stop!" and drops and you can be sure it will not be hit. Much faster response than a "Come" command.) *'''Back up''' – keepers of large dogs or dogs with a reputation for aggressiveness can make strangers more comfortable by teaching the dog to back up on command. (Also useful if you are carrying a large box or something and the dog's in your way.) *'''Growl''' – the inverse of backing up. Some owners teach non-aggressive dogs to growl on a subtle command – not the word ''growl'', usually a small hand gesture – as a way of letting strangers know that you and your dog value being left alone. *'''Steady''' – keep near by. The dog can walk free, but not dash off. Train to this command with a long leash, calling out '''Steady''' when the leash is taut. Continue off leash. *'''Stand''' – dog stands still. Train from lying-down position by lifting under belly while repeating command. Useful for grooming. Many dogs are groomed frequently and need to stand quietly during the process. *'''Speak''' – for amusement or showing off, a dog may be trained to bark on command. *'''Chase Recall''' – *'''Paw, or Give Paw''' – Pretty much for showing off, a dog may be trained to give you a "handshake". (Though it's also very useful if the dog needs to get their nails clipped or they have an injury.) *'''Shake''' – Very useful after baths, or walks in snow or rain. *'''Roll Over''' – *'''Jump''' – *'''Calm''' – tells the dog to stop growling and/or playing roughly. Similar to '''Back Up'''. == Games == Games can be fun for both the dog and the owner. Here are some games that can be played with a dog: *'''Fetch''' – This is a game where the owner throws out an object and the dog retrieves it and gives it back to the owner. It can be played with a small ball like a tennis ball, a frisbee, a stick, or any small light object that is easy to throw and easy for the dog to pick up and carry. Large balls can also be used. *'''Hide and Seek''' – You hide and your dog seeks. It is more difficult but worth attempting to make your dog hide while you seek. *'''Tug-of-War''' – It should first be noted, that some (perhaps most) experts state that this game can teach or instil aggressive behavior in your dog. However, most dogs love playing 'Tug-of-War,' and if vigorously participated in by the owner, will allow the dog, especially a younger dog, to use a lot of its extra energy. One rule of the thumb is that you decide when the game ends and you always win. Never let your dog win even if it means pinching your dog's lips against it's teeth to get it to let go. A 'drop it' command is very useful for this. == Problem Behavior == ====Chewing==== One of the causes of destructive chewing behavior in younger dogs, as with children, is 'teething.' A good suggestion, that will allow your dog to relieve it's discomfort, without destroying your home, uses only a used, but clean hand, dish, or other small towel. Soak the towel in clean drinking water. Wring out the excess, until the towel no longer drips. Tie the towel in a knot, and place in the freezer (you may want to place the towel in a freezer bag to protect other items). Once frozen it can be given to the dog as a chew toy. A more expensive but better way is to purchase toys for your dog. The most popular amongst chewers is the Kong toy. Stuffable and challenging to even the most seasoned of veterans. Squeaky toys are noisy but fun to the dog as it mimics an animal that the dog has attacked. Dogs are often observed 'pouncing' on these. ====Jumping up==== First you have to decide if you want to allow your dog to jump up on people or not. Then you need to be consistent in enforcing the rules. Being consistent is the important thing to help your dog learn what is acceptable behavior. Even if you decide it's okay, you may encounter other people who don't like it at all. NOT jumping on people is generally considered good doggie manners. Once you've made the decision that it will not be allowed you have to train your dog to understand what the rules are. To teach a dog not to jump up on you, simply turn your back on the dog when he jumps up. The dog wants your attention. When you turn away from him, you give him the message that jumping up on you will not earn your attention. After a short time (a few seconds) of having you back to the dog, turn back to him and give him another chance to keep his feet on the ground. If he does stay down, praise or reward him for it. He may well try to jump up again then, because he hasn't yet learned what is getting him the praise and what is making you go away. But the dog will figure it out. Most dogs catch on quickly, after just a few times of ignoring him. But remember, it will take a while for your dog to really learn what is expected. So, don't be surprised if the next time he greets you he jumps up. Just be consistent in letting him know it's not acceptable. Keep the emotion out of it. You don't need to scold the dog or correct him. The fact that he is not getting the desired result from jumping on you will be self correcting to him. You should also ask your visitors not to encourage jumping up on people. You can explain to them that they should turn their back on your dog if he attempts to jump up on them. A good alternative to permitting a dog to jump up on people is to teach him to sit when greeting people. Only praise and reward your dog when he is sitting. Turn away if he jumps up, as described above. He will learn to offer sitting to get the attention he seeks. ====Barking==== ====Scratching on doors==== ====Begging==== Don't reward your dog for begging. Dogs learn to beg quickly if you drop food even just a few times and even if you dropped the food by accident. Teach it to lay down out of the way while you are eating or cooking. Crating or a stuffed Kong is also recommended. If you can't prevent the dog from getting the food (this is usually the case when small children have the food) it is best to remove the dog from the room while eating. A well timed correction is also another way to deter Begging forever. ====Chasing Other Small Animals==== Everyone has heard stories about the dog who ate the gerbil, hamster, or even human baby. Try not to let this happen. Correct the dog (via training collar or voice) for attempting to even sniff the animal. It will soon learn to ignore it. ====Aggression==== ====Submissiveness==== ====Stealing Food==== Once the dog learns it can steal food, it's hard to break it out of the habit. A good way is also corrections, teaching the Leave It and anticipating the dog's action and reacting (verbal correction, taking the food away and turning the dog away, etc.). ====Getting in the Trash==== There are two situations to consider 1) dog gets into trash when you are present (supervising) It will be helpful to teach your dog a "Leave It" command. But start by teaching the command in a more controlled situation with a single piece of food. 2) dog gets into trash when you are NOT there to supervise Dogs are dogs, they get into trash if it's left out for them when they are unsupervised. Put the trash somewhere where your dog cannot get to it. Or get a trash can that your dog cannot get open. ====Digging==== Best way to avoid this is to occupy the dog's time. Training, toys and walks are excellent ways. You can also use [[Cookbook:Chili Powder|chili powder]]<ref>[http://www.djournal.com/lifestyle/home-gardening/master-gardener-dogs-can-create-challenges-in-landscape/article_fcae52d0-9474-5586-bbca-c8f1b2b6c29e.html "The Chili Powder Method" ''Mississippi Street Journal'']</ref> to cover up the digging spot. ==External Links== {{BookCat}} <references /> l6yocpqp8ex66lvy2vxg27ccs57rni1 4634250 4634249 2026-05-05T10:21:40Z Darrelljon 45960 /* Games */ File:A-Test-of-Canine-Olfactory-Capacity-Comparing-Various-Dog-Breeds-and-Wolves-in-a-Natural-Detection-pone.0154087.s003.ogv 4634250 wikitext text/x-wiki {{npov}} == Introduction == [[File:Venus and I at the park.jpg|thumb|Zak George, a dog trainer and content creator]] The proper training of the canine companion is essential to the coexistence of human and dog. While the task of training a dog or any other pet can seem daunting, the processes for training both everyday behavior and tricks are well established. Many people unfamiliar with dog training believe that it must be difficult, since so few dogs have any modicum of training. In fact, training a dog to be a well-adjusted member of a family is well within the reach of most people. Dog owners normally train their dogs to be [[Dog Care/Training/Obedience|obedient]] and loving, to do tricks, and sometimes to compete in dog sports. There are multiple schools of thought on dog training, which run the gamut from training based on escape/avoidance to so-called "positive reinforcement" training in which no correction is used. While positive-only methods such as clicker training are currently in vogue, much if not most dog training is still accomplished using some sort of correction at some point in the training process. The single most important factor in dog training is that whatever method is applied is done so consistently. Dogs can be trained by amateur enthusiasts to compete in obedience trials, various dog sports, for use in hunting, and to serve e.g. on volunteer search and rescue teams or as therapy dogs. Moving to the professional side, dogs are trained for personal protection, security, police patrol, drug and bomb detection, evidence identification, etc. == Meta == [[File:Cesar Millan 285.jpg|thumb|Cesar Millan]] There are several schools of thought on how to train dogs, ranging from what are often termed "Traditional" methods, based largely on avoidance or escape, to "Positive-Only" methods, such as Clicker Training. All of these methods when properly applied can be used to train most dogs to be tractable companions. This project is aimed at '''novice''' and '''intermediately''' experienced dog owners. This book is about the basic training all dogs will need to have, for example to pass a Canine Good Citizen (CGC) or other similar certification. The training methods recommended in this book should be safe enough that a novice dog owner won't be in danger of harming a dog by following the instructions (or vice versa). Additional topics in dog training include * [[Dog Care/Training/Gun Training|Gun training]] * General dog care * Electrical, prong, choke collars, gentle leaders * [[Dog Care/Training/Clicker training|Clicker training]] Please, if you can contribute to this book, do so. I'm also not sure what the best way to organize the chapters is yet. Please feel free to rearrange the sections if it makes more sense to you. <gallery> File:dog.png|Training requires practice and patience </gallery> {{stages}} == Choosing Commands == Voice Commands Hand signals Looks == What is dog training? == The key to successful dog training is communication. Dogs don't speak our language so we have to use a language they do understand. == Set your dog up to succeed... or to fail?== There are three stages to dog training. Motivational, correction and distraction (or 'proofing'). In the motivational stage, you will set your dog up to succeed, giving it short training sessions and big rewards in a quiet environment and with plenty of encouragement. For example, Sit. You will lure your dog, click, treat, big smile, excitement and if your dog slips, you shrug it off and do it all over again. Come the correction stage. Positive Reinforcement trainers view not getting the reward as a correction. They also teach a "no reward marker", a word or sound such as "oops" or "uh uh" to signal the dog that no reward is coming and pick a new behavior. You're sure your dog knows Sit already. It does it even before the lure comes and you're very pleased. Now you try a 2 second stay without a lure. Your dog does it. You're pretty excited and the dog can feel it too as you dump a big reward on it. Next is a 5 second stay. Your dog slips. You give your no reward marker and help the dog figure out what is expected. Your dog learns to choose, correctly = reward, wrongly = correction, or no reward. The dog might get another correction but then it learns, a lightbulb goes up in its head, it has chosen the right path and gets the reward it has been waiting for all along. Using common sense, it is better if you are told what's wrong rather than be given little hints that aren't straight-forward. Training should be done in increments. The biggest mistake novice trainers make is to move too fast. The dog has the mental capacity of the average 2 year old human child. They are sponges, but can only absorb so much at a sitting. Distractions should also be increased slowly. At first, you teach your dog a command, such as "Sit", in its own house. As the dog masters this, you start moving the dog to places with more distractions, the back yard, the front yard, the sidewalk in front of the house, etc. There are certain common sense rules: when teaching stays, "with time comes distance". Teach your dog to stay while you are close to your dog and can keep him/her in the stay position, before you disappear around the corner. Once your dog learns to stay with you there for 5 minutes, putting that leash down and walking away is a piece of cake. Also, never call your dog to you and punish him/her. If your dog escapes, after you have panicked, chased him around, screamed yourself senseless, etc. When your dog is finally back to you, YOU CANNOT PUNISH HER. She is incapable of understanding she is being punished for running away. She only knows when she got back to you, bad things happened to her and next time, she won't come back at all. This indicates a huge problem with your relationship with your dog, and says your dog is not interested in being with you. Perhaps the dog hasn't been trained, or has fear issues, but you need to go back to square one and train your dog. == Food Lures == Luring with food is a very natural way to show the dog what you'd like it to do. Dogs generally will follow your hand with food. This can be used to teach many commands such as "sit" or "down". If you've ever wanted to create a cool treat for your doggie, with style AND flavor then try "Doggie Popsicles" <!--This content merged from [[Transwiki:Doggie popsicles]] --> ===Doggie Popsicles=== '''Ingredients''' * 2 bouillon cubes (beef, chicken, any flavor works0 * 2 cups of water * an ice cube tray * a pot '''Preparation''' # Start by boiling the water in the pot. # After the water is boiling, put the boullion cubes into the water. # Let them cook until they dissolve, gently stirring them occasionally. # After they are completely dissolved, take them off the stove. Let them cool for 5-10 minutes. # Pour the broth into the ice cube tray. Put it in the freezer. # Once frozen, give to your doggie. Watch him play with and eat his new treat!! Cook time: approx. 15 min. Freeze time: approx. 2 hrs. <!--End merge --> == Discouraging Bad Behavior == There are many things dogs do that humans find unacceptable: Jumping up, mouthing, running away, urinating in the house, chewing, etc. The human has the big brain and should be able to manage the dog's environment so the dog doesn't get a chance to practice objectionable behavior. Don't leave shoes where the puppy can find them, teach the dog to "sit" when greeting people, yell "OUCH!!!" loudly when the puppy puts his teeth on you, go out with the puppy to be sure he potties outside and reward him instantly when he potties appropriately. Teach your dog to do something that make the objectionable behavior impossible: teaching your dog to touch the palm of your hand with its nose, makes it impossible for the dog to mouth your hand at the same time. So instead of constantly correcting bad behavior, or just yelling "NO!" to your dog, you will learn to be proactive and not give it a chance to misbehave. Everyone is happier that way. Redirect your dog when the behavior is inappropriate. If your dog is loose at the dog park, for example, and is starting to be rude to other dogs, call your dog and start walking briskly away. Your dog should want to be with you and will come. === Ignoring Bad Behavior === Sometimes it is best to ignore the bad behavior. Many times people inadvertently reinforce the bad behavior by giving the dog attention. For example, letting a dog inside while it is outside barking teaches the dog to bark to get inside. You are better off to wait until the dog has stopped barking for several minutes before letting it inside. === Distracting === Distracting the dog can be a useful tool to reduce the frequency of an undesirable behavior. A small rattle made from a plastic soda bottle, or a can with pennies placed inside can be shaken to distract the dog from repeating the behavior. Most dogs however only require your voice. A well timed 'Hey, quit it!' is very effective. Then ask the dog to do something that is incompatible with the undesired behavior. Instead of jumping up to Counter surf, call the dog to you and play some tug. Be very careful using sound distractions, many dogs are sound sensitive and the shaking of the penny can may make your dog skittish. If your dog is sound sensitive, you can create a situation when your dog will learn to mistrust you. Using Equipment to get control of your dog while you are training. If you have a dog that pulls or lunges at other dogs barking, it is imperative that you not give your dog the opportunity to practice that behavior. ''''''Pulling'''''' If your dog just pulls, using something like the Sense-ation or other No pull harness. In this style of harness, the leash is connected in front of the dog's chest, so when the dog pulls, it inhibits should action and stops the pulling. If your dog pulls and bark/lunges at other dogs, you need a head halter. There are several types of head halters available and all fit a bit differently from each other. Some of the most popular brands are the Gentle Leader, the Halti, the Comfort Trainer, the Snoot Loop. The basic idea is like the halters used on horses. A person can control a beast weighing over a ton by controlling the head. The same is true for dogs. The strap over the nose is the control. It hits a pressure point that both controls and helps calm the dog. Another piece of equipment that can help with control is a prong, or pinch collar. Contrary to some myths, this is not designed to dig into the dog's neck or puncture the dog. If there is blood, the human is not only using the equipment wrong, but is guilty of abusing the dog. The prong should only be used as a last resort, after other alternatives have been exhausted. It can be an effective tool for dedicated pullers, but it is not recommended for dogs that lunge/bark. The tightening of the prongs on the dog's neck as it is looking at the dog it is lungeing at, can increase aggression. === Boobie-traps === Boobie-traps are items that will surprise a dog by making a loud noise when tripped or knocked over. They have a big advantage in that you don't have to be right there in order to correct the dog. This prevents the dog from associating you with the correction and allow for consistent correction even when you are out of the dogs sight. The effectiveness of these traps depends on the dog; some dogs are very calm and won't care that something fell, while others will learn on the first try and never trip the trap again. As always, use good judgment when formulating a trap. Do not cause harm to the dog, or cause an overconfident dog to get too scared. Again, this can cause a lot of sound sensitivity. Management is the first defense. Pick up the shoes, keep food of off the counters, put the trash under the sink, etc. '''Boobie-traps for use while training dogs can be made from various items:''' Some traps can easily be produced from items found around the house. An object balanced on the edge of a counter may fall and frighten the dog when the dog sniffs at it. This is useful to deter a dog from patrolling the counter for food. *A 12 oz. soda can with several coins inside will make a lot of noise when it falls. {{TODO|todonote=add picture of can on windowsill}} *A small tuna can with water will splash the dog when it is tipped. (Of course, this is only useful if getting some water on the floor is acceptable.) {{TODO|todonote=add picture of tuna can with water on it on edge of counter}} Some alarm systems to deter a dog from unwanted behavior can be purchased at your local pet store. *Motion alarms *trash can lid alarms {{TODO|todonote=add pictures of alarms}} == Walking on a Leash == Walking a dog gives it exercise to help it remain healthy. It is also an easy way for the person walking the dog to get a little exercise. A dog will enjoy being walked because it will be able to explore and see new things. A dog being walked can often be distracted by things like cars, strange noises, objects, plants, other people, or other dogs, so the person walking the dog will want to keep a good hold on the leash. Walking on a leash requires a collar and a leash, which may be purchased at a pet store. It is important to teach a dog "loose leash walking". This involves teaching the dog not to pull and to walk with you regardless of distractions. Treats/clicker can be helpful in this task. On of the most effective techniques is 'be a tree'. Dogs pull because they want to go somewhere. If you hold the leash tightly against your body, plant your feet and refuse to move forward when the dog pulls, the dog isn't getting what it wants. At some point, the dog will turn to look at you. When the dog looks back, the leash will get slack, you immediately reward the dog by moving in the direction the dog originally wanted to go. If the dog pulls again, stop moving until the dog looks at you. This is effective because the dog learns that by not pulling, he gets what he wants. The dog is also learning to pay attention to where you are in relation to the end of the leash. This can build your bond and relationship. Let's work together instead of away from each other. Another technique is reversing direction immediately when the dog begins to pull. This technique is not effective on a determined dog and will often result in the owner being rather dizzy. It works best on young pups as it is virtually painless. People often use 'Prong collars' or other devices such as 'Haltis' to discourage and teach the dog how to walk nicely. Never ever use a traditional halter as it only encourages the dog to pull more (think sled dog). However, the Sense-ation, Sense-ible and Easy Walk harnesses are designed to lessen pulling and work very well. == House Training == {{sectstub}} == Crating == Crating is the practice of keeping a puppy or dog in a kennel when you are not at home and at night. This provides a safe place for the dog and keeps them from being destructive when unsupervised. This is an excellent way to housebreak a new dog. ==Basic Commands== Here are a few commands that almost every dog should respond to: *'''Come''': This command, also referred to as the '''recall''', is crucial. If the dog won't come when called, it is not an obedient dog. One method for training begins by allowing the dog to wander out on a long leash or line, then calling it by name and the command '''Come'''. This method might require a quick, light tug on the leash to get the dog moving when first teaching this command. Like all commands, it is successful only if the dog is rewarded when it completes the command and only if the practice is repeated&mdash;under different circumstances and distances and gradually removing the controls; until the dog performs flawlessly. Another good way to train them without reinforcement is to praise them while afar. They will hear this and come to you. Then, grant them more "good dog!" and such. *'''Sit''': This command is also crucial. Sitting dogs are under the handler's direct control. It is common to precede other commands, such as the '''Stay''' command, with a sit command. One method for training uses a treat held in front of the dog's nose and passed back over its head, forcing the dog to sit. '''Sit''' and '''Stay''' are used in conjunction with many other commands. *'''Stay''': This command gives peace of mind. An owner can park her dog while doing something else. One method of training involves placing the dog in a sit or a down position, then telling it to stay while stepping away from the dog. If the dog stays, the handler rewards it while it is still in the position. Indoors, use this command to park your dog under a favorite table or bench. *'''Lie down''' or '''down''': this command allows even greater control than sitting. One training method uses a treat drawn forward and down across the dog's face, forcing it to lie down to get at it. Since even people without dogs are familiar with this command and use it when dogs are bothering them, the better the dog is at it, the better it can get along with strangers and visitors. But don't get discouraged if the dog refuses or is reluctant to drop into position. The Down is a submissive position and often a dominant dog will refuse to give in. *'''Go to bed''' or '''get in''': Directs the dog to go to its bed or its crate and to remain there until released. The dog has freedom of movement in that location to stand up, turn around, or lie down, unlike when placed in a '''Stay'''. Useful to keep a dog out from underfoot and safe in a busy or complicated situation. Not a necessary command as the dog is taught to 'stay' already while in Down or Sit. Useful for Stand stays though. *'''Drop''' or '''drop it''': Dogs pick up all sorts of things, some of which they shouldn't have. A dog that drops anything on command, no matter how attractive (which to a dog can be rotten and smelly), is a dog under control that the owner can prevent from eating dangerous items or from destroying valued personal property. *'''Leave it''': An adjunct to '''Drop''', directing the dog to not touch an item. Also useful before the dog has picked anything up. One method of training involves leaving a treat on the ground and walking the dog past it without allowing the dog to pick it up. '''Leave it''' is also used in conjunction with '''Take it'''. *'''Take it''': The dog leaves a desired object, such as a toy or treat, untouched until given this command. This can protect an owner's, visitor's, or child's fingers. *'''Heel''', '''Close''', '''By me''': The dog walks with its head directly next to the handler's leg and does not deviate until released. One method of training accompanies the command with a slap to the thigh indicating where the handler wants the dog's head. *'''Okay''', '''Free''', '''Break''', or '''Release''': Releases the dog from '''Stay''', '''Heel''', '''Sit''', and so forth. Also a general release to play. A clicker acts as a release. The specific command word is not important, although the preceding list covers some of the more common words. Short, clear words that are easily understood by other humans are generally recommended; that way, people will understand what a handler is telling his dog to do and other handlers have a good chance of controlling someone else's dog if necessary. In fact, dogs can learn commands in any language or other communications medium, including whistles, mouth sounds, hand gestures, and so forth. == Less Common Commands == While dogs can be trained far beyond these rudiments, a dog that obeys these commands will be a pleasure to keep and take out. Off-leash obedience is the hallmark of a well-trained dog. There are a few commands that many domestic dogs learn, but that are not part of the basic repertoire. *'''Stop''' – a dog that will simply stop whatever it is doing and lie down on command no matter how far it is from its keeper is a dog that can be taken anywhere. Some handlers use the German word '''''Platz''''' (related to "place", i.e. stay in position) for this action. (Useful if your dog is in danger, or headed for some trouble. I.e., your dog is about to get run over by a car. He/she hears "Stop!" and drops and you can be sure it will not be hit. Much faster response than a "Come" command.) *'''Back up''' – keepers of large dogs or dogs with a reputation for aggressiveness can make strangers more comfortable by teaching the dog to back up on command. (Also useful if you are carrying a large box or something and the dog's in your way.) *'''Growl''' – the inverse of backing up. Some owners teach non-aggressive dogs to growl on a subtle command – not the word ''growl'', usually a small hand gesture – as a way of letting strangers know that you and your dog value being left alone. *'''Steady''' – keep near by. The dog can walk free, but not dash off. Train to this command with a long leash, calling out '''Steady''' when the leash is taut. Continue off leash. *'''Stand''' – dog stands still. Train from lying-down position by lifting under belly while repeating command. Useful for grooming. Many dogs are groomed frequently and need to stand quietly during the process. *'''Speak''' – for amusement or showing off, a dog may be trained to bark on command. *'''Chase Recall''' – *'''Paw, or Give Paw''' – Pretty much for showing off, a dog may be trained to give you a "handshake". (Though it's also very useful if the dog needs to get their nails clipped or they have an injury.) *'''Shake''' – Very useful after baths, or walks in snow or rain. *'''Roll Over''' – *'''Jump''' – *'''Calm''' – tells the dog to stop growling and/or playing roughly. Similar to '''Back Up'''. == Games == [[File:A-Test-of-Canine-Olfactory-Capacity-Comparing-Various-Dog-Breeds-and-Wolves-in-a-Natural-Detection-pone.0154087.s003.ogv|thumb]] Games can be fun for both the dog and the owner. Here are some games that can be played with a dog: *'''Fetch''' – This is a game where the owner throws out an object and the dog retrieves it and gives it back to the owner. It can be played with a small ball like a tennis ball, a frisbee, a stick, or any small light object that is easy to throw and easy for the dog to pick up and carry. Large balls can also be used. *'''Hide and Seek''' – You hide and your dog seeks. It is more difficult but worth attempting to make your dog hide while you seek. *'''Tug-of-War''' – It should first be noted, that some (perhaps most) experts state that this game can teach or instil aggressive behavior in your dog. However, most dogs love playing 'Tug-of-War,' and if vigorously participated in by the owner, will allow the dog, especially a younger dog, to use a lot of its extra energy. One rule of the thumb is that you decide when the game ends and you always win. Never let your dog win even if it means pinching your dog's lips against it's teeth to get it to let go. A 'drop it' command is very useful for this. == Problem Behavior == ====Chewing==== One of the causes of destructive chewing behavior in younger dogs, as with children, is 'teething.' A good suggestion, that will allow your dog to relieve it's discomfort, without destroying your home, uses only a used, but clean hand, dish, or other small towel. Soak the towel in clean drinking water. Wring out the excess, until the towel no longer drips. Tie the towel in a knot, and place in the freezer (you may want to place the towel in a freezer bag to protect other items). Once frozen it can be given to the dog as a chew toy. A more expensive but better way is to purchase toys for your dog. The most popular amongst chewers is the Kong toy. Stuffable and challenging to even the most seasoned of veterans. Squeaky toys are noisy but fun to the dog as it mimics an animal that the dog has attacked. Dogs are often observed 'pouncing' on these. ====Jumping up==== First you have to decide if you want to allow your dog to jump up on people or not. Then you need to be consistent in enforcing the rules. Being consistent is the important thing to help your dog learn what is acceptable behavior. Even if you decide it's okay, you may encounter other people who don't like it at all. NOT jumping on people is generally considered good doggie manners. Once you've made the decision that it will not be allowed you have to train your dog to understand what the rules are. To teach a dog not to jump up on you, simply turn your back on the dog when he jumps up. The dog wants your attention. When you turn away from him, you give him the message that jumping up on you will not earn your attention. After a short time (a few seconds) of having you back to the dog, turn back to him and give him another chance to keep his feet on the ground. If he does stay down, praise or reward him for it. He may well try to jump up again then, because he hasn't yet learned what is getting him the praise and what is making you go away. But the dog will figure it out. Most dogs catch on quickly, after just a few times of ignoring him. But remember, it will take a while for your dog to really learn what is expected. So, don't be surprised if the next time he greets you he jumps up. Just be consistent in letting him know it's not acceptable. Keep the emotion out of it. You don't need to scold the dog or correct him. The fact that he is not getting the desired result from jumping on you will be self correcting to him. You should also ask your visitors not to encourage jumping up on people. You can explain to them that they should turn their back on your dog if he attempts to jump up on them. A good alternative to permitting a dog to jump up on people is to teach him to sit when greeting people. Only praise and reward your dog when he is sitting. Turn away if he jumps up, as described above. He will learn to offer sitting to get the attention he seeks. ====Barking==== ====Scratching on doors==== ====Begging==== Don't reward your dog for begging. Dogs learn to beg quickly if you drop food even just a few times and even if you dropped the food by accident. Teach it to lay down out of the way while you are eating or cooking. Crating or a stuffed Kong is also recommended. If you can't prevent the dog from getting the food (this is usually the case when small children have the food) it is best to remove the dog from the room while eating. A well timed correction is also another way to deter Begging forever. ====Chasing Other Small Animals==== Everyone has heard stories about the dog who ate the gerbil, hamster, or even human baby. Try not to let this happen. Correct the dog (via training collar or voice) for attempting to even sniff the animal. It will soon learn to ignore it. ====Aggression==== ====Submissiveness==== ====Stealing Food==== Once the dog learns it can steal food, it's hard to break it out of the habit. A good way is also corrections, teaching the Leave It and anticipating the dog's action and reacting (verbal correction, taking the food away and turning the dog away, etc.). ====Getting in the Trash==== There are two situations to consider 1) dog gets into trash when you are present (supervising) It will be helpful to teach your dog a "Leave It" command. But start by teaching the command in a more controlled situation with a single piece of food. 2) dog gets into trash when you are NOT there to supervise Dogs are dogs, they get into trash if it's left out for them when they are unsupervised. Put the trash somewhere where your dog cannot get to it. Or get a trash can that your dog cannot get open. ====Digging==== Best way to avoid this is to occupy the dog's time. Training, toys and walks are excellent ways. You can also use [[Cookbook:Chili Powder|chili powder]]<ref>[http://www.djournal.com/lifestyle/home-gardening/master-gardener-dogs-can-create-challenges-in-landscape/article_fcae52d0-9474-5586-bbca-c8f1b2b6c29e.html "The Chili Powder Method" ''Mississippi Street Journal'']</ref> to cover up the digging spot. ==External Links== {{BookCat}} <references /> 9mthk3sp9r9cn1ojmlrw75h19d2rvr0 2 88763 4634183 4088821 2026-05-04T19:56:42Z Koavf 16549 {{DISPLAYTITLE:User:<span style="color:grey">''ko'''a'''</span><span style="color:black">v</span><span style="color:grey">f''</span>}} 4634183 wikitext text/x-wiki {{#babel:en|es-2|de-1|pt-1}} You're much more likely to find me on [[w:User:Koavf|Wikipedia]]. Reviewer since 2012-12-01T20:30:12. ==My contributions== *[[Annotations to The Autobiography of a Catholic Anarchist|Annotations to ''The Autobiography of a Catholic Anarchist'']] *[[:{{BOOKCATEGORY|Annotations to The Autobiography of a Catholic Anarchist}}]] *[[:{{SUBJECTCATEGORY|Christianity}}]] *[[:{{BOOKCATEGORY|Human Nature: Catholic Thought and the Sciences}}]] *[[:{{SUBJECTCATEGORY|Anarchism}}]] *[[Module:Check isxn]] *[[Module:Check isxn/doc]] *[[Template:ISBN]] *[[Template:ISBN/doc]] ;''Social Statistics'' *[[:{{BOOKCATEGORY|Social Statistics}}]] *[[Social Statistics]] {{-}} {{User:Koavf/Template:Wiki}} {{DEFAULTSORT:Koavf}} {{DISPLAYTITLE:User:<span style="color:grey">''ko'''a'''</span><span style="color:black">v</span><span style="color:grey">f''</span>}} [[Category:Users in the United States]] 25fmk2g6gouyie72ywejsqn7koizh48 4 112405 4634221 4633797 2026-05-05T06:04:07Z Fundingpipsreferralcode 3581340 /* What is Funding Pips Referral Code : 2A40D477 */ new section 4634221 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:CHAT|WB:RR/G|WB:GENERAL}} {{TOC left|limit=3}} {{User:MiszaBot/config |archive = Wikibooks:Reading room/Archives/%(year)d/%(monthname)s |algo = old(60d) |counter = 1 |minthreadstoarchive = 1 |minthreadsleft = 1 |key = 7a0ac23cf8049e4d9ff70cabb5649d1a }} Welcome to the '''General reading room'''. On this page, Wikibookians are free to talk about the Wikibooks project in general. For proposals for improving Wikibooks, see the [[../Proposals/]] reading room. {{clear}} [[Category:Reading room]] == Upcoming deployment of CampaignEvents extension to Wikibooks == <section begin="message"/> Hello everyone, We are writing to inform you that the [[mw:Help:Extension:CampaignEvents|CampaignEvents extension]] will be deployed to all Wikibooks projects during the week of '''23 March 2026'''. This follows last year’s broader rollout across Wikimedia projects. We realized that Wikibooks was not included at the time, and we’re now addressing that to ensure consistency across all communities. The CampaignEvents extension provides tools to support event and campaign organization on-wiki, including features like on-wiki event registration and collaboration lists(global event list). We welcome any questions, feedback, or concerns you may have. We are also happy to support anyone interested in trying out the tools. ''Apologies if this message is not in your preferred language. If you’re able to help translate it for your community, please feel free to do so.'' <section end="message"/> <bdi lang="en" dir="ltr">[[User:Udehb-WMF|Udehb-WMF]] ([[User talk:Udehb-WMF|discuss]]) 18:22, 19 March 2026 (UTC)</bdi> <!-- Message sent by User:Udehb-WMF@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Udehb-WMF/sandbox/MM_target&oldid=30284073 --> == Regarding the project's FlaggedRevs extension == Hello, everyone. I want to discuss with the community about the use of this project's FlaggedRevs (flagged revisions) extension, which was deployed many years ago (and configured recently). === Many unreviewed edits, and edit quality options === According to [[Special:PendingChanges]], there are almost 4000 unreviewed edits (per the standard FlaggedRevs configuration). In addition, on the edit review interface when evaluating a diff, there are three radio buttons that determine the quality of the edit (minimal, average, good). Do we have to utilize these buttons if the quality of the edit or the book matters, according to [[WB:REVIEW]]? This proposal is to whether discontinue the edit rating buttons or not. One way to reduce such a large amount of unreviewed edits is to set the following to <code>true</code>: * <code>wgFlaggedRevsProtection</code> (pending changes protection, to be used on Wikijunior pages; this might negate the need to show the stable version by default) * (optional) <code>wgSimpleFlaggedRevsUI</code> (simpler, icon-based UI on the edit review interface) We should also include the following configuration (partially based from English Wikipedia), if this proposal passes: <syntaxhighlight lang="php"> elseif ( $wgDBname == 'enwikibooks' ) { // Limited to the main, Cookbook, and Wikijunior namespaces (T408110) $wgFlaggedRevsNamespaces = [ NS_MAIN, 102, 110 ]; # We have only one tag with one level $wgFlaggedRevsTags = [ 'status' => [ 'levels' => 1 ] ]; # Restrict autoconfirmed to flagging semi-protected $wgFlaggedRevsTagsRestrictions = [ 'status' => [ 'review' => 1, 'autoreview' => 1 ], ]; # Restriction levels for auto-review/review rights $wgFlaggedRevsRestrictionLevels = [ 'autoreview' ]; # Remove 'validate' from reviewers $wgGroupPermissions['reviewer']['validate'] = false; # Group permissions for sysops $wgGroupPermissions['sysop']['review'] = true; $wgGroupPermissions['sysop']['stablesettings'] = true; # Allow sysops to add and remove the 'reviewer' group $wgAddGroups['sysop'][] = 'reviewer'; $wgRemoveGroups['sysop'][] = 'reviewer'; # Remove the 'editor' user group unset( $wgGroupPermissions['editor'] ); } </syntaxhighlight> === Inactive reviewers === After conducting an audit of over 1000 reviewers, most, if not many of them are completely inactive. === User group changes for reviewers === The reviewer user group is known to the software as <code>editor</code>, which might sound misleading (the actual [[MediaWiki:Group-editor/qqq|/qqq definition]] is "Editors"). To fix that, we might have to consider switching to <code>reviewer</code> and unset <code>editor</code>. I am also not sure whether administrators should have the <code>validate</code> user right, since <code>reviewer</code> has it on by default (but it is currently disabled). On the above configuration I proposed, administrators (and users in the <code>reviewer</code> user group) would no longer have <code>validate</code>. === Page patrolling === Currently, only administrators can mark new pages as patrolled (<code>patrol</code>) by using the MediaWiki page patrol software, but clicking on "Accept revision" (via FlaggedRevs) would also mark the page as patrolled, in question. I believe that using FlaggedRevs to patrol new pages is redundant, given that we might not want to use one or the other. If we are considering on switching to pending changes, we should also allow reviewers to mark new pages as patrolled, as they are trusted to have the <code>autopatrol</code> right in addition to administrators and autoreviewed users. Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:05, 21 March 2026 (UTC) :I agree on replacing <code>editor</code> with <code>reviewer</code> to avoid confusion. Reviewers don't need to have patrol permissions as a reviewed page would be patrolled as well. I don't think people will use it much as a page or edit being reviewed already means that it has been checked by someone else. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:00, 22 March 2026 (UTC) ::When I said that reviewers would have <code>patrol</code>, they can review new pages that other users created, but not any new pages they create themselves. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:16, 22 March 2026 (UTC) :::How can that be the case if they have <code>autopatrol</code>? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:26, 22 March 2026 (UTC) ::::I will give you an example. On the English Wikiquote, there are two user groups that have <code>autopatrol</code>: autopatrollers and patrollers. Autopatrollers have their page creations marked as patrolled by the software, while patrollers (whilst also having their page creations marked as patrolled) can mark new pages as patrolled (in addition to administrators). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 22 March 2026 (UTC) :::::But what is the point of giving reviewers <code>patrol</code> if we are already using FlaggedRevs? I think that we won't need patrol because we already have reviewing, and patrol only seems to be a confirmation that the page is up to policy from what I have seen, so giving them reviewers to mark pages as patrolled seems pointless to me when we already have FlaggedRevs. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 19:06, 22 March 2026 (UTC) ::::::I understand, but my proposal was to convert FlaggedRevs into a protection-like mechanism which would be used alongside page protection; it might turn off FlaggedRevs's ability to patrol new pages for reviewers, hence why I suggested this above. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:30, 22 March 2026 (UTC) ::::::: @[[User:Kingofnuthin|Kingofnuthin]] I will summarize what you said from above: :::::::* You agree about the reviewer user group to be moved from <code>editor</code> to <code>reviewer</code> to avoid confusion (technically). :::::::* However, you probably disagree about allowing reviewers to patrol new pages ''and'' having their page creations automatically marked as patrolled, because FlaggedRevs can do all of this, and <code>$wgUseNPPatrol</code> might seem to be redundant. ::::::: A compromise about your disagreement is that we might have to consider removing <code>autopatrol</code> and/or <code>patrol</code> from our existing user groups, similar to [[phab:T423461]]. ::::::: I started this because in addition to that, one of my concerns was the extreme backlog of unreviewed edits and pages [4000!]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:31, 19 April 2026 (UTC) :I may be missing some things here, so let me know if I haven't answered any points here: :# I don't think we currently need to have the review status indicate the quality of the edit (i.e. minimal, average, good). I don't think this is used at all anymore. :# I think it makes sense to reassign the reviewer user group to <code>editor</code>. I always like clarity in language. :# Are you saying that pages marked as reviewed are currently also classed as patrolled? If that's the case, I think we should not have reviewed pages automatically classed as patrolled, and we should keep reviewing and patrolling separate. :I'll note that honestly don't know much about patrolling, since I've never engaged with it—I have only ever referenced the reviewing system. If there is a significant functional difference, I would love to know it. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:00, 23 March 2026 (UTC) ::When someone clicks "Accept revision" on an unreviewed page, it is listed under [[Special:Log/review]]; if an admin marks a page as patrolled with "Mark this page as patrolled", it will show up under [[Special:Log/patrol]], which is not really logged much compared to the former log (review). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:12, 23 March 2026 (UTC) :I agree to your thoughts about the <code>editor</code> group and edit quality ratings, but I don't understand what this proposal changes for FlaggedRevs, since I don't have much technical knowledge. Can you explain what the proposal changes here, how are we going to convert FlaggedRevs into a "protection-like mechanism"? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:24, 23 March 2026 (UTC) ::The proposal of changing FlaggedRevs into a protection-like feature (pending changes) is when an editor (unregistered/one not holding autoreviewer, reviewer, or administrator permissions) makes an edit, but their edit will be hidden from the public until it is approved by a reviewer or an administrator, and it will solely apply to Wikijunior pages. The configuration above is similar to what English Wikipedia uses. {{quote|::I think it makes sense to reassign the reviewer user group to <code>editor</code>.}} ::@[[User:Kittycataclysm|Kittycataclysm]]: I believe you might have misunderstood. What I meant is that <code>(editor)</code> will be changed to <code>(reviewer)</code> to avoid confusion, but I plan to remove <code>editor</code> from all inactive reviewers, then do the same for recently active reviewers. However, given that there are a lot of reviewers, a script will possibly do all the work (under {{no ping|Maintenance script}} or similar). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:29, 23 March 2026 (UTC) :::Gotcha! I can't currently foresee an issue with this —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:09, 30 March 2026 (UTC) :'''Re FlaggedRevs generally: '''The [[mw:Extension:FlaggedRevs|Mediawiki page of the extension]] says it is not being maintained and not recommended for production use. We should consider whether we need this extension at all. :What is the actual policy justification for having FlaggedRevs? :[[Help:Tracking_changes#Reviewing_pages]] says it's "our primary counter-vandalism tool". I don't know if it is that: it doesn't prevent vandalism or reduce exposure to vandalism (as with stable versions). The "counter-vandalism" bit comes from human editors looking at the edits, identifying vandalism, and reverting. FlaggedRevs isn't necessary for that. Maybe it makes it a little easier to spot edits in recent changes from new editors that may need a little more help (wikicode etc, not just spam), but can that be achieved just with the patrolled edits functionality? :If we still want something like FlaggedRevs, as an anti-vandalism tool or for draft control, then Mediawiki has a [[mw:Content approval extensions|list of alternatives]] that may be more suited and better maintained. :'''Re minimal/average/good specifically:''' I agree that we don't need the three categories. I thought I read somewhere that these were intended to show the quality of the REVIEW not of the page? That is, a "minimal" review is "I checked there was no obvious vandalism" and a "good" review was "I've thoroughly fact-checked everything". [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 11:34, 5 April 2026 (UTC) :: This was enabled back in 2008, which resulted in [[Wikibooks:New page patrol]] currently being obsolete. To be honest, I would keep FlaggedRevs, but I was proposing to change it to pending changes protection, similar to how Wikipedia utilizes it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:04, 19 April 2026 (UTC) :Pinging <span class="template-ping">@[[:User:JJPMaster|JJPMaster]]:</span> and <span class="template-ping">@[[:User:Kittycataclysm|Kittycataclysm]]:</span> for additional input. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) <span style="font-size: smaller;" class="autosigned">—Preceding [[w:Wikipedia:Signatures|undated]] comment added 22:29, 22 March 2026.</span><!--Template:Undated--> == Global ban for Faster than Thunder == * {{user|Faster than Thunder}} Hello, this message is to notify that [[User:Faster than Thunder|Faster than Thunder]] has been nominated for a global ban at [[m:Requests for comment/Global ban for Faster than Thunder]]. You are receiving this notification as required per the [[m:global ban|global ban]] policy as they have made at least 1 edit on this wiki. Thanks, --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 01:52, 22 March 2026 (UTC) == Upcoming Wikimedia Café meetup regarding the [[:meta:Wikimedia Foundation Annual Plan/2026-2027|the 2026-2027 Wikimedia Foundation Annual Plan]] == {{tmbox | image = [[File:Wikimedia Café logo in plain SVG format.svg|45px]] | type=notice | text = Hello! There will be a '''[[:meta:Wikimedia Café|Wikimedia Café]]''' meetup on '''Saturday, 11 April 2026 at 14:00 UTC''', focusing on the [[:meta:Wikimedia Foundation Annual Plan/2026-2027|the 2026-2027 Wikimedia Foundation Annual Plan]]. The featured guests will be {{Noping|KStineRowe (WMF)|label1=Kelsi Stine-Rowe}} (senior manager, [[:meta:Movement Communications|Movement Communications]], Wikimedia Foundation), and {{Noping|Samwalton9 (WMF)|label1=Sam Walton}} (senior product manager, [[:mw:Moderator Tools|Moderator Tools]], Wikimedia Foundation). <br /> In addition to this Café session, [[:meta:Wikimedia Foundation Annual Plan/2026-2027/Collaboration|several additional meetings regarding the Annual Plan are listed on the Collaboration page]], and you may participate on the [[:meta:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. <br /> This Café meetup will be approximately two hours long. Attendees may choose to attend only for a part. Please see the Café page for more information, including [[:meta:Wikimedia Café#Signups for the April 2026 session|how to register]]. <br /> [[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]] }} <span style="white-space:nowrap;">[[User:Pine|<span style="color:#01796f; text-shadow:#00BFFF 0 0 1.0em">↠Pine</span>]] [[User talk:Pine|<span style="color:DeepSkyBlue">(<b style="color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em">✉</b>)</span>]]</span> 05:23, 29 March 2026 (UTC) == Regarding copyright of recipes found on online cooking forums == What is the copyright situation regarding cooking recipes found on online recipe books with recipes made by other people? I ask this because I want to add/translate recipes from 下厨房 (xià chúfáng) for Chinese recipes, and while I was intending to add the original writer of the recipe with the translation I still want to ask for clarification. [[User:Fukukitaru|Fukukitaru]] ([[User talk:Fukukitaru|discuss]] • [[Special:Contributions/Fukukitaru|contribs]]) 19:06, 30 March 2026 (UTC) :Recipes are in principle not copyright-able, as they are just facts. When someone includes descriptive text or anything that elaborates on the basic ingredients and steps, that is copyright-able. I am not a lawyer or legal scholar and cannot give legal advice. See (e.g.) https://www.copyrightlaws.com/copyright-protection-recipes/ —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:16, 30 March 2026 (UTC) ::In that case, would simplifying ingredients and methods to where they are simple yet can still be understood be sufficient for said recipes? [[User:Fukukitaru|Fukukitaru]] ([[User talk:Fukukitaru|discuss]] • [[Special:Contributions/Fukukitaru|contribs]]) 19:23, 30 March 2026 (UTC) :::Yes, you can add a recipe here as long as the instructions and text are not too overlapping with the copyrighted original. As the linked page says, the '''ideas''' behind the ingredient list and steps to prepare a given food item are not currently copyrightable, but the way you write the ideas may be copyrightable. You should also cite where you took the recipe from so we can trace its origins. I personally recommend only adding recipes that you have successfully made so we don't become a massive repository of potentially low-quality or untested recipes—I only add recipes once I have made them successfully. Let me know if you have any more questions about the Cookbook! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:06, 30 March 2026 (UTC) ::::To build up on this, if you want to understand what is copyright-able and what is not, the "[[:w:en:Idea–expression distinction|idea versus expression]]" distinction. You cannot own the idea of "Boy meets girl, boy loses girl, boy and girl commit suicide" but you can copyright a specific version of ''Romeo and Juliet'' with your own innovative ideas. And, for that matter, this is context-specific, but if you can understand the distinction, it can help with future questions about "could this be protected by copyright?", which can be a subtle one. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:50, 30 March 2026 (UTC) :::::To further build up on this, there's something called the merger doctrine (see ''[[w:Baker v. Selden|Baker v. Selden]]''). This is why you can't copyright drawings of [[w:Structural formula|structural formulas]]. This doctrine means that if there's only one or a handful of ways to express an idea, then any such expression cannot be copyrighted, since copyrighting that expression would essentially be copyrighting the idea itself. This comes in a lot with recipes. I very likely can't copyright this list (from [[Cookbook:Cornmeal Pancakes (Arepa)]]: :::::* 2.4 cups corn flour :::::* 1.2 tsp salt :::::* 0.6 cup grated white cheese :::::* 2.4 cups cool water :::::Since there's essentially only one way to express the idea of that combination of ingredients. However, if I say: :::::* 2.4 cups corn flour: for this, I strongly recommend Harina P.A.N., because my grandma always used to make me arepas from that stuff every day, and it was delicious. :::::That is copyrightable. At that point, I cease to merely be expressing the idea of a food item with those four ingredients, and add a minimum degree of creativity. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:02, 31 March 2026 (UTC) ::::::And to build on all <em>that</em>, even if individual pieces of information are in the public domain (or are fair use), the <em>arrangement</em> of them can be copyrighted. This is why even if ''Bartlett's Quotations'' only had public domain material, the act of selectively editing and positioning them thematically for the user's benefit could constitute a sufficiently original work. So we could copy the material from a bunch of recipes, but could run a foul of copyright issues if we arranged and sorted them in some kind of manner that replicated someone else's original work. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 02:28, 31 March 2026 (UTC) == Style Guidelines for Advanced Points == Is there a general style guideline to refer the reader to advanced information, while the main text gives the short-answer version? For example, how would I specify that in practical applications, A is true, but if you use the theory you see that A is not quite true, or has caveats, or similar?-- [[User:Iain marcuson|Iain marcuson]] ([[User talk:Iain marcuson|discuss]] • [[Special:Contributions/Iain marcuson|contribs]]) 17:50, 22 April 2026 (UTC) == Request: Help adding Objective Projection writing guide (filter blocked) == Hello, I am Levent Bulut (ORCID: 0009-0007-7500-2261), author of the Objective Projection methodology. I am trying to contribute a practical writing guide to Wikibooks under CC BY-SA 4.0. Book title: "Objective Projection: Why the Brain Never Forgets Some Stories" The automated filter blocked my edits due to external links and content volume. I have already created the page with the introduction and contents, but could not add the chapters. The Turkish version of the same book is already live on Wikibooks: https://tr.wikibooks.org/wiki/Nesnel_%C4%B0zd%C3%BC%C5%9F%C3%BCm:_Beyin_Neden_Baz%C4%B1_Hikayeleri_Unutmuyor%3F This is not a new theory — it is an instructional guide teaching a published methodology documented in DOI-registered publications: https://doi.org/10.5281/zenodo.18689179 Open license declaration on my site: https://leventbulut.com/acik-lisans-bildirimi-wikibooks/ All content is my own work, written for Wikibooks, under CC BY-SA 4.0. Could an experienced editor help add the remaining chapters, or whitelist my account so the filter does not block future edits? Thank you. Levent Bulut | leventbulut.com [[User:LeventBulut|LeventBulut]] ([[User talk:LeventBulut|discuss]] • [[Special:Contributions/LeventBulut|contribs]]) 21:28, 24 April 2026 (UTC) : @[[User:LeventBulut|LeventBulut]] This happened because you added too much content when creating the book. Also, when reporting false positives from an edit filter, please report on [[Wikibooks:Edit filter/False positives]]. Thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:03, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:57, 26 April 2026 (UTC)</bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == After WikiNews shuts down....? == Can people try and write news articles here? Thank you! [[User:BigKrow|BigKrow]] ([[User talk:BigKrow|discuss]] • [[Special:Contributions/BigKrow|contribs]]) 22:30, 1 May 2026 (UTC) :Thanks for asking. You have a similar thread at our sister project Wikiversity and I am the equivalent of an admin there (we have a "curators" and "custodians" that are similar to admins on other projects). I'm not an admin here, but speaking as someone who has generally contributed here, writing news articles would not be appropriate. It would be great to write a textbook on [[journalism]]: we could use a great guide for ethics, finding sources, asking questions, objectivity and neutrality, etc. Unlike on Wikiversity, where the learning materials can be virtually anything, this project is specifically for a textbook/guide/manual, so writing news articles and posting them here is not really appropriate, but you could have a few example articles that you write for the purpose of having a textbook. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:46, 1 May 2026 (UTC) :: Heads up, a wiki was created: <span class="plainlinks">[https://news.wikioasis.org/wiki/Main_Page news.wikioasis.org]</span>. @[[User:Koavf|Koavf]]; I was temporarily granted some user rights to manage the wiki's setup and migration. I'll give you sysop rights since you are currently one on English Wikinews. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:11, 2 May 2026 (UTC) :::Thanks. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 02:14, 2 May 2026 (UTC) == What is Funding Pips Referral Code : 2A40D477 == Funding Pips Referral Code – 2A40D477 to unlock exclusive discounts, bonuses, and faster account approval with one of the top global prop trading firms, use this code and get 15% discount instantly. Funding Pips is a leading proprietary trading firm that empowers traders with real capital after completing a simple evaluation challenge. With no hidden rules, flexible account types, and fast payouts, it’s designed for serious traders who want to scale fast. Using the referral code 2A40D477 gives you an advantage at signup  including discounted challenge fees, priority support, and exclusive access to new trading features. [[User:Fundingpipsreferralcode|Fundingpipsreferralcode]] ([[User talk:Fundingpipsreferralcode|discuss]] • [[Special:Contributions/Fundingpipsreferralcode|contribs]]) 06:04, 5 May 2026 (UTC) dxdo18lyrew60xyp63k8qcdjfty5dbk 4634222 4634221 2026-05-05T06:08:08Z Fundingpipsreferralcode 3581340 /* What is 91 Club Invite Code : 3788222275038 */ new section 4634222 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:CHAT|WB:RR/G|WB:GENERAL}} {{TOC left|limit=3}} {{User:MiszaBot/config |archive = Wikibooks:Reading room/Archives/%(year)d/%(monthname)s |algo = old(60d) |counter = 1 |minthreadstoarchive = 1 |minthreadsleft = 1 |key = 7a0ac23cf8049e4d9ff70cabb5649d1a }} Welcome to the '''General reading room'''. On this page, Wikibookians are free to talk about the Wikibooks project in general. For proposals for improving Wikibooks, see the [[../Proposals/]] reading room. {{clear}} [[Category:Reading room]] == Upcoming deployment of CampaignEvents extension to Wikibooks == <section begin="message"/> Hello everyone, We are writing to inform you that the [[mw:Help:Extension:CampaignEvents|CampaignEvents extension]] will be deployed to all Wikibooks projects during the week of '''23 March 2026'''. This follows last year’s broader rollout across Wikimedia projects. We realized that Wikibooks was not included at the time, and we’re now addressing that to ensure consistency across all communities. The CampaignEvents extension provides tools to support event and campaign organization on-wiki, including features like on-wiki event registration and collaboration lists(global event list). We welcome any questions, feedback, or concerns you may have. We are also happy to support anyone interested in trying out the tools. ''Apologies if this message is not in your preferred language. If you’re able to help translate it for your community, please feel free to do so.'' <section end="message"/> <bdi lang="en" dir="ltr">[[User:Udehb-WMF|Udehb-WMF]] ([[User talk:Udehb-WMF|discuss]]) 18:22, 19 March 2026 (UTC)</bdi> <!-- Message sent by User:Udehb-WMF@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Udehb-WMF/sandbox/MM_target&oldid=30284073 --> == Regarding the project's FlaggedRevs extension == Hello, everyone. I want to discuss with the community about the use of this project's FlaggedRevs (flagged revisions) extension, which was deployed many years ago (and configured recently). === Many unreviewed edits, and edit quality options === According to [[Special:PendingChanges]], there are almost 4000 unreviewed edits (per the standard FlaggedRevs configuration). In addition, on the edit review interface when evaluating a diff, there are three radio buttons that determine the quality of the edit (minimal, average, good). Do we have to utilize these buttons if the quality of the edit or the book matters, according to [[WB:REVIEW]]? This proposal is to whether discontinue the edit rating buttons or not. One way to reduce such a large amount of unreviewed edits is to set the following to <code>true</code>: * <code>wgFlaggedRevsProtection</code> (pending changes protection, to be used on Wikijunior pages; this might negate the need to show the stable version by default) * (optional) <code>wgSimpleFlaggedRevsUI</code> (simpler, icon-based UI on the edit review interface) We should also include the following configuration (partially based from English Wikipedia), if this proposal passes: <syntaxhighlight lang="php"> elseif ( $wgDBname == 'enwikibooks' ) { // Limited to the main, Cookbook, and Wikijunior namespaces (T408110) $wgFlaggedRevsNamespaces = [ NS_MAIN, 102, 110 ]; # We have only one tag with one level $wgFlaggedRevsTags = [ 'status' => [ 'levels' => 1 ] ]; # Restrict autoconfirmed to flagging semi-protected $wgFlaggedRevsTagsRestrictions = [ 'status' => [ 'review' => 1, 'autoreview' => 1 ], ]; # Restriction levels for auto-review/review rights $wgFlaggedRevsRestrictionLevels = [ 'autoreview' ]; # Remove 'validate' from reviewers $wgGroupPermissions['reviewer']['validate'] = false; # Group permissions for sysops $wgGroupPermissions['sysop']['review'] = true; $wgGroupPermissions['sysop']['stablesettings'] = true; # Allow sysops to add and remove the 'reviewer' group $wgAddGroups['sysop'][] = 'reviewer'; $wgRemoveGroups['sysop'][] = 'reviewer'; # Remove the 'editor' user group unset( $wgGroupPermissions['editor'] ); } </syntaxhighlight> === Inactive reviewers === After conducting an audit of over 1000 reviewers, most, if not many of them are completely inactive. === User group changes for reviewers === The reviewer user group is known to the software as <code>editor</code>, which might sound misleading (the actual [[MediaWiki:Group-editor/qqq|/qqq definition]] is "Editors"). To fix that, we might have to consider switching to <code>reviewer</code> and unset <code>editor</code>. I am also not sure whether administrators should have the <code>validate</code> user right, since <code>reviewer</code> has it on by default (but it is currently disabled). On the above configuration I proposed, administrators (and users in the <code>reviewer</code> user group) would no longer have <code>validate</code>. === Page patrolling === Currently, only administrators can mark new pages as patrolled (<code>patrol</code>) by using the MediaWiki page patrol software, but clicking on "Accept revision" (via FlaggedRevs) would also mark the page as patrolled, in question. I believe that using FlaggedRevs to patrol new pages is redundant, given that we might not want to use one or the other. If we are considering on switching to pending changes, we should also allow reviewers to mark new pages as patrolled, as they are trusted to have the <code>autopatrol</code> right in addition to administrators and autoreviewed users. Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:05, 21 March 2026 (UTC) :I agree on replacing <code>editor</code> with <code>reviewer</code> to avoid confusion. Reviewers don't need to have patrol permissions as a reviewed page would be patrolled as well. I don't think people will use it much as a page or edit being reviewed already means that it has been checked by someone else. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:00, 22 March 2026 (UTC) ::When I said that reviewers would have <code>patrol</code>, they can review new pages that other users created, but not any new pages they create themselves. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:16, 22 March 2026 (UTC) :::How can that be the case if they have <code>autopatrol</code>? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:26, 22 March 2026 (UTC) ::::I will give you an example. On the English Wikiquote, there are two user groups that have <code>autopatrol</code>: autopatrollers and patrollers. Autopatrollers have their page creations marked as patrolled by the software, while patrollers (whilst also having their page creations marked as patrolled) can mark new pages as patrolled (in addition to administrators). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 22 March 2026 (UTC) :::::But what is the point of giving reviewers <code>patrol</code> if we are already using FlaggedRevs? I think that we won't need patrol because we already have reviewing, and patrol only seems to be a confirmation that the page is up to policy from what I have seen, so giving them reviewers to mark pages as patrolled seems pointless to me when we already have FlaggedRevs. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 19:06, 22 March 2026 (UTC) ::::::I understand, but my proposal was to convert FlaggedRevs into a protection-like mechanism which would be used alongside page protection; it might turn off FlaggedRevs's ability to patrol new pages for reviewers, hence why I suggested this above. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:30, 22 March 2026 (UTC) ::::::: @[[User:Kingofnuthin|Kingofnuthin]] I will summarize what you said from above: :::::::* You agree about the reviewer user group to be moved from <code>editor</code> to <code>reviewer</code> to avoid confusion (technically). :::::::* However, you probably disagree about allowing reviewers to patrol new pages ''and'' having their page creations automatically marked as patrolled, because FlaggedRevs can do all of this, and <code>$wgUseNPPatrol</code> might seem to be redundant. ::::::: A compromise about your disagreement is that we might have to consider removing <code>autopatrol</code> and/or <code>patrol</code> from our existing user groups, similar to [[phab:T423461]]. ::::::: I started this because in addition to that, one of my concerns was the extreme backlog of unreviewed edits and pages [4000!]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:31, 19 April 2026 (UTC) :I may be missing some things here, so let me know if I haven't answered any points here: :# I don't think we currently need to have the review status indicate the quality of the edit (i.e. minimal, average, good). I don't think this is used at all anymore. :# I think it makes sense to reassign the reviewer user group to <code>editor</code>. I always like clarity in language. :# Are you saying that pages marked as reviewed are currently also classed as patrolled? If that's the case, I think we should not have reviewed pages automatically classed as patrolled, and we should keep reviewing and patrolling separate. :I'll note that honestly don't know much about patrolling, since I've never engaged with it—I have only ever referenced the reviewing system. If there is a significant functional difference, I would love to know it. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:00, 23 March 2026 (UTC) ::When someone clicks "Accept revision" on an unreviewed page, it is listed under [[Special:Log/review]]; if an admin marks a page as patrolled with "Mark this page as patrolled", it will show up under [[Special:Log/patrol]], which is not really logged much compared to the former log (review). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:12, 23 March 2026 (UTC) :I agree to your thoughts about the <code>editor</code> group and edit quality ratings, but I don't understand what this proposal changes for FlaggedRevs, since I don't have much technical knowledge. Can you explain what the proposal changes here, how are we going to convert FlaggedRevs into a "protection-like mechanism"? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:24, 23 March 2026 (UTC) ::The proposal of changing FlaggedRevs into a protection-like feature (pending changes) is when an editor (unregistered/one not holding autoreviewer, reviewer, or administrator permissions) makes an edit, but their edit will be hidden from the public until it is approved by a reviewer or an administrator, and it will solely apply to Wikijunior pages. The configuration above is similar to what English Wikipedia uses. {{quote|::I think it makes sense to reassign the reviewer user group to <code>editor</code>.}} ::@[[User:Kittycataclysm|Kittycataclysm]]: I believe you might have misunderstood. What I meant is that <code>(editor)</code> will be changed to <code>(reviewer)</code> to avoid confusion, but I plan to remove <code>editor</code> from all inactive reviewers, then do the same for recently active reviewers. However, given that there are a lot of reviewers, a script will possibly do all the work (under {{no ping|Maintenance script}} or similar). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:29, 23 March 2026 (UTC) :::Gotcha! I can't currently foresee an issue with this —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:09, 30 March 2026 (UTC) :'''Re FlaggedRevs generally: '''The [[mw:Extension:FlaggedRevs|Mediawiki page of the extension]] says it is not being maintained and not recommended for production use. We should consider whether we need this extension at all. :What is the actual policy justification for having FlaggedRevs? :[[Help:Tracking_changes#Reviewing_pages]] says it's "our primary counter-vandalism tool". I don't know if it is that: it doesn't prevent vandalism or reduce exposure to vandalism (as with stable versions). The "counter-vandalism" bit comes from human editors looking at the edits, identifying vandalism, and reverting. FlaggedRevs isn't necessary for that. Maybe it makes it a little easier to spot edits in recent changes from new editors that may need a little more help (wikicode etc, not just spam), but can that be achieved just with the patrolled edits functionality? :If we still want something like FlaggedRevs, as an anti-vandalism tool or for draft control, then Mediawiki has a [[mw:Content approval extensions|list of alternatives]] that may be more suited and better maintained. :'''Re minimal/average/good specifically:''' I agree that we don't need the three categories. I thought I read somewhere that these were intended to show the quality of the REVIEW not of the page? That is, a "minimal" review is "I checked there was no obvious vandalism" and a "good" review was "I've thoroughly fact-checked everything". [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 11:34, 5 April 2026 (UTC) :: This was enabled back in 2008, which resulted in [[Wikibooks:New page patrol]] currently being obsolete. To be honest, I would keep FlaggedRevs, but I was proposing to change it to pending changes protection, similar to how Wikipedia utilizes it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:04, 19 April 2026 (UTC) :Pinging <span class="template-ping">@[[:User:JJPMaster|JJPMaster]]:</span> and <span class="template-ping">@[[:User:Kittycataclysm|Kittycataclysm]]:</span> for additional input. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) <span style="font-size: smaller;" class="autosigned">—Preceding [[w:Wikipedia:Signatures|undated]] comment added 22:29, 22 March 2026.</span><!--Template:Undated--> == Global ban for Faster than Thunder == * {{user|Faster than Thunder}} Hello, this message is to notify that [[User:Faster than Thunder|Faster than Thunder]] has been nominated for a global ban at [[m:Requests for comment/Global ban for Faster than Thunder]]. You are receiving this notification as required per the [[m:global ban|global ban]] policy as they have made at least 1 edit on this wiki. Thanks, --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 01:52, 22 March 2026 (UTC) == Upcoming Wikimedia Café meetup regarding the [[:meta:Wikimedia Foundation Annual Plan/2026-2027|the 2026-2027 Wikimedia Foundation Annual Plan]] == {{tmbox | image = [[File:Wikimedia Café logo in plain SVG format.svg|45px]] | type=notice | text = Hello! There will be a '''[[:meta:Wikimedia Café|Wikimedia Café]]''' meetup on '''Saturday, 11 April 2026 at 14:00 UTC''', focusing on the [[:meta:Wikimedia Foundation Annual Plan/2026-2027|the 2026-2027 Wikimedia Foundation Annual Plan]]. The featured guests will be {{Noping|KStineRowe (WMF)|label1=Kelsi Stine-Rowe}} (senior manager, [[:meta:Movement Communications|Movement Communications]], Wikimedia Foundation), and {{Noping|Samwalton9 (WMF)|label1=Sam Walton}} (senior product manager, [[:mw:Moderator Tools|Moderator Tools]], Wikimedia Foundation). <br /> In addition to this Café session, [[:meta:Wikimedia Foundation Annual Plan/2026-2027/Collaboration|several additional meetings regarding the Annual Plan are listed on the Collaboration page]], and you may participate on the [[:meta:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. <br /> This Café meetup will be approximately two hours long. Attendees may choose to attend only for a part. Please see the Café page for more information, including [[:meta:Wikimedia Café#Signups for the April 2026 session|how to register]]. <br /> [[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]] }} <span style="white-space:nowrap;">[[User:Pine|<span style="color:#01796f; text-shadow:#00BFFF 0 0 1.0em">↠Pine</span>]] [[User talk:Pine|<span style="color:DeepSkyBlue">(<b style="color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em">✉</b>)</span>]]</span> 05:23, 29 March 2026 (UTC) == Regarding copyright of recipes found on online cooking forums == What is the copyright situation regarding cooking recipes found on online recipe books with recipes made by other people? I ask this because I want to add/translate recipes from 下厨房 (xià chúfáng) for Chinese recipes, and while I was intending to add the original writer of the recipe with the translation I still want to ask for clarification. [[User:Fukukitaru|Fukukitaru]] ([[User talk:Fukukitaru|discuss]] • [[Special:Contributions/Fukukitaru|contribs]]) 19:06, 30 March 2026 (UTC) :Recipes are in principle not copyright-able, as they are just facts. When someone includes descriptive text or anything that elaborates on the basic ingredients and steps, that is copyright-able. I am not a lawyer or legal scholar and cannot give legal advice. See (e.g.) https://www.copyrightlaws.com/copyright-protection-recipes/ —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:16, 30 March 2026 (UTC) ::In that case, would simplifying ingredients and methods to where they are simple yet can still be understood be sufficient for said recipes? [[User:Fukukitaru|Fukukitaru]] ([[User talk:Fukukitaru|discuss]] • [[Special:Contributions/Fukukitaru|contribs]]) 19:23, 30 March 2026 (UTC) :::Yes, you can add a recipe here as long as the instructions and text are not too overlapping with the copyrighted original. As the linked page says, the '''ideas''' behind the ingredient list and steps to prepare a given food item are not currently copyrightable, but the way you write the ideas may be copyrightable. You should also cite where you took the recipe from so we can trace its origins. I personally recommend only adding recipes that you have successfully made so we don't become a massive repository of potentially low-quality or untested recipes—I only add recipes once I have made them successfully. Let me know if you have any more questions about the Cookbook! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:06, 30 March 2026 (UTC) ::::To build up on this, if you want to understand what is copyright-able and what is not, the "[[:w:en:Idea–expression distinction|idea versus expression]]" distinction. You cannot own the idea of "Boy meets girl, boy loses girl, boy and girl commit suicide" but you can copyright a specific version of ''Romeo and Juliet'' with your own innovative ideas. And, for that matter, this is context-specific, but if you can understand the distinction, it can help with future questions about "could this be protected by copyright?", which can be a subtle one. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:50, 30 March 2026 (UTC) :::::To further build up on this, there's something called the merger doctrine (see ''[[w:Baker v. Selden|Baker v. Selden]]''). This is why you can't copyright drawings of [[w:Structural formula|structural formulas]]. This doctrine means that if there's only one or a handful of ways to express an idea, then any such expression cannot be copyrighted, since copyrighting that expression would essentially be copyrighting the idea itself. This comes in a lot with recipes. I very likely can't copyright this list (from [[Cookbook:Cornmeal Pancakes (Arepa)]]: :::::* 2.4 cups corn flour :::::* 1.2 tsp salt :::::* 0.6 cup grated white cheese :::::* 2.4 cups cool water :::::Since there's essentially only one way to express the idea of that combination of ingredients. However, if I say: :::::* 2.4 cups corn flour: for this, I strongly recommend Harina P.A.N., because my grandma always used to make me arepas from that stuff every day, and it was delicious. :::::That is copyrightable. At that point, I cease to merely be expressing the idea of a food item with those four ingredients, and add a minimum degree of creativity. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:02, 31 March 2026 (UTC) ::::::And to build on all <em>that</em>, even if individual pieces of information are in the public domain (or are fair use), the <em>arrangement</em> of them can be copyrighted. This is why even if ''Bartlett's Quotations'' only had public domain material, the act of selectively editing and positioning them thematically for the user's benefit could constitute a sufficiently original work. So we could copy the material from a bunch of recipes, but could run a foul of copyright issues if we arranged and sorted them in some kind of manner that replicated someone else's original work. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 02:28, 31 March 2026 (UTC) == Style Guidelines for Advanced Points == Is there a general style guideline to refer the reader to advanced information, while the main text gives the short-answer version? For example, how would I specify that in practical applications, A is true, but if you use the theory you see that A is not quite true, or has caveats, or similar?-- [[User:Iain marcuson|Iain marcuson]] ([[User talk:Iain marcuson|discuss]] • [[Special:Contributions/Iain marcuson|contribs]]) 17:50, 22 April 2026 (UTC) == Request: Help adding Objective Projection writing guide (filter blocked) == Hello, I am Levent Bulut (ORCID: 0009-0007-7500-2261), author of the Objective Projection methodology. I am trying to contribute a practical writing guide to Wikibooks under CC BY-SA 4.0. Book title: "Objective Projection: Why the Brain Never Forgets Some Stories" The automated filter blocked my edits due to external links and content volume. I have already created the page with the introduction and contents, but could not add the chapters. The Turkish version of the same book is already live on Wikibooks: https://tr.wikibooks.org/wiki/Nesnel_%C4%B0zd%C3%BC%C5%9F%C3%BCm:_Beyin_Neden_Baz%C4%B1_Hikayeleri_Unutmuyor%3F This is not a new theory — it is an instructional guide teaching a published methodology documented in DOI-registered publications: https://doi.org/10.5281/zenodo.18689179 Open license declaration on my site: https://leventbulut.com/acik-lisans-bildirimi-wikibooks/ All content is my own work, written for Wikibooks, under CC BY-SA 4.0. Could an experienced editor help add the remaining chapters, or whitelist my account so the filter does not block future edits? Thank you. Levent Bulut | leventbulut.com [[User:LeventBulut|LeventBulut]] ([[User talk:LeventBulut|discuss]] • [[Special:Contributions/LeventBulut|contribs]]) 21:28, 24 April 2026 (UTC) : @[[User:LeventBulut|LeventBulut]] This happened because you added too much content when creating the book. Also, when reporting false positives from an edit filter, please report on [[Wikibooks:Edit filter/False positives]]. Thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:03, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:57, 26 April 2026 (UTC)</bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == After WikiNews shuts down....? == Can people try and write news articles here? Thank you! [[User:BigKrow|BigKrow]] ([[User talk:BigKrow|discuss]] • [[Special:Contributions/BigKrow|contribs]]) 22:30, 1 May 2026 (UTC) :Thanks for asking. You have a similar thread at our sister project Wikiversity and I am the equivalent of an admin there (we have a "curators" and "custodians" that are similar to admins on other projects). I'm not an admin here, but speaking as someone who has generally contributed here, writing news articles would not be appropriate. It would be great to write a textbook on [[journalism]]: we could use a great guide for ethics, finding sources, asking questions, objectivity and neutrality, etc. Unlike on Wikiversity, where the learning materials can be virtually anything, this project is specifically for a textbook/guide/manual, so writing news articles and posting them here is not really appropriate, but you could have a few example articles that you write for the purpose of having a textbook. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:46, 1 May 2026 (UTC) :: Heads up, a wiki was created: <span class="plainlinks">[https://news.wikioasis.org/wiki/Main_Page news.wikioasis.org]</span>. @[[User:Koavf|Koavf]]; I was temporarily granted some user rights to manage the wiki's setup and migration. I'll give you sysop rights since you are currently one on English Wikinews. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:11, 2 May 2026 (UTC) :::Thanks. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 02:14, 2 May 2026 (UTC) == What is Funding Pips Referral Code : 2A40D477 == Funding Pips Referral Code – 2A40D477 to unlock exclusive discounts, bonuses, and faster account approval with one of the top global prop trading firms, use this code and get 15% discount instantly. Funding Pips is a leading proprietary trading firm that empowers traders with real capital after completing a simple evaluation challenge. With no hidden rules, flexible account types, and fast payouts, it’s designed for serious traders who want to scale fast. Using the referral code 2A40D477 gives you an advantage at signup  including discounted challenge fees, priority support, and exclusive access to new trading features. [[User:Fundingpipsreferralcode|Fundingpipsreferralcode]] ([[User talk:Fundingpipsreferralcode|discuss]] • [[Special:Contributions/Fundingpipsreferralcode|contribs]]) 06:04, 5 May 2026 (UTC) == What is 91 Club Invite Code : 3788222275038 == Using this '''91 Club Invite Code 3788222275038''' not only gives you a head start with ₹1001 but also unlocks special rewards and exclusive access to promotions. Without the invite code, you might miss out on the signup bonus and early earning opportunities. '''How to use the 91 Club Invite Code:''' # '''Download the 91 Club App''' Visit the official 91 '''91 Club Invite Code 3788222275038 is the best code currently''' use this code and get '''₹1001 signup bonus''' by using our '''91 Club Invite Code 3788222275038''' during registration. Club website or search for “91 Club” online to download the APK file. # '''Install and Open the App''' Allow installation from unknown sources on your phone and open the app once installed. # '''Sign Up with Your Mobile Number''' Enter your mobile number to register for a new account. # '''Enter the 91 Club Invite Code – 3788222275038''' In the referral or invite code box, enter '''3788222275038''' and click on “Submit.” # '''Get ₹1001 Bonus Instantly''' Once the invite code is verified, ₹1001 will be added to your wallet as a welcome reward. [[User:Fundingpipsreferralcode|Fundingpipsreferralcode]] ([[User talk:Fundingpipsreferralcode|discuss]] • [[Special:Contributions/Fundingpipsreferralcode|contribs]]) 06:08, 5 May 2026 (UTC) ocpxnc6mnkrdcanyblig5s3e4bh3f6e 4634223 4634222 2026-05-05T07:34:31Z MathXplore 3097823 [[WB:REVERT|Reverted]] edits by [[Special:Contributions/Fundingpipsreferralcode|Fundingpipsreferralcode]] ([[User talk:Fundingpipsreferralcode|talk]]) to last version by ArchiverBot 4633797 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:CHAT|WB:RR/G|WB:GENERAL}} {{TOC left|limit=3}} {{User:MiszaBot/config |archive = Wikibooks:Reading room/Archives/%(year)d/%(monthname)s |algo = old(60d) |counter = 1 |minthreadstoarchive = 1 |minthreadsleft = 1 |key = 7a0ac23cf8049e4d9ff70cabb5649d1a }} Welcome to the '''General reading room'''. On this page, Wikibookians are free to talk about the Wikibooks project in general. For proposals for improving Wikibooks, see the [[../Proposals/]] reading room. {{clear}} [[Category:Reading room]] == Upcoming deployment of CampaignEvents extension to Wikibooks == <section begin="message"/> Hello everyone, We are writing to inform you that the [[mw:Help:Extension:CampaignEvents|CampaignEvents extension]] will be deployed to all Wikibooks projects during the week of '''23 March 2026'''. This follows last year’s broader rollout across Wikimedia projects. We realized that Wikibooks was not included at the time, and we’re now addressing that to ensure consistency across all communities. The CampaignEvents extension provides tools to support event and campaign organization on-wiki, including features like on-wiki event registration and collaboration lists(global event list). We welcome any questions, feedback, or concerns you may have. We are also happy to support anyone interested in trying out the tools. ''Apologies if this message is not in your preferred language. If you’re able to help translate it for your community, please feel free to do so.'' <section end="message"/> <bdi lang="en" dir="ltr">[[User:Udehb-WMF|Udehb-WMF]] ([[User talk:Udehb-WMF|discuss]]) 18:22, 19 March 2026 (UTC)</bdi> <!-- Message sent by User:Udehb-WMF@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Udehb-WMF/sandbox/MM_target&oldid=30284073 --> == Regarding the project's FlaggedRevs extension == Hello, everyone. I want to discuss with the community about the use of this project's FlaggedRevs (flagged revisions) extension, which was deployed many years ago (and configured recently). === Many unreviewed edits, and edit quality options === According to [[Special:PendingChanges]], there are almost 4000 unreviewed edits (per the standard FlaggedRevs configuration). In addition, on the edit review interface when evaluating a diff, there are three radio buttons that determine the quality of the edit (minimal, average, good). Do we have to utilize these buttons if the quality of the edit or the book matters, according to [[WB:REVIEW]]? This proposal is to whether discontinue the edit rating buttons or not. One way to reduce such a large amount of unreviewed edits is to set the following to <code>true</code>: * <code>wgFlaggedRevsProtection</code> (pending changes protection, to be used on Wikijunior pages; this might negate the need to show the stable version by default) * (optional) <code>wgSimpleFlaggedRevsUI</code> (simpler, icon-based UI on the edit review interface) We should also include the following configuration (partially based from English Wikipedia), if this proposal passes: <syntaxhighlight lang="php"> elseif ( $wgDBname == 'enwikibooks' ) { // Limited to the main, Cookbook, and Wikijunior namespaces (T408110) $wgFlaggedRevsNamespaces = [ NS_MAIN, 102, 110 ]; # We have only one tag with one level $wgFlaggedRevsTags = [ 'status' => [ 'levels' => 1 ] ]; # Restrict autoconfirmed to flagging semi-protected $wgFlaggedRevsTagsRestrictions = [ 'status' => [ 'review' => 1, 'autoreview' => 1 ], ]; # Restriction levels for auto-review/review rights $wgFlaggedRevsRestrictionLevels = [ 'autoreview' ]; # Remove 'validate' from reviewers $wgGroupPermissions['reviewer']['validate'] = false; # Group permissions for sysops $wgGroupPermissions['sysop']['review'] = true; $wgGroupPermissions['sysop']['stablesettings'] = true; # Allow sysops to add and remove the 'reviewer' group $wgAddGroups['sysop'][] = 'reviewer'; $wgRemoveGroups['sysop'][] = 'reviewer'; # Remove the 'editor' user group unset( $wgGroupPermissions['editor'] ); } </syntaxhighlight> === Inactive reviewers === After conducting an audit of over 1000 reviewers, most, if not many of them are completely inactive. === User group changes for reviewers === The reviewer user group is known to the software as <code>editor</code>, which might sound misleading (the actual [[MediaWiki:Group-editor/qqq|/qqq definition]] is "Editors"). To fix that, we might have to consider switching to <code>reviewer</code> and unset <code>editor</code>. I am also not sure whether administrators should have the <code>validate</code> user right, since <code>reviewer</code> has it on by default (but it is currently disabled). On the above configuration I proposed, administrators (and users in the <code>reviewer</code> user group) would no longer have <code>validate</code>. === Page patrolling === Currently, only administrators can mark new pages as patrolled (<code>patrol</code>) by using the MediaWiki page patrol software, but clicking on "Accept revision" (via FlaggedRevs) would also mark the page as patrolled, in question. I believe that using FlaggedRevs to patrol new pages is redundant, given that we might not want to use one or the other. If we are considering on switching to pending changes, we should also allow reviewers to mark new pages as patrolled, as they are trusted to have the <code>autopatrol</code> right in addition to administrators and autoreviewed users. Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:05, 21 March 2026 (UTC) :I agree on replacing <code>editor</code> with <code>reviewer</code> to avoid confusion. Reviewers don't need to have patrol permissions as a reviewed page would be patrolled as well. I don't think people will use it much as a page or edit being reviewed already means that it has been checked by someone else. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:00, 22 March 2026 (UTC) ::When I said that reviewers would have <code>patrol</code>, they can review new pages that other users created, but not any new pages they create themselves. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:16, 22 March 2026 (UTC) :::How can that be the case if they have <code>autopatrol</code>? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 18:26, 22 March 2026 (UTC) ::::I will give you an example. On the English Wikiquote, there are two user groups that have <code>autopatrol</code>: autopatrollers and patrollers. Autopatrollers have their page creations marked as patrolled by the software, while patrollers (whilst also having their page creations marked as patrolled) can mark new pages as patrolled (in addition to administrators). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 22 March 2026 (UTC) :::::But what is the point of giving reviewers <code>patrol</code> if we are already using FlaggedRevs? I think that we won't need patrol because we already have reviewing, and patrol only seems to be a confirmation that the page is up to policy from what I have seen, so giving them reviewers to mark pages as patrolled seems pointless to me when we already have FlaggedRevs. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 19:06, 22 March 2026 (UTC) ::::::I understand, but my proposal was to convert FlaggedRevs into a protection-like mechanism which would be used alongside page protection; it might turn off FlaggedRevs's ability to patrol new pages for reviewers, hence why I suggested this above. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:30, 22 March 2026 (UTC) ::::::: @[[User:Kingofnuthin|Kingofnuthin]] I will summarize what you said from above: :::::::* You agree about the reviewer user group to be moved from <code>editor</code> to <code>reviewer</code> to avoid confusion (technically). :::::::* However, you probably disagree about allowing reviewers to patrol new pages ''and'' having their page creations automatically marked as patrolled, because FlaggedRevs can do all of this, and <code>$wgUseNPPatrol</code> might seem to be redundant. ::::::: A compromise about your disagreement is that we might have to consider removing <code>autopatrol</code> and/or <code>patrol</code> from our existing user groups, similar to [[phab:T423461]]. ::::::: I started this because in addition to that, one of my concerns was the extreme backlog of unreviewed edits and pages [4000!]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:31, 19 April 2026 (UTC) :I may be missing some things here, so let me know if I haven't answered any points here: :# I don't think we currently need to have the review status indicate the quality of the edit (i.e. minimal, average, good). I don't think this is used at all anymore. :# I think it makes sense to reassign the reviewer user group to <code>editor</code>. I always like clarity in language. :# Are you saying that pages marked as reviewed are currently also classed as patrolled? If that's the case, I think we should not have reviewed pages automatically classed as patrolled, and we should keep reviewing and patrolling separate. :I'll note that honestly don't know much about patrolling, since I've never engaged with it—I have only ever referenced the reviewing system. If there is a significant functional difference, I would love to know it. Cheers! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:00, 23 March 2026 (UTC) ::When someone clicks "Accept revision" on an unreviewed page, it is listed under [[Special:Log/review]]; if an admin marks a page as patrolled with "Mark this page as patrolled", it will show up under [[Special:Log/patrol]], which is not really logged much compared to the former log (review). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:12, 23 March 2026 (UTC) :I agree to your thoughts about the <code>editor</code> group and edit quality ratings, but I don't understand what this proposal changes for FlaggedRevs, since I don't have much technical knowledge. Can you explain what the proposal changes here, how are we going to convert FlaggedRevs into a "protection-like mechanism"? [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:24, 23 March 2026 (UTC) ::The proposal of changing FlaggedRevs into a protection-like feature (pending changes) is when an editor (unregistered/one not holding autoreviewer, reviewer, or administrator permissions) makes an edit, but their edit will be hidden from the public until it is approved by a reviewer or an administrator, and it will solely apply to Wikijunior pages. The configuration above is similar to what English Wikipedia uses. {{quote|::I think it makes sense to reassign the reviewer user group to <code>editor</code>.}} ::@[[User:Kittycataclysm|Kittycataclysm]]: I believe you might have misunderstood. What I meant is that <code>(editor)</code> will be changed to <code>(reviewer)</code> to avoid confusion, but I plan to remove <code>editor</code> from all inactive reviewers, then do the same for recently active reviewers. However, given that there are a lot of reviewers, a script will possibly do all the work (under {{no ping|Maintenance script}} or similar). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:29, 23 March 2026 (UTC) :::Gotcha! I can't currently foresee an issue with this —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:09, 30 March 2026 (UTC) :'''Re FlaggedRevs generally: '''The [[mw:Extension:FlaggedRevs|Mediawiki page of the extension]] says it is not being maintained and not recommended for production use. We should consider whether we need this extension at all. :What is the actual policy justification for having FlaggedRevs? :[[Help:Tracking_changes#Reviewing_pages]] says it's "our primary counter-vandalism tool". I don't know if it is that: it doesn't prevent vandalism or reduce exposure to vandalism (as with stable versions). The "counter-vandalism" bit comes from human editors looking at the edits, identifying vandalism, and reverting. FlaggedRevs isn't necessary for that. Maybe it makes it a little easier to spot edits in recent changes from new editors that may need a little more help (wikicode etc, not just spam), but can that be achieved just with the patrolled edits functionality? :If we still want something like FlaggedRevs, as an anti-vandalism tool or for draft control, then Mediawiki has a [[mw:Content approval extensions|list of alternatives]] that may be more suited and better maintained. :'''Re minimal/average/good specifically:''' I agree that we don't need the three categories. I thought I read somewhere that these were intended to show the quality of the REVIEW not of the page? That is, a "minimal" review is "I checked there was no obvious vandalism" and a "good" review was "I've thoroughly fact-checked everything". [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 11:34, 5 April 2026 (UTC) :: This was enabled back in 2008, which resulted in [[Wikibooks:New page patrol]] currently being obsolete. To be honest, I would keep FlaggedRevs, but I was proposing to change it to pending changes protection, similar to how Wikipedia utilizes it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:04, 19 April 2026 (UTC) :Pinging <span class="template-ping">@[[:User:JJPMaster|JJPMaster]]:</span> and <span class="template-ping">@[[:User:Kittycataclysm|Kittycataclysm]]:</span> for additional input. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) <span style="font-size: smaller;" class="autosigned">—Preceding [[w:Wikipedia:Signatures|undated]] comment added 22:29, 22 March 2026.</span><!--Template:Undated--> == Global ban for Faster than Thunder == * {{user|Faster than Thunder}} Hello, this message is to notify that [[User:Faster than Thunder|Faster than Thunder]] has been nominated for a global ban at [[m:Requests for comment/Global ban for Faster than Thunder]]. You are receiving this notification as required per the [[m:global ban|global ban]] policy as they have made at least 1 edit on this wiki. Thanks, --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 01:52, 22 March 2026 (UTC) == Upcoming Wikimedia Café meetup regarding the [[:meta:Wikimedia Foundation Annual Plan/2026-2027|the 2026-2027 Wikimedia Foundation Annual Plan]] == {{tmbox | image = [[File:Wikimedia Café logo in plain SVG format.svg|45px]] | type=notice | text = Hello! There will be a '''[[:meta:Wikimedia Café|Wikimedia Café]]''' meetup on '''Saturday, 11 April 2026 at 14:00 UTC''', focusing on the [[:meta:Wikimedia Foundation Annual Plan/2026-2027|the 2026-2027 Wikimedia Foundation Annual Plan]]. The featured guests will be {{Noping|KStineRowe (WMF)|label1=Kelsi Stine-Rowe}} (senior manager, [[:meta:Movement Communications|Movement Communications]], Wikimedia Foundation), and {{Noping|Samwalton9 (WMF)|label1=Sam Walton}} (senior product manager, [[:mw:Moderator Tools|Moderator Tools]], Wikimedia Foundation). <br /> In addition to this Café session, [[:meta:Wikimedia Foundation Annual Plan/2026-2027/Collaboration|several additional meetings regarding the Annual Plan are listed on the Collaboration page]], and you may participate on the [[:meta:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. <br /> This Café meetup will be approximately two hours long. Attendees may choose to attend only for a part. Please see the Café page for more information, including [[:meta:Wikimedia Café#Signups for the April 2026 session|how to register]]. <br /> [[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]] }} <span style="white-space:nowrap;">[[User:Pine|<span style="color:#01796f; text-shadow:#00BFFF 0 0 1.0em">↠Pine</span>]] [[User talk:Pine|<span style="color:DeepSkyBlue">(<b style="color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em">✉</b>)</span>]]</span> 05:23, 29 March 2026 (UTC) == Regarding copyright of recipes found on online cooking forums == What is the copyright situation regarding cooking recipes found on online recipe books with recipes made by other people? I ask this because I want to add/translate recipes from 下厨房 (xià chúfáng) for Chinese recipes, and while I was intending to add the original writer of the recipe with the translation I still want to ask for clarification. [[User:Fukukitaru|Fukukitaru]] ([[User talk:Fukukitaru|discuss]] • [[Special:Contributions/Fukukitaru|contribs]]) 19:06, 30 March 2026 (UTC) :Recipes are in principle not copyright-able, as they are just facts. When someone includes descriptive text or anything that elaborates on the basic ingredients and steps, that is copyright-able. I am not a lawyer or legal scholar and cannot give legal advice. See (e.g.) https://www.copyrightlaws.com/copyright-protection-recipes/ —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:16, 30 March 2026 (UTC) ::In that case, would simplifying ingredients and methods to where they are simple yet can still be understood be sufficient for said recipes? [[User:Fukukitaru|Fukukitaru]] ([[User talk:Fukukitaru|discuss]] • [[Special:Contributions/Fukukitaru|contribs]]) 19:23, 30 March 2026 (UTC) :::Yes, you can add a recipe here as long as the instructions and text are not too overlapping with the copyrighted original. As the linked page says, the '''ideas''' behind the ingredient list and steps to prepare a given food item are not currently copyrightable, but the way you write the ideas may be copyrightable. You should also cite where you took the recipe from so we can trace its origins. I personally recommend only adding recipes that you have successfully made so we don't become a massive repository of potentially low-quality or untested recipes—I only add recipes once I have made them successfully. Let me know if you have any more questions about the Cookbook! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:06, 30 March 2026 (UTC) ::::To build up on this, if you want to understand what is copyright-able and what is not, the "[[:w:en:Idea–expression distinction|idea versus expression]]" distinction. You cannot own the idea of "Boy meets girl, boy loses girl, boy and girl commit suicide" but you can copyright a specific version of ''Romeo and Juliet'' with your own innovative ideas. And, for that matter, this is context-specific, but if you can understand the distinction, it can help with future questions about "could this be protected by copyright?", which can be a subtle one. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:50, 30 March 2026 (UTC) :::::To further build up on this, there's something called the merger doctrine (see ''[[w:Baker v. Selden|Baker v. Selden]]''). This is why you can't copyright drawings of [[w:Structural formula|structural formulas]]. This doctrine means that if there's only one or a handful of ways to express an idea, then any such expression cannot be copyrighted, since copyrighting that expression would essentially be copyrighting the idea itself. This comes in a lot with recipes. I very likely can't copyright this list (from [[Cookbook:Cornmeal Pancakes (Arepa)]]: :::::* 2.4 cups corn flour :::::* 1.2 tsp salt :::::* 0.6 cup grated white cheese :::::* 2.4 cups cool water :::::Since there's essentially only one way to express the idea of that combination of ingredients. However, if I say: :::::* 2.4 cups corn flour: for this, I strongly recommend Harina P.A.N., because my grandma always used to make me arepas from that stuff every day, and it was delicious. :::::That is copyrightable. At that point, I cease to merely be expressing the idea of a food item with those four ingredients, and add a minimum degree of creativity. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:02, 31 March 2026 (UTC) ::::::And to build on all <em>that</em>, even if individual pieces of information are in the public domain (or are fair use), the <em>arrangement</em> of them can be copyrighted. This is why even if ''Bartlett's Quotations'' only had public domain material, the act of selectively editing and positioning them thematically for the user's benefit could constitute a sufficiently original work. So we could copy the material from a bunch of recipes, but could run a foul of copyright issues if we arranged and sorted them in some kind of manner that replicated someone else's original work. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 02:28, 31 March 2026 (UTC) == Style Guidelines for Advanced Points == Is there a general style guideline to refer the reader to advanced information, while the main text gives the short-answer version? For example, how would I specify that in practical applications, A is true, but if you use the theory you see that A is not quite true, or has caveats, or similar?-- [[User:Iain marcuson|Iain marcuson]] ([[User talk:Iain marcuson|discuss]] • [[Special:Contributions/Iain marcuson|contribs]]) 17:50, 22 April 2026 (UTC) == Request: Help adding Objective Projection writing guide (filter blocked) == Hello, I am Levent Bulut (ORCID: 0009-0007-7500-2261), author of the Objective Projection methodology. I am trying to contribute a practical writing guide to Wikibooks under CC BY-SA 4.0. Book title: "Objective Projection: Why the Brain Never Forgets Some Stories" The automated filter blocked my edits due to external links and content volume. I have already created the page with the introduction and contents, but could not add the chapters. The Turkish version of the same book is already live on Wikibooks: https://tr.wikibooks.org/wiki/Nesnel_%C4%B0zd%C3%BC%C5%9F%C3%BCm:_Beyin_Neden_Baz%C4%B1_Hikayeleri_Unutmuyor%3F This is not a new theory — it is an instructional guide teaching a published methodology documented in DOI-registered publications: https://doi.org/10.5281/zenodo.18689179 Open license declaration on my site: https://leventbulut.com/acik-lisans-bildirimi-wikibooks/ All content is my own work, written for Wikibooks, under CC BY-SA 4.0. Could an experienced editor help add the remaining chapters, or whitelist my account so the filter does not block future edits? Thank you. Levent Bulut | leventbulut.com [[User:LeventBulut|LeventBulut]] ([[User talk:LeventBulut|discuss]] • [[Special:Contributions/LeventBulut|contribs]]) 21:28, 24 April 2026 (UTC) : @[[User:LeventBulut|LeventBulut]] This happened because you added too much content when creating the book. Also, when reporting false positives from an edit filter, please report on [[Wikibooks:Edit filter/False positives]]. Thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:03, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:57, 26 April 2026 (UTC)</bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == After WikiNews shuts down....? == Can people try and write news articles here? Thank you! [[User:BigKrow|BigKrow]] ([[User talk:BigKrow|discuss]] • [[Special:Contributions/BigKrow|contribs]]) 22:30, 1 May 2026 (UTC) :Thanks for asking. You have a similar thread at our sister project Wikiversity and I am the equivalent of an admin there (we have a "curators" and "custodians" that are similar to admins on other projects). I'm not an admin here, but speaking as someone who has generally contributed here, writing news articles would not be appropriate. It would be great to write a textbook on [[journalism]]: we could use a great guide for ethics, finding sources, asking questions, objectivity and neutrality, etc. Unlike on Wikiversity, where the learning materials can be virtually anything, this project is specifically for a textbook/guide/manual, so writing news articles and posting them here is not really appropriate, but you could have a few example articles that you write for the purpose of having a textbook. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:46, 1 May 2026 (UTC) :: Heads up, a wiki was created: <span class="plainlinks">[https://news.wikioasis.org/wiki/Main_Page news.wikioasis.org]</span>. @[[User:Koavf|Koavf]]; I was temporarily granted some user rights to manage the wiki's setup and migration. I'll give you sysop rights since you are currently one on English Wikinews. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:11, 2 May 2026 (UTC) :::Thanks. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 02:14, 2 May 2026 (UTC) q9vhfv9fo99h1h0qffw06gftsmj9r5b 0 113580 4634065 4410818 2026-05-04T12:25:19Z Jcb 90773 4634065 wikitext text/x-wiki ==Heart== [[Image:Heart-and-lungs.jpg|thumb|right|230px|The heart and lungs, from an older edition of '' Gray's Anatomy''.]] The '''heart''' is a pear shaped, muscular organ in vertebrates, responsible for pumping blood through the blood vessels by repeated, rhythmic contractions<ref>{{cite web | url = http://www.kmle.com/search.php?Search=heart | title = ''KMLE Medical Dictionary Definition of heart'' | author = [http://www.kmle.com The American Heritage Stedman's Medical Dictionary]}}.</ref> The term ''cardiac'' (as in cardiology) means "related to the heart" and comes from the Greek. The heart is composed of cardiac muscle, an involuntary muscle tissue which is found only within this organ.<ref>{{cite web | url = http://www.kmle.com/search.php?Search=cardiac | title = ''KMLE Medical Dictionary Definition of cardiac'' | author = [http://www.kmle.com The American Heritage Stedman's Medical Dictionary]}}</ref> ===Structure=== In the human body, the heart is normally situated to the left of the middle of the thorax, underneath the breastbone (see [http://www.easyrashi.com/TEFILLIN/Position_of_heart.htm diagrams]). The heart is usually felt to be on the left side because the left heart (left ventricle) is stronger (it pumps to all body parts). The left lung is smaller than the right lung because the heart occupies more of the left hemithorax. The heart is enclosed by a sac known as the pericardium and is surrounded by the lungs. The pericardium is a double membrane structure containing a serous fluid to reduce friction during heart contractions. The mediastinum, a subdivision of the thoracic cavity, is the name of the heart cavity. The ''apex'' is the blunt point situated in an inferior (pointing down and left) direction. A stethoscope can be placed directly over the apex so that the beats can be counted. This physical location is between the sixth and seventh rib, just to the left of the sternum [http://www.easyrashi.com/TEFILLIN/sternum.htm]. In normal adults, the mass of the heart is 250-350 g (9-12&nbsp;oz), or about three fourths the size of a clenched fist, but extremely diseased hearts can be up to 1000 g (2&nbsp;lb) in mass due to hypertrophy. It consists of four chambers, the two upper ''atria'' (singular: atrium ) and the two lower ''ventricles''. On the left is a picture of a fresh human heart which was removed from a 64-year-old British male. [[Image:Humhrt2.jpg|thumb|200px|left|Human heart]] The function of the right side of the heart (see right heart) is to collect deoxygenated blood, in the right atrium, from the body and pump it, via the right ventricle, into the lungs (pulmonary circulation) so that carbon dioxide can be dropped off and oxygen picked up (gas exchange). This happens through a passive process called diffusion. The left side (see left heart) collects oxygenated blood from the lungs into the left atrium. From the left atrium the blood moves to the left ventricle which pumps it out to the body. On both sides, the lower ventricles are thicker and stronger than the upper atria. The muscle wall surrounding the left ventricle is thicker than the wall surrounding the right ventricle due to the higher force needed to pump the blood through the systemic circulation. ===Illustrations=== These diagrams of the heart show its basic anatomy: {| |[[Image:Heart numlabels.svg|300 px]] | # Right Atrium # Left Atrium # Superior Vena Cava # Aorta # Pulmonary Artery # Pulmonary Vein # Bicupsid ('Mitral') Valve # Aortic Semilunar Valve # Left Ventricle # Right Ventricle # Inferior Vena Cava # Tricuspid Valve # Pulmonary Semilunar Valve |} [[Image:Heart.jpg|450px]] {| |[[Image:Heart_systole.png|250px]] Systole |[[Image:Heart_diastole.png|250px]] Diastole |} The electrical signals pass through the heart from the SAN, through the atria, to the AVN and then to the vetricales via the Purkinje fibres. <!-- [[Image:Heart_conduct_explain.gif]] --> [[Image:Heart_conduct_sinus.gif]] The electrical signals can be monitored using electrodes on the skin of the chest. The electrocardiogram is an important tool for diagnosing heart problems: {| |[[Image:ECG_principle_slow.gif|300 px]] |[[Image:ECG_Principle_fast.gif|300 px]] |} Animations of the electrical pulses and the ECG generated. {| |[[Image:EKG2.png|200 px]] Normal ECG |[[Image:SinusRhythmLabels.svg|200 px]] Analysis of normal ECG waves |} In '''normal sinus rhythm''': *each P wave is followed by a QRS *P wave rate 60 - 100 bpm with <10% variation If the SAN is diseased or inherits a malfunction then the heart may develop rapid (tachycardia), slow (bradycardia), or both rapid and slow rhythms (arrhythmia). Treatment may involve drugs and/or a cardiac pacemaker.<ref>P228 Black’s Medical Dictionary</ref> *If rate <60 = '''sinus bradycardia''' *If rate >100 = '''sinus tachycardia''' *If variation >10% = '''sinus arrhythmia''' '''Ventricular fibrillation''': Dangerous and rapid arrhythmia of the ventricle. The ECG shows a "bizarre, irregular, random waveform; no clearly identifiable QRS complexes or P waves."<ref>[http://www.ecglibrary.com/] ECG Library.</ref> [[Image:EKG VF.jpg|450 px]] ECG showing ventricular fibrillation. ==Heart rate== '''Heart rate''' is a term used to describe the frequency of the cardiac cycle. It is considered one of the four vital signs. Usually it is calculated as the number of contractions ('''heart beats''') of the heart in one minute and expressed as "beats per minute" (bpm). When resting, the adult human heart beats at about 70&nbsp;bpm (males) and 75&nbsp;bpm (females), but this rate varies among people. However, the reference range is normally between 60&nbsp;bpm (if less termed bradycardia) and 100&nbsp;bpm (if greater, termed tachycardia). Resting heart rates can be significantly lower in athletes. The pulse is the most straightforward way of measuring the heart rate, but it can be deceptive when some heart beats do not have much cardiac output. In these cases (as happens in some arrhythmias), the heart rate may be considerably higher than the pulse rate. Auscultation is also a method of heart rate measurement. ===Control of heart rate=== The heart is controlled by the autonomic nervous system and circulating adrenaline. The autonomic nervous system has two divisions: The sympathetic nervous system ('fight or flight' response) stimulates cardiac output by acting on the SAN, the cardiac muscle and the AVN. The parasympathetic nervous system ('rest and digest' response) has the opposite effect. Blood pressure is detected by baroreceptors in the carotid arteries. Chemoreceptors in the medulla oblongata detect changes in pH and carbon dioxide levels. Decreased blood pressure, pH or increased CO₂ levels cause stimulation of the heart via the sympathetic nervous system. Although chemoreceptors in the aorta and carotid arteries detect oxygen levels, the response is counterintuitive. Low oxygen levels cause the heart rate to decrease, which protects the heart muscle from the effects of anaerobic respiration. ===Heart rate abnormalities=== ====Tachycardia==== '''Tachycardia''' refers to a rapid beating of the heart. By convention the term refers to heart rates greater than 100 beats per minute in the adult patient. Tachycardia may be a perfectly normal physiological response to stress. However, depending on the mechanism of the tachycardia and the health status of the patient, tachycardia may be harmful, and require medical treatment. In extreme cases, tachycardia can be life threatening. Tachycardia can be harmful in two ways. First, when the heart beats too rapidly, it may perform inefficiently. Second, the faster the heart beats, the more oxygen and nutrients the heart requires. This may leave patients feeling out of breath. This can be especially problematic for patients suffering from ischemic heart disease. ====Haemodynamic responses==== The body contains several feedback mechanisms to maintain adequate blood flow and blood pressure. If blood pressure decreases, the heart beats faster in an attempt to raise it. This is called reflex tachycardia. This can happen in response to a decrease in blood volume (through dehydration or bleeding), or an unexpected change in blood flow. The most common cause of the latter is orthostatic hypotension (also called postural hypotension), a sudden drop of blood pressure that occurs with a change in body position (e.g., going from lying down to standing up). Fever and infection leading to sepsis are also common causes of tachycardia, primarily due to increase in metabolic demands and compensatory increase in heart rate. ====Autonomic and endocrine causes==== An increase in sympathetic nervous system stimulation causes the heart rate to increase, both by the direct action of sympathetic nerve fibres on the heart and by causing the endocrine system to release hormones such as epinephrine (adrenaline), which have a similar effect. Increased sympathetic stimulation is usually due to physical or psychological stress (the so-called "fight or flight" response), but can also be induced by stimulant]s such as amphetamines. Endocrine disorders such as pheochromocytoma can cause epinephrine release and tachycardia independent of the nervous system. Hyperthyroidism is also known to cause tachycardia. =====Sinus tachycardia===== The most common type of tachycardia is sinus tachycardia, which is the body's normal reaction to stress, including fever, dehydration, or blood loss (shock). In the absence of heart disease, it tends to have a narrow QRS complex on the ECG. Treatment is generally directed at identifying the underlying cause. ====External links==== * [http://www.dinet.org/pots_an_overview.htm Postural Orthostatic Tachycardia Syndrome - overview from Dysautonomia Information Network] * [http://www.healthcare.ucla.edu/vitalsigns/article-display?article_id=503 Heart Arrhythmias Respond to Ablation] UCLA Healthcare * [http://www.aral.org.uk/html/tachycardia.html Arrhythmia Alliance Tachycardia Page] ====Bradycardia==== Bradycardia is defined as a heart rate less than 60 beats per minute although it is seldom symptomatic until below 50&nbsp;bpm. Trained athletes tend to have slow resting heart rates, and resting bradycardia in athletes should not be considered abnormal if the individual has no symptoms associated with it. Again, this number can vary as smaller people and children have faster heart rates than adults. ==Pulse== A person's '''pulse''' is the throbbing of their arteries as an effect of the heartbeat. It can be felt at the [neck, at the wrist and other places. Pressure waves move through the blood vessels, which are pliable; these waves are not caused by the forward movement of the blood. When the heart contracts, blood is ejected into the aorta and the aorta stretches. At this point the wave of distention ('''pulse wave''') is pronounced but relatively slow-moving (3 to 6&nbsp;m/s). As it travels towards the peripheral blood vessels, it gradually diminishes and becomes faster. In the large arterial branches, its velocity is 7 to 10&nbsp;m/s; in the small arteries, it is 15 to 35&nbsp;m/s. The pressure pulse is transmitted 15 or more times more rapidly than the blood flow. The term ''pulse'' is also used, although incorrectly, to denote the frequency of the heart beat, usually measured in beats per minute. In most people, the pulse is an accurate measure of heart rate. Under certain circumstances, including arrhythmias, some of the heart beats are ineffective and the aorta is not stretched enough to create a palpable pressure wave. The pulse is irregular and the heart rate can be (much) higher than the pulse rate. In this case, the heart rate should be determined by auscultation of the heart apex, in which case it is not the pulse. The '''pulse deficit''' (difference between heart beats and pulsations at the periphery) should be determined by simultaneous palpation at the radial artery and auscultation at the heart apex. A normal pulse rate for a healthy adult, while resting, can range from 60 to 100 '''beats per minute''' ('''BPM'''). During sleep, this can drop to as low as 40 BPM; during strenuous exercise, it can rise as high as 200&ndash;220 BPM. Generally, pulse rates are higher in younger persons. A resting heart rate for an infant is as high as or higher than an adult's pulse rate during strenuous exercise. Pulses are manually palpated with fingers or thumb. When palpating the carotid artery, the femoral artery or the brachial artery, the thumb may be used. However, the thumb has its own pulse which can interfere with detecting the patient's pulse at other points, where two or three fingers should be used. Fingers or thumb must be placed near an artery and pressed gently against a firm structure, usually a bone, in order to feel the pulse. An alternative way of finding the pulse rate is by palpating or listening to the heartbeat. This is most commonly done with the examiner's palm or a through a stethoscope. Before the invention of the stethoscope examiners would press their ear directly to the chest. [[Image:Radial pulse.jpg|thumb|right|250px|Checking the radial pulse.]] ===Common pulse points=== *'''radial pulse''' - located on the thumb side of the wrist *'''ulnar pulse''' - located on the little finger side of the wrist (ulnar artery) *'''carotid pulse''' - located in the neck (carotid artery). The carotid artery should be palpated gently. Stimulating its baroreceptors with vigorous palpitation can provoke severe bradycardia or even stop the heart in some sensitive persons. Also, a person's two carotid arteries should not be palpated at the same time, to avoid a risk of fainting or brain ischaemia. *'''brachial pulse''' - located between the biceps and triceps, on the medial side of the elbow cavity; frequently used in place of carotid pulse in infants (brachial artery) *'''femoral pulse''' - located in the thigh (femoral artery) *'''popliteal pulse''' - located behind the knee in the popliteal fossa, found by holding the bent knee. The patient bends the knee at approximately 120°, and the physician holds it in both hands to find the popliteal artery in the pit behind the knee. *'''dorsalis pedis pulse''' - located on top of the foot (dorsalis pedis artery) *'''tibialis posterior pulse''' - located in the back of the ankle behind the medial malleolus (posterior tibial artery). *'''temporal pulse''' - located on the temple directly in front of the ear (temporal artery) The ease of palpability of a pulse is dictated by the patient's blood pressure. If his or her systolic blood pressure is below 90 mmHg, the radial pulse will not be palpable. Below 80 mmHg, the brachial pulse will not be palpable. Below 60 mmHg, the carotid pulse will not be palpable. Since systolic blood pressure rarely drops that low, the lack of a carotid pulse usually indicates death. It is not unheard of, however, for patients with certain injuries, illnesses or other medical problems to be conscious and aware with no palpable pulse. ==Lungs== [[Image:heart-and-lungs.jpg|thumb|right|230px|The '''lungs''' flank the heart and great vessels in the chest cavity. <small>(Source: ''Gray's Anatomy of the Human Body'', 20th ed. 1918.)</small> [[Image:Lungs.gif|thumb|right|230px|Air enters and leaves the lungs via a conduit of cartilaginuous passageways — the bronchi and bronchioles. In this image, lung tissue has been dissected away to reveal the bronchioles]] The '''lung''' is the essential respiration organ in air-breathing vertebrates. Its principal function is to transport oxygen from the atmosphere into the bloodstream, and to excrete carbon dioxide from the bloodstream into the atmosphere. This exchange of gases is accomplished in the mosaic of specialised cells that form millions of tiny, exceptionally thin-walled air sacs called alveoli. The lungs also have nonrespiratory functions. Medical terms related to the lung often begin with '''''pulmo-''''', from the Latin ''pulmonarius'' ("of the lungs"), or with '''''pneumo-''''' (from Greek πνεύμω "lung")<ref>{{cite web | url = http://www.kmle.com/search.php?Search=pneumo-| title = ''KMLE Medical Dictionary Definition of pneumo-'' | author = [http://www.kmle.com The American Heritage Stedman's Medical Dictionary]}}</ref><ref>{{cite web | url = http://www.kmle.com/search.php?Search=pulmo| title = ''KMLE Medical Dictionary Definition of pulmo-'' | author = [http://www.kmle.com The American Heritage Stedman's Medical Dictionary]}}</ref> ===Respiratory function=== Energy production from aerobic respiration requires oxygen and produces carbon dioxide as a by-product, creating a need for an efficient means of oxygen delivery ''to'' cells and excretion of carbon dioxide ''from'' cells. In air-breathing vertebrates, respiration occurs in a series of steps. Air is brought into the animal via the airways — this consists of the nose; the pharynx; the larynx; the trachea (also called the windpipe); the bronchi and bronchioles; and the terminal branches of the respiratory tree. The lungs are a rich lattice of alveoli, which provide an enormous surface area for gas exchange. A network of fine capillaries allows transport of blood over the surface of alveoli. Oxygen from the air inside the alveoli diffuses into the bloodstream, and carbon dioxide diffuses from the blood to the alveoli, both across thin alveolar membranes. The drawing and expulsion of air is driven by muscular action; a complicated musculoskeletal system is used. A large muscle, the diaphragm (in addition to the internal intercostal muscles), drive ventilation by periodically altering the intra-thoracic volume and pressure; by increasing volume and thus decreasing pressure, air flows into the airways down a pressure gradient, and by reducing volume and increasing pressure, the reverse occurs. During normal breathing, expiration is passive and no muscles are contracted (the diaphragm relaxes). Another name for this inspiration and expulsion of air is ventilation. The lungs of mammals have a spongy texture and are honeycombed with epithelium having a much larger surface area in total than the outer surface area of the lung itself. Breathing is largely driven by the muscular diaphragm at the bottom of the thorax. Contraction of the diaphragm pulls the bottom of the cavity in which the lung is enclosed downward. Air enters through the oral and nasal cavities; it flows through the larynx and into the trachea, which branches out into bronchi. Relaxation of the diaphragm has the opposite effect, passively recoiling during normal breathing. During exercise, the diaphragm contracts, forcing the air out more quickly and forcefully. The rib cage itself is also able to expand and contract to some degree, through the action of other respiratory and accessory respiratory muscles. As a result, air is sucked into or expelled out of the lungs, always moving down its pressure gradient. This type of lung is known as a '''bellows lung''' as it resembles a blacksmith's bellows. ===Anatomy=== In humans, it is the two main bronchi (produced by the bifurcation of the trachea) that enter the roots of the lungs. The bronchi continue to divide within the lung, and after multiple divisions, give rise to bronchioles. The bronchial tree continues branching until it reaches the level of terminal bronchioles, which lead to alveolar sacks. Alveolar sacs are made up of clusters of alveoli, like individual grapes within a bunch. The individual alveoli are tightly wrapped in blood vessels, and it is here that gas exchange actually occurs. Deoxygenated blood from the heart is pumped through the pulmonary artery to the lungs, where oxygen diffuses into blood and is exchanged for carbon dioxide in the haemoglobin of the erythrocytes (red blood cells). The oxygen-rich blood returns to the heart via the pulmonary veins to be pumped back into systemic circulation. [[Image:Illu_bronchi_lungs.jpg|thumb|Bronchi, bronchial tree, and lungs. (Cardiac notch labeled at bottom left.)|350px]] Human lungs are located in two cavities on either side of the heart. Though similar in appearance, the two are not identical. Both are separated into lobes, with three lobes on the right and two on the left. The lobes are further divided into lobules, hexagonal divisions of the lungs that are the smallest subdivision visible to the naked eye. The connective tissue that divides lobules is often blackened in smokers and city dwellers. The medial border of the right lung is nearly vertical, while the left lung contains a cardiac notch. The cardiac notch is a concave impression molded to accommodate the shape of the heart. Lungs are to a certain extent 'overbuilt' and have a tremendous reserve volume as compared to the oxygen exchange requirements when at rest. This is the reason that individuals can smoke for years without having a noticeable decrease in lung function while still or moving slowly; in situations like these only a small portion of the lungs are actually perfused with blood for gas exchange. As oxygen requirements increase due to exercise, a greater volume of the lungs is perfused, allowing the body to match its CO₂/O₂ exchange requirements. The environment of the lung is very moist, which makes it hospitable for bacteria. Many respiratory illnesses are the result of bacterial or viral infection of the lungs. [[Image:Illu bronchi lungs.jpg]] [[Image:Bronchial anatomy.jpg| 250 px]] [[Image:Bell jar lungs.png]] [[Image:Lungs diagram simple.svg]] [[Image:Lung capacity measures.png]] ===Vital capacity=== '''Vital capacity''' is the maximum volume of air that a person can exhale after maximum inhalation. A person's vital capacity can be measured by a spirometer which can be a wet or regular spirometer (spirometry). In combination with other physiological measurements, the vital capacity can help make a diagnosis of underlying lung disease. Vital capacity is the maximum amount of air a person can expel from the lungs after first filling the lungs to their maximum extent and then expiring to the maximum extent (about 4600 milliters). It equals the inspiratory reserve volume plus the tidal volume plus the expiratory reserve volume. ===Further reading=== * {{McGrawHillAnimation|biochemistry|Oxygen%20Carbon%20Dioxide}} * Lung Function Fundamentals. http://www.anaesthetist.com/icu/organs/lung/lungfx.htm * [http://www.leeds.ac.uk/chb/lectures/anatomy7.html Dr D.R. Johnson: Introductory anatomy, respiratory system] * [http://sln.fi.edu/biosci/systems/respiration.html Franlink Institute Online: The Respiratory System] * [http://www.lungsonline.com Lungs OnLine] ==Breathing== '''Breathing''' transports oxygen into the body and carbon dioxide out of the body. Aerobic organisms require oxygen to create energy via respiration, in the form of energy-rich molecules such as glucose. The medical term for normal relaxed breathing is eupnoea. ===Mechanics=== Breathing in, or inhaling, is usually an active movement, with the contraction of the diaphragm muscles needed. At rest, breathing out, or exhaling, is normally a passive process powered by the elastic recoil of the chest, similar to a deflating balloon. ===Gas exchange=== Breathing is only part of the process of delivering oxygen to where it is needed in the body. The process of gas exchange occurs in the alveoli by passive diffusion of gasses between the alveolar gas and the blood passing by in the lung capillaries. Once in the blood, the heart powers the flow dissolved gasses around the body in the circulation. As well as carbon dioxide, breathing also results in loss of water from the body. Exhaled air has a relative humidity of 100% because of water diffusing across the moist surface of breathing passages and alveoli. ===Control of breathing=== Breathing is one of the few bodily functions which, within limits, can be controlled both consciously and unconsciously. Unconsciously, breathing is controlled by specialised centres in the brainstem, which automatically regulate the rate and depth of breathing depending on the body’s needs at any time. When carbon dioxide levels increase in the blood, it reacts with the water in blood, producing carbonic acid. The drop in the blood's pH will then cause the medulla oblongata signalling centre in brain to send nerve impulses to the diaphragm and the intercostal muscles, increasing the rate of breathing. While exercising, the level of carbon dioxide in the blood increases due to increased cellular respiration by the muscles, and so breathing rate increases. During rest, the level of carbon dioxide is lower, so breathing rate is lower. This ensures an appropriate amount of oxygen is delivered to the muscles and other organs. It is important to reiterate that it is the buildup of carbon dioxide making the blood acidic that elicits the desperation for a breath much more than lack of oxygen. Rarely, individuals with chronic lung disease may adapt to high CO₂ levels in their blood by regulating their breathing according to O₂ levels. Hyperventilating causes a drop in CO₂ below normal levels, lowering blood acidity to trick the brain into thinking it has more oxygen than is actually present. ===Respiratory rate=== Humans typically breathe between 12 and 20 times per minute. ===Composition of air=== The air we inhale is roughly 21% oxygen (% by volume). Not all of the oxygen breathed in is converted into carbon dioxide; around 13% of what we breathe out is still oxygen. This is what makes resuscitation possible. Also our reliance on this relatively small amount of oxygen can cause overactivity or euphoria in pure or oxygen rich environments. ===Gas exchange=== The process of gas exchange occurs in the alveoli by passive diffusion of gasses between the alveolar gas and the blood passing by in the lung capillaries. Once in the blood, the heart powers the flow dissolved gasses around the body in the circulation. ===References=== * {{cite journal | author=Parkes M | title=Breath-holding and its breakpoint. | journal=Exp Physiol | volume=91 | issue=1 | pages=1–15 | year=2006 | id={{PMID|16272264}}}} ''[http://ep.physoc.org/cgi/content/full/91/1/1 Full text]'' ==Blood pressure== [[Image:Sphygmomanometer.jpg| 250 px]] [[Image:Sphygmomanometer1.jpg| 250 px]] [[Image:Electronic tensiometre.jpg| 250 px]] [[Image:Digital Blood Pressure Monitor.jpg| 250 px]] [[Image:Blood pressure on Omron RX 20050604.jpg| 250 px]] [[Image:Valsalva2.jpg| 250 px]] [[Image:Korotkow_deutsch.png| 250 px]] == External links == *[http://www.3dscience.com/popup.php?title=Heart%20Beat%20with%20Anterior%20Cut&url=http://www.3dscience.com/img/Products/Animations/heartbeat_anterior_cut_clip.mov 3D Animated Heart with Anterior Cut] - life-like 3D human heart animation with anterior cut. *[http://www.3dscience.com/popup.php?title=Heart%20Beat&url=http://www.3dscience.com/img/Products/Animations/heartbeat_base_clip.mov 3D Animated Heart Beat] - life-like 3D human heart animation. *[http://www.vimo.com/heart American Heart Month] - National month devoted to discussion of heart disease. *[http://rad.usuhs.edu/medpix/master.php3?mode=topic_images&recnum=7747&quiz=#top MedPix: Radiologic Anatomy of Lung] *[http://www.emedicine.com/ped/topic2902.htm eMedicine: Surgical anatomy of the heart] *[http://library.thinkquest.org/C003758/home.htm Very Comprehensive Heart Site] *[http://www.invisionguide.com/heart The InVision Guide to a Healthy Heart] An interactive website *[http://web.archive.org/web/20060511164846/http://www.abc.net.au/sydney/stories/s1572459.htm Self Improvement Wednesday] - ABC 702 Drive audio *[http://www.heartone.com/index.php?option=com_wrapper&Itemid=96 3D Animated Heart] - A great resource to view and interact with the anatomy of a 3 dimensional heart *[http://www.emc.maricopa.edu/faculty/farabee/BIOBK/BioBookcircSYS.html The circulatory system] *[http://www.easyrashi.com/TEFILLIN/sternum.htm The position of the heart] *[http://www.americanheart.org American Heart Association] * {{GPnotebook|-1281753041}} * {{FPnotebook|LUN102}} ==References== <references/> {{BookCat}} avzltk0sj1h3semi3p6fzxq8yfcmzzb 0 134243 4634063 4585754 2026-05-04T12:20:24Z Jcb 90773 4634063 wikitext text/x-wiki {{:Radiation_Oncology/Uterus:TOC}} <big>'''Uterine Papillary Serous Carcinoma'''</big> ==Overview== *''Please also see [[Radiation_Oncology/Endometrium/Overview|Endometrium Overview]] page'' *First identified at Stanford in 1982, where it comprised ~10% of Stage I endometrial CA but resulted in 50% of relapses. Many relapses were characterized by upper abdominal failure *5-year disease-specific survival is worse for USC compared with grade 3 endometrioid carcinoma **Stage I USC 72% vs ECCG3 76% (NS) **Stage I/II USC 74% vs ECCG3 85% (SS) **Stage III/IV USC 33% vs ECCG3 54% (SS) *Due to similar behavior as ovarian carcinoma, adjuvant abdominal radiation was proposed. *GOG started a trial in 1986 (GOG 94) to evaluate treatment of [[Radiation_Oncology/Endometrium/Locally_Advanced_Stage#Whole_abdominal_irradiation|advanced]] endometrial cancer with whole abdominal RT (WART), pelvic RT, and para-aortic boost as necessary. Eligible patients included Stage I-II UPSC and CC. Over 50% of failures for UPSC/CC patients were within the radiation field. WART alone is not sufficient ==Pathology== *Endometrioid (75-80%) *Clear cell (5-10%) **Clear due to presence of glycogen **Tubulocystic, papillary, or solid patterns **[[w:Psammoma|Psammoma bodies]] not as common **Have to be present in at least 25-50% (depending on pathologist) of sample to qualify as clear cell **Aggressive, with myometrial invasion in ~80% *Papillary serous (1-5%) **Complex papillary architecture, similar to papillary serous CA of ovary **Presence of [[w:Psammoma|psammoma bodies]] **Marked nuclear atypia **Believed to transform from endometrial surface epithelium *Mixed pattern **Serous and endometrioid histology present next to each other in the specimen **If >50% serous component, classified as papillary serous **If 10-50% serous component, classified as mixed serous *Rare tumor types (<2%) **Mucinous, squamous cell, transitional cell, small cell ==Pathology== *'''Stanford; 1982''' {{PMID|7102898}} -- "Uterine papillary serous carcinoma: a highly malignant form of endometrial adenocarcinoma." (Hendrickson M, Am J Surg Pathol. 1982 Mar;6(2):93-108.) **Retrospective. 256 Stage I uterine adenoCA reviewed, 26 UPSC identified. High cytologic anaplasia and papillary growth pattern. Frequent LVI+, frequent Stage IC (40% vs. 12%) **Outcome: relapse rate ~50% vs. 5%; Stage IC relapse 63% vs. 30%. Tendency to relapse over peritoneal surfaces **Conclusion: Clinically aggressive, similar to ovarian CA ==Sentinel Node Staging== *'''Memorial Sloan Kettering; 2017''' (2005 - 2015) {{PMID|28258415}} -- "Survival of Patients with Serous Uterine Carcinoma Undergoing Sentinel Lymph Node Mapping." (Schiavone MB, Ann Surg Oncol. 2017 Jul;24(7):1965-1971. doi: 10.1245/s10434-017-5816-4. Epub 2017 Mar 3.) **Retrospective. 248 patients (153 SLN and 95 LND). Stage distribution comparable (I-II in 69% vs 62%, III in 31% vs 38%). Median LN removed 12 vs 21 (SS). Adjuvant chemo or chemo-RT comparable (80% vs 83%), adjuvant RT alone comparable (8% vs 7%). Median F/U 3.3 years **Outcome: 2-year PFS SLN 77% vs LND 71% (NS) **Conclusion: Incorporating SLN into staging of uterine serous cancer does not appear to compromise prognosis ==Stage I== *'''Mayo; 2007''' (1982-2005) {{PMID|17688926}} -- "Role of systematic lymphadenectomy and adjuvant therapy in stage I uterine papillary serous carcinoma." (Thomas MB, Gynecol Oncol. 2007 Aug 2; [Epub ahead of print]) **Retrospective. 42 patients (IA 15, IB 21, IC 6). 81% LND, 69% omentectomy, 45% peritoneal biopsies. Median F/U 3.2 years **Outcome: 5-year OS 85%, PFS 78%. By stage OS IA 100%, IB 89%, IC 60%. **Recurences: LN recurrence in LND 0/34 vs. no LND 1/8 (NS); none in IA regardless of post-op therapy; 0/20 IB and IC who had vaginal BT vs. 2/7 with no vaginal BT (SS). Hematogenous/peritoneal recurrence in 0/6 patients with chemo vs. 3/13 patients with no chemo. **Conclusion: Observation reasonable for IA if LND done; for IB and IC consider chemotherapy and vaginal brachytherapy *'''Yale; 1998''' {{PMID|9422561}} -- "Effective treatment of stage I uterine papillary serous carcinoma with high dose-rate vaginal apex radiation (192Ir) and chemotherapy." (Turner BC, Int J Radiat Oncol Biol Phys. 1998 Jan 1;40(1):77-84.) **Retrospective. 38 patients treated with TAH/BSO, +/-LND, with combinations of chemo and RT. 20 patients vaginal LDR with WART or WPRT (6/20 had complete surgical staging, 2/20 concurrent chemo). 18 patients vaginal HDR (15/18 had complete surgical staging, 5/18 concurrent chemo). **Outcome: 5-year OS complete surgical staging and HDR /chemo 100% vs. incomplete staging HDR/chemo 61% vs. complete staging LDR/WART 100% vs. incomplete staging LDR/WART 65%. OS by stage IA 100%, Stage IB 71%, Stage IC 40% **Toxicity: WART and/or LDR had Grade 3-4 toxicity in 15%, complications from vaginal HDR minimal **Conclusion: If complete surgical staging, can be effectively and safely treated with vaginal HDR and chemotherapy ==General== *'''Harvard; 2011''' (1980-2006) {{PMID|21963091}} -- "The importance of chemotherapy and radiation in uterine papillary serous carcinoma." (Viswanathan AN, Gynecol Oncol. 2011 Dec;123(3):542-7. doi: 10.1016/j.ygyno.2011.09.005. Epub 2011 Oct 2.) **Retrospective. 135 women, Stage I-IVA UPSC. Stage I 47%, Stage II 12%, Stage III 37%, Stage IVA 4%. Chemotherapy in 32%. Radiation in 66% (whole abdomen 24%, pelvis 31%, brachytherapy 33%). Mean F/U 5.5 years. **Outcome: Median 5-year OS 52%, RFS 42%. OS improved by paclitaxel-containing chemotherapy (HR 0.34, SS). RFS improved by radiation (HR 0.44, SS). 5-year LR 15%, reduced by RT (HR 0.2). 5-year DM 26%, not reduced by paclitaxel/carboplatin **Stage IA outcome: N=21. 5-year OS 71%. No further therapy N=17, pelvic RT N=4. Relapse in 5 patients (24%), vaginal 1, vaginal/pelvic 1, lymphatic 1, peritoneal 1, distant 1. **Toxicity: Grade 3+ in 3.5% with RT, 2.9% without RT (NS) **Conclusion: RFS was improved by radiation and chemotherapy, and should be attempted whenever feasible =="Sandwich" chemotherapy and radiation== *'''Albert Einstein College of Medicine; 2012''' {{PMID|22035806}} -- "Phase II trial of adjuvant pelvic radiation "sandwiched" between combination paclitaxel and carboplatin in women with uterine papillary serous carcinoma." (Einstein MH, Gynecol Oncol. 2012 Jan;124(1):21-5. Epub 2011 Oct 27.) **Phase II. 81 patients (89% completed chemo->RT and are reported here), surgically staged UPSC, no visible residual. Stage I/II 82%, Stage III/IV 18%. Adjuvant paclitaxel 175 mg/m2 and carboplatin AUC 6 Q3 weeks x 3 cycles, followed by RT (pelvis 45/25, PA if 2+ pelvic nodes or documented PA disease, HDR vaginal brachytherapy 5 Gy x 3 at 0.5 cm), followed by chemotherapy x 3 cycles. Protocol completion 83% **Outcome: Stage I/II OS 6.3 years, Stage III/IV OS 3.0 years. 3-year OS 84% and 50%. PFS 5.4 years and 2.1 years **Toxicity: G3/4 non-hematologic toxicity 2.5% **Conclusion: RT-chemotherapy "sandwich" is well and highly efficacious in completely resected UPSC ==Patterns of Failure== *'''Westmead Hospital, Sydney, Australia; 2009''' (1995-2006) {{PMID|19694700}} -- "Uterine papillary serous carcinoma: patterns of failure and survival." (Wang W, Aust N Z J Obstet Gynaecol. 2009 Aug;49(4):419-25.) **Retrospective. ? patients, TAH/BSO/surgical staging, majority with platinum-based chemotherapy and radiotherapy **Outcome: 2-year OS 65%, 5-year OS 43%. Macroscopic residual disease only predictor of survival (if R2, median OS 11 months). Site of recurrence vagina (n=5; for VBT 1/16 recurrences, for EBRT 4/7 recurrences), pelvic LN (n=24), para-aortic LN (n=6), inguinal LN (n=2), abdomen (n=11), and distant mets (n=7) **Conclusion: Recommend optimal cytoreduction; vaginal brachytherapy should be considered as a component of adjuvant radiotherapy. Abdominal failure most common ==Whole Abdomen RT== *'''GOG 94''' (1986-1994) **'''2006''' {{PMID|16213007}} -- "Adjuvant whole abdominal irradiation in clinical stages I and II papillary serous or clear cell carcinoma of the endometrium: a phase II study of the Gynecologic Oncology Group." (Sutton G, Gynecol Oncol. 2006 Feb;100(2):349-54.) **Phase II. 21 patients treated with TAH/BSO, PPALND, WART 30/20 and pelvic boost to 50 Gy **Outcome: >50% failures within RT field ***UPSC: 5-year OS 38%, PFS 38% ***Clear cell: 5-year OS 54%, PFS 54% **Toxicity: 17% Grade 3-4 GI toxicity (SBO, proctitis, N/V) **Conclusion: WART alone not adequate, chemotherapy needs to be a component of treatment. Clear cell better outcome than UPSC *'''Stanford; 2000''' (1979-1998) {{PMID|11020574}} -- "Treatment of high-risk uterine cancer with whole abdominopelvic radiation therapy." (Smith RS, Int J Radiat Oncol Biol Phys. 2000 Oct 1;48(3):767-78.) **Retrospective. 48 patients with Stage III-IV endometrial ACA (n=22) or Stage I-IV UPSC or CC (n=26), treated with postop WART. Median dose 30 Gy abdomen (in 1.2-1.5 Gy/fx) and 50 Gy pelvis (in 1.2-1.8 Gy/fx). PALN boost to 44 Gy in 9 patients. Vaginal brachy in 24 patients. Mean F/U 3.1 years **Outcome: 3-year OS all patients 77%, ACA 89% vs. UPSC/CC 68%; UPSC/CC Stage I-II OS 87% vs. Stage III-IV 61%; DFS 87% vs. 31% **Toxicity: major complications (SBO) 7%, no deaths, 23% required break >1 week **Conclusion: WART is safe, effective. Recommend with vaginal cuff brachy for Stage I-II. Recommend with concurrent or sequential chemo in Stage III-IV UPSC/CC until results of GOG 94 and GOG 122 become available (see [[Radiation_Oncology/Endometrium/Locally_Advanced_Stage|Advanced Stage]] chapter). ==Phosphorus-32 (P³²)== *'''HOG 97-01''' {{PMID|15721431}} -- "Intraperitoneal radioactive phosphorus (32P) and vaginal brachytherapy as adjuvant treatment for uterine papillary serous carcinoma and clear cell carcinoma: a phase II Hoosier Oncology Group (HOG 97-01) study." (Fakiris AJ, Gynecol Oncol. 2005 Mar;96(3):818-23.) **Phase II. 21 patients s/p TAH-BSO, residual peritoneal disease <3mm, negative PPALN. Intraperitoneal P-32 15 mCi within 8 weeks. Vaginal BT. Median F/U **Outcome: 2-year OS 89%, DFS 80%; recurrences 5/21, but only 2/21 intraperitoneal **Toxicity: No Grade 2-4 **Conclusion: Adjuvant intraperitoneal P-32 and vaginal BT feasible, well tolerated ==Reviews== *'''2009: SGO''' {{PMID|19592079}} [http://www.sgo.org/assets/0/58/62/AA0E178A-8533-4BCE-A64D-54000F01A21B.pdf PDF] -- "Management of women with uterine papillary serous cancer: a Society of Gynecologic Oncology (SGO) review." (Boruta DM, Gynecol Oncol. 2009 Oct;115(1):142-53.) 8lpian4ojofz3wew5ig0nhwvcc6k4pr 0 150113 4634101 4622080 2026-05-04T15:44:17Z ~2026-27032-87 3581206 I added 4634101 wikitext text/x-wiki Explorer {{honor_header|2|1975|Outreach|General Conference}} ==1. What well-balanced combination of strengths did Jesus develop as a youth? (Luke 2:52) == {{Bible verse | book = Luke | chapter = 2 | verse = 52 | version =NIV | text = And Jesus grew in wisdom and stature, and in favor with God and men. }} This verse indicates that Jesus grew mentally (''wisdom'') as well as physically (''stature''). He also grew spiritually (''in favor of God'') and emotionally (''in favor of men''). These four aspects of personal growth are the focus of the Adventist education system as well as the Pathfinder program. ==2. According to Psalm 8, what estimate does God place on your personal worth? == The New International Version translates Psalm 8 as follows: {{Bible verse | book = Psalm | chapter = 8 | verse = 1-9 | version = NIV | text =<br> :'''1''' ''O LORD, our Lord,'' ::''how majestic is your name in all the earth!'' ::''You have set your glory'' ::''above the heavens.'' :'''2''' ''From the lips of children and infants'' ::''you have ordained praise'' ::''because of your enemies,'' ::''to silence the foe and the avenger.'' :'''3''' ''When I consider your heavens,'' ::''the work of your fingers,'' ::''the moon and the stars,'' ::''which you have set in place,'' :'''4''' ''what is man that you are mindful of him,'' ::''the son of man that you care for him?'' :'''5''' ''You made him a little lower than the heavenly beings'' ::''and crowned him with glory and honor.'' :'''6''' ''You made him ruler over the works of your hands;'' ::''you put everything under his feet:'' :'''7''' ''all flocks and herds,'' ::''and the beasts of the field,'' :'''8''' ''the birds of the air,'' ::''and the fish of the sea,'' ::''all that swim the paths of the seas.'' :'''9''' ''O LORD, our Lord,'' ::''how majestic is your name in all the earth!'' }} This is saying that God sees man as the crowning (most significant) act of His creation. He made us a little lower than the angels in importance and gave us the charge to rule and manage the rest of his creation. ==3. Are names important to God? Does He know your name? (Isaiah 43:1, Exodus 33:17, Isaiah 45:4)== These three verses are quoted from the New International Version: {{Bible verse | book = Isaiah | chapter = 43 | verse = 1 | version =NIV | text =<br> :''But now, this is what the LORD says—'' :''he who created you, O Jacob,'' :''he who formed you, O Israel:'' :''"Fear not, for I have redeemed you;'' :''I have summoned you by name; you are mine.'' }} {{Bible verse | book = Exodus | chapter = 33 | verse = 17 | version =NIV | text =<br> :''And the LORD said to Moses, "I will do the very thing you have asked, because I am pleased with you and I know you by name."'' }} {{Bible verse | book = Isaiah | chapter = 45 | verse = 4 | version =NIV | text =<br> :''For the sake of Jacob my servant,'' :''of Israel my chosen,'' :''I summon you by name'' :''and bestow on you a title of honor,'' :''though you do not acknowledge me.'' }} Names are important enough to God that He has protected His own name in the Ten Commandments. He knows each of us by name which also signifies His personal interest in us individually. ==4. Demonstrate or discuss proper conversational skills, including == ===a. The proper way to talk to adults === Children should address adults using the words Mr, Mrs, and Miss outside of church, or Brother, Sister in a church setting followed by that person's last name. They should avoid using an adult's first name unless it is also used with a last name. For example, "I talked to John about borrowing his tools," would be considered disrespectful, but saying "I talked to John Smith about borrowing his tools" or "I talked to Mr. Smith about borrowing his tools" shows proper respect. When speaking to an adult (or anyone else), do not mumble. Avoid slang. Be sure to use such words as "sir," "ma'am," "please," and "thank you." Make eye contact. ===b. How to address people and make proper introductions === When addressing adults, again it is respectful to use their last names, as in "Mr Smith" or "Miss Jones." When making introductions, say a woman's name before a man's. If they are both the same gender, use the older person's name before using younger person's. For example, you would introduce Mr. Smith and Miss Jones by saying "Miss Jones, I would like for you to meet Mr. Smith." Be sure to allow room so that they may shake hands. You would introduce Mr. Smith to your friend William by saying "Mr. Smith, this is my friend William." You may then tell something about William: "William and I have known each other since the third grade." ===c. Questions to avoid === Do not comment on any physical defects in a person, or ask personal questions: *"When did you last have a shower?" *"Don't you think you should try to lose a little weight?" *"How much money do you make?" *"How old are you?" (When speaking to someone older than you) *"How is your mother?" (If mother died.) ===d. How to think of pleasant things to say === *Think of something that has happened to you in the recent past that you found pleasant and talk about that. *When talking to adults with children or grandchildren, ask about them. *Ask where the person grew up and what it was like there. *Ask if the person has a pet, and if so, what that pet's favorite thing to do is. *Tell about a recent Pathfinder event, such as a campout or a club meeting. *Tell about an honor that you have enjoyed earning, and what you had to do to earn it. ===e. How to show concern for the feelings of others === One way to show concern for others during a conversation is to practice ''active listening''. In active listening, you restate what the other person has said to you, but in different words. If you misunderstand what was said and restate it incorrectly, your partner in conversation will know and can clarify. Active listening is one way to let the other person know that you are indeed listening. One mistake that people often make in conversing is changing the subject before the partner was ready to. For example: '''Bad Form''' :Alice: "My sister was in a car accident yesterday." :Bob: "That's too bad. Did I tell you I beat level 14 in 'Mega Chipmunk Death Rally' this morning?" :Alice: "She broke her finger." :Bob: " I don't care at all." '''Better Form''' :Alice: "My sister was in a car accident yesterday." :Bob: "Your sister was in an accident? Is she OK?" :Alice: "She broke her finger." :Bob: "I hope her finger heals soon." It is also important to show concern for the person before considering other ramifications: '''Bad Form''' :Alice: "My sister was in a car accident yesterday." :Bob: "Really? She still owes me five bucks!" :Alice: "She broke her finger." :Bob: Hahaha that's funny!" '''Better Form''' :Alice: "My sister was in a car accident yesterday." :Bob: "I'm sorry to hear that. Did she go to the hospital?" ===f. What to say when you answer the door === When answering the door, if the visitor has come to speak to an adult in the family and he is known to you, invite him in while you get the person requested. If the visitor is unknown, kindly ask him to wait until you can get the person requested. If no one else is home, tell the visitor so only if you know the visitor, and ask if you can relay a message for him. ===g. How to answer the telephone correctly === When answering the phone at home, nothing beats this old classic: ''"Hello?"'' It is also good to say after this greeting the period of day, that is: {| align="center" |- |align=right|12:00 AM ||- |align=right| 11:59 AM || Morning |- |align=right|12:00 PM ||- |align=right|5:59 PM || Afternoon |- |align=right|6:00 PM ||- |align=right|8:59 PM || Evening |- |align=right|9:00 PM ||- |align=right|11:59 PM || Night |} There is no need to give out personal information by saying "Anthony residence, this is Susan," nor do you need to tell them the number they have just dialed. A simple "Hello" and a smile in your voice is all you really need. Bad Form: "What?!" Good Form: "Hello" When answering for a business, the rules change. In this case, you are expected to answer with the name of the company, as in "Campy Rockets, how may I help you?" If you ever need to answer the phone at your church, you should answer the same as if it were a business: "Northside SDA Church, how may I help you?". You don't need to say your name, unless the person on the other end of the line asks to whom he/she is speaking. ==5. If you want to use your gift of speech to God's glory, what should your prayer be? (Psalm 19:14) == {{Bible verse | book = Psalm | chapter =19 | verse = 14 | version =NIV | text =<br> :''May the words of my mouth and the meditation of my heart'' ::''be pleasing in your sight,'' ::''O LORD, my Rock and my Redeemer.'' }} ==6. List seven points showing the power of correct posture. Check your posture and body profile. Demonstrate how to stand and sit correctly. Read Education, by Ellen G. White, page 198, paragraph 3, and note the benefits mentioned that come to you as a result of correct posture. == Good posture does the following: # Provides optimal balance. # Optimizes breathing. # Affects the circulation of bodily fluids. # Reduces back pain. # Protects the joints from strain. # Expresses confidence. # Is considered an integral part of physical attractiveness. # Improves the body's ability to carry heavy loads. # Protects against spinal deformity as a person ages. ''Education'', page 198, paragraph 3 reads as follows: :''"Among the first things to be aimed at should be a correct position, both in sitting and in standing. God made man upright, and He desires him to possess not only the physical but the mental and moral benefit, the grace and dignity and self-possession, the courage and self-reliance, which an erect bearing so greatly tends to promote. Let the teacher give instruction on this point by example and by precept. Show what a correct position is, and insist that it shall be maintained."'' ===Sitting=== [[Image:Illu vertebral column.svg|thumb|250px|Vertebral column showing healthy curvature]] The spine has four normal curvatures. From top to bottom they are the cervical, thoracic, lumbar, and sacral curves. The upper three of these should be aligned as shown in the image to the right when sitting. To get them into this position, do the following: * Sit in a chair with your buttocks touching the back of the chair. * Do NOT Slouch forward. * Straighten up and accentuate the lumbar curve arching our shoulders back. Hold this position for a few seconds. * Release and relax, drawing your abdomen back into a comfortable position, but with your shoulders still straight and back. * Make sure your weight is distributed evenly on both hips. * Keep your feet flat on the floor. Your knees should be level with your hips or a bit higher. If you cannot do this and keep your feet flat on the floor, adjust your chair (if it is adjustable) or use a smaller chair. * Do not cross your legs. If working at a computer, your forearm should extend directly in front of you and remain horizontal. The wrists should arch downwards towards the keyboard. You may need to use a wrist support to help you with this. Source: http://www.globalspine.net/correct_sitting_technique.html ===Standing=== When standing, the spine should follow all four curvatures as in the image above. Observe the following points: * Hold your head up with your chin in. * Thrust the chest forward and the tummy tucked in. * Keep your knees straight. * Make sure your pelvis is not tilted (neither forward nor back). * If standing for a long period of time, rest one foot on a slightly elevated surface, such as a step. If working in the kitchen, you can open the cabinet door and rest your foot on the lower shelf. * Do not stand in the same position for a long period of time. You should change positions every 5 to 15 minutes. Source: http://www.globalspine.net/correct_standing_position.html ==7. Give two reasons why physical fitness is important and explain the relationship between proper diet, exercise, and weight control. == Exercise keeps your organs functioning properly, avoiding blockages and poor circulation. A healthy diet is also important for weight control. Excessive weight will cause diseases. On average, the number of calories you consume should equal the number of calories you burn. Calories enter the body through the things we eat and drink - in other words, from the diet. Calories are burned by physical activity. The more physically active you are, the more calories you will burn. If you consume more calories than you burn, you will gain weight. If you burn more calories than you consume, you will lose weight. If your caloric intake equals your caloric expenditure, you will maintain your current weight. This applies no matter what your weight is. There is no weight beyond which a person cannot get any heavier (unless the excess weight results in death, as it often does). ==8. Tell the importance of proper grooming, including bathing, body hygiene, breath, proper care of clothes, shoes, etc. == ===Importance=== A person with poor hygiene is unpleasant to be around. Foul odors, dirty clothing, and gross things stuck between their teeth have a tendency to drive people away. Most people will not take a habitually unclean person seriously, and will instead do everything they can to avoid that person. It is very difficult to be an effective witness for your faith under these conditions. ===Social cues=== Be on the lookout for social cues that indicate you may have a problem. If someone is continually averting their eyes from you, or you find them staring at some part of your face other than your eyes, discretely excuse yourself and have a look in a mirror. Check your teeth, and make sure your face is clean. If a person offers you a piece of gum or a breath mint, it may be a polite way of curing your bad breath. The proper response is "Thank you." Accept the breath freshener without asking why it was being offered. Perhaps you'd rather not know! ==9. Describe the proper way to wash your hair and care for your "hair tools." == Wet your hair thoroughly, being sure it is wet all the way to the scalp. Pour {{units|15-30 ml|1-2 tablespoons}} of shampoo into the palm of your hand, and then work it into the hair to form a lather. Lather the hair until all surfaces have been washed. Rinse ''thoroughly'' - if any shampoo is left in the hair, it will dry in place forming clumps of yellowish flakes. Comb or brush your hair immediately after washing it, and again several times through the day. Longer hair needs more frequent care. Very short hair may not need combing at all. When you are finished combing or brushing, run water over the comb or brush to clean it. Over time, a comb will collect a build-up of dirt which is difficult to rinse off. When this happens, run the teeth of the comb through the bristles of the brush. Rinse both. Do not share a comb, brush, hat, or other headgear with another person, as this can help the spread of lice. ==10. Describe the proper care for your hands and fingernails.== Hands should be washed frequently throughout the day, especially after using the restroom. Germs and viruses are spread by hand-contact, and washing them is an effective way to prevent their spread. Be sure to use soap on the palms, fingers, the back of the hands, and under the fingernails, and rinse well. Many people avoid handwashing because it dries their hands, but this is really an effect of improper rinsing. If you find that handwashing still dries your skin even after thorough rinsing, apply a lotion. It is even more important to wash dried, cracked skin, as the cracks offer an entry for germs into your system. Drink plenty of water to keep your skin hydrated. Fingernails should be trimmed neatly using nail clippers. Do not chew the fingernails or tear them off. Clean beneath the nails whenever you see dirt under them. ==11. Know the importance of daily "soul-grooming" and of building a Christian character and why "belonging to Christ" makes a difference in the way you dress and act. == "Soul-grooming" is done through daily communion with God. Any relationship is built by communication, and we communicate with God through prayer and by reading His Word. It is best to start the day by talking to the Lord, asking Him to be with you through the day. Time spent praying over specific temptations you face will better prepare you to resist that temptation. "Christian character" is demonstrated when you do the right thing even when it is difficult. Be in the practice of always telling the truth, and put the feelings of others ahead of your own desires. This will add compassion to your character. Knowing that you belong to Christ will give you a sense of self-worth and confidence. After all, Christ died for ''you'', so He must feel you were worth that sacrifice. Because He has forgiven you of your sins, you will want to treat His other children with love and respect. You will find yourself wanting to lead others to Him, and help them resist temptation. People go through several important physiological changes during the pre-teen and teen years. They find that their sexual desires begin to waken, and sometimes they may find them difficult to control. Dressing modestly will help others to control these desires, while dressing suggestively and engaging in flirtation can unnecessarily excite a person of the opposite sex. When you belong to Christ, you will not willingly become a stumbling block to another person's salvation. You will find your self-worth anchored in being a child of the King rather than through gaining the attention and acceptance of other people. ==12. Discuss scriptural guidelines that will help you cope with your sexuality and keep your thoughts-life clean. Discuss intelligently the do's and don'ts" of dating.== ===Scriptural Guidelines=== {{Bible verse | book = Philippians | chapter = 4 | verse = 8 | version = [http://ebible.org/web/web.htm World English Bible] | text = Finally, brothers, whatever things are true, whatever things are honorable, whatever things are just, whatever things are pure, whatever things are lovely, whatever things are of good report; if there is any virtue, and if there is any praise, think about these things. }} {{Bible verse | book = 1 Corinthians | chapter = 6 | verse = 9, 10 | version = [http://ebible.org/web/web.htm World English Bible] | text = Or don’t you know that the unrighteous will not inherit the Kingdom of God? Don’t be deceived. Neither the sexually immoral, nor idolaters, nor adulterers, nor male prostitutes, nor homosexuals, nor thieves, nor covetous, nor drunkards, nor slanderers, nor extortioners, will inherit the Kingdom of God. }} The longer one thinks about sinful things, the more likely that person is to engage in that activity. Philippians 4:8 recommends against impure thoughts. {{Bible verse | book = Exodus | chapter = 20 | verse = 14 | version = [http://ebible.org/web/web.htm World English Bible] | text = You shall not commit adultery. }} Adultery and sexual immorality are any sexual activities that take place outside the marriage. {{Bible verse |book = Matthew |chapter =5 | version = [http://ebible.org/web/web.htm World English Bible] |verse = 27,28 | text = "You have heard that it was said, 'Do not commit adultery.' But I tell you that anyone who looks at a woman lustfully has already committed adultery with her in his heart. }} This text tells us that adultery is a sin that a person can commit in private. Do not entertain ideas of sexual immorality, even in your own private thoughts. ===Dating=== When inviting a person on a date, it is better to immediately reveal what you have in mind rather than asking if the person is busy. Asking if the person is busy may cause them to feel cornered. After admitting that they are not busy, they will feel trapped if they do not like the plans you are proposing. Make sure you go to the door when you arrive. It is rude to stay in the car and honk the horn, Honking the horn will also disturb the neighbors. If invited inside to meet the parents, do so as pleasantly as you can. Do not attempt to get your date to do anything you know violates either his/her or your own sense of morality. Pay attention to your date during your time together. It is rude to invite someone on a date and then spend most of your time together focusing on someone else (of either sex). It goes without saying that you should never flirt with someone else during the date. When the date has concluded, escort your date back to the front door. Don't just dump her out of the car at the curb. Make sure you return home at the appointed time. Doing otherwise will make you look bad to your date's parents, and may get your date into trouble. This will not reflect well on you. ==13. List four reasons why your face is important to you, and show how the way you exercise and sleep can improve your facial appearance. What relationship do thoughts have to facial "print-out"? Describe proper facial care. == ===Importance=== Reasons why your face is important: a It is the first thing that others see when they look at you. b It is the first thing that you see (when you look in the mirror). c It is one of the main communicators of your emotions. d Most people define "cute" or "handsome" based on the way a person's face appears. e People recognize you more by your face than by any other part of your body. Your face ''defines'' you. ===Sleep and Exercise=== Because your face is so central to who you are, you should take care to make it look its best. Lack of sleep will not only make you tired, it will make you ''look'' tired too. Regular (and sufficient) sleep will keep you from looking tired all the time. Regular exercise will do this too, because if you exercise regularly, you will not only be more fit, you will have more energy. ===Facial Print-out=== People can adopt a facial expression as a voluntary action. However, because expressions are closely tied to emotion, they are more often involuntary. It can be nearly impossible to avoid expressions for certain emotions, even when it would be strongly desirable to do so; a person who is trying to avoid insult to an individual he or she finds highly unattractive might nevertheless show a brief expression of disgust before being able to resume a neutral expression. The close link between emotion and expression can also work in the other direction; it has been observed that voluntarily assuming an expression can actually cause the associated emotion. ===Facial Care=== The most important aspect of facial care is regular and frequent cleansing with soap and water. Begin by wetting the hands and face with water, then lather the hands with soap and apply to the face. Work the soap by rubbing over the face. Then rinse thoroughly. If desired, apply lotion to moisture the skin, but little proof exists that this provides any health benefits at all. ==14. Know the rules of table etiquette which make it easier for you and those around you, such as what to do with your knife and fork after using them. Know how to be a welcome dinner guest and a joy to your hostess. == Table manners are the etiquette used when eating. This includes the appropriate use of utensils. Different cultures have different standards for table manners. Many table manners evolved out of practicality. For example, it is generally impolite to put elbows on tables since doing so creates a risk of tipping over bowls and cups. Within different families or groups, there may be less rigorous enforcement of some traditional table manners of their culture while still maintaining others. For example, some families ignore elbows on the table or mixing of foods. ===Table Layout=== [[File:PlaceSettingCharger.jpg|thumb|300px|A properly set table]] * Bread plates are to the left of the main plate, beverage glasses are to the right. * Salad fork, knife, and soup spoon are further from the main plate than the main course knife, fork, and spoon. Dessert utensils are either placed above the main plate or served with dessert. * The sharp edge of the knife blade faces the plate. ===General Behavior=== * Always chew with your mouth closed. * Do not talk at an excessively loud volume. * Refrain from coughing, sneezing or blowing nose at the table. * Never tilt back your chair while at the table, or at any other time. * Do not make unbecoming noises while eating. * Do not play with food or table utensils. * Do not single out or chastise someone who has shown poor table manners. * Do not put your elbows on the table or slouch. It is acceptable, however, to rest forearms, up to the elbow, on the table. * Always ask the host or hostess to be excused before leaving the table. * Do not stare at anyone while he or she is eating. * Never talk on your phone at the table. If urgent, ask host or hostess to be excused, and go outside. Apologize after returning. ===Utensils=== * Do not eat food with your fingers unless you are eating foods customarily eaten with fingers, such as bread, French fries, chicken wings, pizza, etc. At more formal occasions, it is acceptable to eat asparagus or some romaine lettuce dishes with ones hands. However, as this is an obscure etiquette rule, in more casual settings, it is customary to use utensils. * The fork may be used either in the American (use the fork in your left hand while cutting; switch to right hand to pick up and eat a piece) or the Continental (fork remains in the left hand) fashion—either is now acceptable. * The fork is used to convey any solid food to the mouth. * The knife blade should be placed on the edge of your plate when not in use. The blade should always face inward. * When you have finished eating soup, the spoon should be placed to the side of the saucer, not left in the bowl. * Keep your napkin on your lap. At more formal occasions all diners will wait to place their napkins on their laps until the host or hostess places his or her napkin on his or her lap. * When eating barbecue or some other messy foods, a 'bib' napkin may be provided for and used by adults. Usually these foods are also eaten by hand, and wet wipes or paper napkins should be used to clean the hands. * When using paper napkins, never ball them up or allow stains to show. * Use your silverware from the outside moving inward toward the main plate. (Salad fork, knife and soup spoon are further from the main plate than the main course knife, fork and spoon. Dessert utensils are either placed above the main plate or served with dessert.) ===Dining=== * A prayer or 'blessing' may be customary in some families, and the guests should join in even if they are not religious or do not follow the same religion. Most prayers are made by the host before the meal is eaten. Instead or in addition, a 'toast' may be offered. * Do not start eating until (a) every person is served or (b) those who have not been served request that you begin without waiting. At more formal occasions all diners will wait to begin until the hostess or host lifts a fork or spoon. * When a dish is presented 'family style', the food is served to one's plate and then passed on to the next person. put the food on your left, take some and pass to the person next to you. * When serving, serve from the left and pick up the dish from the right. Beverages are both served and removed from the right. * Eat soup noiselessly and with the side of the spoon. * Hot drinks should never be poured into the saucer to cool but should be sipped from the cup. Alternatively, ice may be used to cool them. * Seasoning ones meal prior to tasting can be considered rude and may insult the chef. === At the end of the meal === * It is acceptable in most places to not finish all of the food on your plate. * When finished with your meal, place your knife and fork with handles at the 4 o'clock position and the tines of the fork down to signal to the server you are done. * Except in a public restaurant, do not ask to take some of your uneaten food away from the meal after it ends, and never when attending a formal dinner. ==15. List ten principles to help you overcome self-consciousness and social embarrassment. == The most important thing for a Christian to remember is that no matter how awkward they are, the Ruler of the Universe loves them and gave His life for them. Spend some time preparing for a social event. Make sure you are clean, your hair is clean, and combed, and your breath is fresh. Put on a clean set of clothes before setting out, and wear deodorant or antiperspirant. Antiperspirant will keep you from sweating. Deodorant will keep your sweat from smelling bad. It also helps to recognize that you are not the only person who may feel self-conscious in a social situation. Every other boy and girl your age will also be worrying about doing something goofy, so the chances are pretty good that if you make an embarrassing error, everyone else will be so preoccupied with themselves that they do not notice. Still, sometimes you ''will'' do something embarrassing, and others ''will'' notice. In this case, it is best to acknowledge your fault, ''admit'' embarrassment, and try to see the humor in the situation. That can be ''very'' hard in the heat of the moment, but if you can pull it off with grace, people will be quick to forgive, and they will not think poorly of you. So here are ten principles to remember: #Christ died for you #Make sure your hair is clean and combed. #Make sure your face and body are clean #Wear deodorant/antiperspirant. #Brush your teeth and have a breath mint or sugar-free gum #You are not the only self-conscious person #People are unlikely to be focusing on ''you'' #Admit your mistakes #Admit your embarrassment #A little humor goes a long way ==For Young Ladies== ===16. Demonstrate two exercises that will improve your posture. === Many different exercises might be chosen to improve different aspects of one's posture, but in light of proper posture as detailed in requirement 6, the following two exercises are chosen as especially important for young women: ====1. Lying on your back==== Lie on your back on the floor with your knees bent and feet flat on the floor. * Use your abdominal and gluteal (buttock) muscles to roll your bottom a little and press your lower back against the floor. * Maintain the pressure for 5 – 10 seconds and slowly let go. * Repeat 10 times. Try to do the same exercise while standing with your legs straight and against a wall. This exercise strengthens the abdominal and gluteal muscles and helps to focus on the pelvis position in order not to exaggerate the lumbar lordosis (an inward curvature of the lumbar and cervical segments of the spine) as is often seen with young women and girls, giving them lot of problems during pregnancy with peri-partus-pelvic pain. ====2. Sitting on a chair==== * Lift your arms to a horizontal position * Swing them slowly outwards and backwards as far as possible. * Repeat 10 times. This exercise strengthens the muscles of the back of your shoulders, stretches the muscles in the front of your chest, and thus works towards lesser thoracic kyphosis (curvature of the upper spine) and makes more room for your lungs and heart. ===17. Know how to choose a hairstyle that makes you look your best. === The choice of a hairstyle is a personal one, but if the goal is to look your best, the generally accepted advice is to style it to even out the shape of your head and face. A girl with a long, narrow face should not choose a hairstyle that makes her face look a little wider. A girl with a round, wide face should not use her hair to lengthen her face by not exposing more of her forehead and not adding height. ===18. Tell the proper style of clothes to wear if you are tall, plump, short, or thin or have a heavy hipline or full bosom. === The most important aspect for a Christian woman to consider when choosing her clothing is modesty. Immodest clothing will make it difficult for young men to control their thoughts. Stripes can be used to emphasize or play down height or width. Vertical stripes emphasize height while playing down width, while horizontal stripes emphasize width while playing down height. Therefore, a tall, thin girl should wear horizontal stripes, and a short, plump girl should wear vertical stripes. Tall girls may not wish to wear shoes with high heels, while shorter girls may benefit from them. A girl with a weight problem should not wear tight clothing as that accentuates her problem. Loose-fitting clothing is always a better choice. ===19. Demonstrate the correct way to put on a coat or outer wrap.=== This requirement assumes that the young lady will be assisted with her coat or wrap by a young man. In this case, the young man should remove the coat from the hanger and hold the coat along the shoulder seams (he should grasp the right shoulder seam with his right hand and the left seam with his left hand so that the back of the garment is facing him). He should then open the coat to reveal the sleeve holes and offer it to the young lady. She should not need to reach up or down to slip her arm into the sleeve of the coat. Once she has both her arms in the sleeves, the young man should release the coat or wrap and the young lady may button it herself (if she so chooses). ==For Young Men== ===16. Tell how to have well-groomed hair and how to choose a hairstyle that makes you look your best. === Wash your hair regularly, and comb it several times between shampooing. Hair at any length should still be washed daily or every other day. The choice of a hairstyle is a personal one, but if the goal is to look your best, the generally accepted advice is to style it to even out the shape of your head. This helps in finding suitable touches for everyone. ===17. List clothing rules and the proper style of clothes to wear if you are tall and thin, or short and chubby. === A tall, thin boy should wear a shirt with horizontal stripes, and a short stocky boy should wear a shirt with vertical stripes. Horizontal stripes emphasize width and play down height. Vertical stripes emphasize height and play down width. ===18. Tell why Christians should practice good manners. Demonstrate how to seat a girl or woman at a table and how to properly escort her from home to a social function.=== Christians should practice good manners because they are ambassadors of Christ. Rudeness on the part of a Christian reflects poorly on all Christians. When escorting a girl or a woman, the boy should offer her the crook of his elbow. The woman may slip her arm around his, and they may walk arm-in-arm to her seat. The boy then pulls her seat out for her so that she may step in front of it. As she sits, he should push the seat forward. This can and should be practiced in a club environment, but the instructor must be vigilant that no one tries to pull the chair under the person sitting, this may cause serious damages. ==References== [[{{BOOKCATEGORY|Adventist Youth Honors Answer Book}}/Completed Honors|{{SUBPAGENAME}}]] f84ng0ro2i89tsgyctlu5jm3uqd22pa 0 151867 4634218 3175442 2026-05-05T04:27:36Z Superamario64 3581328 Math formatting edits (\left and \right) 4634218 wikitext text/x-wiki <noinclude>{{navigation|Book=Linear Algebra |current=Topic: Voting Paradoxes |previous=Topic: Crystals |next=Topic: Dimensional Analysis}}</noinclude> Imagine that a Political Science class studying the American presidential process holds a mock election. Members of the class are asked to rank, from most preferred to least preferred, the nominees from the Democratic Party, the Republican Party, and the Third Party, and this is the result (<math>></math> means "is preferred to"). <center> {|cellspacing=0px cellpadding=5| |- | style="font-style:italic; font-weight:normal; text-align:right; border-right: solid 2px black; border-bottom:solid 2px black;"| Preference order &nbsp; | style="font-style:italic; font-weight=normal; text-align:left; border-bottom:solid 2px black;" | &nbsp; Number with <br> &nbsp; that preference |- |style="text-align:right; border-right: solid 2px black"| Democrat > Republican > Third &nbsp; |style="text-align:left;"| &nbsp; 5 |- |style="text-align:right; border-right: solid 2px black"| Democrat > Third > Republican &nbsp; |style="text-align:left;"| &nbsp; 4 |- |style="text-align:right; border-right: solid 2px black"| Republican > Democrat > Third &nbsp; |style="text-align:left;"| &nbsp; 2 |- |style="text-align:right; border-right: solid 2px black"| Republican > Third > Democrat &nbsp; |style="text-align:left;"| &nbsp; 8 |- |style="text-align:right; border-right: solid 2px black"| Third > Democrat > Republican &nbsp; |style="text-align:left;"| &nbsp; 8 |- |style="text-align:right; border-right: solid 2px black; border-bottom:solid 2px black;"| Third > Republican > Democrat &nbsp; |style="text-align:left; border-bottom:solid 2px black;"| &nbsp; 2 |- |style="text-align:right; border-right: solid 2px black"|Total &nbsp; |style="text-align:left;"| &nbsp; 29 |} </center> What is the preference of the group as a whole? Overall, the group prefers the Democrat to the Republican by five votes; seventeen voters ranked the Democrat above the Republican versus twelve the other way. And, overall, the group prefers the Republican to the Third's nominee, fifteen to fourteen. But, strangely enough, the group also prefers the Third to the Democrat, eighteen to eleven. <center> [[Image:Linalg_voting_diagram_1.png|200px]]‎ </center> {{anchor|voting paradox}}This is an example of a '''voting paradox''', specifically, a '''majority cycle'''. Voting paradoxes are studied in part because of their implications for practical politics. For instance, the instructor can manipulate the class into choosing the Democrat as the overall winner by first asking the class to choose between the Republican and the Third, and then asking the class to choose between the winner of that contest, the Republican, and the Democrat. By similar manipulations, any of the other two candidates can be made to come out as the winner. (In this Topic we will stick to three-candidate elections, but similar results apply to larger elections.) Voting paradoxes are also studied simply because they are mathematically interesting. {{anchor|rational preference}}One interesting aspect is that the group's overall majority cycle occurs despite that each single voters's preference list is '''rational'''&mdash; in a straight-line order. That is, the majority cycle seems to arise in the aggregate, without being present in the elements of that aggregate, the preference lists. Recently, however, linear algebra has been used {{harv|Zwicker|1991}} to argue that a tendency toward cyclic preference is actually present in each voter's list, and that it surfaces when there is more adding of the tendency than cancelling. For this argument, abbreviating the choices as <math>D</math>, <math>R</math>, and <math>T</math>, we can describe how a voter with preference order <math>D>R>T</math> contributes to the above cycle. <center> [[Image:Linalg_voting_diagram_2.png|175px]] </center> (The negative sign is here because the arrow describes <math>T</math> as preferred to <math>D</math>, but this voter likes them the other way.) The descriptions for the other preference lists are in the ''Voting preferences'' table below. Now, to conduct the election we linearly combine these descriptions; for instance, the Political Science mock election :<math>5\cdot\,</math>[[Image:Linalg_voting_diagram_43.png|100px]]<math>\,+4\cdot\,</math>[[Image:Linalg_voting_diagram_44.png|100px]]<math>\,+\cdots+2\cdot\,</math>[[Image:Linalg_voting_diagram_45.png|100px]] yields the circular group preference shown earlier. Of course, taking linear combinations is linear algebra. The above cycle notation is suggestive but inconvienent, so we temporarily switch to using column vectors by starting at the <math>D</math> and taking the numbers from the cycle in counterclockwise order. Thus, the mock election and a single <math>D>R>T</math> vote are represented in this way. :<math> \begin{pmatrix} 7 \\ 1 \\ 5 \end{pmatrix} \quad\text{and}\quad \begin{pmatrix} -1 \\ 1 \\ 1 \end{pmatrix} </math> We will decompose vote vectors into two parts, one cyclic and the other acyclic. For the first part, we say that a vector is '''purely cyclic''' if it is in this subspace of <math>\mathbb{R}^3</math>. :<math> C =\left\{\begin{pmatrix} k \\ k \\ k \end{pmatrix} \,\big|\, k \in\mathbb{R}\right\} =\left\{k\cdot\begin{pmatrix} 1 \\ 1 \\ 1 \end{pmatrix} \,\big|\, k \in\mathbb{R}\right\} </math> For the second part, consider the subspace (see [[#exer:PerpIsSubSp|Problem 6]]<!--\ref{exer:PerpIsSubSp}-->) of vectors that are perpendicular to all of the vectors in <math>C</math>. :<math> C^\perp =\left\{\begin{pmatrix} c_1 \\ c_2 \\ c_3 \end{pmatrix} \,\big|\, \begin{pmatrix} c_1 \\ c_2 \\ c_3 \end{pmatrix}\cdot\begin{pmatrix} k \\ k \\ k \end{pmatrix} =0 \text{ for all } k\in\mathbb{R}\right\} </math> ::<math> =\left\{\begin{pmatrix} c_1 \\ c_2 \\ c_3 \end{pmatrix} \,\big|\, c_1+c_2+c_3=0\right\} =\left\{c_2\begin{pmatrix} -1 \\ 1 \\ 0 \end{pmatrix} +c_3\begin{pmatrix} -1 \\ 0 \\ 1 \end{pmatrix} \,\big|\, c_2,c_3\in\mathbb{R}\right\} </math> (Read that aloud as "<math>C</math> perp".) So we are led to this basis for <math>\mathbb{R}^3</math>. :<math> \left\langle \begin{pmatrix} 1 \\ 1 \\ 1 \end{pmatrix}, \begin{pmatrix} -1 \\ 1 \\ 0 \end{pmatrix}, \begin{pmatrix} -1 \\ 0 \\ 1 \end{pmatrix} \right\rangle </math> We can represent votes with respect to this basis, and thereby decompose them into a cyclic part and an acyclic part. ''(Note for readers who have covered the optional section in this chapter: that is, the space is the direct sum of <math>C</math> and <math>C^\perp</math>.)'' For example, consider the <math>D>R>T</math> voter discussed above. The representation in terms of the basis is easily found, :<math>\begin{array}{rcl} \begin{array}{*{3}{rc}r} c_1 &- &c_2 &- &c_3 &= &-1 \\ c_1 &+ &c_2 & & &= &1 \\ c_1 & & &+ &c_3 &= &1 \end{array} &\xrightarrow[-\rho_1+\rho_3]{-\rho_1+\rho_2}\; \xrightarrow[]{(-1/2)\rho_2+\rho_3} &\begin{array}{*{3}{rc}r} c_1 &- &c_2 &- &c_3 &= &-1 \\ & &2c_2 &+ &c_3 &= &2 \\ & & & &(3/2)c_3 &= &1 \end{array} \end{array} </math> so that <math>c_1=1/3</math>, <math>c_2=2/3</math>, and <math>c_3=2/3</math>. Then :<math> \begin{pmatrix} -1 \\ 1 \\ 1 \end{pmatrix} =\frac{1}{3}\cdot\begin{pmatrix} 1 \\ 1 \\ 1 \end{pmatrix} +\frac{2}{3}\cdot\begin{pmatrix} -1 \\ 1 \\ 0 \end{pmatrix} +\frac{2}{3}\cdot\begin{pmatrix} -1 \\ 0 \\ 1 \end{pmatrix} =\begin{pmatrix} 1/3 \\ 1/3 \\ 1/3 \end{pmatrix} +\begin{pmatrix} -4/3 \\ 2/3 \\ 2/3 \end{pmatrix} </math> gives the desired decomposition into a cyclic part and an acyclic part. :[[Image:Linalg_voting_diagram_3.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_4.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_5.png|x100px]] Thus, this <math>D>R>T</math> voter's rational preference list can indeed be seen to have a cyclic part. The <math>T>R>D</math> voter is opposite to the one just considered in that the "<math>></math>" symbols are reversed. This voter's decomposition [[Image:Linalg_voting_diagram_6.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_7.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_8.png|x100px]] shows that these opposite preferences have decompositions that are opposite. {{anchor|spin}}We say that the first voter has positive '''spin''' since the cycle part is with the direction we have chosen for the arrows, while the second voter's spin is negative. The fact that that these opposite voters cancel each other is reflected in the fact that their vote vectors add to zero. This suggests an alternate way to tally an election. We could first cancel as many opposite preference lists as possible, and then determine the outcome by adding the remaining lists. The rows of the table below contain the three pairs of opposite preference lists. The columns group those pairs by spin. For instance, the first row contains the two voters just considered. <center>{{anchor|voting}}<!--\label{table:Voting}--> {|border=1 cellspacing=0 |+Voting preferences |- |style="font-style:italic; text-align:center"|positive sign |style="font-style:italic; text-algin:center"|negative spin |- ||Democrat > Republican > Third <br> [[Image:Linalg_voting_diagram_9.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_10.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_11.png|x100px]] ||Third > Republican > Democrat <br> [[Image:Linalg_voting_diagram_12.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_13.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_14.png|x100px]] |- ||Republican > Third > Democrat <br> [[Image:Linalg_voting_diagram_15.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_16.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_17.png|x100px]] ||Democrat > Third > Republican <br> [[Image:Linalg_voting_diagram_18.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_19.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_20.png|x100px]] |- ||Third > Democrat > Republican <br> [[Image:Linalg_voting_diagram_21.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_22.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_23.png|x100px]] ||Republican > Democrat > Third <br> [[Image:Linalg_voting_diagram_24.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_25.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_26.png|x100px]] |} </center> If we conduct the election as just described then after the cancellation of as many opposite pairs of voters as possible, there will be left three sets of preference lists, one set from the first row, one set from the second row, and one set from the third row. We will finish by proving that a voting paradox can happen only if the spins of these three sets are in the same direction. That is, for a voting paradox to occur, the three remaining sets must all come from the left of the table or all come from the right (see [[#exer:CancelPolSci|Problem 3]]<!--\ref{exer:CancelPolSci}-->). This shows that there is some connection between the majority cycle and the decomposition that we are using---a voting paradox can happen only when the tendencies toward cyclic preference reinforce each other. For the proof, assume that opposite preference orders have been cancelled, and we are left with one set of preference lists from each of the three rows. Consider the sum of these three (here, the numbers <math>a</math>, <math>b</math>, and <math>c</math> could be positive, negative, or zero). :[[Image:Linalg_voting_diagram_27.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_28.png|x100px]]<math>\,+\,</math>[[Image:Linalg_voting_diagram_29.png|x100px]]<math>\,=\,</math>[[Image:Linalg_voting_diagram_30.png|x100px]] A voting paradox occurs when the three numbers on the right, <math>a-b+c</math> and <math>a+b-c</math> and <math>-a+b+c</math>, are all nonnegative or all nonpositive. On the left, at least two of the three numbers, <math>a</math> and <math>b</math> and <math>c</math>, are both nonnegative or both nonpositive. We can assume that they are <math>a</math> and <math>b</math>. That makes four cases: the cycle is nonnegative and <math>a</math> and <math>b</math> are nonnegative, the cycle is nonpositive and <math>a</math> and <math>b</math> are nonpositive, etc. We will do only the first case, since the second is similar and the other two are also easy. So assume that the cycle is nonnegative and that <math>a</math> and <math>b</math> are nonnegative. The conditions <math>0\leq a-b+c</math> and <math>0\leq -a+b+c</math> add to give that <math>0\leq 2c</math>, which implies that <math>c</math> is also nonnegative, as desired. That ends the proof. This result says only that having all three spin in the same direction is a necessary condition for a majority cycle. It is not sufficient; see [[#exer:VoterCondNotSuff|Problem 4]]<!--\ref{exer:VoterCondNotSuff}-->. Voting theory and associated topics are the subject of current research. There are many intriguing results, most notably the one produced by K. Arrow {{harv|Arrow|1963}}, who won the Nobel Prize in part for this work, showing that no voting system is entirely fair (for a reasonable definition of "fair"). For more information, some good introductory articles are {{harv|Gardner|1970}}, {{harv|Gardner|1974}}, {{harv|Gardner|1980}}, and {{harv|Neimi|Riker 1976}}. A quite readable recent book is {{harv|Taylor|1995}}. The long list of cases from recent American political history given in {{harv|Poundstone|2008}} show that manipulation of these paradoxes is routine in practice (and the author proposes a solution). This Topic is largely drawn from {{harv|Zwicker|1991}}. ''(Author's Note: I would like to thank Professor Zwicker for his kind and illuminating discussions.)'' == Exercises == {{TextBox|1= ;Problem 1{{anchor|exer:IrrIndVote}}: <!--\label{exer:IrrIndVote}--> Here is a reasonable way in which a voter could have a cyclic preference. Suppose that this voter ranks each candidate on each of three criteria. <ol type=1 start=1> <li> Draw up a table with the rows labelled "Democrat", "Republican", and "Third", and the columns labelled "character", "experience", and "policies". Inside each column, rank some candidate as most preferred, rank another as in the middle, and rank the remaining oneas least preferred. <li> In this ranking, is the Democrat preferred to the Republican in (at least) two out of three criteria, or vice versa? Is the Republican preferred to the Third? <li> Does the table that was just constructed have a cyclic preference order? If not, make one that does. </ol> So it is possible for a voter to have a cyclic preference among candidates. The paradox described above, however, is that even if each voter has a straight-line preference list, a cyclic preference can still arise for the entire group. }} {{TextBox|1= ;Problem 2{{anchor|exer:VoteCalcTable}}: <!--\label{exer:VoteCalcTable}--> Compute the values in the table of decompositions. }} {{TextBox|1= ;Problem 3{{anchor|exer:CancelPolSci}}: <!--\label{exer:CancelPolSci}--> Do the cancellations of opposite preference orders for the Political Science class's mock election. Are all the remaining preferences from the left three rows of the table or from the right? }} {{TextBox|1= ;Problem 4{{anchor|exer:VoterCondNotSuff}}: <!--\label{exer:VoterCondNotSuff}--> The necessary condition that is proved above&mdash;a voting paradox can happen only if all three preference lists remaining after cancellation have the same spin&mdash;is not also sufficient. <ol type=1 start=1> <li> Continuing the positive cycle case considered in the proof, use the two inequalities <math>0\leq a-b+c</math> and <math>0\leq -a+b+c</math> to show that <math>|a-b|\leq c</math>. <li> Also show that <math>c\leq a+b</math>, and hence that <math>|a-b|\leq c\leq a+b</math>. <li> Give an example of a vote where there is a majority cycle, and addition of one more voter with the same spin causes the cycle to go away. <li> Can the opposite happen; can addition of one voter with a "wrong" spin cause a cycle to appear? <li> Give a condition that is both necessary and sufficient to get a majority cycle. </ol> }} {{TextBox|1= ;Problem 5: A one-voter election cannot have a majority cycle because of the requirement that we've imposed that the voter's list must be rational. <ol type=1 start=1> <li> Show that a two-voter election may have a majority cycle. (We consider the group preference a majority cycle if all three group totals are nonnegative or if all three are nonpositive---that is, we allow some zero's in the group preference.) <li> Show that for any number of voters greater than one, there is an election involving that many voters that results in a majority cycle. </ol> }} {{TextBox|1= ;Problem 6{{anchor|exer:PerpIsSubSp}}: <!--\label{exer:PerpIsSubSp}--> Let <math>U</math> be a subspace of <math>\mathbb{R}^3</math>. Prove that the set <math>U^\perp=\{\vec{v}\,\big|\,\vec{v}\cdot\vec{u}=0 \text{ for all } \vec{u}\in U\}</math> of vectors that are perpendicular to each vector in <math>U</math> is also a subspace of <math>\mathbb{R}^3</math>. }} <noinclude> [[/Solutions/]] ==References== * {{citation|first=J.|last=Arrow|title=Social Choice and Individual Values|publisher=Wiley|year=1963}}. * {{citation|first=Martin|last=Gardner|title=Mathematical Games, Some mathematical curiosities embedded in the solar system|journal=Scientific American|year=April 1970|pages=108-112}}. * {{citation|first=Martin|last=Gardner|title=Mathematical Games, On the paradoxical situations that arise from nontransitive relations|journal=Scientific American|year=October 1974}}. * {{citation|first=Martin|last=Gardner|title=Mathematical Games, From counting votes to making votes count: the mathematics of elections|journal=Scientific American|year=October 1980}}. * {{citation|first1=G.|last1=Neimi|first2=W.|last2=Riker|title=The Choice of Voting Systems|journal=Scientific American|year=June 1976|pages=21-27}}. * {{citation|first=W.|last=Poundstone|title=Gaming the vote|publisher=Hill and Wang|year=2008|ISBN=978-0-8090-4893-9}}. * {{citation|first=Alan D.|last=Taylor|title=Mathematics and Politics: Strategy, Voting, Power, and Proof|publisher=Springer-Verlag|year=1995}}. * {{citation|first=S.|last=Zwicker|title=The Voters' Paradox, Spin, and the Borda Count|journal=Mathematical Social Sciences|year=1991|volume=22|pages=187-227}} {{navigation|Book=Linear Algebra |current=Topic: Voting Paradoxes |previous=Topic: Crystals |next=Topic: Dimensional Analysis}} {{BookCat}} </noinclude> ax33o0ln6e9ymioahgn8hbmqtdhud44 4 155682 4634064 4634024 2026-05-04T12:21:41Z Kingofnuthin 3566511 /* Introduce speedy deletion criteria? */ Reply 4634064 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left<!--|limit=2-->}} Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks. {{User:MiszaBot/config |archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s |algo = old(120d) |counter = 1 |key = 1f2adc5eee951900b65c7b981b786191 |minthreadstoarchive = 1 |minthreadsleft = 1 }} {{clear}} <!--Take threads to archive below this line--> <!--Add new threads to bottom of page--> == Retiring [[Template:Deleted page]] == {{tlx|Deleted page}} is a template that was used back in the day before salting (page creation protection) existed. Back then, if an admin wanted to prevent a page from being recreated, they would delete it and then recreate it with just that template, before fully protecting it. This method is completely unnecessary now that we can directly create-protect pages, and no new page has been added to [[:Category:Protected deleted pages]] in nearly eight years. Furthermore, I would like to propose that all the pages that currently have {{tlx|Naming policy notice}} be deleted and added to the ''title blacklist''. In the [[MediaWiki:Titleblacklist|title blacklist]], the error message should be set to an interface message that transcludes {{tlx|Naming policy notice}}. Since this is an editor-facing template, only would-be editors should be able to see it. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 22:55, 31 December 2025 (UTC) : Do you think we should delete {{tlx|Deleted page}} via RfD, but keep {{tlx|Naming policy notice}}? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:04, 31 December 2025 (UTC) ::@[[User:Codename Noreste|Codename Noreste]]: Yes. {{tlx|Deleted page}} should be deleted, and {{tlx|Naming policy notice}} should be fully protected and transcluded in a MediaWiki namespace message. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 23:16, 31 December 2025 (UTC) :::Considering there were no objections to this proposal here, {{Doing|I am doing this...}} [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:44, 30 March 2026 (UTC) ::::{{done|All done}}, but the discussion about {{tlx|Deleted page}} is awaiting to be closed (since I initiated it). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:37, 30 March 2026 (UTC) :[[User:JJPMaster|JJPMaster]], I filed a request at [[Wikibooks:Requests for deletion#Template:Deleted page]] to discuss whether to delete this template (and the categories used). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:38, 29 January 2026 (UTC) == Some proposals involving a separate permission request page and notification of ongoing RFAs == I would like to propose the following below: === Proposal 1 === <s>We split off [[Wikibooks:Requests for adminship]] as a separate page for requesting adminship, bureaucrat, checkuser and suppressor (oversight) permissions. All other permissions, except the former mentioned permissions, would still be requested at [[Wikibooks:Requests for permissions]] (this is also the case for requesting interface administrator permissions, for admins).</s> === Proposal 2 === Given the low activity on this project, I propose that we must notify the community about ongoing RFAs, which could be either [[MediaWiki:Sitenotice]] or adding a notification at [[Wikibooks:Reading room/General]]. A general rule is that the notification must be written in a neutral fashion. === In conclusion... === Feel free to comment, ask, or anything else. Thanks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:31, 1 January 2026 (UTC) :1. I don't see [[WB:RFP]] being clogged to justify creating a fork just for advanced permissions. :2. That is already something we do occasionally on a case-by-case basis. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 07:40, 1 January 2026 (UTC) :My thoughts below: :# I agree with @[[User:Leaderboard|Leaderboard]] and don't really see a need for splitting off [[Wikibooks:Requests for adminship]] as a separate page, since there are generally not so many requests. :# I do think it could potentially be useful to notify the community about requests for adminship using [[MediaWiki:Sitenotice]]—it's not something I've seen us do before. @[[User:Codename Noreste|Codename Noreste]] are you proposing specifically that we codify it in policy? :—[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:59, 1 January 2026 (UTC) ::After considering, I've crossed out proposal 1, and regarding proposal 2, I would still think it should be in a guideline, not a policy. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:22, 1 January 2026 (UTC) :Proposal 2 seems reasonable to me. It could help people find requests if they are not watching RFP. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 15:01, 2 January 2026 (UTC) :I've been thinking about proposal 2, and it seems like it would be a good idea to create a template for this purpose that we could just pop into [[MediaWiki:Sitenotice]]. What about creating [[Template:RFA notice]], which could take as parameters the requestor and the path to the discussion? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:35, 24 January 2026 (UTC) ::I agree. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:12, 27 January 2026 (UTC) == Implement Visual Editor in more namespaces == {{closed|The Phabricator task has been resolved, and VE is enabled on the proposed namespaces as of today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:06, 27 January 2026 (UTC)}} See the [[Wikibooks:Reading room/Technical Assistance#Visual Editor Implementation|original discussion]] for reference. ===Proposal=== Currently, the visual editor is implemented on the following namespaces: * Main * User * Help * Category * Cookbook * Wikijunior I am proposing that we implement the visual editor on the following namespaces: * Wikibooks * Transwiki ===Reasoning=== I use the source editor and the visual editor for different purposes. One of my primary uses of the visual editor is for text-heavy pages, where I use it for writing content and proofreading/copyediting. In contrast, I use the source editor for more complex and technical edits. I find it very difficult to parse text in the source editor, especially when there are many templates, tables, links, etc, and it is a pretty significant accessibility issue for me—I imagine that it could be so for other users as well. The Wikibooks and Transwiki namespaces are both namespaces that contain text- and content-heavy pages (e.g. policies, guidelines, essays), and I know I would benefit from the visual editor here—for example, I am currently working on the [[Wikibooks:Artificial intelligence/Unstable|unstable branch of a policy]], and it is proving to be kind of a pain to do without having the visual editor as an adjunct tool. The main challenge I see is that the Wikibooks namespace contains some talk pages (i.e. the reading room), and the visual editor is not intended for talk pages. However, there is [https://phabricator.wikimedia.org/T370158 precedent] for implementing the visual editor in namespaces that contain talk pages as long as it is understood that the visual editor is not intended for these talk pages. Overall, it looks technically feasible. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:40, 11 January 2026 (UTC) === Discussion === Kicking off the discussion here! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:37, 24 January 2026 (UTC) :Pinging people who were part of the original discussion thread: @[[User:Leaderboard|Leaderboard]] @[[User:Codename Noreste|Codename Noreste]] @[[User:SHB2000|SHB2000]]. :Also pinging some other active administrators: @[[User:JJPMaster|JJPMaster]] @[[User:MarcGarver|MarcGarver]] @[[User:Atcovi|Atcovi]] @[[User:Xania|Xania]] @[[User:JackPotte|JackPotte]] @[[User:TunnelESON|TunnelESON]]. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:48, 24 January 2026 (UTC) ::No objections. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:30, 24 January 2026 (UTC) ::I'm fine as well. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:04, 24 January 2026 (UTC) :::Ditto. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 22:49, 24 January 2026 (UTC) ::All good on my end. —[[User:Atcovi|Atcovi]] [[User talk:Atcovi|(Talk]] - [[Special:Contributions/Atcovi|Contribs)]] 17:09, 25 January 2026 (UTC) :Phab ticket has been created at {{phab|T415595}}! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:49, 26 January 2026 (UTC) {{end closed}} == Redefining the inactivity policy for administrators and bots == Hi. I would like to propose that we redefine the inactivity policy for administrators (superseding the current procedure), and to create a local inactivity policy for bots. * For administrators that have made zero edits '''''and''''' zero logged actions for over a year, they will be listed under the removal section of [[Wikibooks:Requests for permissions]] (and notified on their user talk pages), where they are given a specific timeframe to respond so that they can retain their access, unless they specify otherwise. If they do not respond after that timeframe, a request will be forwarded to the removal section of [[:m:SRP]]. Should the timeframe last at least one week, two weeks, or one month? * For bots, the process is slightly different. Bots that are inactive (made no edits/logged actions) for over two years will be listed under the removal section of RfP (in the same manner as inactive administrators), but their operators must be notified first, and a week is given for the operators to respond. After the timeframe passes and an operator does not respond to the inactive bot removal request (for example), a request will be forwarded to the removal section of [[:m:SRB]]. Bot users that do not have the bot user group might be exempt, unless the discussion proposes otherwise. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:34, 18 January 2026 (UTC) :Sounds fine to me. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 06:58, 21 January 2026 (UTC) ::Agreed here. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 00:36, 25 January 2026 (UTC) :I have no problem with this. Regarding the timeframe for administrators, one months seems reasonable. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:29, 24 January 2026 (UTC) ::I think one month might be excessive IMO, but one week might not be enough for a timeframe, especially given the lack of discussion activity. Let’s compromise by choosing two weeks instead, if that's okay. ::Also, the reason I made this is because the inactivity policy on [[Wikibooks:Administrators]] seems vague. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:15, 24 January 2026 (UTC) :::@[[User:Kittycataclysm|Kittycataclysm]], what timeframe would be feasible, two weeks, or one month? I'll be ready to implement this today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:20, 30 January 2026 (UTC) ::::Two weeks should probably be fine unless anyone else has thoughts! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:55, 31 January 2026 (UTC) :::::[[User:Kittycataclysm|Kittycataclysm]], I am reconsidering the current timeframe. I think we should revise by lowering the timeframe to one week for administrator inactivity removal, similar to how we currently do this for bots. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:17, 10 February 2026 (UTC) ::::::I think we should check to see what other people think here —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:49, 10 February 2026 (UTC) :I'm afraid I don't fully understand the procedure you're proposing for administrators. When someone is listed to be removed on RFP, is there a vote? Or is the poster just waiting for the inactive admin to reply? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:31, 24 January 2026 (UTC) ::In my new proposal, there will be no votes for removal, but inactive admins will be notified and given a timeframe to respond if they wish to retain their rights, unless they specify otherwise. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:42, 24 January 2026 (UTC) :{{done|Implemented}}. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:51, 31 January 2026 (UTC) ::Should I reduce the timeframe from two weeks down to one week? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:55, 22 February 2026 (UTC) == Create a "file" that is an Example Book structured to be copied/used to quickly start a new book? == I am new to Wikibooks, if this already exists let me know.... If there was a Wikibook "file" that contained all the templates and "parts" that are used to create a properly structured book, it might be easier and quicker to create and contribute books here. This would have to include text that would explain the purpose of each of the sections and templates and offer advice for making changes that customize the example. One might copy it to their sandbox, follow the directions and make the updates that create the framework for their book. Then the work would be to fill in the text. I suppose the downside is that books would be categorized and shelved that are in progress. Abandoned books would need to be deleted or some template might need to be developed that might indicate that the book is incomplete. This would be removed when the book is ready for prime-time. {{unsigned|Rchaswms01|01:32, 3 February 2026}} == Allow all users (registered and unregistered) to view edit filters and their logs? == Hello, everyone. I would like to propose allowing all users to view not just edit filters and [[Special:AbuseLog|their log]], but also detailed edit filter log entries. In addition to that, I am also proposing that we set <code>$wgAbuseFilterNotifications</code> to <code>true</code> by removing <code>$wgAbuseFilterNotifications = false;</code>. {{collapse top|This proposal aims to reverse a part of [[phab:T26304]] for the AbuseFilter extension:}} <syntaxhighlight lang="wikitext"> We would like to enable the AbuseFilter extension (see below) with custom permissions. Please *add*: $wgGroupPermissions['*']['abusefilter-view'] = false; $wgGroupPermissions['*']['abusefilter-log'] = false; $wgGroupPermissions['autoconfirmed']['abusefilter-view'] = true; $wgGroupPermissions['autoconfirmed']['abusefilter-log'] = true; </syntaxhighlight> <syntaxhighlight lang="wikitext"> I'm sorry for yet another reply, but the user rights for the abuse filter need to be tweaked to match the request. abusefilter-view should be for autoconfirmed/confirmed only and not for all users. abusefilter-log should be for autoconfirmed/confirmed only and not for all users. The logic behind this was to prevent casual vandals from gaming the system. Thank you for your efforts. </syntaxhighlight> {{collapse bottom}} {{collapse top|Current configuration}} <syntaxhighlight lang="php"> case 'enwikibooks': $wgGroupPermissions['*']['abusefilter-view'] = false; $wgGroupPermissions['*']['abusefilter-log'] = false; $wgAbuseFilterNotifications = false; $wgGroupPermissions['autoconfirmed']['abusefilter-view'] = true; $wgGroupPermissions['autoconfirmed']['abusefilter-log'] = true; $wgGroupPermissions['autoconfirmed']['abusefilter-log-detail'] = true; // T383332 $wgGroupPermissions['sysop']['abusefilter-revert'] = true; // T411828 $wgAbuseFilterActions['block'] = true; // T273864 break; </syntaxhighlight> {{collapse bottom}} {{collapse top|Proposed configuration}} <syntaxhighlight lang="php"> case 'enwikibooks': $wgGroupPermissions['*']['abusefilter-log-detail'] = true; $wgGroupPermissions['sysop']['abusefilter-revert'] = true; // T411828 $wgAbuseFilterActions['block'] = true; // T273864 break; </syntaxhighlight> {{collapse bottom}} Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:55, 2 April 2026 (UTC) :See also: {{section link|Wikibooks:Reading room/Proposals/2025/January#Reforming the edit filter}}. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 22:50, 2 April 2026 (UTC) == Introduce speedy deletion criteria? == I would like to propose that we introduce speedy deletion criteria to Wikibooks, such as {{tq|G1: [reason]}}. I suggest that we adapt from the English Wikipedia's CSD criteria ([[:w:Wikipedia:Speedy deletion]]) but utilize our existing deletion reasons, and even include '''G''' for general, '''R''' for redirects, and so on. Speedy deletion reasons are already included in the [[Wikibooks:Deletion policy|deletion policy]], but should this proposal pass, the new speedy deletion criteria can be split out to a separate policy page, if needed (e.g. [[Wikibooks:Speedy deletion]]). Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:39, 7 April 2026 (UTC) :On the whole, that seems like it could be useful to expand out our CSD in a more detailed way. Why don't you go ahead and create [[Wikibooks:Speedy deletion]] as a draft, write out your initial proposal, and then we can workshop it together? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:33, 10 April 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]]: How can this proposal avoid accusations of [[m:Instruction creep|instruction creep]]? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 23:21, 14 April 2026 (UTC) :: How does instruction creep have anything to do with this? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:31, 14 April 2026 (UTC) ::: Well, in that case, we might keep the descriptions simple, not overly detailed. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:30, 17 April 2026 (UTC) ::::In that case, we may need to introduce that motion. – [[User:RestoreAccess111|RestoreAccess111]] <sup style="font-family:Arimo, Arial;">[[User talk:RestoreAccess111|Talk!]]</sup> <sup style="font-family:Times New Roman, Tinos;">[[Special:Contributions/RestoreAccess111|Watch!]]</sup> 04:38, 17 April 2026 (UTC) :We already have speedy deletion though so I don't understand this proposal. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 15:56, 24 April 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]] I created a very early draft in [[User:Kingofnuthin/sandbox|my sandbox]] by merging content from [[w:Wikipedia:Speedy deletion]] and [[Wikibooks:Deletion policy]]. I added most of the criteria from English Wikipedia's page but I left some that can't be in Wikibooks (such as notability criteria). As I said, the draft is currently very undetailed and only provides simple explanations for criteria except for a few of them. You can add this draft to [[Wikibooks:Speedy deletion]] to clarify the details of the proposal. I am also open to any feedback regarding the draft. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:11, 26 April 2026 (UTC) :: I moved your draft to [[Wikibooks:Speedy deletion]]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:15, 26 April 2026 (UTC) ::This generally looks good; I've got a couple comments on specific criteria: ::* "G5. Pages dependent on a non-existent or deleted page" includes subpages with no parent page. Given the extent to which Wikibooks uses page nesting, this seems risky - at a minimum, the criterion should be revised to "subpages with no parent '''book'''", and existing pages which meet this criterion should be grandfathered in or otherwise addressed. ::* "B4. Books that duplicate an existing topic" should probably be removed. Unlike Wikipedia, Wikibooks has historically allowed multiple books to address the same topic, e.g. [[Mandarin Chinese]] and [[Chinese (Mandarin)]], or [[C++ Language]] and [[C++ Programming]]. Whether a book "expands upon, details or improves information" in another book is very subjective; determining whether this is the case should be handled in a deletion discussion, not by an admin processing speedy deletions. ::Additionally, I'd suggest that three criteria be added: ::* Books which are over a week old and which contain no instructional content (e.g. books which are nothing but a table of contents). These books are already routinely deleted under [[WB:NMC]]; adopting this as a CSD streamlines the process. ::* Pages in any namespace which are unambiguously advertisements or promotional in nature (akin to [[:w:WP:CSD#G11]]). ::* Pages in any namespace which infringe upon copyright, akin to [[:w:WP:CSD#G12]]. F6/F7 address ''files'' which are copyvios, but not text. ::[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:54, 29 April 2026 (UTC) ::: [[User:Omphalographer|Omphalographer]], feel free to make those changes to [[Wikibooks:Speedy deletion]], from your comments. It's a draft proposal. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:21, 29 April 2026 (UTC) :::@[[User:Omphalographer|Omphalographer]]: I agree on your thoughts for the removal of B4 and the addition of a new general criterion for copyvios, so I did those. However, I think that G5 is fine in its current state. I don't understand what situation would be "risky" in this case, so please provide some example for that. Additionally, I don't think we need an advertisement criterion right now, as Wikibooks does not seem to have a promotion problem, as it is a collection of textbooks. Also, you mentioned [[Wikibooks:NMC]] as a new criterion even though I copy-pasted criterion G1 from the exact part you mentioned. Such pages could be deleted under G1. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:06, 29 April 2026 (UTC) ::::With regards to G5, I've seen some situations where a book was incorrectly renamed in such a way that some of the subpages remained under the original title of the book, or pages of a book are inadvertently created under an incorrect title. Given the proposed wording for G5, those pages would be eligible for speedy deletion, even though they are in use as part of the book. ::::With regards to advertisements, Wikibooks does get some spam page creations; you'll see some if you scroll through [https://en.wikibooks.org/wiki/Special:Log?type=delete the deletion log]. It's typically deleted quickly by admins, but if we're codifying criteria for speedy deletion, this should be included as an allowable reason. ::::As far as G1 / NMC is concerned, I initially read G1 as applying only to pages which contain no meaningful content at all, like pages which are empty, nonsense, or vandalism, and which should be deleted promptly. I see this as distinct from books which are superficially well-formed, but which fail to develop, e.g. a user who creates an ambitious-sounding table of contents for a book, but never returns to write any of the text. These shouldn't be deleted immediately (since it takes time to write content!), but are routinely speedily deleted once it's clear that no further content is forthcoming. Since this is a bit of a different process, it should probably be treated as a separate criterion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:28, 29 April 2026 (UTC) :::::I added "Editors should be careful when nominating such pages, as they might be incorrectly named instead. In such cases, editors should move the page to its correctly-titled version." to G5. For advertising you said "Wikibooks does get some spam page creations", but we already have "Spam and vandalism" for G1. In G1, I removed "abandoned content" and made it a new criterion B5 under the book section. (As this would only apply to books.) [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:43, 29 April 2026 (UTC) :Quite frankly I don't see the need for a wiki of this size, in addition to what {{u|Leaderboard}} has mentioned. The current reasonings are perfectly fine, and subtly discourage the use of using abbreviations meaningless to new users. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 05:51, 4 May 2026 (UTC) ::Maybe we could do it without abbreviations, whilst keeping the categories. Our current speedy deletion policy is too short, and only includes main and userspace pages. We need more criteria for the Cookbook and Wikijunior for example. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 12:21, 4 May 2026 (UTC) == Questions about [[Wikibooks:Annotated texts]] == I was recently reading over the policy on annotated texts and had a few questions aimed at reforming that policy. (The talk page for the policy has been inactive for eleven years, so I figured a post there would be unlikely to attract attention.) # First and foremost - how many annotated texts of the type described by this policy are actually hosted on Wikibooks? I am only aware of one, [[Annotations to James Joyce's Ulysses]], which is quite incomplete. Are there a significant number more that I am unable to find? If not, might it be appropriate to revise this policy and related documents to reflect that annotated texts are, at best, an experimental part of the project? # The policy on annotated texts currently permits '''unannotated''' source texts to be hosted on Wikibooks provided that either the text is not on Wikisource, or that it is "widely used in classrooms". This seems like a rather large unintended loophole in the policy - there are innumerable texts which have not been transcribed on Wikisource, but which it would not make sense for Wikibooks to house either. Similarly, there are many texts which are "widely used in classrooms", but which have never been annotated on Wikibooks and are unlikely to ever be. The policy also notes the possibility that a multilingual project could create annotated texts with parallel page names across all language editions; I am certainly unaware of any such. Are there any texts on Wikibooks which rely on this policy, or would it be appropriate to strike this section? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:54, 28 April 2026 (UTC) :The policy seems to be contradicting [[Wikibooks:SOURCE]], which states that annotated texts are the only exception to published texts being on Wikibooks. This means that we have a policy that says unannotated source texts are permitted, and another one that says they aren't allowed. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 19:02, 28 April 2026 (UTC) :There is also [[Annotations of The Complete Peanuts]]. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 14:26, 29 April 2026 (UTC) ::That isn't an annotated text of the type described by this policy, as it doesn't include the original text that's being commented on. (Which it can't, because ''Peanuts'' is still under copyright.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 16:29, 29 April 2026 (UTC) :::Correct, it is not an inline annotation: I was just pointing it out as another kind of annotated text here. :::For what it's worth, our sister project Wikisource [[:s:en:Category:Wikisource annotations|also hosts inline annotations]], such as [[:s:en:What to the Slave Is the Fourth of July?/Annotated]], which I made. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:33, 29 April 2026 (UTC) :::The main problem here is that the policy permits "unannotated texts" even though we don't host them here. I think that the first thing you mentioned can stay but we might need to strike out the second part from the policy as it is contradictory. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:38, 29 April 2026 (UTC) ::::Yeah - I certainly don't mean to suggest that the ''Ulysses'' annotations need to go away; I'm mostly curious if this policy has any wider applicability, or if its only function is to allow this one text. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:37, 29 April 2026 (UTC) == Proposal related to FlaggedRevs == As said per [[Wikibooks:Reading room/General#Page patrolling]], I would like to propose the following: # <code>$wgUseNPPatrol</code> and <code>$wgUseFilePatrol</code> are both to be set to <code>false</code>. # <code>autopatrol</code> and <code>patrol</code> are to be removed from some user groups on this wiki. This is because FlaggedRevs is used to review new pages and edits, so I don't think MediaWiki's native patrol function is needed here. It's similar to [[phab:T423461]] (completely turning off the new page patrol function on Ukrainian Wikipedia). Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:05, 3 May 2026 (UTC) :{{support}}, patrolling is obsolete since we have FlaggedRevs extension here. Additionally, we should also consider renaming <code>editor</code> to <code>reviewer</code> to avoid confusion. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 15:19, 3 May 2026 (UTC) :: I agree, but about the <code>validate</code> user right, is this still needed? <code>reviewer</code> has it by default, and administrators already have that user right; we might need to consider whether to remove <code>validate</code> completely from this wiki. :: Also, <code>reviewer</code> is ''not'' under autopromotion, so this means an administrator will have to manually grant and remove that user group, unlike <code>editor</code>. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:45, 3 May 2026 (UTC) 7rud3hl9a2j134nooka0bk58qm7j603 4634224 4634064 2026-05-05T07:55:49Z SHB2000 3332924 /* Introduce speedy deletion criteria? */ Reply 4634224 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left<!--|limit=2-->}} Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks. {{User:MiszaBot/config |archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s |algo = old(120d) |counter = 1 |key = 1f2adc5eee951900b65c7b981b786191 |minthreadstoarchive = 1 |minthreadsleft = 1 }} {{clear}} <!--Take threads to archive below this line--> <!--Add new threads to bottom of page--> == Retiring [[Template:Deleted page]] == {{tlx|Deleted page}} is a template that was used back in the day before salting (page creation protection) existed. Back then, if an admin wanted to prevent a page from being recreated, they would delete it and then recreate it with just that template, before fully protecting it. This method is completely unnecessary now that we can directly create-protect pages, and no new page has been added to [[:Category:Protected deleted pages]] in nearly eight years. Furthermore, I would like to propose that all the pages that currently have {{tlx|Naming policy notice}} be deleted and added to the ''title blacklist''. In the [[MediaWiki:Titleblacklist|title blacklist]], the error message should be set to an interface message that transcludes {{tlx|Naming policy notice}}. Since this is an editor-facing template, only would-be editors should be able to see it. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 22:55, 31 December 2025 (UTC) : Do you think we should delete {{tlx|Deleted page}} via RfD, but keep {{tlx|Naming policy notice}}? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:04, 31 December 2025 (UTC) ::@[[User:Codename Noreste|Codename Noreste]]: Yes. {{tlx|Deleted page}} should be deleted, and {{tlx|Naming policy notice}} should be fully protected and transcluded in a MediaWiki namespace message. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 23:16, 31 December 2025 (UTC) :::Considering there were no objections to this proposal here, {{Doing|I am doing this...}} [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:44, 30 March 2026 (UTC) ::::{{done|All done}}, but the discussion about {{tlx|Deleted page}} is awaiting to be closed (since I initiated it). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:37, 30 March 2026 (UTC) :[[User:JJPMaster|JJPMaster]], I filed a request at [[Wikibooks:Requests for deletion#Template:Deleted page]] to discuss whether to delete this template (and the categories used). [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:38, 29 January 2026 (UTC) == Some proposals involving a separate permission request page and notification of ongoing RFAs == I would like to propose the following below: === Proposal 1 === <s>We split off [[Wikibooks:Requests for adminship]] as a separate page for requesting adminship, bureaucrat, checkuser and suppressor (oversight) permissions. All other permissions, except the former mentioned permissions, would still be requested at [[Wikibooks:Requests for permissions]] (this is also the case for requesting interface administrator permissions, for admins).</s> === Proposal 2 === Given the low activity on this project, I propose that we must notify the community about ongoing RFAs, which could be either [[MediaWiki:Sitenotice]] or adding a notification at [[Wikibooks:Reading room/General]]. A general rule is that the notification must be written in a neutral fashion. === In conclusion... === Feel free to comment, ask, or anything else. Thanks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:31, 1 January 2026 (UTC) :1. I don't see [[WB:RFP]] being clogged to justify creating a fork just for advanced permissions. :2. That is already something we do occasionally on a case-by-case basis. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 07:40, 1 January 2026 (UTC) :My thoughts below: :# I agree with @[[User:Leaderboard|Leaderboard]] and don't really see a need for splitting off [[Wikibooks:Requests for adminship]] as a separate page, since there are generally not so many requests. :# I do think it could potentially be useful to notify the community about requests for adminship using [[MediaWiki:Sitenotice]]—it's not something I've seen us do before. @[[User:Codename Noreste|Codename Noreste]] are you proposing specifically that we codify it in policy? :—[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:59, 1 January 2026 (UTC) ::After considering, I've crossed out proposal 1, and regarding proposal 2, I would still think it should be in a guideline, not a policy. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:22, 1 January 2026 (UTC) :Proposal 2 seems reasonable to me. It could help people find requests if they are not watching RFP. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 15:01, 2 January 2026 (UTC) :I've been thinking about proposal 2, and it seems like it would be a good idea to create a template for this purpose that we could just pop into [[MediaWiki:Sitenotice]]. What about creating [[Template:RFA notice]], which could take as parameters the requestor and the path to the discussion? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:35, 24 January 2026 (UTC) ::I agree. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:12, 27 January 2026 (UTC) == Implement Visual Editor in more namespaces == {{closed|The Phabricator task has been resolved, and VE is enabled on the proposed namespaces as of today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:06, 27 January 2026 (UTC)}} See the [[Wikibooks:Reading room/Technical Assistance#Visual Editor Implementation|original discussion]] for reference. ===Proposal=== Currently, the visual editor is implemented on the following namespaces: * Main * User * Help * Category * Cookbook * Wikijunior I am proposing that we implement the visual editor on the following namespaces: * Wikibooks * Transwiki ===Reasoning=== I use the source editor and the visual editor for different purposes. One of my primary uses of the visual editor is for text-heavy pages, where I use it for writing content and proofreading/copyediting. In contrast, I use the source editor for more complex and technical edits. I find it very difficult to parse text in the source editor, especially when there are many templates, tables, links, etc, and it is a pretty significant accessibility issue for me—I imagine that it could be so for other users as well. The Wikibooks and Transwiki namespaces are both namespaces that contain text- and content-heavy pages (e.g. policies, guidelines, essays), and I know I would benefit from the visual editor here—for example, I am currently working on the [[Wikibooks:Artificial intelligence/Unstable|unstable branch of a policy]], and it is proving to be kind of a pain to do without having the visual editor as an adjunct tool. The main challenge I see is that the Wikibooks namespace contains some talk pages (i.e. the reading room), and the visual editor is not intended for talk pages. However, there is [https://phabricator.wikimedia.org/T370158 precedent] for implementing the visual editor in namespaces that contain talk pages as long as it is understood that the visual editor is not intended for these talk pages. Overall, it looks technically feasible. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:40, 11 January 2026 (UTC) === Discussion === Kicking off the discussion here! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:37, 24 January 2026 (UTC) :Pinging people who were part of the original discussion thread: @[[User:Leaderboard|Leaderboard]] @[[User:Codename Noreste|Codename Noreste]] @[[User:SHB2000|SHB2000]]. :Also pinging some other active administrators: @[[User:JJPMaster|JJPMaster]] @[[User:MarcGarver|MarcGarver]] @[[User:Atcovi|Atcovi]] @[[User:Xania|Xania]] @[[User:JackPotte|JackPotte]] @[[User:TunnelESON|TunnelESON]]. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:48, 24 January 2026 (UTC) ::No objections. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:30, 24 January 2026 (UTC) ::I'm fine as well. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:04, 24 January 2026 (UTC) :::Ditto. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 22:49, 24 January 2026 (UTC) ::All good on my end. —[[User:Atcovi|Atcovi]] [[User talk:Atcovi|(Talk]] - [[Special:Contributions/Atcovi|Contribs)]] 17:09, 25 January 2026 (UTC) :Phab ticket has been created at {{phab|T415595}}! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:49, 26 January 2026 (UTC) {{end closed}} == Redefining the inactivity policy for administrators and bots == Hi. I would like to propose that we redefine the inactivity policy for administrators (superseding the current procedure), and to create a local inactivity policy for bots. * For administrators that have made zero edits '''''and''''' zero logged actions for over a year, they will be listed under the removal section of [[Wikibooks:Requests for permissions]] (and notified on their user talk pages), where they are given a specific timeframe to respond so that they can retain their access, unless they specify otherwise. If they do not respond after that timeframe, a request will be forwarded to the removal section of [[:m:SRP]]. Should the timeframe last at least one week, two weeks, or one month? * For bots, the process is slightly different. Bots that are inactive (made no edits/logged actions) for over two years will be listed under the removal section of RfP (in the same manner as inactive administrators), but their operators must be notified first, and a week is given for the operators to respond. After the timeframe passes and an operator does not respond to the inactive bot removal request (for example), a request will be forwarded to the removal section of [[:m:SRB]]. Bot users that do not have the bot user group might be exempt, unless the discussion proposes otherwise. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:34, 18 January 2026 (UTC) :Sounds fine to me. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 06:58, 21 January 2026 (UTC) ::Agreed here. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 00:36, 25 January 2026 (UTC) :I have no problem with this. Regarding the timeframe for administrators, one months seems reasonable. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:29, 24 January 2026 (UTC) ::I think one month might be excessive IMO, but one week might not be enough for a timeframe, especially given the lack of discussion activity. Let’s compromise by choosing two weeks instead, if that's okay. ::Also, the reason I made this is because the inactivity policy on [[Wikibooks:Administrators]] seems vague. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:15, 24 January 2026 (UTC) :::@[[User:Kittycataclysm|Kittycataclysm]], what timeframe would be feasible, two weeks, or one month? I'll be ready to implement this today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:20, 30 January 2026 (UTC) ::::Two weeks should probably be fine unless anyone else has thoughts! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:55, 31 January 2026 (UTC) :::::[[User:Kittycataclysm|Kittycataclysm]], I am reconsidering the current timeframe. I think we should revise by lowering the timeframe to one week for administrator inactivity removal, similar to how we currently do this for bots. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:17, 10 February 2026 (UTC) ::::::I think we should check to see what other people think here —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:49, 10 February 2026 (UTC) :I'm afraid I don't fully understand the procedure you're proposing for administrators. When someone is listed to be removed on RFP, is there a vote? Or is the poster just waiting for the inactive admin to reply? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:31, 24 January 2026 (UTC) ::In my new proposal, there will be no votes for removal, but inactive admins will be notified and given a timeframe to respond if they wish to retain their rights, unless they specify otherwise. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:42, 24 January 2026 (UTC) :{{done|Implemented}}. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:51, 31 January 2026 (UTC) ::Should I reduce the timeframe from two weeks down to one week? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:55, 22 February 2026 (UTC) == Create a "file" that is an Example Book structured to be copied/used to quickly start a new book? == I am new to Wikibooks, if this already exists let me know.... If there was a Wikibook "file" that contained all the templates and "parts" that are used to create a properly structured book, it might be easier and quicker to create and contribute books here. This would have to include text that would explain the purpose of each of the sections and templates and offer advice for making changes that customize the example. One might copy it to their sandbox, follow the directions and make the updates that create the framework for their book. Then the work would be to fill in the text. I suppose the downside is that books would be categorized and shelved that are in progress. Abandoned books would need to be deleted or some template might need to be developed that might indicate that the book is incomplete. This would be removed when the book is ready for prime-time. {{unsigned|Rchaswms01|01:32, 3 February 2026}} == Allow all users (registered and unregistered) to view edit filters and their logs? == Hello, everyone. I would like to propose allowing all users to view not just edit filters and [[Special:AbuseLog|their log]], but also detailed edit filter log entries. In addition to that, I am also proposing that we set <code>$wgAbuseFilterNotifications</code> to <code>true</code> by removing <code>$wgAbuseFilterNotifications = false;</code>. {{collapse top|This proposal aims to reverse a part of [[phab:T26304]] for the AbuseFilter extension:}} <syntaxhighlight lang="wikitext"> We would like to enable the AbuseFilter extension (see below) with custom permissions. Please *add*: $wgGroupPermissions['*']['abusefilter-view'] = false; $wgGroupPermissions['*']['abusefilter-log'] = false; $wgGroupPermissions['autoconfirmed']['abusefilter-view'] = true; $wgGroupPermissions['autoconfirmed']['abusefilter-log'] = true; </syntaxhighlight> <syntaxhighlight lang="wikitext"> I'm sorry for yet another reply, but the user rights for the abuse filter need to be tweaked to match the request. abusefilter-view should be for autoconfirmed/confirmed only and not for all users. abusefilter-log should be for autoconfirmed/confirmed only and not for all users. The logic behind this was to prevent casual vandals from gaming the system. Thank you for your efforts. </syntaxhighlight> {{collapse bottom}} {{collapse top|Current configuration}} <syntaxhighlight lang="php"> case 'enwikibooks': $wgGroupPermissions['*']['abusefilter-view'] = false; $wgGroupPermissions['*']['abusefilter-log'] = false; $wgAbuseFilterNotifications = false; $wgGroupPermissions['autoconfirmed']['abusefilter-view'] = true; $wgGroupPermissions['autoconfirmed']['abusefilter-log'] = true; $wgGroupPermissions['autoconfirmed']['abusefilter-log-detail'] = true; // T383332 $wgGroupPermissions['sysop']['abusefilter-revert'] = true; // T411828 $wgAbuseFilterActions['block'] = true; // T273864 break; </syntaxhighlight> {{collapse bottom}} {{collapse top|Proposed configuration}} <syntaxhighlight lang="php"> case 'enwikibooks': $wgGroupPermissions['*']['abusefilter-log-detail'] = true; $wgGroupPermissions['sysop']['abusefilter-revert'] = true; // T411828 $wgAbuseFilterActions['block'] = true; // T273864 break; </syntaxhighlight> {{collapse bottom}} Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:55, 2 April 2026 (UTC) :See also: {{section link|Wikibooks:Reading room/Proposals/2025/January#Reforming the edit filter}}. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 22:50, 2 April 2026 (UTC) == Introduce speedy deletion criteria? == I would like to propose that we introduce speedy deletion criteria to Wikibooks, such as {{tq|G1: [reason]}}. I suggest that we adapt from the English Wikipedia's CSD criteria ([[:w:Wikipedia:Speedy deletion]]) but utilize our existing deletion reasons, and even include '''G''' for general, '''R''' for redirects, and so on. Speedy deletion reasons are already included in the [[Wikibooks:Deletion policy|deletion policy]], but should this proposal pass, the new speedy deletion criteria can be split out to a separate policy page, if needed (e.g. [[Wikibooks:Speedy deletion]]). Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:39, 7 April 2026 (UTC) :On the whole, that seems like it could be useful to expand out our CSD in a more detailed way. Why don't you go ahead and create [[Wikibooks:Speedy deletion]] as a draft, write out your initial proposal, and then we can workshop it together? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:33, 10 April 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]]: How can this proposal avoid accusations of [[m:Instruction creep|instruction creep]]? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 23:21, 14 April 2026 (UTC) :: How does instruction creep have anything to do with this? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:31, 14 April 2026 (UTC) ::: Well, in that case, we might keep the descriptions simple, not overly detailed. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:30, 17 April 2026 (UTC) ::::In that case, we may need to introduce that motion. – [[User:RestoreAccess111|RestoreAccess111]] <sup style="font-family:Arimo, Arial;">[[User talk:RestoreAccess111|Talk!]]</sup> <sup style="font-family:Times New Roman, Tinos;">[[Special:Contributions/RestoreAccess111|Watch!]]</sup> 04:38, 17 April 2026 (UTC) :We already have speedy deletion though so I don't understand this proposal. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 15:56, 24 April 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]] I created a very early draft in [[User:Kingofnuthin/sandbox|my sandbox]] by merging content from [[w:Wikipedia:Speedy deletion]] and [[Wikibooks:Deletion policy]]. I added most of the criteria from English Wikipedia's page but I left some that can't be in Wikibooks (such as notability criteria). As I said, the draft is currently very undetailed and only provides simple explanations for criteria except for a few of them. You can add this draft to [[Wikibooks:Speedy deletion]] to clarify the details of the proposal. I am also open to any feedback regarding the draft. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:11, 26 April 2026 (UTC) :: I moved your draft to [[Wikibooks:Speedy deletion]]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:15, 26 April 2026 (UTC) ::This generally looks good; I've got a couple comments on specific criteria: ::* "G5. Pages dependent on a non-existent or deleted page" includes subpages with no parent page. Given the extent to which Wikibooks uses page nesting, this seems risky - at a minimum, the criterion should be revised to "subpages with no parent '''book'''", and existing pages which meet this criterion should be grandfathered in or otherwise addressed. ::* "B4. Books that duplicate an existing topic" should probably be removed. Unlike Wikipedia, Wikibooks has historically allowed multiple books to address the same topic, e.g. [[Mandarin Chinese]] and [[Chinese (Mandarin)]], or [[C++ Language]] and [[C++ Programming]]. Whether a book "expands upon, details or improves information" in another book is very subjective; determining whether this is the case should be handled in a deletion discussion, not by an admin processing speedy deletions. ::Additionally, I'd suggest that three criteria be added: ::* Books which are over a week old and which contain no instructional content (e.g. books which are nothing but a table of contents). These books are already routinely deleted under [[WB:NMC]]; adopting this as a CSD streamlines the process. ::* Pages in any namespace which are unambiguously advertisements or promotional in nature (akin to [[:w:WP:CSD#G11]]). ::* Pages in any namespace which infringe upon copyright, akin to [[:w:WP:CSD#G12]]. F6/F7 address ''files'' which are copyvios, but not text. ::[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:54, 29 April 2026 (UTC) ::: [[User:Omphalographer|Omphalographer]], feel free to make those changes to [[Wikibooks:Speedy deletion]], from your comments. It's a draft proposal. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:21, 29 April 2026 (UTC) :::@[[User:Omphalographer|Omphalographer]]: I agree on your thoughts for the removal of B4 and the addition of a new general criterion for copyvios, so I did those. However, I think that G5 is fine in its current state. I don't understand what situation would be "risky" in this case, so please provide some example for that. Additionally, I don't think we need an advertisement criterion right now, as Wikibooks does not seem to have a promotion problem, as it is a collection of textbooks. Also, you mentioned [[Wikibooks:NMC]] as a new criterion even though I copy-pasted criterion G1 from the exact part you mentioned. Such pages could be deleted under G1. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:06, 29 April 2026 (UTC) ::::With regards to G5, I've seen some situations where a book was incorrectly renamed in such a way that some of the subpages remained under the original title of the book, or pages of a book are inadvertently created under an incorrect title. Given the proposed wording for G5, those pages would be eligible for speedy deletion, even though they are in use as part of the book. ::::With regards to advertisements, Wikibooks does get some spam page creations; you'll see some if you scroll through [https://en.wikibooks.org/wiki/Special:Log?type=delete the deletion log]. It's typically deleted quickly by admins, but if we're codifying criteria for speedy deletion, this should be included as an allowable reason. ::::As far as G1 / NMC is concerned, I initially read G1 as applying only to pages which contain no meaningful content at all, like pages which are empty, nonsense, or vandalism, and which should be deleted promptly. I see this as distinct from books which are superficially well-formed, but which fail to develop, e.g. a user who creates an ambitious-sounding table of contents for a book, but never returns to write any of the text. These shouldn't be deleted immediately (since it takes time to write content!), but are routinely speedily deleted once it's clear that no further content is forthcoming. Since this is a bit of a different process, it should probably be treated as a separate criterion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:28, 29 April 2026 (UTC) :::::I added "Editors should be careful when nominating such pages, as they might be incorrectly named instead. In such cases, editors should move the page to its correctly-titled version." to G5. For advertising you said "Wikibooks does get some spam page creations", but we already have "Spam and vandalism" for G1. In G1, I removed "abandoned content" and made it a new criterion B5 under the book section. (As this would only apply to books.) [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 17:43, 29 April 2026 (UTC) :Quite frankly I don't see the need for a wiki of this size, in addition to what {{u|Leaderboard}} has mentioned. The current reasonings are perfectly fine, and subtly discourage the use of using abbreviations meaningless to new users. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 05:51, 4 May 2026 (UTC) ::Maybe we could do it without abbreviations, whilst keeping the categories. Our current speedy deletion policy is too short, and only includes main and userspace pages. We need more criteria for the Cookbook and Wikijunior for example. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 12:21, 4 May 2026 (UTC) :::But why? [[:w:Wikipedia:If it ain't broke, don't fix it|If it ain't broke, don't fix it]]. Cookbook and Wikijunior for all purposes of policy can generally be implied to be mainspace pages. I find this really overkill for a wiki of this size. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 07:55, 5 May 2026 (UTC) == Questions about [[Wikibooks:Annotated texts]] == I was recently reading over the policy on annotated texts and had a few questions aimed at reforming that policy. (The talk page for the policy has been inactive for eleven years, so I figured a post there would be unlikely to attract attention.) # First and foremost - how many annotated texts of the type described by this policy are actually hosted on Wikibooks? I am only aware of one, [[Annotations to James Joyce's Ulysses]], which is quite incomplete. Are there a significant number more that I am unable to find? If not, might it be appropriate to revise this policy and related documents to reflect that annotated texts are, at best, an experimental part of the project? # The policy on annotated texts currently permits '''unannotated''' source texts to be hosted on Wikibooks provided that either the text is not on Wikisource, or that it is "widely used in classrooms". This seems like a rather large unintended loophole in the policy - there are innumerable texts which have not been transcribed on Wikisource, but which it would not make sense for Wikibooks to house either. Similarly, there are many texts which are "widely used in classrooms", but which have never been annotated on Wikibooks and are unlikely to ever be. The policy also notes the possibility that a multilingual project could create annotated texts with parallel page names across all language editions; I am certainly unaware of any such. Are there any texts on Wikibooks which rely on this policy, or would it be appropriate to strike this section? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:54, 28 April 2026 (UTC) :The policy seems to be contradicting [[Wikibooks:SOURCE]], which states that annotated texts are the only exception to published texts being on Wikibooks. This means that we have a policy that says unannotated source texts are permitted, and another one that says they aren't allowed. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 19:02, 28 April 2026 (UTC) :There is also [[Annotations of The Complete Peanuts]]. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 14:26, 29 April 2026 (UTC) ::That isn't an annotated text of the type described by this policy, as it doesn't include the original text that's being commented on. (Which it can't, because ''Peanuts'' is still under copyright.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 16:29, 29 April 2026 (UTC) :::Correct, it is not an inline annotation: I was just pointing it out as another kind of annotated text here. :::For what it's worth, our sister project Wikisource [[:s:en:Category:Wikisource annotations|also hosts inline annotations]], such as [[:s:en:What to the Slave Is the Fourth of July?/Annotated]], which I made. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:33, 29 April 2026 (UTC) :::The main problem here is that the policy permits "unannotated texts" even though we don't host them here. I think that the first thing you mentioned can stay but we might need to strike out the second part from the policy as it is contradictory. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 16:38, 29 April 2026 (UTC) ::::Yeah - I certainly don't mean to suggest that the ''Ulysses'' annotations need to go away; I'm mostly curious if this policy has any wider applicability, or if its only function is to allow this one text. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 17:37, 29 April 2026 (UTC) == Proposal related to FlaggedRevs == As said per [[Wikibooks:Reading room/General#Page patrolling]], I would like to propose the following: # <code>$wgUseNPPatrol</code> and <code>$wgUseFilePatrol</code> are both to be set to <code>false</code>. # <code>autopatrol</code> and <code>patrol</code> are to be removed from some user groups on this wiki. This is because FlaggedRevs is used to review new pages and edits, so I don't think MediaWiki's native patrol function is needed here. It's similar to [[phab:T423461]] (completely turning off the new page patrol function on Ukrainian Wikipedia). Thoughts? [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:05, 3 May 2026 (UTC) :{{support}}, patrolling is obsolete since we have FlaggedRevs extension here. Additionally, we should also consider renaming <code>editor</code> to <code>reviewer</code> to avoid confusion. [[User:kingofnuthin|<span style="font-family: Georgia; color: lime">kingofnuthin</span>]] ([[User talk:kingofnuthin|<span style="font-family: Georgia; color: teal">talk</span>]]) 15:19, 3 May 2026 (UTC) :: I agree, but about the <code>validate</code> user right, is this still needed? <code>reviewer</code> has it by default, and administrators already have that user right; we might need to consider whether to remove <code>validate</code> completely from this wiki. :: Also, <code>reviewer</code> is ''not'' under autopromotion, so this means an administrator will have to manually grant and remove that user group, unlike <code>editor</code>. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:45, 3 May 2026 (UTC) i6e5v6qaqkyp3n93axxk6sm6xb8akwd 0 157129 4634170 3229884 2026-05-04T19:06:33Z JCrue 2226064 updated. rare sideline. rm name "Burris gambit", which seems to only go back to a chess.com thread from 2007 and isn't otherwise attested. 4634170 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Classical variation |eco=[[Chess/ECOB|B18]] |parent=[[Chess Opening Theory/1. e4/1...c6|Caro-Kann]] → [[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Nc3/3...dxe4/4. Nxe4/4...Bf5|Classical variation]] }} == 5. Bd3?!== {{Chess/sideline}} White develops a piece and gives up defence of the d4-pawn, allowing '''5...Qxd4''', in return for the compensation of getting to develop 6. Nf3 with tempo. {{ChessMid}} ==References== {{reflist}} {{Chess Opening Theory/Footer}} 0hd7rpxpk1vm420w9oid70n5vmzgtgk 0 157131 4634173 4410976 2026-05-04T19:11:52Z JCrue 2226064 delete 4634173 wikitext text/x-wiki {{delete|Out of scope (rare sideline, not theory); Burris is vanity name.}} {{Chess Opening Theory/Position|= |Caro-Kann Defence:Burris Gambit accepted| |rd|nd| | |kd|bd|nd|rd|= |pd|pd| | |pd|pd|pd|pd|= | | |pd| | | | | |= | | | | | |bd| | |= | | | |qd|nl| | | |= | | | |bl| | | | |= |pl|pl|pl| | |pl|pl|pl|= |rl| |bl|ql|kl| |nl|rl|= || }} = Caro-Kann Defence:Burris Gambit accepted = <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">6</th> <th align="left">7</th> </tr> <tr> <th align="right"></th> <td>[[/6.Nf3|Nf3]]<br>Qd8</td> <td>Qe2<br>e6</td> <td>+/= </td> </tr> <tr> <th align="right"></th> <td>...<br>...</td> <td>...<br>Bxe4</td> <td>+/= </td> </tr> <tr> <th align="right"></th> <td>...<br>...</td> <td>...<br>[[/7.Nf6|Nf6]]</td> <td>+/= </td> </tr> </table> {{ChessMid}} ==References== {{reflist}} {{BCO2}} {{Chess Opening Theory/Footer}} {{ChessStub}} cezsc4oirxcx69m7mprxkprwi7z03to 0 185812 4634226 4032925 2026-05-05T08:25:16Z ~2026-26995-93 3581107 Expanded page. 4634226 wikitext text/x-wiki {{Chess Opening Theory/Position|= |Caro-Kann Defence| |eco=[[Chess/ECOB|B15]] |parent=[[Chess/Caro-Kann Defence|Caro-Kann Defence]] }} = Caro-Kann Defence= == 4...Nf6 == The standard move in amateur play, offering a trade of knights. This move challenges white's strong e4-knight but allows white to double black's pawns with the main move, '''[[/5. Nxf6+/]]'''. Other moves also exist. '''[[/5. Qd3/]]'''defends the knight and sets up a trap, 5...Bf5?? 6. Nxf6+! exf6 7. Qxf5!. '''[[/5. Bd3/]]''' is the '''Alekhine Gambit'''. White gives up their d-pawn in exchange for development after 5...Qxd4 6. Nf3. Some players have also tried '''[[/5. Ng5/]]''', with the intention of entering the [[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Nc3/3...dxe4/4. Nxe4/4...Nf6/5. Ng5/5...h6/6. Nxf7|Alien Gambit]], a dubious but scary knight sacrrifice on f7. '''[[/5. Ng3/]]''' is not really a bad move, but allows Black to begin creating threats themselves with the move 5...h5. ==Theory table== {{Chess Opening Theory/Table}}. 1.e4 c6 2.d4 d5 3.Nc3 dxe4 4. Nxe4 Nf6 <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">5</th> </tr> <tr> <th align="right"></th> <td>[[/5. Nxf6|Nxf6+]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng3|Ng3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Bd3|Bd3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Qd3|Qd3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng5|Ng5]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Nc3|Nc3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. f3|f3]] </td> </tr> <tr> </table> {{ChessMid}} ==References== {{reflist}} {{Chess Opening Theory/Footer}} {{BookCat}} ay429t8wp56a6yfrfwbwtajrhxa1qi7 4634227 4634226 2026-05-05T08:25:44Z ~2026-26995-93 3581107 Minor edit, fixed typos. 4634227 wikitext text/x-wiki {{Chess Opening Theory/Position|= |Caro-Kann Defence| |eco=[[Chess/ECOB|B15]] |parent=[[Chess/Caro-Kann Defence|Caro-Kann Defence]] }} = Caro-Kann Defence= == 4...Nf6 == The standard move in amateur play, offering a trade of knights. This move challenges white's strong e4-knight but allows white to double black's pawns with the main move, '''[[/5. Nxf6+/]]'''. Other moves also exist. '''[[/5. Qd3/]]''' defends the knight and sets up a trap, 5...Bf5?? 6. Nxf6+! exf6 7. Qxf5!. '''[[/5. Bd3/]]''' is the '''Alekhine Gambit'''. White gives up their d-pawn in exchange for development after 5...Qxd4 6. Nf3. Some players have also tried '''[[/5. Ng5/]]''', with the intention of entering the [[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Nc3/3...dxe4/4. Nxe4/4...Nf6/5. Ng5/5...h6/6. Nxf7|Alien Gambit]], a dubious but scary knight sacrifice on f7. '''[[/5. Ng3/]]''' is not really a bad move, but allows Black to begin creating threats themselves with the move 5...h5. ==Theory table== {{Chess Opening Theory/Table}}. 1.e4 c6 2.d4 d5 3.Nc3 dxe4 4. Nxe4 Nf6 <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">5</th> </tr> <tr> <th align="right"></th> <td>[[/5. Nxf6|Nxf6+]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng3|Ng3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Bd3|Bd3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Qd3|Qd3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng5|Ng5]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Nc3|Nc3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. f3|f3]] </td> </tr> <tr> </table> {{ChessMid}} ==References== {{reflist}} {{Chess Opening Theory/Footer}} {{BookCat}} igwek2ikr5wmbhyky82n6h38pl7tn4y 4634228 4634227 2026-05-05T08:27:10Z ~2026-26995-93 3581107 Minor edit, fixed another typo. 4634228 wikitext text/x-wiki {{Chess Opening Theory/Position|= |Caro-Kann Defence| |eco=[[Chess/ECOB|B15]] |parent=[[Chess/Caro-Kann Defence|Caro-Kann Defence]] }} = Caro-Kann Defence= == 4...Nf6 == The standard move in amateur play, offering a trade of knights. This move challenges white's strong e4-knight but allows white to double black's pawns with the main move, '''[[/5. Nxf6|5. Nxf6+]]'''. Other moves also exist. '''[[/5. Qd3/]]''' defends the knight and sets up a trap, 5...Bf5?? 6. Nxf6+! exf6 7. Qxf5!. '''[[/5. Bd3/]]''' is the '''Alekhine Gambit'''. White gives up their d-pawn in exchange for development after 5...Qxd4 6. Nf3. Some players have also tried '''[[/5. Ng5/]]''', with the intention of entering the [[Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Nc3/3...dxe4/4. Nxe4/4...Nf6/5. Ng5/5...h6/6. Nxf7|Alien Gambit]], a dubious but scary knight sacrifice on f7. '''[[/5. Ng3/]]''' is not really a bad move, but allows Black to begin creating threats themselves with the move 5...h5. ==Theory table== {{Chess Opening Theory/Table}}. 1.e4 c6 2.d4 d5 3.Nc3 dxe4 4. Nxe4 Nf6 <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">5</th> </tr> <tr> <th align="right"></th> <td>[[/5. Nxf6|Nxf6+]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng3|Ng3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Bd3|Bd3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Qd3|Qd3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng5|Ng5]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Nc3|Nc3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. f3|f3]] </td> </tr> <tr> </table> {{ChessMid}} ==References== {{reflist}} {{Chess Opening Theory/Footer}} {{BookCat}} 94nsquuwooqe7t9f46z9wvdz2bypill 0 216378 4634066 4441570 2026-05-04T12:25:47Z Jcb 90773 4634066 wikitext text/x-wiki =='''Acetylation'''== Acetylation introduces an [[w:acetyl|acetyl]] group to a molecule. More specifically, the reaction replaces a hydrogen from an alcohol group with an acetyl. An example is the synthesis of [[w:aspirin|aspirin]] from [[w:salicylic acid|salicylic acid]]: [[Image:Aspirin_synthesis.svg|right|thumb|Aspirin synthesis]] Acetylation is an important post-translational protein modification and regulation. An example is the acetylation/deacetylation of [[w:histone|histone]] which subsequently express/inhibit genes since histone binds to DNA itself. [[w:Histone Acetyltransferase|Histone Acetyltransferase]] catalyzes the acetylation of lysine from the histone tail with an acetyl group from [[w:Acetyl CoA|Acetyl CoA]]. The acetylation of lysine in histone removes the positive charged ammonium group and renders the side chain neutral, which decreases the histone tail affinity for DNA and loosens the histone complex. The now-acetylated histone can interact with an [[w:acetyllysine|acetyllysine]]-binding domain in many eukaryotic proteins called [[w:bromodomain]], an 110 amino acids protein with a four-helix bundle and a peptide-binding site at one end. {{BookCat}} Acetylation is the reaction in which an acetyl functional group is added to an organic molecule. In proteins, an acetyl group to either added to the N-terminus of proteins and at lysine residues as a post-translational protein modification. '''N-alpha-Terminal Acetylation''' The role of N-alpha-Terminal Acetylation is still relatively unknown and under research. However, it is known that this modification is actually widely prevalent in eukaryotes and yeast, though uncommon in prokaryotes, and is performed by a subgroup of acetlytransferases known as N-alpha-acetyltransferases (NATs). There are three major NATs (A,B,C) which perform the majority of the N-alpha-terminal acetylations of eukaryotes The reaction is begun with the cleaving of N-terminal methionine residues with small side chains containing, glycine, alanine, serine, cysteine, threonine, proline, and valine, by methionine aminopeptidases (MAP), Map1p and Map2p. Subsequently, the NATs recognize and acetylate specific sequences of the cleaved proteins. '''Lysine Acetylation''' One major area in which lysine acetylation is prevalent is in the acetylation of histones, which is performed by histone acetyltransferases (HATs) and deacetylases (HDACs). In both acetylation and deacetylation reactions that attach to the NH3+ tail from an acetyl group from Acetyl-Coenzyme A and remove the acetyl group from lysine onto Coenzyme A, respectively. The acetylation and deacetylation of histones partake in gene regulation. Histones are packages of strongly alkaline protein around which DNA is wound to allow DNA to be stored in an orderly fashion. Since the acetylation occurs at the NH3+ tail of lysine, the charge of the protein is affected. When acetylated, the positive charge of lysine is eliminated. This decreases the histones affinity to the negatively charged DNA strand, thereby loosening the strand, and the reverse results occur with deacetylation. However, Lysine acetylation isn’t limited to histone acetylation. Among other things, it is also involved in the modification and regulation of non-histones such as cytoplasmic enzymes and p35, a tumor suppressor and involved with signal transmittance and signaling. ==Drug Acetylation== Many of the drugs used today for common diseases require additional structuring in order for efficient metabolism in the body. Drugs that are significantly metabolized by acetylation include isoniazid, hydralazine, procainamide, phenelzine, and dapsone that are used to treat tuberculosis, cardiac failure/hypertension, ventricular arrhythmias, depression, and leprosy/skin infections respectively. =='''Reference'''== Berg, Tymoczko, Stryer. Biochemistry Sixth Edition. Yang XJ, Seto E (2008). "Lysine acetylation: codified crosstalk with other posttranslational modifications". Mol Cell 31: 449–61. doi:10.1016/j.molcel.2008.07.002. {{PMID|18722172}}. [http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6WSR-4T8B978-1&_user=10&_coverDate=08%2F22%2F2008&_rdoc=1&_fmt=full&_orig=search&_cdi=7053&_sort=d&_docanchor=&view=c&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=55d9f9d5e5ea1460283ec6214ce464fa#bib89] Arnesen T, Polevoda B, Sherman F.(2009)"A synopsis of eukaryotic Nα-terminal acetyltransferases: nomenclature, subunits and substrates" [http://www.biomedcentral.com/1753-6561/3/S6/S2#refs] "Histone Acetylation, DNA Methylation and Epigenetics" [http://www.web-books.com/MoBio/Free/Ch4G.htm] 4esis78fts4kcm7j9s1v0mlufqey18q 0 226692 4634071 1794256 2026-05-04T12:29:25Z Jcb 90773 4634071 wikitext text/x-wiki {{Radiation_Oncology/TOC}} <big>'''Epilepsy'''</big> *'''UC San Francisco''' -- SRS 20 Gy vs SRS 24 Gy **Randomized. 30 patients, intractable medial temporal lobe epilepsy. Arm 1) SRS 20 Gy vs Arm 2) SRS 24 Gy. Target at the amygdala, 2 cm of the anterior hippocampus and parahipocampal gyrus, 50% prescription isodose. Used post-treatment MRI, and seizure remission (complete seizure control between 24 and 36 months after therapy) **'''2010''' {{PMID|20065252}} -- "Predictors of efficacy after stereotactic radiosurgery for medial temporal lobe epilepsy." (Chang EF, Neurology. 2010 Jan 12;74(2):165-72.) ***Outcome: seizure-free 20 Gy 59% vs 24 Gy 77% (NS). MRI response variable, despite standardized targeting. Degree of early MRI alterations predicted long-term seizure remission ***Conclusion: Temporal lobe SRS resulted in significant seizure reduction, in a delayed fashion 7kf17j1e916xd6d58h0gv1o7ubzj9s7 0 237399 4634107 4633811 2026-05-04T15:59:25Z Jeff1138 301139 4634107 wikitext text/x-wiki ==Introduction== [[#Graphical Image Editing Art]] [[#Office Application]] [[#Audio]] [[#Misc Application]] [[#Games & Emulation]] [[#Application Guides]] [[#top|...to the top]] [[#top|...to the top]] Most apps can be opened on the Workbench (aka publicscreen pubscreen) which is the default display option but can offer a custom one set to your configurations (aka custom screen mode promotion). These custom ones tend to stack so the possible use of A-M/A-N method of switching between full screens and the ability to pull down screens as well If you are interested in creating or porting new software, see [http://en.wikibooks.org/wiki/Aros/Developer/Docs here] {| class="wikitable sortable" |- !width:30%;|Internet Applications !width:10%;|AROS(x86) !width:10%;|Commodore-Amiga OS 3.1 (68k) !width:10%;|Hyperion OS4(PPC) !width:10%;|MorphOS(PPC) |- |<!--Sub Menu-->Web Online Browser [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=network/browser Odyssey 2.0], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1175&highlight=odyssey&rowstart=100 Odyssey 3.0], |<!--Amiga OS-->[https://blog.alb42.de/programs/amifox/ amifox] with [https://github.com/alb42/wrp wrp server], IBrowse*, Voyager*, [ AWeb], [https://github.com/matjam/aweb AWeb Src], [http://aminet.net/package/comm/www/NetSurf-m68k-sources Netsurf], [], |<!--AmigaOS4-->[ Odyssey OWB], [ Timberwolf (Firefox port 2011)], [http://amigaworld.net/modules/newbb/viewtopic.php?forum=32&topic_id=32847 OWB-mui], [http://strohmayer.org/owb/ OWB-Reaction], IBrowse*, [http://os4depot.net/index.php?function=showfile&file=network/browser/aweb.lha AWeb], Voyager, [http://www.os4depot.net/index.php?function=browse&cat=network/browser Netsurf], |<!--MorphOS-->Wayfarer, [http://fabportnawak.free.fr/owb/ Odyssey OWB], [ Netsurf], IBrowse*, AWeb, [], |- |<!--Sub Menu-->YouTube Viewing and downloading videos |<!--AROS-->Odyssey 2.0 can show Youtube webpage, [https://blog.alb42.de/amitube/ Amitube], |[https://blog.alb42.de/amitube/ Amitube], [https://github.com/YePpHa/YouTubeCenter/releases or this one], |[https://blog.alb42.de/amitube/ Amitube], getVideo, Tubexx, [https://github.com/walkero-gr/aiostreams aiostreams], |[ Wayfarer], [https://blog.alb42.de/amitube/ Amitube],Odyssey (OWB), [http://morphos.lukysoft.cz/en/vypis.php?kat=5 getVideo], Tubexx |- |<!--Sub Menu-->E-mailing SMTP POP3 IMAP based |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=network/email SimpleMail], [http://sourceforge.net/projects/simplemail/files/ src], [https://github.com/jens-maus/yam YAM] |<!--Amiga OS-->[http://sourceforge.net/projects/simplemail/files/ SimpleMail], [https://github.com/jens-maus/yam YAM] |<!--AmigaOS4-->SimpleMail, YAM, |<!--MorphOS--> SimpleMail, YAM |- |<!--Sub Menu-->IRC |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=network/chat WookieChat], [https://sourceforge.net/projects/wookiechat/ Wookiechat src], [http://archives.arosworld.org/index.php?function=browse&cat=network/chat AiRcOS], Jabberwocky, |<!--Amiga OS-->Wookiechat, AmIRC |<!--AmigaOS4-->Wookiechat |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Wookiechat], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 AmIRC], |- |<!--Sub Menu-->Instant Messaging IM like [https://github.com/BlitterStudio/amidon Hollywood Mastodon client], BlueSky AT protocol, Facebook(TM), Twitter (TM) and others |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=network/chat jabberwocky], Bitlbee IRC Gateway |<!--Amiga OS-->[http://amitwitter.sourceforge.net/ AmiTwitter], CLIMM, SabreMSN, jabberwocky, |<!--AmigaOS4-->[http://amitwitter.sourceforge.net/ AmiTwitter], SabreMSN, |<!--MorphOS-->[http://amitwitter.sourceforge.net/ AmiTwitter], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 PolyglotNG], SabreMSN, |- |<!--Sub Menu-->Torrents |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=network/p2p ArTorr], |<!--Amiga OS--> |<!--AmigaOS4-->CTorrent, Transmission |<!--MorphOS-->MLDonkey, Beehive, [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Transmission], CTorrent, |- |<!--Sub Menu-->FTP |<!--AROS-->Plugin included with Dopus Magellan, MarranoFTP, |<!--Amiga OS-->[http://aminet.net/package/comm/tcp/AmiFTP AmiFTP], AmiTradeCenter, ncFTP, |<!--AmigaOS4--> |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Pftp], [http://aminet.net/package/comm/tcp/AmiFTP-1.935-OS4 AmiFTP], |- |<!--Sub Menu-->WYSIWYG Web Site Editor |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Internet Radio Streaming Audio [http://www.gnu.org/software/gnump3d/ gnump3d], [http://www.icecast.org/ Icecast2] Server (Broadcast) and Client (Listen), [ mpd], [http://darkice.sourceforge.net/ DarkIce], [http://www.dyne.org/software/muse/ Muse], |<!--AROS-->Mplayer (Icecast Client only), |<!--Amiga OS-->[https://github.com/sandlbn/TuneFinder TuneFinder C Src], [https://github.com/sandlbn/TuneFinderMUI TuneFinderMUI], [http://amigazeux.net/anr/ AmiNetRadio], [], [], |<!--AmigaOS4-->[http://www.tunenet.co.uk/ Tunenet], |<!--MorphOS-->Mplayer, AmiNetRadio, |- |<!--Sub Menu-->VoIP (Voice over IP) with SIP Client (Session Initiation Protocol) or Asterisk IAX2 Clients Softphone (skype like) |<!--AROS--> |<!--Amiga OS-->AmiPhone with Speak Freely, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Weather Forecast |<!--AROS-->[http://sourceforge.net/projects/zunetools/files/ WeatherBar], [http://archives.arosworld.org/index.php?function=browse&cat=utility/workbench AWeather], [] |<!--Amiga OS-->[http://amigazeux.net/wetter/ Wetter], |<!--AmigaOS4-->[http://os4depot.net/?function=showfile&file=utility/workbench/flipclock.lha FlipClock], |<!--MorphOS-->[http://amigazeux.net/wetter/ Wetter], |- |<!--Sub Menu-->Street Road Maps Route Planning GPS Tracking |<!--AROS-->[https://blog.alb42.de/programs/muimapparium/ MuiMapparium] [https://build.alb42.de/ Build of MuiMapp versions], |<!--Amiga OS-->AmiAtlas*, UKRoutePlus*, [http://blog.alb42.de/ AmOSM], |<!--AmigaOS4--> |<!--MorphOS-->[http://blog.alb42.de/programs/mapparium/ Mapparium], |- |<!--Sub Menu-->Clock and Date setting from the internet (either ntp or websites) [https://www.timeanddate.com/worldclock/ World Clock], [http://www.time.gov/ NIST], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=network/misc ntpsync], |<!--Amiga OS-->ntpsync |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Newsgroups |<!--AROS--> |<!--Amiga OS-->[http://newscoaster.sourceforge.net/ Newscoaster], [https://github.com/jens-maus/newsrog NewsRog], [ WorldNews], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->IP-based video production workflows with High Dynamic Range (HDR), 10-bit color collaborative NDI, |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Blogging like Lemmy or kbin |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->VR face recognition for Vtubers |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->VR chatting Live 2D models with Cubism type editor <pre> Model data (cmo3) Basic motions (can3) Background image (png) Set of files for embedding (runtime folder) • Model data (moc3) • Motion data (motion3.json) • Model settings file (model3.json) • Physics settings file (physics3.json) • Display auxiliary file (cdi3.json) </pre> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->VR chatting chatters .VRML models - standardized 3D file format for VR avatars |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->V-tubers V-tubing like Vseeface with Openseeface tracker or Vpuppr (virtual puppet project) for 2d / 3d art models rigging rigged LIV |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |} <nowiki>*</nowiki> Commercial product. ==Graphical Image Editing Art== {| class="wikitable sortable" |- !width:30%;|Image Editing !width:10%;|AROS(x86) !width:10%;|Commodore-Amiga OS 3.1(68k) !width:10%;|Hyperion OS4(PPC) !width:10%;|MorphOS(PPC) |- |<!--Sub Menu-->Pixel Raster Artwork [https://github.com/LibreSprite/LibreSprite LibreSprite based on GPL aseprite], [https://github.com/abetusk/hsvhero hsvhero], [], |<!--AROS-->[https://sourceforge.net/projects/zunetools/files/ZunePaint/ ZunePaint], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/edit LunaPaint], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/edit GrafX2], [ LodePaint needs OpenGL], |<!--Amiga OS-->[http://www.amigaforever.com/classic/download.html PPaint], GrafX2, [https://github.com/grovdata/Amiga_Sources/blob/master/software.md DeluxePaint], [http://www.amiforce.de/perfectpaint/perfectpaint.php PerfectPaint], Zoetrope, Brilliance2*, |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=graphics/edit LodePaint], GrafX2, |<!--MorphOS-->Sketch, Pixel*, GrafX2, [http://morphos.lukysoft.cz/en/vypis.php?kat=3 LunaPaint] |- |<!--Sub Menu-->Image viewing |<!--AROS-->[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/viewer LookHere], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/viewer LoView], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/viewer PicShow] , [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=31400&forum=32&start=80&viewmode=flat&order=0#583458 Picture Album], |<!--Amiga OS-->PicShow, PicView, Photoalbum, |<!--AmigaOS4-->WarpView, PicShow, flPhoto, Thumbs, [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=31400&forum=32&start=80&viewmode=flat&order=0#583458 Picture Album], |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&topic_id=31400&forum=32&start=80&viewmode=flat&order=0#583458 Picture Album] |- |<!--Sub Menu-->Photography retouching / Image Manipulation like Photoshop(tm) |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=graphics/edit RNOEffects], [https://sourceforge.net/projects/zunetools/files/ ZunePaint], [http://sourceforge.net/projects/zunetools/files/ ZuneView], |<!--Amiga OS-->[ Tecsoft Video Paint aka TVPaint], Photogenics*, ArtEffect*, ImageFX*, XiPaint, fxPaint, ImageMasterRT, Opalpaint, |<!--AmigaOS4-->WarpView, flPhoto, [http://www.os4depot.net/index.php?function=browse&cat=graphics/edit Photocrop] |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], ImageFX*, |- |<!--Sub Menu-->Manage RAW picture folder galleries like Darktable, RAWtherapy, etc |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Graphic Format Converter - ICC profile support sRGB, Adobe RGB, XYZ and linear RGB |<!--AROS--> |<!--Amiga OS-->GraphicsConverter, ImageStudio, [http://www.coplabs.org/artpro.html ArtPro] |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Thumbnail Generator [], |<!--AROS-->[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&cat=utility/shell Thumbnail Generator] |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Icon Editor |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=graphics/iconedit Archives], [http://archives.arosworld.org/index.php?function=browse&cat=utility/workbench Icon Toolbox], |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=graphics/iconedit IconEditor] |<!--MorphOS--> |- |<!--Sub Menu-->2D Pixel Art Animation |<!--AROS-->Lunapaint |<!--Amiga OS-->PPaint, AnimatED, Scala*, GoldDisk MovieSetter*, Walt Disney's Animation Studio*, ProDAD*, [https://github.com/historicalsource/DeluxePaint DeluxePaint src], Brilliance |<!--AmigaOS4--> |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=3 Titler] |- |<!--Sub Menu-->2D SVG based MovieSetter type |<!--AROS--> |<!--Amiga OS-->MovieSetter*, Fantavision* |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Morphing |<!--AROS-->[ GLMorph] |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->2D Cad (qcad->LibreCAD, etc.) |<!--AROS--> |<!--Amiga OS-->Xcad, MaxonCAD |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->3D Cad like FreeCad, BRL-CAD, OpenSCAD, AvoCADo, etc. using dxf, obj (vertices), blend, |<!--AROS--> |<!--Amiga OS-->XCad3d*, DynaCADD*, Cycas, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->3D Model Rendering of glft (json) gbl (png jpg), usdz (USD files with materials, textures, and animations), FBX Filmbox is a proprietary Autodesk format, |<!--AROS-->POV-Ray |<!--Amiga OS-->[http://www.discreetfx.com./amigaproducts.html CINEMA 4D]*, POV-Ray, Lightwave3D*, Real3D*, Caligari24*, Reflections/Monzoom*, [https://github.com/privatosan/RayStorm Raystorm src], Tornado 3D |<!--AmigaOS4-->Blender, POV-Ray, Yafray |<!--MorphOS-->Blender, POV-Ray, Yafray |- |<!--Sub Menu-->3D Format Converter [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=showfile&file=graphics/convert/ivcon.lha IVCon] |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Screen grabbing display |<!--AROS-->[ Screengrabber], [http://archives.arosworld.org/index.php?function=browse&cat=utility/misc snapit], [http://archives.arosworld.org/index.php?function=browse&cat=video/record screen recorder], [] |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Grab graphics music from apps [https://github.com/Malvineous/ripper6 ripper6], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |} <nowiki>*</nowiki> Commercial product. [[#top|...to the top]] ==Office Application== {| class="wikitable sortable" |- !width:30%;|Office !width:10%;|AROS (x86) !width:10%;|[http://en.wikipedia.org/wiki/Amiga_software Commodore-Amiga OS 3.1] (68k) !width:10%;|[http://en.wikipedia.org/wiki/AmigaOS_4 Hyperion OS4] (PPC) !width:10%;|[http://en.wikipedia.org/wiki/MorphOS MorphOS] (PPC) |- |<!--Sub Menu-->Word-processing |<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=office/wordprocessing Cinnamon Writer], [https://finalwriter.godaddysites.com/ Final Writer 7*], [https://github.com/sodero/MUI-Vim/releases MUI-Vim], [ ], |<!--AmigaOS-->[ Softwood FinalCopy II*], Haage AmigaWriter*, Digita WordWorth*, Softwood FinalWriter*, Micro-Systems Excellence 3*, Arnor Protext, Rashumon, [ InterWord], [ KindWords], [WordPerfect], [ New Horizons Flow], [ CygnusEd Pro], [ Micro-systems Scribble], |<!--AmigaOS4-->AbiWord, [ CinnamonWriter] |<!--MorphOS-->[ Cinnamon Writer], [http://www.meta-morphos.org/viewtopic.php?topic=1246&forum=53 scriba], [http://morphos.lukysoft.cz/en/index.php Papyrus Office], |- |<!--Sub Menu-->Spreadsheets |<!--AROS-->[https://blog.alb42.de/programs/leu/ Leu], [https://archives.arosworld.org/index.php?function=browse&cat=office/spreadsheet], |<!--AmigaOS-->[https://aminet.net/package/biz/spread/ignition-src Ignition Src 1.3], [MaxiPlan 500 Plus], [OXXI Plan/IT v2.0 Speadsheet], [ Superplan], [ Creative Developments TurboCalc], [ ProCalc], [ InterSpread], [Digita DGCalc], [ Gold Disk Advantage], [ Micro-systems Analyze!] |<!--AmigaOS4-->Gnumeric, [https://ignition-amiga.sourceforge.net/ Ignition], |<!--MorphOS-->[ ignition], [http://morphos.lukysoft.cz/en/vypis.php Papyrus Office], |- |<!--Sub Menu-->Presentations |<!--AROS-->[http://www.hollywoood-mal.com/ Hollywood]*, |<!--Amiga OS-->[http://www.hollywoood-mal.com/ Hollywood]*, MediaPoint, PointRider, Scala*, |<!--Amiga OS4-->[http://www.hollywoood-mal.com/ Hollywood]*, PointRider |<!--MorphOS-->[http://www.hollywoood-mal.com/ Hollywood]*, PointRider |- |<!--Sub Menu-->Databases |<!--AROS-->[http://sdb.freeforums.org/ SDB], [http://archives.arosworld.org/index.php?function=browse&cat=office/database BeeBase], |<!--Amiga OS-->Precision Superbase 4 Pro*, Arnor Prodata*, BeeBase, Datastore, FinalData*, AmigaBase, Fiasco, Twist2*, [Digita DGBase], [], |<!--AmigaOS4-->BeeBase, SQLite, |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=6 BeeBase], |- |<!--Sub Menu-->PDF Viewing and editing digital signatures |<!--AROS-->[http://sourceforge.net/projects/arospdf/ ArosPDF via splash], [https://github.com/wattoc/AROS-vpdf vpdf wip], |<!--Amiga OS-->APDF |<!--AmigaOS4-->AmiPDF |<!--MorphOS-->APDF, vPDF, |- |<!--Sub Menu-->Printing |<!--AROS-->Postscript 3 laser printers and Ghostscript internal, [ GutenPrint], |<!--Amiga OS-->[http://www.irseesoft.de/tp_what.htm TurboPrint]* |<!--AmigaOS4-->(some native drivers), |<!--MorphOS-->early TurboPrint included, |- |<!--Sub Menu-->Note Taking Rich Text support like joplin, OneNote, EverNote Notes, xournalpp, etc |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->PIM Personal Information Manager - Day Diary Planner Calendar App |<!--AROS-->[ ], [ ], [ ], |<!--Amiga OS-->Digita Organiser*, On The Ball, Everyday Organiser, [ Contact Manager], |<!--AmigaOS4-->AOrganiser, |<!--MorphOS-->[http://polymere.free.fr/orga_en.html PolyOrga], |- |<!--Sub Menu-->Accounting |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=office/misc ETB], LoanCalc, [ ], [ ], [ ], |[ Digita Home Accounts2], Accountant, Small Business Accounts, Account Master, [ Amigabok], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Project Management |<!--AROS--> |<!--Amiga OS-->SuperGantt, SuperPlan, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->System Wide Dictionary - multilingual [http://sourceforge.net/projects/babiloo/ Babiloo], [http://code.google.com/p/stardict-3/ StarDict], |<!--AROS-->[ ], |<!--AmigaOS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->System wide Thesaurus - multi lingual |<!--AROS-->[ ], |Kuma K-Roget*, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Sticky Desktop Notes (post it type) |<!--AROS-->[http://aminet.net/package/util/wb/amimemos.i386-aros AmiMemos], [https://aminet.net/package/util/wb/amimemos.src-aros AmiMemos Src], [], |<!--Amiga OS-->[http://aminet.net/package/util/wb/StickIt-2.00 StickIt v2], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->DTP Desktop Publishing |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=graphics/edit RNOPublisher], |<!--Amiga OS-->[http://pagestream.org/ Pagestream]*, Professional Pro Page*, Saxon Publisher, Pagesetter, PenPal, |<!--AmigaOS4-->[http://pagestream.org/ Pagestream]* |<!--MorphOS-->[http://pagestream.org/ Pagestream]* |- |<!--Sub Menu-->Scanning |<!--AROS-->[ SCANdal], [], |<!--Amiga OS-->FxScan*, ScanQuix* |<!--AmigaOS4-->SCANdal (Sane) |<!--MorphOS-->SCANdal |- |<!--Sub Menu-->OCR |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=graphics/convert gOCR] |<!--AmigaOS--> |<!--AmigaOS4--> |<!--MorphOS-->[http://morphos-files.net/categories/office/text Tesseract] |- |<!--Sub Menu-->Text Editing |<!--AROS-->Jano Editor (already installed as Editor), [http://archives.arosworld.org/index.php?function=browse&cat=development/edit EdiSyn], [http://archives.arosworld.org/index.php?function=browse&cat=utility/text/edit Annotate], [https://archives.arosworld.org/index.php?function=browse&cat=development/edit Vim], [http://archives.arosworld.org/index.php?function=browse&cat=utility/text/edit FrexxEd] [https://github.com/vidarh/FrexxEd src], [ NoWinEd], |<!--Amiga OS-->Annotate, MicroGoldED/CubicIDE*, CygnusED*, Turbotext, Protext*, NoWinED, |<!--AmigaOS4-->Notepad, Annotate, CygnusED*, NoWinED, |<!--MorphOS-->MorphOS ED, NoWinED, GoldED/CubicIDE*, CygnusED*, Annotate, |- |<!--Sub Menu-->Office Fonts [http://sourceforge.net/projects/fontforge/files/fontforge-source/ Font Designer] |<!--AROS-->[ ], [ ], |<!--Amiga OS-->TypeSmith*, SaxonScript (GetFont Adobe Type 1), |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Drawing Vector |<!--AROS-->[http://sourceforge.net/projects/amifig/ ZuneFIG previously AmiFIG] |<!--Amiga OS-->Drawstudio*, ProVector*, ArtExpression*, Professional Draw*, AmiFIG, MetaView, [https://gitlab.com/amigasourcecodepreservation/designworks Design Works Src], [], |<!--AmigaOS4-->MindSpace, [http://www.os4depot.net/index.php?function=browse&cat=graphics/edit amifig], |<!--MorphOS-->SteamDraw, [http://aminet.net/package/gfx/edit/amifig amiFIG], |- |<!--Sub Menu-->video conferencing (jitsi) |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->source code hosting |<!--AROS-->Gitlab, |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Remote Desktop (server) |<!--AROS-->[http://sourceforge.net/projects/zunetools/files/VNC_Server ArosVNCServer], |<!--Amiga OS-->[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC], [http://dspach.free.fr/amiga/avnc/index.html AVNC] |<!--AmigaOS4-->[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC] |MorphVNC, vncserver |- |<!--Sub Menu-->Remote Desktop (client) |<!--AROS-->[https://sourceforge.net/projects/zunetools/files/VNC_Client/ ArosVNC], [http://archives.arosworld.org/index.php?function=browse&cat=network/misc rdesktop], |<!--Amiga OS-->[http://twinvnc.free.fr/index.php?menu=01&lang=eng TwinVNC], [http://dspach.free.fr/amiga/vva/index.html VVA], [http://www.hd-zone.com/ RDesktop] |<!--AmigaOS4-->[http://twinvnc.free.fr/index.php?menu=01&lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop] |[http://twinvnc.free.fr/index.php?menu=01&lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop] |- |<!--Sub Menu-->notifications |<!--AROS--> |<!--Amiga OS-->Ranchero |<!--AmigaOS4-->Ringhio |<!--MorphOS-->MagicBeacon |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |} <nowiki>*</nowiki> Commercial product. [[#top|...to the top]] ==Audio== {| class="wikitable sortable" |- !width:30%;|Audio !width:10%;|AROS(x86) !width:10%;|Commodore-Amiga OS 3.1(68k) !width:10%;|Hyperion OS4(PPC) !width:10%;|MorphOS(PPC) |- |<!--Sub Menu-->Playing playback Audio like MP3, [https://github.com/chrg127/gmplayer NSF], [https://github.com/kode54/lazyusf miniusf .usflib], [], etc |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=video/play Mplayer], [ HarmonyPlayer hp], [http://www.a500.org/downloads/audio/index.xhtml playcdda] CDs, [ WildMidi Player], [https://bszili.morphos.me/ UADE mod player], [], [RNOTunes ], [ mp3Player], [], |<!--Amiga OS-->AmiNetRadio, AmigaAmp, playOGG, |<!--AmigaOS4-->TuneNet, SimplePlay, AmigaAmp, TKPlayer |AmiNetRadio, Mplayer, Kaya, AmigaAmp |- |<!--Sub Menu-->Editing Audio |<!--AROS-->[ Audio Evolution 4] |<!--Amiga OS-->[ Samplitude Opus Key], [https://sourceforge.net/projects/hd-rec/ HD-Rec Src], [http://www.sonicpulse.de/eng/news.html SoundFX], |<!--AmigaOS4-->[https://sourceforge.net/projects/hd-rec/ HD-Rec], AmiSoundED, [http://os4depot.net/?function=showfile&file=audio/record/audioevolution4.lha Audio Evolution 4] |[http://www.hd-rec.de/HD-Rec/index.php?site=home HD-Rec], |- |<!--Sub Menu-->Editing Tracker Music |<!--AROS-->[https://github.com/hitchhikr/protrekkr Protrekkr], [ Schism Tracker], [http://archives.arosworld.org/index.php?function=browse&cat=audio/tracker MilkyTracker], [http://www.hivelytracker.com/ HivelyTracker], [ Radium in AROS already], [http://www.a500.org/downloads/development/index.xhtml libMikMod], |<!--Amiga OS-->MilkyTracker, HivelyTracker, DigiBooster, Octamed SoundStudio, |<!--AmigaOS4-->MilkyTracker, HivelyTracker, GoatTracker |MilkyTracker, GoatTracker, DigiBooster, |- |<!--Sub Menu-->Editing Music [], [https://github.com/kmatheussen/camd CAMD] and/or staves and notes manuscript |<!--AROS-->[http://bnp.hansfaust.de/ Bars and Pipes for AROS], [ Audio Evolution], [], |<!--Amiga OS-->[http://bnp.hansfaust.de/ Bars'n'Pipes], MusicX* David "Talin" Joiner & Craig Weeks (for Notator-X), Deluxe Music Construction 2*, [https://github.com/timoinutilis/midi-sequencer-amigaos Horny c Src], HD-Rec, [https://aminet.net/package/mus/midi/dominatorV1_51 Dominator], |<!--AmigaOS4-->[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Rockbeat, [http://bnp.hansfaust.de/download.html Bars'n'Pipes], [http://os4depot.net/index.php?function=browse&cat=audio/edit Horny], Audio Evolution 4, |<!--MorphOS-->Bars'n'Pipes, |- |<!--Sub Menu-->Sound Sampling |<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=audio/record Audio Evolution 4], [http://www.imica.net/SitePortalPage.aspx?siteid=1&did=162 Quick Record], [https://archives.arosworld.org/index.php?function=browse&cat=audio/misc SOX to get AIFF 16bit files], [https://github.com/aros-development-team/AROS/tree/master/workbench/tools/AHIRecord AHIRecord], |<!--Amiga OS-->[https://aminet.net/package/mus/edit/AudioEvolution3_src Audio Evolution 3 c src], [ Samplitude-MS Opus Key], Audiomaster IV*, |<!--AmigaOS4-->[https://github.com/timoinutilis/phonolith-amigaos phonolith c src], HD-Rec, Audio Evolution 4, |<!--MorphOS-->[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Audio Evolution 4, |- |<!--Sub Menu-->Live Looping or Audio Misc - Groovebox like |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->CD/DVD burn |[https://code.google.com/p/amiga-fryingpan/ FryingPan], |<!--Amiga OS-->FryingPan, [http://www.estamos.de/makecd/#CurrentVersion MakeCD], |<!--AmigaOS4-->FryingPan, AmiDVD, |[http://www.amiga.org/forums/printthread.php?t=58736 FryingPan], Jalopeano, |- |<!--Sub Menu-->CD/DVD audio rip |Lame, [http://www.imica.net/SitePortalPage.aspx?siteid=1&cfid=0&did=167 Quick CDrip], |<!--Amiga OS-->Lame, |<!--AmigaOS4-->Lame, |Lame, |- |<!--Sub Menu-->MP3 v1 and v2 Tagger |<!--AROS-->id3ren (v1), [http://archives.arosworld.org/index.php?function=browse&cat=audio/edit mp3info], |<!--Amiga OS--> |<!--AmigaOS4--> | |- |<!--Sub Menu-->Audio Convert |<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=audio/misc Sox], [], |<!--Amiga OS-->[http://aminet.net/package/mus/misc/SoundBox SoundBox], [http://aminet.net/package/mus/misc/SoundBoxKey SoundBox Key], [http://aminet.net/package/mus/edit/SampleE SampleE], sox |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->DJ mixing jamming |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Radio Automation Software [http://www.rivendellaudio.org/ Rivendell], [http://code.campware.org/projects/livesupport/report/3 Campware LiveSupport], [http://www.sourcefabric.org/en/airtime/ SourceFabric AirTime], [http://www.ohloh.net/p/mediabox404 MediaBox404], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Speakers Audio Sonos Mains AC networked wired controlled *2005 ZP100 with ZP80 *2008 Zoneplayer ZP120 (multi-room wireless amp) ZP90 receiver only with CR100 controller, *2009 ZonePlayer S5, *2010 BR100 wireless Bridge (no support), *2011 Play:3 *2013 Bridge (no support), Play:1, *2016 Arc, Play:1, *Beam (Gen 2), Playbar, Ray, Era 100, Era 300, Roam, Move 2, *Sub (Gen 3), Sub Mini, Five, Amp S2 |<!--AROS-->SonosController |<!--Amiga OS-->SonosController |<!--AmigaOS4-->SonosController |<!--MorphOS-->SonosController |- |<!--Sub Menu-->Smart Speakers |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |} <nowiki>*</nowiki> Commercial product. [[#top|...to the top]] ==Video Creativity and Production== {| class="wikitable sortable" |- !width:30%;|Video !width:10%;|AROS(x86) !width:10%;|Commodore-Amiga OS 3.1(68k) !width:10%;|Hyperion OS4(PPC) !width:10%;|MorphOS(PPC) |- |<!--Sub Menu-->Playing Video |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=video/play Mplayer VAMP], [http://www.a500.org/downloads/video/index.xhtml CDXL player], [http://www.a500.org/downloads/video/index.xhtml IffAnimPlay], [], |<!--Amiga OS-->Frogger*, AMP2, MPlayer, RiVA*, MooViD*, |<!--AmigaOS4-->DvPlayer, MPlayer |<!--MorphOS-->MPlayer, Frogger, AMP2, VLC |- |<!--Sub Menu-->Streaming Video and game streaming like OBS studio, Parsec, etc |<!--AROS-->Mplayer, |<!--Amiga OS--> |<!--AmigaOS4-->Mplayer, Gnash, Tubexx |<!--MorphOS-->Mplayer, OWB, Tubexx |- |<!--Sub Menu-->Playing DVD |<!--AROS-->[http://a-mc.biz/ AMC]*, Mplayer |<!--Amiga OS-->AMP2, Frogger |<!--AmigaOS4-->[http://a-mc.biz/ AMC]*, DvPlayer*, AMP2, |<!--MorphOS-->Mplayer |- |<!--Sub Menu-->Screen Recording |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=video/record Screenrecorder], [ ], [ ], [ ], [ ], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS-->Screenrecorder, |- |<!--Sub Menu-->Create and Edit Individual Video NLE |<!--AROS-->[ Mencoder], [ Quick Videos], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/edit AVIbuild], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/misc FrameBuild], FFMPEG, |<!--Amiga OS-->[ MainConcept Mainactor Broadcast*], [http://en.wikipedia.org/wiki/Video_Toaster Video Toaster*], MacroSystem MovieShop 4.3*, proDAD Adorage*, [ IOSpirit VHI studio]*, [Gold Disk ShowMaker], [], |<!--AmigaOS4-->FFMpeg/GUI |<!--MorphOS-->Blender, Mencoder, FFmpeg |- |<!--Sub Menu-->Subtitle editor |<!--AROS-->[https://aminet.net/package/text/edit/Slarti_Arosx86ABIv0 Slarti_Arosx86ABIv0], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |} <nowiki>*</nowiki> Commercial product. [[#top|...to the top]] ==Misc Application== {| class="wikitable sortable" |- !width:30%;|Misc Application !width:10%;|AROS(x86) !width:10%;|Commodore-Amiga OS 3.1 (68k) !width:10%;|Hyperion OS4(PPC) !width:10%;|MorphOS(PPC) |- |<!--Sub Menu-->File Management |<!--AROS-->DOpus4, [https://github.com/BlitterStudio/dopus5 DOpus Magellan aka DOpus 5], [ Scalos], [ ], |<!--Amiga OS-->DOpus2, DOpus 4, [http://sourceforge.net/projects/dopus5allamigas/files/?source=navbar DOpus Magellan DOpus5], ClassAction, FileMaster, [http://kazong.privat.t-online.de/archive.html DM2], [http://www.amiga.org/forums/showthread.php?t=4897 DirWork 2]*, [https://github.com/RudolphRiedel/DiskMaster2 DiskMaster2 src], |<!--AmigaOS4-->DOpus4, DOpus5, Filer, AmiDisk |<!--MorphOS-->DOpus4, DOpus5 |- |<!--Sub Menu-->File Verification / Repair |<!--AROS-->md5 (works in linux compiling shell), [http://archives.arosworld.org/index.php?function=browse&cat=utility/filetool workpar2] (PAR2), [http://zakalwe.fi/~shd/foss/cksfv/files/ compile cksfv from website], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS-->Par2, |- |App Installer |<!--AROS-->[], [ InstallerNG], |<!--Amiga OS-->InstallerNG, Grunch, |<!--AmigaOS4-->Jack |<!--MorphOS-->Jack |- |<!--Sub Menu-->Compression archiver [https://github.com/FS-make-simple/paq9a paq9a], [], |<!--AROS-->XAD system is a toolkit designed for handling various file and disk archiver |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->C/C++ IDE |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=utility/text/edit FrexxEd], [https://github.com/vidarh/FrexxEd FrexxEd src], Annotate, Murks, |<!--Amiga OS-->[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Annotate, |<!--AmigaOS4-->CodeBench , [https://gitlab.com/boemann/codecraft CodeCraft], |<!--MorphOS-->[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Anontate, |- |<!--Sub Menu-->Gui Creators |<!--AROS-->[ MuiBuilder], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS-->[ MuiBuilder], |- |<!--Sub Menu-->Catalog .cd .ct Editors |<!--AROS-->FlexCat |<!--Amiga OS-->[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat |<!--AmigaOS4-->[http://aminet.net/package/dev/misc/simplecat SimpleCat], FlexCat |[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat |- |<!--Sub Menu-->Binary Hexadecimal Editor |<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=development/edit Zaphod], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Repository |<!--AROS-->[ Git] |<!--Amiga OS--> |<!--AmigaOS4-->Git |<!--MorphOS--> |- |<!--Sub Menu-->Filesystem Backup |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Filesystem Repair |<!--AROS-->ArSFSDoctor, |<!--Amiga OS--> Quarterback Tools, [ ], [ ], [ ], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Multiple File renaming |<!--AROS-->DOpus 4 or 5, |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Anti Virus |<!--AROS--> |<!--Amiga OS-->VChecker, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Random Wallpaper Desktop changer [ DOpus5], [ Scalos], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Alarm Clock, Timer, Stopwatch, Countdown |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=utility/workbench DClock], [http://aminet.net/util/time/AlarmClockAROS.lha AlarmClock], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Digital Signage |<!--AROS-->Hollywood, Hollywood Designer |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Fortune Cookie Quotes Sayings |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=utility/misc AFortune], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Languages |<!--AROS--> |<!--Amiga OS-->Fun School, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Mathematics ([http://www-fourier.ujf-grenoble.fr/~parisse/install_en.html Xcas], etc.), |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=utility/scientific mathX] |<!--Amiga OS-->Maple V, mathX, Fun School, GCSE Maths, [ ], [ ], [ ], |<!--AmigaOS4-->Yacas |<!--MorphOS-->Yacas |- |} <nowiki>*</nowiki> Commercial product. ==Misc Application 2== {| class="wikitable sortable" |- !width:30%;|Misc Application !width:10%;|AROS(x86) !width:10%;|Commodore-Amiga OS 3.1(68k) !width:10%;|Hyperion OS4(PPC) !width:10%;|MorphOS(PPC) |- |<!--Sub Menu-->BASIC |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=development/language Basic4SDL], [ Ace Basic], [ X-AMOS], [SDLBasic], [ Alvyn], |<!--Amiga OS-->[http://www.amiforce.de/main.php Amiblitz 3], [http://amos.condor.serverpro3.com/AmosProManual/contents/c1.html Amos Pro], [http://aminet.net/package/dev/basic/ace24dist ACE Basic], |<!--AmigaOS4--> |<!--MorphOS-->sdlBasic |- |<!--Sub Menu-->OSK On Screen Keyboard |<!--AROS-->[], |<!--Amiga OS-->[https://aminet.net/util/wb/OSK.lha OSK] |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Screen Magnifier Magnifying Glass Magnification |<!--AROS-->[http://www.onyxsoft.se/files/zoomit.lha ZoomIT], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Comic Book CBR CBZ format reader viewer |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=graphics/viewer comics], [http://archives.arosworld.org/index.php?function=browse&cat=graphics/viewer comicon], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Ebook Reader |<!--AROS-->[https://blog.alb42.de/programs/#legadon Legadon EPUB],[] |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Ebook Converter |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Text to Speech tts [https://github.com/JonathanFly/bark-installer Bark], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=audio/misc flite], |<!--Amiga OS-->[http://www.text2speech.com translator], |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=search&tool=simple FLite] |<!--MorphOS-->[http://se.aminet.net/pub/aminet/mus/misc/ FLite] |- |<!--Sub Menu-->Speech Voice Recognition Dictation - [http://sourceforge.net/projects/cmusphinx/files/ CMU Sphinx], [http://julius.sourceforge.jp/en_index.php?q=en/index.html Julius], [http://www.isip.piconepress.com/projects/speech/index.html ISIP], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Speech Voice Changer [], [], [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Fractals |<!--AROS--> |<!--Amiga OS-->ZoneXplorer, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Landscape Rendering |<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=graphics/raytrace WCS World Construction Set], |<!--Amiga OS-->[ Vista Pro], [http://en.wikipedia.org/wiki/World_Construction_Set World Construction Set] |<!--AmigaOS4-->[ WCS World Construction Set], |<!--MorphOS-->[ WCS World Construction Set], |- |<!--Sub Menu-->Astronomy |<!--AROS-->[ Digital Almanac (ABIv0 only)], |<!--Amiga OS-->[http://aminet.net/search?query=planetarium Aminet search], [http://aminet.net/misc/sci/DA3V56ISO.zip Digital Almanac], [https://aminet.net/package/misc/sci/da3sourceV58 Src c V58], [ Galileo renamed to Distant Suns]*, [http://www.syz.com/DU/ Digital Universe]*, |<!--AmigaOS4-->[http://sourceforge.net/projects/digital-almanac/ Digital Almanac], Distant Suns*, [http://www.digitaluniverse.org.uk/ Digital Universe]*, |<!--MorphOS-->[http://www.aminet.net/misc/sci/da3.lha Digital Almanac], [http://www.aminet.net/package/misc/sci/da3-mos-src Src c V56], |- |<!--Sub Menu-->PCB design |<!--AROS--> |<!--Amiga OS-->[ ], [ ], [ ], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Genealogy History Family Tree Ancestry Records (FreeBMD, FreeREG, and FreeCEN file formats or GEDCOM GenTree) |<!--AROS--> |<!--Amiga OS--> [ Origins], [ Your Family Tree], [ ], [ ], [ ], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Screen Display Blanker screensaver |<!--AROS-->Blanker Commodity (built in), [https://archives.arosworld.org/index.php?function=browse&cat=graphics/screenblanker GarshneBlanker], [http://sourceforge.net/projects/gblanker/ GBlanker Src], [], |<!--Amiga OS-->MultiCX, |<!--AmigaOS4--> |<!--MorphOS-->ModernArt Blanker, |- |<!--Sub Menu-->Maths Graph Function Plotting |<!--AROS-->[https://blog.alb42.de/programs/#MUIPlot MUIPlot], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->App Utility Launcher Dock toolbar |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=utility/docky BoingBar], [], |<!--Amiga OS-->[https://github.com/adkennan/DockBot Dockbot], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Classroom Aids |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Assessments |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Reference |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Training |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Courseware |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Skills Builder |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->System |<!--AROS-->[ SysExplorer], [ SysMon], [ Scout], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |} <nowiki>*</nowiki> Commercial product. ==Games & Emulation== Some emulators/games require OpenGL to function and to adjust ahi prefs channels, frequency and unit0 and unit1 and [http://aros.sourceforge.net/documentation/users/shell/changetaskpri.php changetaskpri -1] Rom patching https://www.marcrobledo.com/RomPatcher.js/ https://www.romhacking.net/patch/ (ips, ups, bps, etc) and this other site supports the latter formats https://hack64.net/tools/patcher.php Free public domain roms for use with emulators can be found [http://www.pdroms.de/ here] as most of the rest are covered by copyright rules. If you like to read about old games see [http://retrogamingtimes.com/ here] and [http://www.armchairarcade.com/neo/ here] and a [http://www.vintagecomputing.com/ blog] about old computers. Possibly some of the [http://www.answers.com/topic/list-of-best-selling-computer-and-video-games best selling] of all time. [http://en.wikipedia.org/wiki/List_of_computer_system_emulators Wiki] with emulated systems list. [https://archive.gamehistory.org/ Archive of VGHF], [https://library.gamehistory.org/ Video Game History Foundation Library search] {| class="wikitable sortable" |- !width:10%;|Games [http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer Emulation] !width:10%;|AROS(x86) !width:10%;|AmigaOS3(68k) !width:10%;|AmigaOS4(PPC) !width:10%;|MorphOS(PPC) |- |<!--Sub Menu-->Games Emulation Amstrad CPC |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer], [ Caprice32 (OpenGL & pure SDL)], [ Arnold], [https://retroshowcase.gr/cpcbox-master/], |<!--Amiga OS--> |<!--AmigaOS4-->[http://os4depot.net/index.php?function=browse&cat=emulation/computer] |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=2], |- |<!--Sub Menu-->Games Emulation Apple2 and 2GS |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Arcade |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem Mame], [ SI Emu (ABIv0 only)], |<!--Amiga OS-->Mame, |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem xmame], amiarcadia, |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=2 Mame], |- |<!--Sub Menu-->Games Emulation Atari 2600 [], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem Stella], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Atari 5200 [https://github.com/wavemotion-dave/A5200DS A5200DS], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Atari 7800 |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Atari 400 800 130XL [https://github.com/wavemotion-dave/A8DS A8DS], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer Atari800], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Atari Lynx |<!--AROS-->[http://myfreefilehosting.com/f/6366e11bdf_1.93MB Handy (ABIv0 only)], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Atari Jaguar |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Bandai Wonderswan |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation BBC Micro and Acorn Electron [http://beehttps://bem-unix.bbcmicro.com/download.html BeebEm], [http://b-em.bbcmicro.com/ B-Em], [http://elkulator.acornelectron.co.uk/ Elkulator], [http://electrem.emuunlim.com/ ElectrEm], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Dragon 32 and Tandy CoCo [http://www.6809.org.uk/xroar/ xroar], [], |<!--AROS-->[], [], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Commodore C16 Plus4 |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Commodore C64 |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer Vice (ABIv0 only)], [], |<!--Amiga OS-->Frodo, |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem viceplus], |<!--MorphOS-->Vice, |- |<!--Sub Menu-->Games Emulation Commodore Amiga |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer Janus UAE], Emumiga, |<!--Amiga OS--> |<!--AmigaOS4-->[http://os4depot.net/index.php?function=browse&cat=emulation/computer UAE], |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=2 UAE], |- |<!--Sub Menu-->Games Emulation Japanese MSX MSX2 |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Mattel Intelivision |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Mattel Colecovision and Adam |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Milton Bradley (MB) Vectrex [ Vectrex OpenGL], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation PICO8 Pico-8 fantasy video game console [https://github.com/egordorichev/pemsa-sdl/ pemsa-sdl], [https://github.com/jtothebell/fake-08 fake-08], [https://github.com/Epicpkmn11/fake-08/tree/wip fake-08 fork], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Nintendo Gameboy |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem vba no sound], [], |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem vba] |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Nintendo NES |<!--AROS-->[ EmiNES], [http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem Fceu], [https://github.com/takahirox/nes-js?tab=readme-ov-file nes-js], [https://github.com/bfirsh/jsnes jsnes], [https://github.com/angelo-wf/NesJs NesJs], |<!--Amiga OS-->AmiNES, [http://www.dridus.com/~nyef/darcnes/ darcNES], |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem amines] |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Nintendo SNES |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem Zsnes], |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem warpsnes] |<!--MorphOS-->[http://fabportnawak.free.fr/snes/ Snes9x], |- |<!--Sub Menu-->Games Emulation Nintendo N64 *HLE and plugins [ mupen64], [https://github.com/ares-emulator/ares ares], [https://github.com/N64Recomp/N64Recomp N64Recomp], [https://github.com/rt64/rt64 rt64], [https://github.com/simple64/simple64 Simple64], *LLE [], |<!--AROS-->[http://code.google.com/p/mupen64plus/ Mupen64+], |<!--Amiga OS-->[http://code.google.com/p/mupen64plus/ Mupen64+], [http://aminet.net/package/misc/emu/tr-981125_src TR64], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->[ Nintendo Gamecube Wii] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->[ Nintendo Wii U] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->[https://github.com/yuzu-emu Nintendo Switch] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation NEC PC Engine |<!--AROS-->[], [], [https://github.com/yhzmr442/jspce js-pce], |[http://www.hugo.fr.fm/ Hugo], [http://mednafen.sourceforge.net/ Mednafen], |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem tgemu] |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sega Master System (SMS) |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem Dega], [http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem sms], |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem osmose] |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sega Genesis/Megadrive |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem gp no sound], [http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem DGen], |<!--Amiga OS-->[http://code.google.com/p/genplus-gx/ Genplus], |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem genesisplus] |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sega Saturn *HLE [https://mednafen.github.io/ mednafen], [http://yabause.org/ yabause], [], *LLE [], [], |<!--AROS-->? |<!--Amiga OS-->[http://yabause.org/ Yabause], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sega Dreamcast *HLE [https://github.com/flyinghead/flycast flycast], [https://code.google.com/archive/p/nulldc/downloads NullDC], *LLE [], [], |<!--AROS-->? |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sinclair ZX80 and ZX81 |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer], [], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sinclair Spectrum |[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer Fuse (crackly sound)], [http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer SimCoupe], [ FBZX slow], [https://jsspeccy.zxdemo.org/ jsspeccy], [http://torinak.com/qaop/games qaop], |<!--Amiga OS-->[http://www.lasernet.plus.com/ Asp], [http://www.zophar.net/sinclair.html Speculator], [http://www.worldofspectrum.org/x128/index.html X128], |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/computer] |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sinclair QL |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer], [], |<!--Amiga OS-->[http://aminet.net/package/misc/emu/QDOS4amiga1 QDOS4amiga] |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation SNK NeoGeo Pocket |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem], |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem gngeo], NeoPop, |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation Sony PlayStation |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/gamesystem FPSE], |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem FPSE] |<!--MorphOS--> |- |<!--Sub Menu-->[ Sony PS2] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->[ Sony PS3] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->[https://vita3k.org/ Sony Vita] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->[https://github.com/shadps4-emu/shadPS4 PS4] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation [http://en.wikipedia.org/wiki/Tangerine_Computer_Systems Tangerine] Oric and Atmos |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer Oricutron] |<!--Amiga OS--> |<!--AmigaOS4-->[http://www.os4depot.net/index.php?function=browse&cat=emulation/gamesystem Oricutron] |<!--MorphOS-->[http://aminet.net/package/misc/emu/oricutron Oricutron] |- |<!--Sub Menu-->Games Emulation TI 99/4 99/4A [https://github.com/wavemotion-dave/DS994a DS994a], [], [https://js99er.net/#/ js99er], [], [http://aminet.net/package/misc/emu/TI4Amiga TI4Amiga], [http://aminet.net/package/misc/emu/TI4Amiga_src TI4Amiga src in c], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=emulation/computer], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation HP 38G 40GS 48 49G/50G Graphing Calculators |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Emulation TI 58 83 84 85 86 - 89 92 Graphing Calculators |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu--> |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |} {| class="wikitable sortable" |- !width:10%;|Games [https://www.rockpapershotgun.com/ General] !width:10%;|AROS(x86) !width:10%;|AmigaOS3(68k) !width:10%;|AmigaOS4(PPC) !width:10%;|MorphOS(PPC) |- style="background:lightgrey; text-align:center; font-weight:bold;" | Games [https://www.trackawesomelist.com/michelpereira/awesome-open-source-games/ Open Source and others] || AROS || Amiga OS || Amiga OS4 || Morphos |- |<!--Sub Menu-->Games Action like [https://github.com/BSzili/OpenLara/tree/amiga/src source of openlara SDL2], [https://github.com/opentomb/OpenTomb opentomb], [https://github.com/LostArtefacts/TRX TRX formerly Tomb1Main], [https://github.com/TombEngine TombEngine], [http://archives.arosworld.org/index.php?function=browse&cat=game/action Thrust], [https://github.com/fragglet/sdl-sopwith sdl sopwith], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/action], [https://archives.arosworld.org/index.php?function=browse&cat=game/action BOH], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Adventure like [http://dotg.sourceforge.net/ DMJ], [https://github.com/kromenak/gengine Gabriel Knight 3], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/adventure], [https://archives.arosworld.org/?function=browse&cat=emulation/misc ScummVM], [http://www.toolness.com/wp/category/interactive-fiction/ Infocom], [http://www.accardi-by-the-sea.org/ Zork Online]. [http://www.sarien.net/ Sierra Sarien], [http://www.ucw.cz/draci-historie/index-en.html Dragon History for ScummVM], [] |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Board like [https://github.com/aperture-software/colditz-escape escape from colditz], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/board], [http://amigan.1emu.net/releases Africa] |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Cards like |<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=game/card ], [], |<!--AmigaOS-->[http://home.arcor.de/amigasolitaire/e/welcome.html Reko], [https://github.com/samskivert/beschei-en beschei Src], |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Misc [https://github.com/michelpereira/awesome-open-source-games Awesome open], [https://github.com/bobeff/open-source-games General Open Source], [https://github.com/SAT-R/sa2 Sonic Advance 2], [https://github.com/velorek1/cwordle Wordle type], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/misc], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games FPS like [https://aminet.net/package/game/shoot/D1X_Rebirth_AGA Descent D1X src], [https://github.com/DescentDevelopers/Descent3 Descent 3], [https://github.com/Fewnity/Counter-Strike-Nintendo-DS Counter-Strike-Nintendo-DS], [https://github.com/Aleph-One-Marathon/alephone Bungie Marathon 1994], [], |<!--AROS-->Doom, Quake, [http://archives.arosworld.org/index.php?function=browse&cat=game/fps Quake 3 Arena (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&cat=game/fps Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&cat=game/fps Assault Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&cat=game/fps Cube 2 Sauerbraten (OpenGL)], [http://fodquake.net/test/ FodQuake QuakeWorld], [ Duke Nukem 3D], [ Darkplaces Nexuiz Xonotic], [http://archives.arosworld.org/index.php?function=browse&cat=game/fps Doom 3 SDL (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&cat=game/fps Hexenworld and Hexen 2], [ Aliens vs Predator Gold 2000 (openGL)], [ Odamex (openGL doom)], |<!--Amiga OS-->Doom, Quake, AB3D, Fears, Breathless, |<!--AmigaOS4-->Doom, Quake, |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=12 Doom], Quake, Quake 3 Arena, [https://github.com/OpenXRay/xray-16 S.T.A.L.K.E.R Xray] |- |<!--Sub Menu-->Games MMORG like |<!--AROS-->[ Eternal Lands (OpenGL)], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Platform like |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/platform], [ Maze of Galious], [ Gish]*(openGL), [ Mega Mario], [http://www.gianas-return.de/ Giana's Return], [http://www.sqrxz.de/ Sqrxz], [.html Aquaria]*(openGL), [http://www.sqrxz2.de/ Sqrxz 2], [http://www.sqrxz.de/sqrxz-3/ Sqrxz 3], [http://www.sqrxz.de/sqrxz-4/ Sqrxz 4], [http://archives.arosworld.org/index.php?function=browse&cat=game/platform Cave Story], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Puzzle [https://github.com/mariopartyrd/marioparty4/tree/port Party], [], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/puzzle], [ Cubosphere (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&cat=game/puzzle Candy Crisis], [http://bszili.morphos.me/ TailTale], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Racing [ Trigger Rally], [ VDrift], [http://www.ultimatestunts.nl/index.php?page=2&lang=en Ultimate Stunts], [http://maniadrive.raydium.org/ Mania Drive], [https://github.com/plowteam/donut Simpsons Hit and Run], [], |<!--AROS-->[ Super Tux Kart (OpenGL)], [http://www.dusabledanslherbe.eu/AROSPage/F1Spirit.30.html F1 Spirit (OpenGL)], [http://bszili.morphos.me/index.html MultiRacer], |<!--AmigaOS--> |<!--AmigaOS4-->[http://bszili.morphos.me/index.html Speed Dreams], |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=12], [http://bszili.morphos.me/index.html TORCS], |- |<!--Sub Menu-->Games 1st first person DRPG [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/OpenEnroth/OpenEnroth OpenEnroth MM], [] |<!--AROS-->[https://github.com/BSzili/aros-stuff Arx Libertatis], [http://www.playfuljs.com/a-first-person-engine-in-265-lines/ js raycaster], [https://github.com/Dorthu/es6-crpg webgl], [https://github.com/sonountaleban/AmiShockolate System Shock], [], [], |<!--AmigaOS-->Phantasie, Faery Tale, Dungeon Master, |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games 3rd third person action CRPG [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/alexbatalov/fallout1-ce fallout ce], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games isometric RPG [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/topics/dungeon?l=javascript Dungeon], [], [https://github.com/clintbellanger/heroine-dusk JS Dusk], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/roleplaying nethack], [https://archives.arosworld.org/index.php?function=browse&cat=game/roleplaying GemRB], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games card based RPG [https://github.com/open-duelyst/duelyst Duelyst], [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Rhythm, Beat, Step [], [], [https://clonehero.net/ clonehero], [https://github.com/MatteoGodzilla/Dj-Engine Dj-Engine], |<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=game/misc Frets on Fire], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Shoot Em Ups [http://www.mhgames.org/oldies/formido/ Formido], [http://code.google.com/p/violetland/ Violetland], ||<!--AROS-->[https://archives.arosworld.org/index.php?function=browse&cat=game/action Open Tyrian], [http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ Alien Blaster], [https://github.com/OpenFodder/openfodder OpenFodder], |<!--AmigaOS--> |<!--AmigaOS4-->[http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], |<!--MorphOS--> |- |<!--Sub Menu-->Games Simulations [http://scp.indiegames.us/ Freespace 2], [http://www.heptargon.de/gl-117/gl-117.html GL117], [http://code.google.com/p/corsix-th/ Theme Hospital], [http://code.google.com/p/freerct/ Rollercoaster Tycoon], [http://hedgewars.org/ Hedgewars], [https://github.com/raceintospace/raceintospace raceintospace], [https://github.com/Return-To-The-Roots RTTR Settlers 2], [https://github.com/OoliteProject/oolite oolite elite], [https://github.com/fesh0r/newkind newkind elite], [], |<!--AROS--> |<!--Amiga OS-->SimCity, SimAnt, Sim Hospital, Theme Park, |<!--AmigaOS4--> |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=12] |- |<!--Sub Menu-->Games Life Sim [https://github.com/ACreTeam/forest Animal Crossing], [ ], [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Strategy [http://rtsgus.org/ RTSgus], [http://wargus.sourceforge.net/ Wargus], [http://stargus.sourceforge.net/ Stargus], [https://github.com/KD-lab-Open-Source/Perimeter Perimeter], [https://matty77.itch.io/conflict-3049 conflict-3049], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=game/strategy MegaGlest (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&cat=game/strategy UFO:AI (OpenGL)], [http://play.freeciv.org/ FreeCiv], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS-->[http://morphos.lukysoft.cz/en/vypis.php?kat=12] |- |<!--Sub Menu-->Games Horror [https://github.com/Mikompilation/MikuPan Fatal Frame], [ ], [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Sandbox Voxel Open World Exploration [https://github.com/UnknownShadow200/ClassiCube Classicube],[http://www.michaelfogleman.com/craft/ Craft], [https://github.com/tothpaul/DelphiCraft DelphiCraft],[https://www.minetest.net/ Luanti formerly Minetest], [ infiniminer], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Battle Royale [https://bruh.io/ Play.Bruh.io], [https://www.coolmathgames.com/0-copter Copter Royale], [https://surviv.io/ Surviv.io], [https://nuggetroyale.io/#Ketchup Nugget Royale], [https://miniroyale2.io/ Miniroyale2.io], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Tower Defense [https://chriscourses.github.io/tower-defense/ HTML5], [https://github.com/SBardak/Tower-Defense-Game TD C++], [https://github.com/bdoms/love_defense LUA and LOVE], [https://github.com/HyOsori/Osori-WebGame HTML5], [https://github.com/PascalCorpsman/ConfigTD ConfigTD Pascal], [https://github.com/GloriousEggroll/wine-ge-custom Wine], [] |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Visual Novel Engines [https://github.com/Kirilllive/tuesday-js Tuesday JS], [ Lua + LOVE], [https://github.com/weetabix-su/renpsp-dev RenPSP], [https://github.com/Galladite27/ONScripter-EN ONScripter-EN], [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Virtual Reality VR [https://gitlab.com/madsbuvi/openmw openmw vr], [https://github.com/Team-Beef-Studios/BeefRaiderXR BeefRaiderXR], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Virtual Table Top VTT [ Roll20], [https://www.owlbear.rodeo/ owlbear rodeo], [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Computer assisted TableTop TTRPG OSR [https://www.rpgsolo.com/play.php RPGSolo], [https://github.com/fpsvogel/solo-ttrpgs Solo TTRPG], [], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games 2D 3D Engines [https://github.com/fegennari/3DWorld 3DWorld], [https://github.com/GarageGames/Torque3D Torque3D], [https://github.com/gameplay3d/GamePlay GamePlay 3D], [https://www.babylonjs.com/ BabylonJS ], [ Godot], [ Ogre], [ Crystal Space], [], [], [], |<!--AROS-->[https://www.arkhamdev.net/wiki.htm?id=agx Arkham Development antiryadgx 8.9 lts with register], [], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games C based game frameworks [https://github.com/orangeduck/Corange Corange], [https://github.com/scottcgi/Mojoc Mojoc], [https://orx-project.org/ Orx], [https://github.com/ioquake/ioq3 Quake 3], [https://www.mapeditor.org/ Tiled], [https://www.raylib.com/ 2d Raylib], [https://github.com/Rabios/awesome-raylib other raylib], [https://github.com/MrFrenik/gunslinger Gunslinger], [https://o3de.org/ o3d], [http://archives.aros-exec.org/index.php?function=browse&cat=development/library GLFW], [], |<!--AROS-->[http://archives.arosworld.org/index.php?function=browse&cat=development/library Raylib 5], |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |- |<!--Sub Menu-->Games Virtual Pinball [https://github.com/vpinball/vpinball vpinball], [], |<!--AROS--> |<!--Amiga OS--> |<!--AmigaOS4--> |<!--MorphOS--> |} ==Application Guides== [[#top|...to the top]] ===Web Browser=== OWB is now at version 2.0 (which got an engine refresh, from July 2015 to February 2019) and 3.0. This latest version has a good support for many/most web sites, even YouTube web page now works. This improved compatibility comes at the expense of higher RAM usage (now 1GB RAM is the absolute minimum). Also, keep in mind that the lack of a JIT (Just-In-Time) JS compiler on the 32 bit version, makes the web surfing a bit slow. Only the 64 bit version of OWB 2.0 will have JIT enabled, thus benefitting of more speed. There are tooltypes that can be added to the icon to provide further features JIT, MSE etc Please make sure you have [https://easylist.to/easylist/easylist.txt easylist.txt] in PROGDIR:Conf before starting browser with enabled AdBlock. and possibly [https://curl.se/docs/caextract.html ca certs] OWB speed is much better when running from RAM Disk, the best way is to add the below into your S:User-Startup which copies OWB drawer from Extras:Internet/OWB to RAM Disk: So add this : <pre> copy Extras:Internet/OWB Ram:OWB/ ALL CLONE >NIL: copy Extras:Internet/OWB.info Ram: >NIL: </pre> Open RAM Disk and open OWB drawer and double click on OWB icon so that the above icon tooltypes are activated Problems are that the copy time is long (around 20 seconds added in the background), but we can make it faster if we delete useless files from the OWB drawer (docs, …) If you don’t copy the drawer back onto the HD, you won’t save your cache, cookies, passwords… So you need a script for it. Error messages SSL error "cant verify with ca-certificates", check bios clock time date is correct Error 6, try checking networking prefs settings and Save / Use preferences again or a '''few times''' otherwise the network chipset may not be compatible with Aros [https://www.google.com/search?q=%s&udm=14 Google search without AI overview] ===E-mail=== YAM does not support SSL and most mail providers now switched to encrypted SMTP/POP3 connections ====SimpleMail==== SimpleMail supports IMAP and appears to work with GMail, but it's never been reliable enough, it can crash with large mailboxes. Please read more on this [http://www.freelists.org/list/simplemail-usr User list] GMail Be sure to activate the pop3 usage in your gmail account setup / configuration first. pop3: pop.gmail.com Use SSL: Yes Port: 995 smtp: smtp.gmail.com (with authentication) Use Authentication: Yes Use SSL: Yes Port: 465 or 587 Hotmail/MSN/outlook/Microsoft Mail mid-2017, all outlook.com accounts will be migrated to Office 365 / Exchange Most users are currently on POP which does not allow showing folders and many other features (technical limitations of POP3). With Microsoft IMAP you will get folders, sync read/unread, and show flags. You still won't get push though, as Microsoft has not turned on the IMAP Idle command as at Sept 2013. If you want to try it, you need to first remove (you can't edit) your pop account (long-press the account on the accounts screen, delete account). Then set it up this way: 1. Email/Password 2. Manual 3. IMAP 4. * Incoming: imap-mail.outlook.com, port 993, SSL/TLS should be checked * Outgoing: smtp-mail.outlook.com, port 587, SSL/TLS should be checked * POP server name pop-mail.outlook.com, port 995, POP encryption method SSL Yahoo Mail On April 24, 2002 Yahoo ceased to offer POP access to its free mail service. Introducing instead a yearly payment feature, allowing users POP3 and IMAP server support, along with such benefits as larger file attachment sizes and no adverts. Sorry to see Yahoo leaving its users to cough up for the privilege of accessing their mail. Understandable, when competing against rivals such as Gmail and Hotmail who hold a large majority of users and were hacked in 2014 as well. Incoming Mail (IMAP) Server * Server - imap.mail.yahoo.com * Port - 993 * Requires SSL - Yes Outgoing Mail (SMTP) Server * Server - smtp.mail.yahoo.com * Port - 465 or 587 * Requires SSL - Yes * Requires authentication - Yes Your login info * Email address - Your full email address (name@domain.com) * Password - Your account's password * Requires authentication - Yes Note that you need to enable “Web & POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program. You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client. Cannot be done since 2002 unless the customer pays Yahoo a subscription subs fee to have access to SMTP and POP3 * Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port. * “Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”. * “Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com * “Password” – Your Yahoo Mail password. Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com. * Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work. ====YAM Yet Another Mailer==== YAM does not support SSL and most mail providers have now switched to encrypted SMTP/POP3 connections This email client is POP3 only if the SSL library is available [http://www.freelists.org/list/yam YAM Freelists] One of the downsides of using a POP3 mailer unfortunately - you have to set an option not to delete the mail if you want it left on the server. IMAP keeps all the emails on the server. Possible issues Sending mail issues is probably a matter of using your ISP's SMTP server, though it could also be an SSL issue. getting a "Couldn't initialise TLSv1 / SSL error Use of on-line e-mail accounts with this email client is not possible as it lacks the OpenSSL AmiSSl v3 compatible library GMail Incoming Mail (POP3) Server - requires SSL: pop.gmail.com Use SSL: Yes Port: 995 Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use authentication) Use Authentication: Yes Use STARTTLS: Yes (some clients call this SSL) Port: 465 or 587 Account Name: your Gmail username (including '@gmail.com') Email Address: your full Gmail email address (username@gmail.com) Password: your Gmail password Anyway, the SMTP is pop.gmail.com port 465 and it uses SSLLv3 Authentication. The POP3 settings are for the same server (pop.gmail.com), only on port 995 instead. Outlook.com access <pre > Outlook.com SMTP server address: smtp.live.com Outlook.com SMTP user name: Your full Outlook.com email address (not an alias) Outlook.com SMTP password: Your Outlook.com password Outlook.com SMTP port: 587 Outlook.com SMTP TLS/SSL encryption required: yes </pre > Yahoo Mail <pre > “POP3 Server” – Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port. “SMTP Server” – Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work. “Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”. “Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com “Password” – Your Yahoo Mail password. </pre > Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com. Note that you need to enable “Web & POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program. You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client. Cannot be done since 2002 unless the customer pays Yahoo a monthly fee to have access to SMTP and POP3 Microsoft Outlook Express Mail 1. Get the files to your PC. By whatever method get the files off your Amiga onto your PC. In the YAM folder you have a number of different folders, one for each of your folders in YAM. Inside that is a file usually some numbers such as 332423.283. YAM created a new file for every single email you received. 2. Open up a brand new Outlook Express. Just configure the account to use 127.0.0.1 as mail servers. It doesn't really matter. You will need to manually create any subfolders you used in YAM. 3. You will need to do a mass rename on all your email files from YAM. Just add a .eml to the end of it. Amazing how PCs still rely mostly on the file name so it knows what sort of file it is rather than just looking at it! There are a number of multiple renamers online to download and free too. 4. Go into each of your folders, inbox, sent items etc. And do a select all then drag the files into Outlook Express (to the relevant folder obviously) Amazingly the file format that YAM used is very compatible with .eml standard and viola your emails appear. With correct dates and working attachments. 5. If you want your email into Microsoft Outlook. Open that up and create a new profile and a new blank PST file. Then go into File Import and choose to import from Outlook Express. And the mail will go into there. And viola.. you have your old email from your Amiga in a more modern day format. ===FTP=== Magellan has a great FTP module. It allows transferring files from/to a FTP server over the Internet or the local network and, even if FTP is perceived as a "thing of the past", its usability is all inside the client. The FTP thing has a nice side effect too, since every Icaros machine can be a FTP server as well, and our files can be easily transferred from an Icaros machine to another with a little configuration effort. First of all, we need to know the 'server' IP address. Server is the Icaros machine with the file we are about to download on another Icaros machine, that we're going to call 'client'. To do that, move on the server machine and 1) run Prefs/Services to be sure "FTP file transfer" is enabled (if not, enable it and restart Icaros); 2) run a shell and enter this command: ifconfig -a Make a note of the IP address for the network interface used by the local area network. For cabled devices, it usually is net0:. Now go on the client machine and run Magellan: Perform these actions: 1) click on FTP; 2) click on ADDRESS BOOK; 3) click on "New". You can now add a new entry for your Icaros server machine: 1) Choose a name for your server, in order to spot it immediately in the address book. Enter the IP address you got before. 2) click on Custom Options: 1) go to Miscellaneous in the left menu; 2) Ensure "Passive Transfers" is NOT selected; 3) click on Use. We need to deactivate Passive Transfers because YAFS, the FTP server included in Icaros, only allows active transfers at the current stage. Now, we can finally connect to our new file source: 1) Look into the address book for the newly introduced server, be sure that name and IP address are right, and 2) click on Connect. A new lister with server's "MyWorkspace" contents will appear. You can now transfer files over the network choosing a destination among your local (client's) volumes. Can be adapted to any FTP client on any platform of your choice, just be sure your client allows Active Transfers as well. ===IRC Internet Relay Chat=== Jabberwocky is ideal for one-to-one social media communication, use IRC if you require one to many. Just type a message in ''lowercase''' letters and it will be posted to all in the [ AROS irc channel]. Please do not use UPPER CASE as it is a sign of SHOUTING which is annoying. Other things to type in - replace <message> with a line of text and <nick> with a person's name <pre> /help /list /who /whois <nick> /msg <nick> <message> /query <nick> <message>s /query /away <message> /away /quit <going away message> </pre> [http://irchelp.org/irchelp/new2irc.html#smiley Intro guide here]. IRC Primer can be found here in [http://www.irchelp.org/irchelp/ircprimer.html html], [http://www.irchelp.org/irchelp/text/ircprimer.txt TXT], [http://www.kei.com/irc/IRCprimer1.1.ps PostScript]. Issue the command /me <text> where <text> is the text that should follow your nickname. Example: /me slaps ajk around a bit with a large trout /nick <newNick> /nickserv register <password> <email address> /ns instead of /nickserv, while others might need /msg nickserv /nickserv identify <password> Alternatives: /ns identify <password> /msg nickserv identify <password> ==== IRC WookieChat ==== WookieChat is the most complete internet client for communication across the IRC Network. WookieChat allows you to swap ideas and communicate in real-time, you can also exchange Files, Documents, Images and everything else using the application's DCC capabilities. add smilies drawer/directory run wookiechat from the shell and set stack to 1000000 e.g. wookiechat stack 1000000 select a server / server window * nickname * user name * real name - optional Once you configure the client with your preferred screen name, you'll want to find a channel to talk in. servers * New Server - click on this to add / add extra - change details in section below this click box * New Group * Delete Entry * Connect to server * connect in new tab * perform on connect Change details * Servername - change text in this box to one of the below Server: * Port number - no need to change * Server password * Channel - add #channel from below * auto join - can click this * nick registration password, Click Connect to server button above <pre> Server: irc.freenode.net Channel: #aros </pre> irc://irc.freenode.net/aros <pre> Server: chat.amigaworld.net Channel: #amigaworld or #amigans </pre> <pre> On Sunday evenings USA time usually starting around 3PM EDT (1900 UTC) Server:irc.superhosts.net Channel #team*amiga </pre> <pre> BitlBee and Minbif are IRCd-like gateways to multiple IM networks Server: im.bitlbee.org Port 6667 Seems to be most useful on WookieChat as you can be connected to several servers at once. One for Bitlbee and any messages that might come through that. One for your normal IRC chat server. </pre> [http://www.bitlbee.org/main.php/servers.html Other servers], <pre> #Amiga.org - irc.synirc.net eu.synirc.net dissonance.nl.eu.synirc.net (IPv6: 2002:5511:1356:0:216:17ff:fe84:68a) twilight.de.eu.synirc.net zero.dk.eu.synirc.net us.synirc.net avarice.az.us.synirc.net envy.il.us.synirc.net harpy.mi.us.synirc.net liberty.nj.us.synirc.net snowball.mo.us.synirc.net - Ports 6660-6669 7001 (SSL) </pre> <pre> Multiple server support "Perform on connect" scripts and channel auto-joins Automatic Nickserv login Tabs for channels and private conversations CTCP PING, TIME, VERSION, SOUND Incoming and Outgoing DCC SEND file transfers Colours for different events Logging and automatic reloading of logs mIRC colour code filters Configurable timestamps GUI for changing channel modes easily Configurable highlight keywords URL Grabber window Optional outgoing swear word filter Event sounds for tabs opening, highlighted words, and private messages DCC CHAT support Doubleclickable URL's Support for multiple languages using LOCALE Clone detection Auto reconnection to Servers upon disconnection Command aliases Chat display can be toggled between AmIRC and mIRC style Counter for Unread messages Graphical nicklist and graphical smileys with a popup chooser </pre> ====IRC Aircos ==== Double click on Aircos icon in Extras:Networking/Apps/Aircos. It has been set up with a guest account for trial purposes. Though ideally, choose a nickname and password for frequent use of irc. ====IRC and XMPP Jabberwocky==== Servers are setup and close down at random You sign up to a server that someone else has setup and access chat services through them. The two ways to access chat from jabberwocky <pre > Jabberwocky -> Server -> XMPP -> open and ad-free Jabberwocky -> Server -> Transports (Gateways) -> Proprietary closed systems </pre > The Jabber.org service connects with all IM services that use XMPP, the open standard for instant messaging and presence over the Internet. The services we connect with include Google Talk (closed), Live Journal Talk, Nimbuzz, Ovi, and thousands more. However, you can not connect from Jabber.org to proprietary services like AIM, ICQ, MSN, Skype, or Yahoo because they don’t yet use XMPP components (XEP-0114) '''but''' you can use Jabber.com's servers and IM gateways (MSN, ICQ, Yahoo etc.) instead. The best way to use jabberwocky is in conjunction with a public jabber server with '''transports''' to your favorite services, like gtalk, Facebook, yahoo, ICQ, AIM, etc. You have to register with one of the servers, [https://list.jabber.at/ this list] or [http://www.jabberes.org/servers/ another list], [http://xmpp.net/ this security XMPP list], Unfortunately jabberwocky can only connect to one server at a time so it is best to check what services each server offers. If you set it up with separate Facebook and google talk accounts, for example, sometimes you'll only get one or the other. Jabberwocky open a window where the Jabber server part is typed in as well as your Nickname and Password. Jabber ID (JID) identifies you to the server and other users. Once registered the next step is to goto Jabberwocky's "Windows" menu and select the "Agents" option. The "Agents List" window will open. Roster (contacts list) [http://search.wensley.org.uk/ Chatrooms] (MUC) are available File Transfer - can send and receive files through the Jabber service but not with other services like IRC, ICQ, AIM or Yahoo. All you need is an installed webbrowser and OpenURL. Clickable URLs - The message window uses Mailtext.mcc and you can set a URL action in the MUI mailtext prefs like SYS:Utils/OpenURL %s NEWWIN. There is no consistent Skype like (H.323 VoIP) video conferencing available over Jabber. The move from xmpp to Jingle should help but no support on any amiga-like systems at the moment. [http://aminet.net/package/dev/src/AmiPhoneSrc192 AmiPhone] and [http://www.lysator.liu.se/%28frame,faq,nobg,useframes%29/ahi/v4-site/ Speak Freely] was an early attempt voice only contact. SIP and Asterisk are other PBX options. Facebook If you're using the XMPP transport provided by Facebook themselves, chat.facebook.com, it looks like they're now requiring SSL transport. This means jabberwocky method below will no longer work. The best thing to do is to create an ID on a public jabber server which has a Facebook gateway. <pre > 1. launch jabberwocky 2. if the login window doesn't appear on launch, select 'account' from the jabberwocky menu 3. your jabber ID will be user@chat.facebook.com where user is your user ID 4. your password is your normal facebook password 5. to save this for next time, click the popup gadget next to the ID field 6. click the 'add' button 7. click the 'close' button 8. click the 'connect' button </pre > you're done. you can also click the 'save as default account' button if you want. jabberwocky configured to auto-connect when launching the program, but you can configure as you like. there is amigaguide documentation included with jabberwocky. [http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=37085&forum=32 Read more here] for Facebook users, you can log-in directly to Facebook with jabberwocky. just sign in as @chat.facebook.com with your Facebook password as the password Twitter For a few years, there has been added a twitter transport. Servers include [http://jabber.hot-chilli.net/ jabber.hot-chili.net], and . An [http://jabber.hot-chilli.net/tag/how-tos/ How-to] :Read [http://jabber.hot-chilli.net/2010/05/09/twitter-transport-working/ more] Instagram no support at the moment best to use a web browser based client ICQ The new version (beta) of StriCQ uses a newer ICQ protocol. Most of the ICQ Jabber Transports still use an older ICQ protocol. You can only talk one-way to StriCQ using the older Transports. Only the newer ICQv7 Transport lets you talk both ways to StriCQ. Look at the server lists in the first section to check. Register on a Jabber server, e.g. this one works: http://www.jabber.de/ Then login into Jabberwocky with the following login data e.g. xxx@jabber.de / Password: xxx Now add your ICQ account under the window->Agents->"Register". Now Jabberwocky connects via the Jabber.de server with your ICQ account. Yahoo Messenger although yahoo! does not use xmpp protocol, you should be able to use the transport methods to gain access and post your replies MSN early months of 2013 Microsoft will ditch MSN Messenger client and force everyone to use Skype...but MSN protocol and servers will keep working as usual for quite a long time.... Occasionally the Messenger servers have been experiencing problems signing in. You may need to sign in at www.outlook.com and then try again. It may also take multiple tries to sign in. (This also affects you if you’re using Skype.) You have to check each servers' Agents List to see what transports (MSN protocol, ICQ protocol, etc.) are supported or use the list address' provided in the section above. Then register with each transport (IRC, MSN, ICQ, etc.) to which you need access. After registering you can Connect to start chatting. msn.jabber.com/registered should appear in the window. From this [http://tech.dir.groups.yahoo.com/group/amiga-jabberwocky/message/1378 JW group] guide which helps with this process in a clear, step by step procedure. 1. Sign up on MSN's site for a passport account. This typically involves getting a Hotmail address. 2. Log on to the Jabber server of your choice and do the following: * Select the "Windows/Agents" menu option in Jabberwocky. * Select the MSN Agent from the list presented by the server. * Click the Register button to open a new window asking for: **Username = passort account email address, typically your hotmail address. **Nick = Screen name to be shown to anyone you add to your buddy list. **Password = Password for your passport account/hotmail address. * Click the Register button at the bottom of the new window. 3. If all goes well, you will see the MSN Gateway added to your buddy list. If not, repeat part 2 on another server. Some servers may show MSN in their list of available agents, but have not updated their software for the latest protocols used by MSN. 4. Once you are registered, you can now add people to your buddy list. Note that you need to include the '''msn.''' ahead of the servername so that it knows what gateway agent to use. Some servers may use a slight variation and require '''msg.gate.''' before the server name, so try both to see what works. If my friend's msn was amiga@hotmail.co.uk and my jabber server was @jabber.meta.net.nz.. then amiga'''%'''hotmail.com@'''msn.'''jabber.meta.net.nz or another the trick to import MSN contacts is that you don't type the hotmail URL but the passport URL... e.g. Instead of: goodvibe%hotmail.com@msn.jabber.com You type: goodvibe%passport.com@msn.jabber.com And the thing about importing contacts I'm afraid you'll have to do it by hand, one at the time... Google Talk any XMPP server will work, but you have to add your contacts manually. a google talk user is typically either @gmail.com or @talk.google.com. a true gtalk transport is nice because it brings your contacts to you and (can) also support file transfers to/from google talk users. implement Jingle a set of extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP) support ended early 2014 as Google moved to Google+ Hangouts which uses it own proprietary format ===Video Player MPlayer=== Many of the menu features (such as doubling) do not work with the current version of mplayer but using 4:3 mplayer -vf scale=800:600 file.avi 16:9 mplayer -vf scale=854:480 file.avi if you want gui use; mplayer -gui 1 <other params> file.avi <pre > stack 1000000 ; using AspireOS 1.xx ; copy FROM SYS:Extras/Multimedia/MPlayer/ TO RAM:MPlayer ALL CLONE > Nil: ; using Icaros Desktop 1.x ; copy FROM SYS:Tools/MPlayer/ TO RAM:MPlayer ALL CLONE > Nil: ; using Icaros Desktop 2.x ; copy FROM SYS:Utilities/MPlayer/ TO RAM:MPlayer ALL CLONE > Nil: cd RAM:MPlayer run MPlayer -gui > Nil: ;run MPlayer -gui -ao ahi_dev -playlist http://www.radio-paralax.de/listen.pls > Nil: </pre > $ mplayer rtsp://127.0.0.1:554/sample_300kbit.mp4 MPlayer supports multicast streaming, and rtp/rtsp protocols (it might require [http://www.live555.com/openRTSP/ live555 library] to work with some streams). But you might have to build it where it's disabled. Also, multicast won't work with some AmiTCP-likes. MIAMI supported it, though. AROS supports IPv4 (old but works) and this includes the needed address space for RTP. If you mean multicast via RTP - mplayer handles it. You can even force UDP over TCP -rtsp-stream-over-tcp If the rtsp Real Time Streaming Protocol server needs authentification: -user -passwd MPlayer - Menu - Open Playlist and load already downloaded .pls or .m3u file - auto starts around 4 percent cache MPlayer - Menu - Open Stream and copy one of the .pls lines below into space allowed, press OK and press play button on main gui interface Old 8bit 16bit remixes chip tune game music http://www.radio-paralax.de/listen.pls http://scenesat.com/ http://www.shoutcast.com/radio/Amiga http://www.theoldcomputer.com/retro_radio/RetroRadio_Main.htm http://www.kohina.com/ http://www.remix64.com/ http://retrogamer.net/forum/ http://retroasylum.podomatic.com/rss2.xml http://retrogamesquad.com/ http://www.retronauts.com/ http://monsterfeet.com/noquarter/ http://www.retrogamingradio.com/ http://www.radiofeeds.co.uk/mp3.asp [[#top|...to the top]] ====ZunePaint==== simplified typical workflow * importing and organizing and photo management * making global and regional local correction(s) - recalculation is necessary after each adjustment as it is not in real-time * exporting your images in the best format available with the preservation of metadata Whilst achieving 80% of a great photo with just a filter, the remaining 20% comes from a manual fine-tuning of specific image attributes. For photojournalism, documentary, and event coverage, minimal touching is recommended. Stick to Camera Raw for such shots, and limit changes to level adjustment, sharpness, noise reduction, and white balance correction. For fashion or portrait shoots, a large amount of adjustment is allowed and usually ends up far from the original. Skin smoothing, blemish removal, eye touch-ups, etc. are common. Might alter the background a bit to emphasize the subject. Product photography usually requires a lot of sharpening, spot removal, and focus stacking. For landscape shots, best results are achieved by doing the maximum amount of preparation before/while taking the shot. No amount of processing can match timing, proper lighting, correct gear, optimal settings, etc. Excessive post-processing might give you a dramatic shot but best avoided in the long term. * White Balance - Left Amiga or F12 and K and under "Misc color effects" tab with a pull down for White Balance - color temperature also known as AKA tint (movies) or tones (painting) - warm temp raise red reduce green blue - cool raise blue lower red green * Exposure - exposure compensation, highlight/shadow recovery * Noise Reduction - during RAW development or using external software * Lens Corrections - distortion, vignetting, chromatic aberrations * Detail - capture sharpening and local contrast enhancement * Contrast - black point, levels (sliders) and curves tools (F12 and K) * Framing - straighten () and crop (F12 and F) * Refinements - color adjustments and selective enhancements - Left Amiga or F12 and K for RGB and YUV histogram tabs - * Resizing - enlarge for a print or downsize for the web or email (F12 and D) * Output Sharpening - customized for your subject matter and print/screen size White Balance - F12 and K scan your image for a shade which was meant to be white (neutral with each RGB value being equal) like paper or plastic which is in the same light as the subject of the picture. Use the dropper tool to select this color, similar colours will shift and you will have selected the perfect white balance for your part of the image - for the whole picture make sure RAZ or CLR button at the bottom is pressed before applying to the image above. Exposure correction F12 and K - YUV Y luminosity - RGB extra red tint - move red curve slightly down and move blue green curves slightly up Workflows in practice * Undo - Right AROS key or F12 and Z * Redo - Right AROS key or F12 and R First flatten your image (if necessary) and then do a rotation until the picture looks level. * Crop the picture. Click the selection button and drag a box over the area of the picture you want to keep. Press the crop button and the rest of the photo will be gone. * Adjust your saturation, exposure, hue levels, etc., (right AROS Key and K for color correction) until you are happy with the photo. Make sure you zoom in all of the way to 100% and look the photo over, zoom back out and move around. Look for obvious problems with the picture. * After coloring and exposure do a sharpen (Right AROS key and E for Convolution and select drop down option needed), e.g. set the matrix to 5x5 (roughly equivalent Amount to 60%) and set the Radius to 1.0. Click OK. And save your picture Implemented or would like to see for simplification and ease of use basic filters (presets) like black and white, monochrome, edge detection (sobel), motion/gaussian blur, * negative, sepiatone, retro vintage, night vision, colour tint, color gradient, color temperature, glows, fire, lightning, lens flare, emboss, filmic, pixelate mezzotint, antialias, etc. adjust / cosmetic tools such as crop, * reshaping tools, straighten, smear, smooth, perspective, liquify, bloat, pucker, push pixels in any direction, dispersion, transform like warp, blending with soft light, page-curl, whirl, ripple, fisheye, neon, etc. * red eye fixing, blemish remover, skin smoothing, teeth whitener, make eyes look brighter, desaturate, effects like oil paint, cartoon, pencil sketch, charcoal, noise/matrix like sharpen/unsharpen, (right AROS key with A for Artistic effects) * blend two image, gradient blend, masking blend, explode, implode, custom collage, surreal painting, comic book style, needlepoint, stained glass, watercolor, mosaic, stencil/outline, crayon, chalk, etc. borders such as * dropshadow, rounded, blurred, color tint, picture frame, film strip polaroid, bevelled edge, etc. brushes e.g. * frost, smoke, etc. and manual control of fix lens issues including vignetting (darkening), color fringing and barrel distortion, and chromatic and geometric aberration - lens and body profiles perspective correction levels - directly modify the levels of the tone-values of an image, by using sliders for highlights, midtones and shadows curves - Color Adjustment and Brightness/Contrast color balance one single color transparent (alpha channel (color information/selections) for masking and/or blending ) for backgrounds, etc. Threshold indicates how much other colors will be considered mixture of the removed color and non-removed colors decompose layer into a set of layers with each holding a different type of pattern that is visible within the image any selection using any selecting tools like lasso tool, marquee tool etc. the selection will temporarily be save to alpha If you create your image without transparency then the Alpha channel is not present, but you can add later. File formats like .psd (Photoshop file has layers, masks etc. contains edited sensor data. The original sensor data is no longer available) .xcf .raw .hdr Image Picture Formats * low dynamic range (JPEG, PNG, TIFF 8-bit), 16-bit (PPM, TIFF), typically as a 16-bit TIFF in either ProPhoto or AdobeRGB colorspace - TIFF files are also fairly universal – although, if they contain proprietary data, such as Photoshop Adjustment Layers or Smart Filters, then they can only be opened by Photoshop making them proprietary. * linear high dynamic range (HDR) images (PFM, [http://www.openexr.com/ ILM .EXR], jpg, [http://aminet.net/util/dtype cr2] (canon tiff based), hdr, NEF, CRW, ARW, MRW, ORF, RAF (Fuji), PEF, DCR, SRF, ERF, DNG files are RAW converted to an Adobe proprietary format - a container that can embed the raw file as well as the information needed to open it) An old version of [http://archives.aros-exec.org/index.php?function=browse&cat=graphics/convert dcraw] There is no single RAW file format. Each camera manufacturer has one or more unique RAW formats. RAW files contain the brightness levels data captured by the camera sensor. This data cannot be modified. A second smaller file, separate XML file, or within a database with instructions for the RAW processor to change exposure, saturation etc. The extra data can be changed but the original sensor data is still there. RAW is technically least compatible. A raw file is high-bit (usually 12 or 14 bits of information) but a camera-generated TIFF file will be usually converted by the camera (compressed, downsampled) to 8 bits. The raw file has no embedded color balance or color space, but the TIFF has both. These three things (smaller bit depth, embedded color balance, and embedded color space) make it so that the TIFF will lose quality more quickly with image adjustments than the raw file. The camera-generated TIFF image is much more like a camera processed JPEG than a raw file. A strong advantage goes to the raw file. The power of RAW files, such as the ability to set any color temperature non-destructively and will contain more tonal values. The principle of preserving the maximum amount of information to as late as possible in the process. The final conversion - which will always effectively represent a "downsampling" - should prevent as much loss as possible. Once you save it as TIFF, you throw away some of that data irretrievably. When saving in the lossy JPEG format, you get tremendous file size savings, but you've irreversibly thrown away a lot of image data. As long as you have the RAW file, original or otherwise, you have access to all of the image data as captured. Keyboard equivalence with Photoshop(tm) would help File PHOTOSHOP SHORTCUT GIMP New Ctrl+n New Open Ctrl+o Open Close Ctrl+w Close Save Ctrl+s Save Save as Shift+Ctrl+s Save as Revert F12 Revert Print Ctrl+p Print Exit Ctrl+q Quit Edit PHOTOSHOP SHORTCUT GIMP Undo/Redo (1 level) Ctrl+z Undo (Redo is Shift+Ctrl+z) Cut Ctrl+x Cut Copy Ctrl+c Copy Paste Ctrl+v Paste Paste Into Shift+Ctrl+v Paste Into Fill with FG color Alt+Backspace Fill with FG color Fill with BG color Control+Backspace Fill with BG color Image/Colors PHOTOSHOP SHORTCUT GIMP Levels Ctrl+l Levels Auto Contrast Shift+Ctrl+Alt+l Stretch Contrast (same?) Curves Ctrl+m Curves Color Balance Ctrl+b Color Balance Hue/Saturation Ctrl+u Hue-Saturation Desaturate Shift+Ctrl+u Desaturate Invert Ctrl+i Invert Default Colors d Default Colors Switch Colors x Switch Colors Layer PHOTOSHOP SHORTCUT GIMP New Layer Shift+Ctrl+n New Layer Layer via Copy Ctrl+j Duplicate Layer Bring (layer) to Front Shift+Ctrl+] Layer to Top Send (layer) to Back Shift+Ctrl+[ Layer to Bottom Bring (layer) Forward Ctrl+] Raise Layer Send (layer) Backward Ctrl+[ Lower Layer Select Top Layer Shift+Alt+] Select Top Layer Select Bottom Layer Shift+Alt+[ Select Bottom Layer Select One Layer Forward Alt+] Select Previous Layer Select One Layer Backward Alt+[ Select Next Layer Merge Down Ctrl+e Merge Down Merge Visible Shift+Ctrl+e Merge Visible Preserve Transparency / Keep Transparency Cycle Modes Forwards Shift+= Next Layer Mode Cycle Modes Backwards Shift+- Previous Layer Mode Select PHOTOSHOP SHORTCUT GIMP Select All Ctrl+a Select All Deselect Ctrl+d Select None Inverse Shift+Ctrl+i Invert Feather Ctrl+Alt+d Feather View PHOTOSHOP SHORTCUT GIMP Zoom In Ctrl+= Zoom In Zoom Out Ctrl+- Zoom Out Fit on Screen Ctrl+0 Zoom to Fit Window Actual Pixels Ctrl+Alt+0 Zoom 1:1 Show/Hide Extras Ctrl+h Toggle Show Selection (close enough?) Show/Hide Guides Ctrl+' Toggle Show Guides Show/Hide Grid Ctrl+Alt+' Toggle Show Grid Show/Hide Rulers Ctrl+r Toggle Show Rulers Snap Ctrl+; Snap to Guides Scroll View Up Page Up Scroll Page Up Scroll View Down Page Down Scroll Page Down Scroll View Left Ctrl+Page Up Scroll Page Left Scroll View Right Ctrl+Page Down Scroll Page Right Window/Dialogs PHOTOSHOP SHORTCUT GIMP ? F5 Tools Dialog Color Tab F6 Colors Dialog Layers Tab F7 Layers Dialog Info Tab F8 Image Information Tools PHOTOSHOP SHORTCUT GIMP Rectangular Marquee Tool m Rect Select Tool Elliptical Marquee Tool Shift+m Ellipse Select Tool *This is a toggle between 'Elliptical Marquee Tool' and 'Rectangular Marquee Tool' in Photoshop Move Tool v Move Tool Lasso Tool l Free Select Tool Magic Wand Tool w Fuzzy Select Tool Crop Tool c Crop & Resize Tool Airbrush Tool j Airbrush Tool Paintbrush Tool b Paintbrush Tool Clone Stamp Tool s Clone Stamp Tool Eraser Tool e Eraser Tool Gradient Tool g Blend Tool Paint Bucket Tool Shift+g Bucket Fill Tool *This is a toggle between 'Paint Bucket Tool' and 'Gradient Tool' in Photoshop Blur Tool r Convolve Tool Dodge Tool o DodgeBurn Tool Type Tool t Text Tool Pen Tool p Bezier Select Tool Eye Dropper Tool i Color Picker Tool Zoom Tool z Magnify Tool Previous Brush , Previous Brush Next Brush . Next Brush First Brush Shift+< First Brush Last Brush Shift+> Last Brush Decrease Brush Size [ Decrease Brush Size Increase Brush Size ] Increase Brush Size Decrease Brush Hardness { Decrease Brush Hardness Increase Brush Hardness } Increase Brush Hardness Help PHOTOSHOP SHORTCUT GIMP Help F1 Help Context Help Shift+F1 Context Help Misc. PHOTOSHOP SHORTCUT GIMP Last Filter Ctrl+f Repeat Last Filter ? Shift+Ctrl+f Reshow Last Filter Preferences Ctrl+k Preferences Liquify Shift+Ctrl+x IWarp (close enough?) Toggle Quick Mask q Toggle Quick Mask Spotlights - triangle of white opaque shape Cutting out and/or replacing unwanted background or features - select large areas with the selection option like the Magic Wand tool (aka Color Range) or the Lasso (quick and fast) with feather 2 to soften edge or the pen tool which adds points/lines/Bézier curves (better control but slower), hold down the shift button as you click to add extra points/areas of the subject matter to remove. Increase the tolerance to cover more areas. To subtract from your selection hold down alt as you're clicking. * Layer masks are a better way of working than Erase they clip (black hides/hidden white visible/reveal). Clone Stamp can be simulated by and brushes for other areas. * Leave the fine details like hair, fur, etc. to later with lasso and the shift key to draw a line all the way around your subject. Gradient Mapping - Inverse - Mask. i.e. Refine your selected image with edge detection and using the radius and edge options / adjuster (increase/decrease contrast) so that you will capture more fine detail from the background allowing easier removal. Remove fringe/halo saving image as png rather than jpg/jpeg to keep transparency background intact. Implemented [http://colorizer.org/ colour model representations] [http://paulbourke.net/texture_colour/colourspace/ Mathematical approach] - Photo stills are spatially 2d (h and w), but are colorimetrically 3d (r g and b, or H L S, or Y U V etc.) as well. * RGB - split cubed mapped color model for photos and computer graphics hardware using the light spectrum (adding and subtracting) * YUV - Y-Lightness U-blue/yellow V-red/cyan (similar to YPbPr and YCbCr) used in the PAL, NTSC, and SECAM composite digital TV color [http://crewofone.com/2012/chroma-subsampling-and-transcoding/#comment-7299 video] Histograms White balanced (neutral) if the spike happens in the same place in each channel of the RGB graphs. If not, you're not balanced. If you have sky you'll see the blue channel further off to the right. RGB is best one to change colours. These elements RGB is a 3-channel format containing data for Red, Green, and Blue in your photo scale between 0 and 255. The area in a picture that appears to be brighter/whiter contains more red color as compared to the area which is relatively darker. Similarly in the green channel the area that appears to be darker contains less amount of green color as compared to the area that appears to be brighter. Similarly in the blue channel the area appears to be darker contains less amount of blue color as compared to the area that appears to be brighter. Brightness luminance histogram also matches the green histogram more than any other color - human eye interprets green better e.g. RGB rough ratio 15/55/30% RGBA (RGB+A, A means alpha channel) . The alpha channel is used for "alpha compositing", which can mostly be associated as "opacity". AROS deals in RGB with two digits for every color (red, green, blue), in ARGB you have two additional hex digits for the alpha channel. The shadows are represented by the left third of the graph. The highlights are represented by the right third. And the midtones are, of course, in the middle. The higher the black peaks in the graph, the more pixels are concentrated in that tonal range (total black area). By moving the black endpoint, which identifies the shadows (darkness) and a white light endpoint (brightness) up and down either sides of the graph, colors are adjusted based on these points. By dragging the central one, can increased the midtones and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative . RGB Curves * Move left endpoint (black point) up or right endpoint (white point) up brightens * Move left endpoint down or right endpoint down darkens Color Curves * Dragging up on the Red Curve increases the intensity of the reds in the image but * Dragging down on the Red Curve decreases the intensity of the reds and thus increases the apparent intensity of its complimentary color, cyan. Green’s complimentary color is magenta, and blue’s is yellow. <pre> Red <-> Cyan Green <->Magenta Blue <->Yellow </pre> YUV Best option to analyse and pull out statistical elements of any picture (i.e. separate luminance data from color data). The line in Y luma tone box represents the brightness of the image with the point in the bottom left been black, and the point in the top right as white. A low-contrast image has a concentrated clump of values nearer to the center of the graph. By comparison, a high-contrast image has a wider distribution of values across the entire width of the Histogram. A histogram that is skewed to the right would indicate a picture that is a bit overexposed because most of the color data is on the lighter side (increase exposure with higher value F), while a histogram with the curve on the left shows a picture that is underexposed. This is good information to have when using post-processing software because it shows you not only where the color data exists for a given picture, but also where any data has been clipped (extremes on edges of either side): that is, it does not exist and, therefore, cannot be edited. By dragging the endpoints of the line and as well as the central one, can increased the dark/shadows, midtones and light/bright parts and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative . The U and V chroma parts show color difference components of the image. It’s useful for checking whether or not the overall chroma is too high, and also whether it’s being limited too much Can be used to create a negative image but also With U (Cb), the higher value you are, the more you're on the blue primary color. If you go to the low values then you're on blue complementary color, i.e. yellow. With V (Cr), this is the same principle but with Red and Cyan. e.g. If you push U full blue and V full red, you get magenta. If you push U full yellow and V full Cyan then you get green. YUV simultaneously adds to one side of the color equation while subtracting from the other. using YUV to do color correction can be very problematic because each curve alters the result of each other: the mutual influence between U and V often makes things tricky. You may also be careful in what you do to avoid the raise of noise (which happens very easily). Best results are obtained with little adjustments sunset that looks uninspiring and needs some color pop especially for the rays over the hill, a subtle contrast raise while setting luma values back to the legal range without hard clipping. Free royalty pictures, [www.freeimages.com ], [http://imageshack.us/ ], [http://photobucket.com/ ], [http://rawpixels.net/], [], [], [], ====Lunapaint==== Pixel based drawing app with onion-skin animation function Blocking, Shading, Coloring, adding detail <pre> b BRUSH e ERASER alt eyedropper v layer tool z ZOOM / MAGNIFY < > n spc panning m marque q lasso w same color selection / region </pre> <pre> , LM RM v V f filter F . size p , pick color [] last / next color </pre> There is not much missing in Lunapaint to be as good as FlipBook and then you have to take into account that Flipbook is considered to be amongst the best and easiest to use animation software out there. Ok to be honest Flipbook has some nice features that require more heavy work but those aren't so much needed right away, things like camera effects, sound, smart fill, export to different movie file formats etc. Tried Flipbook with my tablet and compared it to Luna. The feeling is the same when sketching. LunaPaint is very responsive/fluent to draw with. Just as Flipbook is, and that responsiveness is something its users have mentioned as one of the positive sides of said software. author was learning MUI. Some parts just have to be rewritten with proper MUI classes before new features can be added. * add [Frame Add] / [Frame Del] * whole animation feature is impossible to use. If you draw 2 color maybe but if you start coloring your cells then you get in trouble * pickup the entire image as a brush, not just a selection ? And consequently remove the brush from memory when one doesn't need it anymore. can pick up a brush and put it onto a new image but cropping isn't possible, nor to load/save brushes. * Undo is something I longed for ages in Lunapaint. * to import into the current layer, other types of images (e.g. JPEG) besides RAW64. * implement graphic tablet features support **GENERAL DRAWING** Miss it very much: UNDO ERASER COLORPICKER - has to show on palette too which color got picked. BACKGROUND COLOR -Possibility to select from "New project screen" Miss it somewhat: ICON for UNDO ICON for ERASER ICON for CLEAR SCREEN ( What can I say? I start over from scratch very often ) BRUSH - possibility to cut out as brush not just copy off image to brush **ANIMATING** Miss it very much: NUMBER OF CELLS - Possibity to change total no. of cells during project ANIM BRUSH - Possibility to pick up a selected part of cells into an animbrush Miss it somewhat: ADD/REMOVE FRAMES: Add/remove single frame In general LunaPaint is really well done and it feels like a new DeluxePaint version. It works with my tablet. Sure there's much missing of course but things can always be added over time. So there is great potential in LunaPaint that's for sure. Animations could be made in it and maybe put together in QuickVideo, saving in .gif or .mng etc some day. LAYERS -Layers names don't get saved globally in animation frames -Layers order don't change globally in an animation (perhaps as default?). EXPORTING IMAGES -Exporting frames to JPG/PNG gives problems with colors. (wrong colors. See my animatiopn --> My robot was blue now it's "gold" ) I think this only happens if you have layers. -Trying to flatten the layers before export doesn't work if you have animation frames only the one you have visible will flatten properly all other frames are destroyed. (Only one of the layers are visible on them) -Exporting images filenames should be for example e.g. file0001, file0002...file0010 instead as of now file1, file2...file10 LOAD/SAVE (Preferences) -Make a setting for the default "Work" folder. * Destroyed colors if exported image/frame has layers * mystic color cycling of the selected color while stepping frames back/forth (annoying) <pre> Deluxe Paint II enhanced key shortcuts NOTE: @ denotes the ALT key [Technique] F1 - Paint F2 - Single Colour F3 - Replace F4 - Smear F5 - Shade F6 - Cycle F7 - Smooth M - Colour Cycle [Brush] B - Restore O - Outline h - Halve brush size H - Double brush size x - Flip brush on X axis X - Double brush size on X axis only y - Flip on Y Y - Double on Y z - Rotate brush 90 degrees Z - Stretch [Stencil] ` - Stencil On [Miscellaneous] F9 - Info Bar F10 - Selection Bar @o - Co-Ordinates @a - Anti-alias @r - Colourise @t - Translucent TAB - Colour Cycle [Picture] L - Load S - Save j - Page to Spare(Flip) J - Page to Spare(Copy) V - View Page Q - Quit [General Keys] m - Magnify < - Zoom In > - Zoom Out [ - Palette Colour Up ] - Palette Colour Down ( - Palette Colour Left ) - Palette Colour Right , - Eye Dropper . - Pixel / Brush Toggle / - Symmetry | - Co-Ordinates INS - Perspective Control +/- - Brush Size (Fine Control) w - Unfilled Polygon W - Filled Polygon e - Unfilled Ellipse E - Filled Ellipse r - Unfilled Rectangle R - Filled Rectangle t - Type/text tool a - Select Font u/U - Undo d - Brush D - Filled Non-Uniform Polygon f/F - Fill Options g/G - Grid h/H - Brush Size (Coarse Control) K - Clear c - Unfilled Circle C - Filled Circle v - Line b - Scissor Select and Toggle B - Brush {,} - Toggle between two background colours </pre> ====Lodepaint==== Pixel based painting artwork app ====Grafx2==== Pixel based painting artwork app aesprite like [https://www.youtube.com/watch?v=59Y6OTzNrhk aesprite workflow keys and tablet use], [], ====Vector Graphics ZuneFIG==== Vector Image Editing of files .svg .ps .eps *Objects - raise lower rotate flip aligning snapping *Path - unify subtract intersect exclude divide *Colour - fill stroke *Stroke - size *Brushes - *Layers - *Effects - gaussian bevels glows shadows *Text - *Transform - AmiFIG ([http://epb.lbl.gov/xfig/frm_introduction.html xfig manual]) [[File:MyScreen.png|thumb|left|alt=Showing all Windows open in AmiFIG.|All windows available to AmiFIG.]] for drawing simple to intermediate vector graphic images for scientific and technical uses and for illustration purposes for those with talent ;Menu options * Load - fig format but import(s) SVG * Save - fig format but export(s) eps, ps, pdf, svg and png * PAN = Ctrl + Arrow keys * Deselect all points There is no selected object until you apply the tool, and the selected object is not highlighted. ;Metrics - to set up page and styles - first window to open on new drawings ;Tools - Drawing Primitives - set Attributes window first before clicking any Tools button(s) * Shapes - circles, ellipses, arcs, splines, boxes, polygon * Lines - polylines * Text "T" button * Photos - bitmaps * Compound - Glue, Break, Scale * POINTs - Move, Add, Remove * Objects - Move, Copy, Delete, Mirror, Rotate, Paste use right mouse button to stop extra lines, shapes being formed and the left mouse to select/deselect tools button(s) * Rotate - moves in 90 degree turns centered on clicked POINT of a polygon or square ;Attributes which provide change(s) to the above primitives * Color * Line Width * Line Style * arrowheads ;Modes Choose from freehand, charts, figures, magnet, etc. ;Library - allows .fig clip-art to be stored * compound tools to add .fig(s) together ;FIG 3.2 [http://epb.lbl.gov/xfig/fig-format.html Format] as produced by xfig version 3.2.5 <pre> Landscape Center Inches Letter 100.00 Single -2 1200 2 4 0 0 50 -1 0 12 0.0000 4 135 1050 1050 2475 This is a test.01 </pre> # change the text alignment within the textbox. I can choose left, center, or right aligned by either changing the integer in the second column from 0 (left) to 1 or 2 (center, or right). # The third integer in the row specifies fontcolor. For instance, 0 is black, but blue is 1 and Green3 is 13. # The sixth integer in the bottom row specifies fontface. 0 is Times-Roman, but 16 is Helvetica (a MATLAB default). # The seventh number is fontsize. 12 represents a 12pt fontsize. Changing the fontsize of an item really is as easy as changing that number to 20. # The next number is the counter-clockwise angle of the text. Notice that I have changed the angle to .7854 (pi/4 rounded to four digits=45 degrees). # twelfth number is the position according to the standard “x-axis” in Xfig units from the left. Note that 1200 Xfig units is equivalent to once inch. # thirteenth number is the “y-position” from the top using the same unit convention as before. * The nested text string is what you entered into the textbox. * The “01″ present at the end of that line in the .fig file is the closing tag. For instance, a change to \100 appends a @ symbol at the end of the period of that sentence. ; Just to note there are no layers, no 3d functions, no shading, no transparency, no animation [[#top|...to the top]] ===Audio=== # AHI uses linear panning/balance, which means that in the center, you will get -6dB. If an app uses panning, this is what you will get. Note that apps like Audio Evolution need panning, so they will have this problem. # When using AHI Hifi modes, mixing is done in 32-bit and sent as 32-bit data to the driver. The Envy24HT driver uses that to output at 24-bit (always). # For the Envy24/Envy24HT, I've made 16-bit and 24-bit inputs (called Line-in 16-bit, Line-in 24-bit etc.). There is unfortunately no app that can handle 24-bit recording. ====Music Mods==== Digital module (mods) trackers are music creation software using samples and sometimes soundfonts, audio plugins (VST, AU or RTAS), MIDI. Generally, MODs are similar to MIDI in that they contain note on/off and other sequence messages that control the mod player. Unlike (most) midi files, however, they also contain sound samples that the sequence information actually plays. MOD files can have many channels (classic amiga mods have 4, corresponding to the inbuilt sound channels), but unlike MIDI, each channel can typically play only one note at once. However, since that note might be a sample of a chord, a drumloop or other complex sound, this is not as limiting as it sounds. Like MIDI, notes will play indefinitely if they're not instructed to end. Most trackers record this information automatically if you play your music in live. If you're using manual note entry, you can enter a note-off command with a keyboard shortcut - usually Caps Lock. In fact when considering file size MOD is not always the best option. Even a dummy song wastes few kilobytes for nothing when a simple SID tune could be few hundreds bytes and not bigger than 64kB. AHX is another small format, AHX tunes are never larger than 64kB excluding comments. [https://www.youtube.com/watch?v=rXXsZfwgil Protrekkr] (previously aka [w:Juan_Antonio_Arguelles_Rius|NoiseTrekkr]) If Protrekkr does not start, please check if the Unit 0 has been setup in the AHI prefs and still not, go to the directory utilities/protrekkr and double click on the Protrekkr icon *Sample *Note - Effect *Track (column) - Pattern - Order It all starts with the Sample which is used to create Note(s) in a Track (column of a tracker) The Note can be changed with an Effect. A Track of Note(s) can be collected into a Pattern (section of a song) and these can be given Order to create the whole song. Patience (notes have to be entered one at a time) or playing the bassline on a midi controller (faster - see midi section above). Best approach is to wait until a melody popped into your head. *Up-tempo means the track should be reasonably fast, but not super-fast. *Groovy and funky imply the track should have some sort of "swing" feel, with plenty of syncopation or off beat emphasis and a recognizable, melodic bass line. *Sweet and happy mean upbeat melodies, a major key and avoiding harsh sounds. *Moody - minor key First, create a quick bass sound, which is basically a sine wave, but can be hand drawn for a little more variance. It could also work for the melody part, too. This is usually a bass guitar or some kind of synthesizer bass. The bass line is often forgotten by inexperienced composers, but it plays an important role in a musical piece. Together with the rhythm section the bass line forms the groove of a song. It's the glue between the rhythm section and the melodic layer of a song. The drums are just pink noise samples, played at different frequencies to get a slightly different sound for the kick, snare, and hihats. Instruments that fall into the rhythm category are bass drums, snares, hi-hats, toms, cymbals, congas, tambourines, shakers, etc. Any percussive instrument can be used to form part of the rhythm section. The lead is the instrument that plays the main melody, on top of the chords. There are many instruments that can play a lead section, like a guitar, a piano, a saxophone or a flute. The list is almost endless. There is a lot of overlap with instruments that play chords. Often in one piece an instrument serves both roles. The lead melody is often played at a higher pitch than the chords. Listened back to what was produced so far, and a counter-melody can be imagined, which can be added with a triangle wave. To give the ends of phrases some life, you can add a solo part with a crunchy synth. By hitting random notes in the key of G, then edited a few of them. For the climax of the song, filled out the texture with a gentle high-pitch pad… …and a grungy bass synth. The arrow at A points at the pattern order list. As you see, the patterns don't have to be in numerical order. This song starts with pattern "00", then pattern "02", then "03", then "01", etcetera. Patterns may be repeated throughout a song. The B arrow points at the song title. Below it are the global BPM and speed parameters. These determine the tempo of the song, unless the tempo is altered through effect commands during the song. The C arrow points at the list of instruments. An instrument may consist of multiple samples. Which sample will be played depends on the note. This can be set in the Instrument Editing screen. Most instruments will consist of just one sample, though. The sample list for the selected instrument can be found under arrow D. Here's a part of the main editing screen. This is where you put in actual notes. Up to 32 channels can be used, meaning 32 sounds can play simultaneously. The first six channels of pattern "03" at order "02" are shown here. The arrow at A points at the row number. The B arrow points at the note to play, in this case a C4. The column pointed at by the C arrow tells us which instrument is associated with that note, in this case instrument #1 "Kick". The column at D is used (mainly) for volume commands. In this case it is left empty which means the instrument should play at its default volume. You can see the volume column being used in channel #6. The E column tells us which effect to use and any parameters for that effect. In this case it holds the "F" effect, which is a tempo command. The "04" means it should play at tempo 4 (a smaller number means faster). Base pattern When I create a new track I start with what I call the base pattern. It is worthwhile to spend some time polishing it as a lot of the ideas in the base pattern will be copied and used in other patterns. At least, that's how I work. Every musician will have his own way of working. In "Wild Bunnies" the base pattern is pattern "03" at order "02". In the section about selecting samples I talked about the four different categories of instruments: drums, bass, chords and leads. That's also how I usually go about making the base pattern. I start by making a drum pattern, then add a bass line, place some chords and top it off with a lead. This forms the base pattern from which the rest of the song will grow. Drums Here's a screenshot of the first four rows of the base pattern. I usually reserve the first four channels or so for the drum instruments. Right away there are a couple of tricks shown here. In the first channel the kick, or bass drum, plays some notes. Note the alternating F04 and F02 commands. The "F" command alters the tempo of the song and by quickly alternating the tempo; the song will get some kind of "swing" feel. In the second channel the closed hi-hat plays a fairly simple pattern. Further down in the channel, not shown here, some open hi-hat notes are added for a bit of variation. In the third and fourth channel the snare sample plays. The "8" command is for panning. One note is panned hard to the left and the other hard to the right. One sample is played a semitone lower than the other. This results in a cool flanging effect. It makes the snare stand out a little more in the mix. Bass line There are two different instruments used for the bass line. Instrument #6 is a pretty standard synthesized bass sound. Instrument #A sounds a bit like a slap bass when used with a quick fade out. By using two different instruments the bass line sounds a bit more ”human”. The volume command is used to cut off the notes. However, it is never set to zero. Setting the volume to a very small value will result in a reverb-like effect. This makes the song sound more "live". The bass line hints at the chords that will be played and the key the song will be in. In this case the key of the song is D-major, a positive and happy key. Chords The D major chords that are being played here are chords stabs; short sounds with a quick decay (fade out). Two different instruments (#8 and #9) are used to form the chords. These instruments are quite similar, but have a slightly different sound, panning and volume decay. Again, the reason for this is to make the sound more human. The volume command is used on some chords to simulate a delay, to achieve more of a live feel. The chords are placed off-beat making for a funky rhythm. Lead Finally the lead melody is added. The other instruments are invaluable in holding the track together, but the lead melody is usually what catches people's attention. A lot of notes and commands are used here, but it looks more complex than it is. A stepwise ascending melody plays in channel 13. Channel 14 and 15 copy this melody, but play it a few rows later at a lower volume. This creates an echo effect. A bit of panning is used on the notes to create some stereo depth. Like with the bass line, instead of cutting off notes the volume is set to low values for a reverb effect. The "461" effect adds a little vibrato to the note, which sounds nice on sustained notes. Those paying close attention may notice the instrument used here for the lead melody is the same as the one used for the bass line (#6 "Square"), except played two or three octaves higher. This instrument is a looped square wave sample. Each type of wave has its own quirks, but the square wave (shown below) is a really versatile wave form. Song structure Good, catchy songs are often carefully structured into sections, some of which are repeated throughout the song with small variations. A typical pop-song structure is: Intro - Verse - Chorus - Verse - Chorus - Bridge - Chorus. Other single sectional song structures are <pre> Strophic or AAA Song Form - oldest story telling with refrain (often title of the song) repeated in every verse section melody AABA Song Form - early popular, jazz and gospel fading during the 1960s AB or Verse/Chorus Song Form - songwriting format of choice for modern popular music since the 1960s Verse/Chorus/Bridge Song Form ABAB Song Form ABAC Song Form ABCD Song Form AAB 12-Bar Song Form - three four-bar lines or sub-sections 8-Bar Song Form 16-Bar Song Form Hybrid / Compound Song Forms </pre> The most common building blocks are: #INTRODUCTION(INTRO) #VERSE #REFRAIN #PRE-CHORUS / RISE / CLIMB #CHORUS #BRIDGE #MIDDLE EIGHT #SOLO / INSTRUMENTAL BREAK #COLLISION #CODA / OUTRO #AD LIB (OFTEN IN CODA / OUTRO) The chorus usually has more energy than the verse and often has a memorable melody line. As the chorus is repeated the most often during the song, it will be the part that people will remember. The bridge often marks a change of direction in the song. It is not uncommon to change keys in the bridge, or at least to use a different chord sequence. The bridge is used to build up tension towards the big finale, the last repetition of chorus. Playing RCTRL: Play song from row 0. LSHIFT + RCTRL: Play song from current row. RALT: Play pattern from row 0. LSHIFT + RALT: Play pattern from current row. Left mouse on '>': Play song from row 0. Right mouse on '>': Play song from current row. Left mouse on '|>': Play pattern from row 0. Right mouse on '|>': Play pattern from current row. Left mouse on 'Edit/Record': Edit mode on/off. Right mouse on 'Edit/Record': Record mode on/off. Editing LSHIFT + ESCAPE: Switch large patterns view on/off TAB: Go to next track LSHIFT + TAB: Go to prev. track LCTRL + TAB: Go to next note in track LCTRL + LSHIFT + TAB: Go to prev. note in track SPACE: Toggle Edit mode On & Off (Also stop if the song is being played) SHIFT SPACE: Toggle Record mode On & Off (Wait for a key note to be pressed or a midi in message to be received) DOWN ARROW: 1 Line down UP ARROW: 1 Line up LEFT ARROW: 1 Row left RIGHT ARROW: 1 Row right PREV. PAGE: 16 Arrows Up NEXT PAGE: 16 Arrows Down HOME / END: Top left / Bottom right of pattern LCTRL + HOME / END: First / last track F5, F6, F7, F8, F9: Jump to 0, 1/4, 2/4, 3/4, 4/4 lines of the patterns + - (Numeric keypad): Next / Previous pattern LCTRL + LEFT / RIGHT: Next / Previous pattern LCTRL + LALT + LEFT / RIGHT: Next / Previous position LALT + LEFT / RIGHT: Next / Previous instrument LSHIFT + M: Toggle mute state of the current channel LCTRL + LSHIFT + M: Solo the current track / Unmute all LSHIFT + F1 to F11: Select a tab/panel LCTRL + 1 to 4: Select a copy buffer Tracking 1st and 2nd keys rows: Upper octave row 3rd and 4th keys rows: Lower octave row RSHIFT: Insert a note off / and * (Numeric keypad) or F1 F2: -1 or +1 octave INSERT / BACKSPACE: Insert or Delete a line in current track or current selected block. LSHIFT + INSERT / BACKSPACE: Insert or Delete a line in current pattern DELETE (NOT BACKSPACE): Empty a column or a selected block. Blocks (Blocks can also be selected with the mouse by holding the right button and scrolling the pattern with the mouse wheel). LCTRL + A: Select entire current track LCTRL + LSHIFT + A: Select entire current pattern LALT + A: Select entire column note in a track LALT + LSHIFT + A: Select all notes of a track LCTRL + X: Cut the selected block and copy it into the block-buffer LCTRL + C: Copy the selected block into the block-buffer LCTRL + V: Paste the data from the block buffer into the pattern LCTRL + I: Interpolate selected data from the first to the last row of a selection LSHIFT + ARROWS PREV. PAGE NEXT PAGE: Select a block LCTRL + R: Randomize the select columns of a selection, works similar to CTRL + I (interpolating them) LCTRL + U: Transpose the note of a selection to 1 seminote higher LCTRL + D: Transpose the note of a selection to 1 seminote lower LCTRL + LSHIFT + U: Transpose the note of a selection to 1 seminote higher (only for the current instrument) LCTRL + LSHIFT + D: Transpose the note of a selection to 1 seminote lower (only for the current instrument) LCTRL + H: Transpose the note of a selection to 1 octave higher LCTRL + L: Transpose the note of a selection to 1 octave lower LCTRL + LSHIFT + H: Transpose the note of a selection to 1 octave higher (only for the current instrument) LCTRL + LSHIFT + L: Transpose the note of a selection to 1 octave lower (only for the current instrument) LCTRL + W: Save the current selection into a file Misc LALT + ENTER: Switch between full screen / windowed mode LALT + F4: Exit program (Windows only) LCTRL + S: Save current module LSHIFT + S: Switch top right panel to synths list LSHIFT + I: Switch top right panel to instruments list <pre> C-x xh xx xx hhhh Volume B-x xh xx xx hhhh Jump to A#x xh xx xx hhhh hhhh Slide F-x xh xx xx hhhh Tempo D-x xh xx xx hhhh Pattern Break G#x xh xx xx hhhh </pre> h Hex 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 d Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 The Set Volume command: C. Input a note, then move the cursor to the effects command column and type a C. Play the pattern, and you shouldn't be able to hear the note you placed the C by. This is because the effect parameters are 00. Change the two zeros to a 40(Hex)/64(Dec), depending on what your tracker uses. Play back the pattern again, and the note should come in at full volume. The Position Jump command next. This is just a B followed by the position in the playing list that you want to jump to. One thing to remember is that the playing list always starts at 0, not 1. This command is usually in Hex. Onto the volume slide command: A. This is slightly more complex (much more if you're using a newer tracker, if you want to achieve the results here, then set slides to Amiga, not linear), due to the fact it depends on the secondary tempo. For now set a secondary tempo of 06 (you can play around later), load a long or looped sample and input a note or two. A few rows after a note type in the effect command A. For the parameters use 0F. Play back the pattern, and you should notice that when the effect kicks in, the sample drops to a very low volume very quickly. Change the effect parameters to F0, and use a low volume command on the note. Play back the pattern, and when the slide kicks in the volume of the note should increase very quickly. This because each part of the effect parameters for command A does a different thing. The first number slides the volume up, and the second slides it down. It's not recommended that you use both a volume up and volume down at the same time, due to the fact the tracker only looks for the first number that isn't set to 0. If you specify parameters of 8F, the tracker will see the 8, ignore the F, and slide the volume up. Using a slide up and down at same time just makes you look stupid. Don't do it... The Set Tempo command: F, is pretty easy to understand. You simply specify the BPM (in Hex) that you want to change to. One important thing to note is that values of lower than 20 (Hex) sets the secondary tempo rather than the primary. Another useful command is the Pattern Break: D. This will stop the playing of the current pattern and skip to the next one in the playing list. By using parameters of more than 00 you can also specify which line to begin playing from. Command 3 is Portamento to Note. This slides the currently playing note to another note, at a specified speed. The slide then stops when it reaches the desired note. <pre> C-2 1 000 - Starts the note playing --- 000 C-3 330 - Starts the slide to C-3 at a speed of 30. --- 300 - Continues the slide --- 300 - Continues the slide </pre> Once the parameters have been set, the command can be input again without any parameters, and it'll still perform the same function unless you change the parameters. This memory function allows certain commands to function correctly, such as command 5, which is the Portamento to Note and Volume Slide command. Once command 3 has been set up command 5 will simply take the parameters from that and perform a Portamento to Note. Any parameters set up for command 5 itself simply perform a Volume Slide identical to command A at the same time as the Portamento to Note. This memory function will only operate in the same channel where the original parameters were set up. There are various other commands which perform two functions at once. They will be described as we come across them. C-3 04 .. .. 09 00 ---> C-3 04 .. .. 09 00 C-3 04 .. .. 09 00 ---> C-3 04 .. .. 09 02 C-3 04 .. .. 09 00 ---> C-3 04 .. .. 09 05 C-3 04 .. .. 09 00 ---> C-3 04 .. .. 09 08 C-3 04 .. .. 09 00 ---> C-3 04 .. .. 09 0A C-3 04 .. .. 09 00 ---> C-3 04 .. .. 09 0D C-3 04 .. .. 09 10 ---> C-3 04 .. .. 09 10 (You can also switch on the Slider Rec to On, and perform parameter-live-recording, such as cutoff transitions, resonance or panning tweaking, etc..) Note: this command only works for volume/panning and fx datas columns. The next command we'll look at is the Portamento up/down: 1 and 2. Command 1 slides the pitch up at a specified speed, and 2 slides it down. This command works in a similar way to the volume slide, in that it is dependent on the secondary tempo. Both these commands have a memory dependent on each other, if you set the slide to a speed of 3 with the 1 command, a 2 command with no parameters will use the speed of 3 from the 1 command, and vice versa. Command 4 is Vibrato. Vibrato is basically rapid changes in pitch, just try it, and you'll see what I mean. Parameters are in the format of xy, where x is the speed of the slide, and y is the depth of the slide. One important point to remember is to keep your vibratos subtle and natural so a depth of 3 or less and a reasonably fast speed, around 8, is usually used. Setting the depth too high can make the part sound out of tune from the rest. Following on from command 4 is command 6. This is the Vibrato and Volume Slide command, and it has a memory like command 5, which you already know how to use. Command 7 is Tremolo. This is similar to vibrato. Rather than changing the pitch it slides the volume. The effect parameters are in exactly the same format. vibrato effect (0x1dxy) x = speed y = depth (can't be used if arpeggio (0x1b) is turned on) <pre> C-7 00 .. .. 1B37 <- Turn Arpeggio effect on --- .. .. .. 0000 --- .. .. .. 0000 --- .. .. .. 0000 --- .. .. .. 1B38 <- Change datas --- .. .. .. 0000 --- .. .. .. 0000 --- .. .. .. 0000 --- .. .. .. 1B00 <- Turn it off </pre> Command 9 is Sample Offset. This starts the playback of the sample from a different place than the start. The effect parameters specify the sample offset, but only very roughly. Say you have a sample which is 8765(Hex) bytes long, and you wanted it to play from position 4321(Hex). The effect parameter could only be as accurate as the 43 part, and it would ignore the 21. Command B is the Playing List/Order Jump command. The parameters specify the position in the Playing List/Order to jump to. When used in conjunction with command D you can specify the position and the line to play from. Command E is pretty complex, as it is used for a lot of different things, depending on what the first parameter is. Let's take a trip through each effect in order. Command E0 controls the hardware filter on an Amiga, which, as a low pass filter, cuts off the highest frequencies being played back. There are very few players and trackers on other system that simulate this function, not that you should need to use it. The second parameter, if set to 1, turns on the filter. If set to 0, the filter gets turned off. Commands E1/E2 are Fine Portamento Up/Down. Exactly the same functions as commands 1/2, except that they only slide the pitch by a very small amount. These commands have a memory the same as 1/2 as well. Command E3 sets the Glissando control. If parameters are set to 1 then when using command 3, any sliding will only use the notes in between the original note and the note being slid to. This produces a somewhat jumpier slide than usual. The best way to understand is to try it out for yourself. Produce a slow slide with command 3, listen to it, and then try using E31. Command E4 is the Set Vibrato Waveform control. This command controls how the vibrato command slides the pitch. Parameters are 0 - Sine, 1 - Ramp Down (Saw), 2 - Square. By adding 4 to the parameters, the waveform will not be restarted when a new note is played e.g. 5 - Sine without restart. Command E5 sets the Fine Tune of the instrument being played, but only for the particular note being played. It will override the default Fine Tune for the instrument. The parameters range from 0 to F, with 0 being -8 and F being +8 Fine Tune. A parameter of 8 gives no Fine Tune. If you're using a newer tracker that supports more than -8 to +8 e.g. -128 to +128, these parameters will give a rough Fine Tune, accurate to the nearest 16. Command E6 is the Jump Loop command. You mark the beginning of the part of a pattern that you want to loop with E60, and then specify with E6x the end of the loop, where x is the number of times you want it to loop. Command E7 is the Set Tremolo Waveform control. This has exactly the same parameters as command E4, except that it works for Tremolo rather than Vibrato. Command E9 is for Retriggering the note quickly. The parameter specifies the interval between the retrigs. Use a value of less than the current secondary tempo, or else the note will not get retrigged. Command EA/B are for Fine Volume Slide Up/Down. Much the same as the normal Volume Slides, except that these are easier to control since they don't depend on the secondary tempo. The parameters specify the amount to slide by e.g. if you have a sample playing at a volume of 08 (Hex) then the effect EA1 will slide this volume to 09 (Hex). A subsequent effect of EB4 would slide this volume down to 05 (Hex). Command EC is the Note Cut. This sets the volume of the currently playing note to 0 at a specified tick. The parameters should be lower than the secondary tempo or else the effect won't work. Command ED is the Note Delay. This should be used at the same time as a note is to be played, and the parameters will specify the number of ticks to delay playing the note. Again, keep the parameters lower than the secondary tempo, or the note won't get played! Command EE is the Pattern Delay. This delays the pattern for the amount of time it would take to play a certain number of rows. The parameters specify how many rows to delay for. Command EF is the Funk Repeat command. Set the sample loop to 0-1000. When EFx is used, the loop will be moved to 1000- 2000, then to 2000-3000 etc. After 9000-10000 the loop is set back to 0- 1000. The speed of the loop "movement" is defined by x. E is two times as slow as F, D is three times as slow as F etc. EF0 will turn the Funk Repeat off and reset the loop (to 0-1000). effects 0x41 and 0x42 to control the volumes of the 2 303 units There is a dedicated panel for synth parameter editing with coherent sections (osc, filter modulation, routing, so on) the interface is much nicer, much better to navigate with customizable colors, the reverb is now customizable (10 delay lines), It accepts newer types of Waves (higher bit rates, at least 24). Has a replay routine. It's pretty much your basic VA synth. The problem isn't with the sampler being to high it's the synth is tuned two octaves too low, but if you want your samples tuned down just set the base note down 2 octaves (in the instrument panel). so the synth is basically divided into 3 sections from left to right: oscillators/envelopes, then filter and LFO's, and in the right column you have mod routings and global settings. for the oscillator section you have two normal oscillators (sine, saw, square, noise), the second of which is tunable, the first one tunes with the key pressed. Attached to OSC 1 is a sub-oscillator, which is a sawtooth wave tuned one octave down. The phase modulation controls the point in the duty cycle at which the oscillator starts. The ADSR envelope sliders (grouped with oscs) are for modulation envelope 1 and 2 respectively. you can use the synth as a sampler by choosing the instrument at the top. In the filter column, the filter settings are: 1 = lowpass, 2 = highpass, 3 = off. cutoff and resonance. For the LFOs they are LFO 1 and LFO 2, the ADSR sliders in those are for the LFO itself. For the modulation routings you have ENV 1, LFO 1 for the first slider and ENV 2, LFO 2 for the second, you can cycle through the individual routings there, and you can route each modulation source to multiple destinations of course, which is another big plus for this synth. Finally the glide time is for portamento and master volume, well, the master volume... it can go quite loud. The sequencer is changed too, It's more like the one in AXS if you've used that, where you can mute tracks to re-use patterns with variation. <pre> Support for the following modules formats: 669 (Composer 669, Unis 669), AMF (DSMI Advanced Module Format), AMF (ASYLUM Music Format V1.0), APUN (APlayer), DSM (DSIK internal format), FAR (Farandole Composer), GDM (General DigiMusic), IT (Impulse Tracker), IMF (Imago Orpheus), MOD (15 and 31 instruments), MED (OctaMED), MTM (MultiTracker Module editor), OKT (Amiga Oktalyzer), S3M (Scream Tracker 3), STM (Scream Tracker), STX (Scream Tracker Music Interface Kit), ULT (UltraTracker), UNI (MikMod), XM (FastTracker 2), Mid (midi format via timidity) </pre> Possible plugin options include [http://lv2plug.in/ LV2], ====Midi - Musical Instrument Digital Interface==== A midi file typically contains music that plays on up to 16 channels (as per the midi standard), but many notes can simultaneously play on each channel (depending on the limit of the midi hardware playing it). '''Timidity''' Although usually already installed, you can uncompress the [http://www.libsdl.org/projects/SDL_mixer/ timidity.tar.gz (14MB)] into a suitable drawer like below's SYS:Extras/Audio/ assign timidity: SYS:Extras/Audio/timidity added to SYSːs/User-Startup '''WildMidi playback''' '''Audio Evolution 4 (2003) 4.0.23 (from 2012)''' *Sync Menu - CAMD Receive, Send checked *Options Menu - MIDI Machine Control - Midi Bar Display - Select CAMD MIDI in / out - Midi Remote Setup MCB Master Control Bus *Sending a MIDI start-command and a Song Position Pointer, you can synchronize audio with an external MIDI sequencer (like B&P). *B&P Receive, start AE, add AudioEvolution.ptool in Bars&Pipes track, press play / record in AE then press play in Pipes *CAMD Receive, receive MIDI start or continue commands via camd.library sync to AE *MIDI Machine Control *Midi Bar Display *Select CAMD MIDI in / out *Midi Remote Setup - open requester for external MIDI controllers to control app mixer and transport controls cc remotely Channel - mixer(vol, pan, mute, solo), eq, aux, fx, Subgroup - Volume, Mute, Solo Transport - Start, End, Play, Stop, Record, Rewind, Forward Misc - Master vol., Bank Down, Bank up <pre> q - quit First 3 already opened when AE started F1 - timeline window F2 - mixer F3 - control F4 - subgroups F5 - aux returns F6 - sample list i - Load sample to use space - start/stop play b - reset time 0:00 s - split mode r - open recording window a - automation edit mode with p panning, m mute and v volume [ / ] - zoom in / out : - previous track * - next track x c v f - cut copy paste cross-fade g - snap grid </pre> '''[http://bnp.hansfaust.de/ Bars n Pipes sequencer]''' BarsnPipes debug ... in shell Menu (right mouse) *Song - Songs load and save in .song format but option here to load/save Midi_Files .mid in FORMAT0 or FORMAT1 *Track - *Edit - *Tool - *Timing - SMTPE Synchronizing *Windows - *Preferences - Multiple MIDI-in option Windows (some of these are usually already opened when Bars n Pipes starts up for the first time) *Workflow -> Tracks, .... Song Construction, Time-line Scoring, Media Madness, Mix Maestro, *Control -> Transport (or mini one), Windows (which collects all the Windows icons together-shortcut), .... Toolbox, Accessories, Metronome, Once you have your windows placed on the screen that suits your workflow, Song -> Save as Default will save the positions, colors, icons, etc as you'd like them If you need a particular setup of Tracks, Tools, Tempos etc, you save them all as a new song you can load each time Right mouse menu -> Preferences -> Environment... -> ScreenMode - Linkages for Synch (to Slave) usbmidi.out.0 and Send (Master) usbmidi.in.0 - Clock MTC '''Tracks''' #Double-click on B&P's icon. B&P will then open with an empty Song. You can also double-click on a song icon to open a song in B&P. #Choose a track. The B&P screen will contain a Tracks Window with a number of tracks shown as pipelines (Track 1, Track 2, etc...). To choose a track, simply click on the gray box to show an arrow-icon to highlight it. This icon show whether a track is chosen or not. To the right of the arrow-icon, you can see the icon for the midi-input. If you double-click on this icon you can change the MIDI-in setup. #Choose Record for the track. To the right of the MIDI-input channel icon you can see a pipe. This leads to another clickable icon with that shows either P, R or M. This stands for Play, Record or Merge. To change the icon, simply click on it. If you choose P, this track can only play the track (you can't record anything). If you choose R, you can record what you play and it overwrites old stuff in the track. If you choose M, you merge new records with old stuff in the track. Choose R now to be able to make a record. #Chose MIDI-channel. On the most right part of the track you can see an icon with a number in it. This is the MIDI-channel selector. Here you must choose a MIDI-channel that is available on your synthesizer/keyboard. If you choose General MIDI channel 10, most synthesizer will play drum sounds. To the left of this icon is the MIDI-output icon. Double-click on this icon to change the MIDI-output configuration. #Start recording. The next step is to start recording. You must then find the control buttons (they look like buttons on a CD-player). To be able to make a record. you must click on the R icon. You can simply now press the play button (after you have pressed the R button) and play something on you keyboard. To playback your composition, press the Play button on the control panel. #Edit track. To edit a track, you simply double click in the middle part of a track. You will then get a new window containing the track, where you can change what you have recorded using tools provided. Take also a look in the drop-down menus for more features. Videos to help understand [https://www.youtube.com/watch?v=A6gVTX-9900 small intro], [https://www.youtube.com/watch?v=abq_rUTiSA4&t=3s Overview], [https://www.youtube.com/watch?v=ixOVutKsYQo Workplace Setup CC PC Sysex], [https://www.youtube.com/watch?v=dDnJLYPaZTs Import Song], [https://www.youtube.com/watch?v=BC3kkzPLkv4 Tempo Mapping], [https://www.youtube.com/watch?v=sd23kqMYPDs ptool Arpeggi-8], [https://www.youtube.com/watch?v=LDJq-YxgwQg PlayMidi Song], [https://www.youtube.com/watch?v=DY9Pu5P9TaU Amiga Midi], [https://www.youtube.com/watch?v=abq_rUTiSA4 Learning Amiga bars and Pipes], Groups like [https://groups.io/g/barsnpipes/topics this] could help '''Tracks window''' * blue "1 2 3 4 5 6 7 8 Group" and transport tape deck VCR-type controls * Flags * [http://theproblem.alco-rhythm.com/org/bp.html Track 1, Track2, to Track 16, on each Track there are many options that can be activated] Each Track has a *Left LHS - Click in grey box to select what Track to work on, Midi-In ptool icon should be here (5pin plug icon), and many more from the Toolbox on the Input Pipeline *Middle - (P, R, M) Play, Record, Merge/Multi before the sequencer line and a blue/red/yellow (Thru Mute Play) Tap *Right RHS - Output pipeline, can have icons placed uopn it with the final ptool icon(s) being the 5pin icon symbol for Midi-OUT Clogged pipelines may need Esc pressed several times '''Toolbox (tools affect the chosen pipeline)''' After opening the Toolbox window you can add extra Tools (.ptool) for the pipelines like keyboard(virtual), midimonitor, quick patch, transpose, triad, (un)quantize, feedback in/out, velocity etc right mouse -> Toolbox menu option -> Install Tool... and navigate to Tool drawer (folder) and select requried .ptool Accompany B tool to get some sort of rythmic accompaniment, Rythm Section and Groove Quantize are examples of other tools that make use of rythms [https://aminet.net/search?query=bars Bars & Pipes pattern format .ptrn] for drawer (folder). Load from the Menu as Track or Group '''Accessories (affect the whole app)''' Accessories -> Install... and goto the Accessories drawer for .paccess like adding ARexx scripting support '''Song Construction''' <pre> F1 Pencil F2 Magic Wand F3 Hand F4 Duplicator F5 Eraser F6 Toolpad F7 Bounding box F8 Lock to A-B-A A-B-A strip, section, edit flags, white boxes, </pre> Bars&Pipes Professional offers three track formats; basic song tracks, linear tracks — which don't loop — and finally real‑time tracks. The difference between them is that both song and linear tracks respond to tempo changes, while real‑time tracks use absolute timing, always trigger at the same instant regardless of tempo alterations '''Tempo Map''' F1 Pencil F2 Magic Wand F3 Hand F4 Eraser F5 Curve F6 Toolpad Compositions Lyrics, Key, Rhythm, Time Signature '''Master Parameters''' Key, Scale/Mode '''Track Parameters''' Dynamics '''Time-line Scoring''' '''Media Madness''' '''Mix Maestro''' *ACCESSORIES Allows the importation of other packages and additional modules *CLIPBOARD Full cut, copy and paste operations, enabling user‑definable clips to be shared between tracks. *INFORMATION A complete rundown on the state of the current production and your machine. *MASTER PARAMETERS Enables global definition of time signatures, lyrics, scales, chords, dynamics and rhythm changes. *MEDIA MADNESS A complete multimedia sequencer which allows samples, stills, animation, etc *METRONOME Tempo feedback via MIDI, internal Amiga audio and colour cycling — all three can be mixed and matched as required. *MIX MAESTRO Completely automated mixdown with control for both volume and pan. All fader alterations are memorised by the software *RECORD ACTIVATION Complete specification of the data to be recorded/merged. Allows overdubbing of pitch‑bend, program changes, modulation etc *SET FLAGS Numeric positioning of location and edit flags in either SMPTE or musical time *SONG CONSTRUCTION Large‑scale cut and paste of individual measures, verses or chorus, by means of bounding box and drag‑n‑drop mouse selections *TEMPO MAP Tempo change using a variety of linear and non‑linear transition curves *TEMPO PALETTE Instant tempo changes courtesy of four user‑definable settings. *TIMELINE SCORING Sequencing of a selection of songs over a defined period — ideal for planning an entire set for a live performance. *TOOLBOX Selection screen for the hundreds of signal‑processing tools available *TRACKS Opens the main track window to enable recording, editing and the use of tools. *TRANSPORT Main playback control window, which also provides access to user‑ defined flags, loop and punch‑in record modes. Bars and Pipes Pro 2.5 is using internal 4-Byte IDs, to check which kind of data are currently processed. Especially in all its files the IDs play an important role. The IDs are stored into the file in the same order they are laid out in the memory. In a Bars 'N' Pipes file (no matter which kind) the ID "NAME" (saved as its ANSI-values) is stored on a big endian system (68k-computer) as "NAME". On a little endian system (x86 PC computer) as "EMAN". The target is to make the AROS-BnP compatible to songs, which were stored on a 68k computer (AMIGA). If possible, setting MIDI channels for Local Control for your keyboard http://www.fromwithin.com/liquidmidi/archive.shtml MIDI files are essentially a stream of event data. An event can be many things, but typically "note on", "note off", "program change", "controller change", or messages that instruct a MIDI compatible synth how to play a given bit of music. * Channel - 1 to 16 - * Messages - PC presets, CC effects like delays, reverbs, etc * Sequencing - MIDI instruments, Drums, Sound design, * Recording - * GUI - Piano roll or Tracker, Staves and Notes MIDI events/messages like step entry e.g. Note On, Note Off MIDI events/messages like PB, PC, CC, Mono and Poly After-Touch, Sysex, etc MIDI sync - Midi Clocks (SPS Measures), Midi Time Code (h, m, s and frames) SMPTE Individual track editing with audition edits so easier to test any changes. Possible to stop track playback, mix clips from the right edit flag and scroll the display using arrow keys. Step entry, to extend a selected note hit the space bar and the note grows accordingly. Ability to cancel mouse‑driven edits by simply clicking the right mouse button — at which point everything snaps back into its original form. Lyrics can now be put in with syllable dividers, even across an entire measure or section. Autoranging when you open a edit window, the notes are automatically displayed — working from the lowest upwards. Flag editing, shift‑click on a flag immediately open the bounds window, ready for numeric input. Ability to cancel edits using the right‑hand mouse button, plus much improved Bounding Box operations. Icons other than the BarsnPipes icon -> PUBSCREEN=BarsnPipes (cannot choose modes higher than 8bit 256 colors) Preferences -> Menu in Tracks window - Send MIDI defaults OFF Prefs -> Environment -> screenmode (saved to BarsnPipes.prefs binary file) Customization -> pics in gui drawer (folder) - Can save as .song files and .mid General Midi SMF is a “Standard Midi File” ([http://www.music.mcgill.ca/~ich/classes/mumt306/StandardMIDIfileformat.html SMF0, SMF1 and SMF2]), [https://github.com/stump/libsmf libsmf], [https://github.com/markc/midicomp MIDIcomp], [https://github.com/MajicDesigns/MD_MIDIFile C++ src], [], [https://github.com/newdigate/midi-smf-reader Midi player], * SMF0 All MIDI data is stored in one track only, separated exclusively by the MIDI channel. * SMF1 The MIDI data is stored in separate tracks/channels. * SMF2 (rarely used) The MIDI data is stored in separate tracks, which are additionally wrapped in containers, so it's possible to have e.g. several tracks using the same MIDI channels. Would it be possible to enrich Bars N’Pipes with software synth and sample support along with audio recording and mastering tools like in the named MAC or PC music sequencers? On the classic AMIGA-OS this is not possible because of missing CPU-power. The hardware of the classic AMIGA is not further developed. So we must say (unfortunately) that those dreams can’t become reality BarsnPipes is best used with external MIDI-equipment. This can be a keyboard or synthesizer with MIDI-connectors. <pre> MIDI can control 16 channels There are USB-MIDI-Interfaces on the market with 16 independent MIDI-lines (multi-port), which can handle 16 MIDI devices independently – 16×16 = 256 independent MIDI-channels or instruments handle up to 16 different USB-MIDI-Interfaces (multi-device). That is: 16X16X16 = 4096 independent MIDI-channels – theoretically </pre> <pre> Librarian MIDI SYStem EXplorer (sysex) - PatchEditor and used to be supplied as a separate program like PatchMeister but currently not at present It should support MIDI.library (PD), BlueRibbon.library (B&P), TriplePlayPlus, and CAMD.library (DeluxeMusic) and MIDI information from a device's user manual and configure a custom interface to access parameters for all MIDI products connected to the system Supports ALL MIDI events and the Patch/Librarian data is stored in MIDI standard format Annette M.Crowling, Missing Link Software, Inc. </pre> Composers <pre> [https://x.com/hirasawa/status/1403686519899054086 Susumu Hirasawa] </pre> <pre> 1988 Todor Fay and his wife Melissa Jordan Gray, who founded the Blue Ribbon Inc 1992 Bars&Pipes Pro published November 2000, Todor Fay announcement to release the sourcecode of Bars&Pipes Pro 2.5c beta end of May 2001, the source of the main program and the sources of some tools and accessories were in a complete and compileable state end of October 2009 stop further development of BarsnPipes New for now on all supported systems and made freeware 2013 Alfred Faust diagnosed with incureable illness, called „Myastenia gravis“ (weak muscles) </pre> Protrekkr How to use Midi In/Out in Protrekkr ? First of all, midi in & out capabilities of this program are rather limited. # Go to Misc. Setup section and select a midi in or out device to use (ptk only supports one device at a time). # Go to instrument section, and select a MIDI PRG (the default is N/A, which means no midi program selected). # Go to track section and here you can assign a midi channel to each track of ptk. # Play notes :]. Note off works. F'x' note cut command also works too, and note-volume command (speed) is supported. Also, you can change midicontrollers in the tracker, using '90' in the panning row: <pre> C-3 02 .. .. 0000.... --- .. .. 90 xxyy.... << This will set the value --- .. .. .. 0000.... of the controller n.'xx' to 'yy' (both in hex) --- .. .. .. 0000.... </pre> So "--- .. .. 90 2040...." will set the controller number $20(32) to $40(64). You will need the midi implementation table of your gear to know what you can change with midi controller messages. N.B. Not all MIDI devices are created equal! Although the MIDI specification defines a large range of MIDI messages of various kinds, not every MIDI device is required to work in exactly the same way and respond to all the available messages and ways of working. For example, we don't expect a wind synthesiser to work in the same way as a home keyboard. Some devices, the older ones perhaps, are only able to respond to a single channel. With some of those devices that channel can be altered from the default of 1 (probably) to another channel of the 16 possible. Other devices, for instance monophonic synthesisers, are capable of producing just one note at a time, on one MIDI channel. Others can produce many notes spread across many channels. Further devices can respond to, and transmit, "breath controller" data (MIDI controller number 2 (CC#2)) others may respond to the reception of CC#2 but not be able to create and to send it. A controller keyboard may be capable of sending "expression pedal" data, but another device may not be capable of responding to that message. Some devices just have the basic GM sound set. The "voice" or "instrument" is selected using a "Program Change" message on its own. Other devices have a greater selection of voices, usually arranged in "banks", and the choice of instrument is made by responding to "Bank Select MSB" (MIDI controller 0 (CC#0)), others use "Bank Select LSB" (MIDI controller number 32 (CC#32)), yet others use both MSB and LSB sent one after the other, all followed by the Program Change message. The detailed information about all the different voices will usually be available in a published MIDI Data List. MIDI Implementation Chart But in the User Manual there is sometimes a summary of how the device works, in terms of MIDI, in the chart at the back of the manual, the MIDI Implementation Chart. If you require two devices to work together you can compare the two implementation charts to see if they are "compatible". In order to do this we will need to interpret that chart. The chart is divided into four columns headed "Function", "Transmitted" (or "Tx"), "Received" (or "Rx"), or more correctly "Recognised", and finally, "Remarks". <pre> The left hand column defines which MIDI functions are being described. The 2nd column defines what the device in question is capable of transmitting to another device. The 3rd column defines what the device is capable of responding to. The 4th column is for explanations of the values contained within these previous two columns. </pre> There should then be twelve sections, with possibly a thirteenth containing extra "Notes". Finally there should be an explanation of the four MIDI "modes" and what the "X" and the "O" mean. <pre> Mode 1: Omni On, Poly; Mode 2: Omni On, Mono; Mode 3: Omni Off, Poly; Mode 4: Omni Off, Mono. </pre> O means "yes" (implemented), X means "no" (not implemented). Sometimes you will find a row of asterisks "**************", these seem to indicate that the data is not applicable in this case. Seen in the transmitted field only (unless you've seen otherwise). Lastly you may find against some entries an asterisk followed by a number e.g. *1, these will refer you to further information, often on a following page, giving more detail. Basic Channel But the very first set of boxes will tell us the "Basic Channel(s)" that the device sends or receives on. "Default" is what happens when the device is first turned on, "changed" is what a switch of some kind may allow the device to be set to. For many devices e.g. a GM sound module or a home keyboard, this would be 1-16 for both. That is it can handle sending and receiving on all MIDI channels. On other devices, for example a synthesiser, it may by default only work on channel 1. But the keyboard could be "split" with the lower notes e.g. on channel 2. If the synth has an arppegiator, this may be able to be set to transmit and or receive on yet another channel. So we might see the default as "1" but the changed as "1-16". Modes. We need to understand Omni On and Off, and Mono and Poly, then we can decipher the four modes. But first we need to understand that any of these four Mode messages can be sent to any MIDI channel. They don't necessarily apply to the whole device. If we send an "Omni On" message (CC#125) to a MIDI channel of a device, we are, in effect, asking it to respond to e.g. a Note On / Off message pair, received on any of the sixteen channels. Sound strange? Read it again. Still strange? It certainly is. We normally want a MIDI channel to respond only to Note On / Off messages sent on that channel, not any other. In other words, "Omni Off". So "Omni Off" (CC#124) tells a channel of our MIDI device to respond only to messages sent on that MIDI channel. "Poly" (CC#127) is for e.g. a channel of a polyphonic sound module, or a home keyboard, to be able to respond to many simultaneous Note On / Off message pairs at once and produce musical chords. "Mono" (CC#126) allows us to set a channel to respond as if it were e.g. a flute or a trumpet, playing just one note at a time. If the device is capable of it, then the overlapping of notes will produce legato playing, that is the attack portion of the second note of two overlapping notes will be removed resulting in a "smoother" transition. So a channel with a piano voice assigned to it will have Omni Off, Poly On (Mode 3), a channel with a saxophone voice assigned could be Omni Off, Mono On (Mode 4). We call these combinations the four modes, 1 to 4, as defined above. Most modern devices will have their channels set to Mode 3 (Omni Off, Poly) but be switchable, on a per channel basis, to Mode 4 (Omni Off, Mono). This second section of data will include first its default value i.e. upon device switch on. Then what Mode messages are acceptable, or X if none. Finally, in the "Altered" field, how a Mode message that can't be implemented will be interpreted. Usually there will just be a row of asterisks effectively meaning nothing will be done if you try to switch to an unimplemented mode. Note Number <pre> The next row will tell us which MIDI notes the device can send or receive, normally 0-127. The second line, "True Voice" has the following in the MIDI specification: "Range of received note numbers falling within the range of true notes produced by the instrument." My interpretation is that, for instance, a MIDI piano may be capable of sending all MIDI notes (0 to 127) by transposition, but only responding to the 88 notes (21 to 108) of a real piano. </pre> Velocity This will tell us whether the device we're looking at will handle note velocity, and what range from 1-127, or maybe just 64, it transmits or will recognise. So usually "O" plus a range or "X" for not implemented. After touch This may have one or two lines two it. If a one liner the either "O" or "X", yes or no. If a two liner then it may include "Keys" or "Poly" and "Channel". This will show whether the device will respond to Polyphonic after touch or channel after touch or neither. Pitch Bend Again "O" for implemented, "X" for not implemented. (Many stage pianos will have no pitch bend capability.) It may also, in the notes section, state whether it will respond to the full 14 bits, or not, as usually encoded by the pitch bend wheel. Control Change This is likely to be the largest section of the chart. It will list all those controllers, starting from CC#0, Bank Select MSB, which the device is capable of sending, and those that it will respond to using "O" or "X" respectively. You will, almost certainly, get some further explanation of functionality in the remarks column, or in more detail elsewhere in the documentation. Of course you will need to know what all the various controller numbers do. Lots of the official technical specifications can be found at the [www.midi.org/techspecs/ MMA], with the table of messages and control change [www.midi.org/techspecs/midimessages.php message numbers] Program Change Again "O" or "X" in the Transmitted or Recognised column to indicate whether or not the feature is implemented. In addition a range of numbers is shown, typically 0-127, to show what is available. True # (number): "The range of the program change numbers which correspond to the actual number of patches selected." System Exclusive Used to indicate whether or not the device can send or recognise System Exclusive messages. A short description is often given in the Remarks field followed by a detailed explanation elsewhere in the documentation. System Common - These include the following: <pre> MIDI Time Code Quarter Frame messages (device synchronisation). Song Position Pointer Song Select Tune Request </pre> The section will indicate whether or not the device can send or respond to any of these messages. System Real Time These include the following: <pre> Timing Clock - often just written as "Clock" Start Stop Continue </pre> These three are usually just referred to as "Commands" and listed. Again the section will indicate which, if any, of these messages the device can send or respond to. <pre> Aux. Messages Again "O" or "X" for implemented or not. Aux. = Auxiliary. Active Sense = Active Sensing. </pre> Often with an explanation of the action of the device. Notes The "Notes" section can contain any additional comments to clarify the particular implementation. Some of the explanations have been drawn directly from the MMA MIDI 1.0 Detailed Specification. And the detailed explanation of some of the functions will be found there, or in the General MIDI System Level 1 or General MIDI System Level 2 documents also published by the MMA. OFFICIAL MIDI SPECIFICATIONS SUMMARY OF MIDI MESSAGES Table 1 - Summary of MIDI Messages The following table lists the major MIDI messages in numerical (binary) order (adapted from "MIDI by the Numbers" by D. Valenti, Electronic Musician 2/88, and updated by the MIDI Manufacturers Association.). This table is intended as an overview of MIDI, and is by no means complete. WARNING! Details about implementing these messages can dramatically impact compatibility with other products. We strongly recommend consulting the official MIDI Specifications for additional information. MIDI 1.0 Specification Message Summary Channel Voice Messages [nnnn = 0-15 (MIDI Channel Number 1-16)] {| class="wikitable sortable" width="90%" ! width="10%" |Status D7----D0 ! width="10%" |Data Byte(s) D7----D0 ! width="20%" |Description |- |<!--Status-->1000nnnn || <!--Data-->0kkkkkkk 0vvvvvvv || <!--Description-->Note Off event. This message is sent when a note is released (ended). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity. |- |<!--Status-->1001nnnn || <!--Data-->0kkkkkkk 0vvvvvvv || <!--Description-->Note On event. This message is sent when a note is depressed (start). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity. |- |<!--Status-->1010nnnn || <!--Data-->0kkkkkkk 0vvvvvvv || <!--Description-->Polyphonic Key Pressure (Aftertouch). This message is most often sent by pressing down on the key after it "bottoms out". (kkkkkkk) is the key (note) number. (vvvvvvv) is the pressure value. |- |<!--Status-->1011nnnn || <!--Data-->0ccccccc 0vvvvvvv || <!--Description-->Control Change. This message is sent when a controller value changes. Controllers include devices such as pedals and levers. Controller numbers 120-127 are reserved as "Channel Mode Messages" (below). (ccccccc) is the controller number (0-119). (vvvvvvv) is the controller value (0-127). |- |<!--Status-->1100nnnn || <!--Data-->0ppppppp || <!--Description-->Program Change. This message sent when the patch number changes. (ppppppp) is the new program number. |- |<!--Status-->1101nnnn || <!--Data-->0vvvvvvv || <!--Description-->Channel Pressure (After-touch). This message is most often sent by pressing down on the key after it "bottoms out". This message is different from polyphonic after-touch. Use this message to send the single greatest pressure value (of all the current depressed keys). (vvvvvvv) is the pressure value. |- |<!--Status-->1110nnnn || <!--Data-->0lllllll 0mmmmmmm || <!--Description-->Pitch Bend Change. This message is sent to indicate a change in the pitch bender (wheel or lever, typically). The pitch bender is measured by a fourteen bit value. Center (no pitch change) is 2000H. Sensitivity is a function of the receiver, but may be set using RPN 0. (lllllll) are the least significant 7 bits. (mmmmmmm) are the most significant 7 bits. |} Channel Mode Messages (See also Control Change, above) {| class="wikitable sortable" width="90%" ! width="10%" |Status D7----D0 ! width="10%" |Data Byte(s) D7----D0 ! width="20%" |Description |- |<!--Status-->1011nnnn || <!--Data-->0ccccccc 0vvvvvvv || <!--Description-->Channel Mode Messages. This the same code as the Control Change (above), but implements Mode control and special message by using reserved controller numbers 120-127. The commands are: *All Sound Off. When All Sound Off is received all oscillators will turn off, and their volume envelopes are set to zero as soon as possible c = 120, v = 0: All Sound Off *Reset All Controllers. When Reset All Controllers is received, all controller values are reset to their default values. (See specific Recommended Practices for defaults) c = 121, v = x: Value must only be zero unless otherwise allowed in a specific Recommended Practice. *Local Control. When Local Control is Off, all devices on a given channel will respond only to data received over MIDI. Played data, etc. will be ignored. Local Control On restores the functions of the normal controllers. c = 122, v = 0: Local Control Off c = 122, v = 127: Local Control On * All Notes Off. When an All Notes Off is received, all oscillators will turn off. c = 123, v = 0: All Notes Off (See text for description of actual mode commands.) c = 124, v = 0: Omni Mode Off c = 125, v = 0: Omni Mode On c = 126, v = M: Mono Mode On (Poly Off) where M is the number of channels (Omni Off) or 0 (Omni On) c = 127, v = 0: Poly Mode On (Mono Off) (Note: These four messages also cause All Notes Off) |} System Common Messages System Messages (0xF0) The final status nybble is a “catch all” for data that doesn’t fit the other statuses. They all use the most significant nybble (4bits) of 0xF, with the least significant nybble indicating the specific category. The messages are denoted when the MSB of the second nybble is 1. When that bit is a 0, the messages fall into two other subcategories. System Common If the MSB of the second second nybble (4 bits) is not set, this indicates a System Common message. Most of these are messages that include some additional data bytes. System Common Messages Type Status Byte Number of Data Bytes Usage <pre> Time Code Quarter Frame 0xF1 1 Indicates timing using absolute time code, primarily for synthronization with video playback systems. A single location requires eight messages to send the location in an encoded hours:minutes:seconds:frames format*. Song Position 0xF2 2 Instructs a sequencer to jump to a new position in the song. The data bytes form a 14-bit value that expresses the location as the number of sixteenth notes from the start of the song. Song Select 0xF3 1 Instructs a sequencer to select a new song. The data byte indicates the song. Undefined 0xF4 0 Undefined 0xF5 0 Tune Request 0xF6 0 Requests that the receiver retunes itself**. </pre> *MIDI Time Code (MTC) is significantly complex. Please see the MIDI Specification **While modern digital instruments are good at staying in tune, older analog synthesizers were prone to tuning drift. Some analog synthesizers had an automatic tuning operation that could be initiated with this command. System Exclusive If you’ve been keeping track, you’ll notice there are two status bytes not yet defined: 0xf0 and 0xf7. These are used by the System Exclusive message, often abbreviated at SysEx. SysEx provides a path to send arbitrary data over a MIDI connection. There is a group of predefined messages for complex data, like fine grained control of MIDI Time code machinery. SysEx is also used to send manufacturer defined data, such as patches, or even firmware updates. System Exclusive messages are longer than other MIDI messages, and can be any length. The messages are of the following format: 0xF0, 0xID, 0xdd, ...... 0xF7 The message is bookended with distinct bytes. It opens with the Start Of Exclusive (SOX) data byte, 0xF0. The next one to three bytes after the start are an identifier. Values from 0x01 to 0x7C are one-byte vendor IDs, assigned to manufacturers who were involved with MIDI at the beginning. If the ID is 0x00, it’s a three-byte vendor ID - the next two bytes of the message are the value. <pre> ID 0x7D is a placeholder for non-commercial entities. ID 0x7E indicates a predefined Non-realtime SysEx message. ID 0x7F indicates a predefined Realtime SysEx message. </pre> After the ID is the data payload, sent as a stream of bytes. The transfer concludes with the End of Exclusive (EOX) byte, 0xF7. The payload data must follow the guidelines for MIDI data bytes – the MSB must not be set, so only 7 bits per byte are actually usable. If the MSB is set, it falls into three possible scenarios. An End of Exclusive byte marks the ordinary termination of the SysEx transfer. System Real Time messages may occur within the transfer without interrupting it. The recipient should handle them independently of the SysEx transfer. Other status bytes implicitly terminate the SysEx transfer and signal the start of new messages. Some inexpensive USB-to-MIDI interfaces aren’t capable of handling messages longer than four bytes. {| class="wikitable sortable" width="90%" ! width="10%" |Status D7----D0 ! width="10%" |Data Byte(s) D7----D0 ! width="20%" |Description |- |<!--Status-->11110000 || <!--Data-->0iiiiiii [0iiiiiii 0iiiiiii] 0ddddddd --- --- 0ddddddd 11110111 || <!--Description-->System Exclusive. This message type allows manufacturers to create their own messages (such as bulk dumps, patch parameters, and other non-spec data) and provides a mechanism for creating additional MIDI Specification messages. The Manufacturer's ID code (assigned by MMA or AMEI) is either 1 byte (0iiiiiii) or 3 bytes (0iiiiiii 0iiiiiii 0iiiiiii). Two of the 1 Byte IDs are reserved for extensions called Universal Exclusive Messages, which are not manufacturer-specific. If a device recognizes the ID code as its own (or as a supported Universal message) it will listen to the rest of the message (0ddddddd). Otherwise, the message will be ignored. (Note: Only Real-Time messages may be interleaved with a System Exclusive.) |- |<!--Status-->11110001 || <!--Data-->0nnndddd || <!--Description-->MIDI Time Code Quarter Frame. nnn = Message Type dddd = Values |- |<!--Status-->11110010 || <!--Data-->0lllllll 0mmmmmmm || <!--Description-->Song Position Pointer. This is an internal 14 bit register that holds the number of MIDI beats (1 beat= six MIDI clocks) since the start of the song. l is the LSB, m the MSB. |- |<!--Status-->11110011 || <!--Data-->0sssssss || <!--Description-->Song Select. The Song Select specifies which sequence or song is to be played. |- |<!--Status-->11110100 || <!--Data--> || <!--Description-->Undefined. (Reserved) |- |<!--Status-->11110101 || <!--Data--> || <!--Description-->Undefined. (Reserved) |- |<!--Status-->11110110 || <!--Data--> || <!--Description-->Tune Request. Upon receiving a Tune Request, all analog synthesizers should tune their oscillators. |- |<!--Status-->11110111 || <!--Data--> || <!--Description-->End of Exclusive. Used to terminate a System Exclusive dump. |} System Real-Time Messages {| class="wikitable sortable" width="90%" ! width="10%" |Status D7----D0 ! width="10%" |Data Byte(s) D7----D0 ! width="20%" |Description |- |<!--Status-->11111000 || <!--Data--> || <!--Description-->Timing Clock. Sent 24 times per quarter note when synchronization is required. |- |<!--Status-->11111001 || <!--Data--> || <!--Description-->Undefined. (Reserved) |- |<!--Status-->11111010 || <!--Data--> || <!--Description-->Start. Start the current sequence playing. (This message will be followed with Timing Clocks). |- |<!--Status-->11111011 || <!--Data--> || <!--Description-->Continue. Continue at the point the sequence was Stopped. |- |<!--Status-->11111100 || <!--Data--> || <!--Description-->Stop. Stop the current sequence. |- |<!--Status-->11111101 || <!--Data--> || <!--Description-->Undefined. (Reserved) |- |<!--Status-->11111110 || <!--Data--> || <!--Description-->Active Sensing. This message is intended to be sent repeatedly to tell the receiver that a connection is alive. Use of this message is optional. When initially received, the receiver will expect to receive another Active Sensing message each 300ms (max), and if it does not then it will assume that the connection has been terminated. At termination, the receiver will turn off all voices and return to normal (non- active sensing) operation. |- |<!--Status-->11111111 || <!--Data--> || <!--Description-->Reset. Reset all receivers in the system to power-up status. This should be used sparingly, preferably under manual control. In particular, it should not be sent on power-up. |} Advanced Messages Polyphonic Pressure (0xA0) and Channel Pressure (0xD0) Some MIDI controllers include a feature known as Aftertouch. While a key is being held down, the player can press harder on the key. The controller measures this, and converts it into MIDI messages. Aftertouch comes in two flavors, with two different status messages. The first flavor is polyphonic aftertouch, where every key on the controller is capable of sending its own independent pressure information. The messages are of the following format: <pre> 0xnc, 0xkk, 0xpp n is the status (0xA) c is the channel nybble kk is the key number (0 to 127) pp is the pressure value (0 to 127) </pre> Polyphonic aftertouch is an uncommon feature, usually found on premium quality instruments, because every key requires a separate pressure sensor, plus the circuitry to read them all. Much more commonly found is channel aftertouch. Instead of needing a discrete sensor per key, it uses a single, larger sensor to measure pressure on all of the keys as a group. The messages omit the key number, leaving a two-byte format <pre> 0xnc, 0xpp n is the status (0xD) c is the channel number pp is the pressure value (0 to 127) </pre> Pitch Bend (0xE0) Many keyboards have a wheel or lever towards the left of the keys for pitch bend control. This control is usually spring-loaded, so it snaps back to the center of its range when released. This allows for both upward and downward bends. Pitch Bend Wheel The wheel sends pitch bend messages, of the format <pre> 0xnc, 0xLL, 0xMM n is the status (0xE) c is the channel number LL is the 7 least-significant bits of the value MM is the 7 most-significant bits of the value </pre> You’ll notice that the bender data is actually 14 bits long, transmitted as two 7-bit data bytes. This means that the recipient needs to reassemble those bytes using binary manipulation. 14 bits results in an overall range of 214, or 0 to 16,383. Because it defaults to the center of the range, the default value for the bender is halfway through that range, at 8192 (0x2000). Control Change (0xB0) In addition to pitch bend, MIDI has provisions for a wider range of expressive controls, sometimes known as continuous controllers, often abbreviated CC. These are transmitted by the remaining knobs and sliders on the keyboard controller shown below. Continuous Controllers These controls send the following message format: <pre> 0xnc, 0xcc, 0xvv n is the status (0xB) c is the MIDI channel cc is the controller number (0-127) vv is the controller value (0-127) </pre> Typically, the wheel next to the bender sends controller number one, assigned to modulation (or vibrato) depth. It is implemented by most instruments. The remaining controller number assignments are another point of confusion. The MIDI specification was revised in version 2.0 to assign uses for many of the controllers. However, this implementation is not universal, and there are ranges of unassigned controllers. On many modern MIDI devices, the controllers are assignable. On the controller keyboard shown in the photos, the various controls can be configured to transmit different controller numbers. Controller numbers can be mapped to particular parameters. Virtual synthesizers frequently allow the user to assign CCs to the on-screen controls. This is very flexible, but it might require configuration on both ends of the link and completely bypasses the assignments in the standard. Program Change (0xC0) Most synthesizers have patch storage memory, and can be told to change patches using the following command: <pre> 0xnc, 0xpp n is the status (0xc) c is the channel pp is the patch number (0-127) </pre> This allows for 128 sounds to be selected, but modern instruments contain many more than 128 patches. Controller #0 is used as an additional layer of addressing, interpreted as a “bank select” command. Selecting a sound on such an instrument might involve two messages: a bank select controller message, then a program change. Audio & Midi are not synchronized, what I can do ? Buy a commercial software package but there is a nasty trick to synchronize both. It's a bit hardcore but works for me: Simply put one line down to all midi notes on your pattern (use Insert key) and go to 'Misc. Setup', adjust the latency and just search a value that will make sound sync both audio/midi. The stock Sin/Saw/Pulse and Rnd waveforms are too simple/common, is there a way to use something more complex/rich ? You have to ability to redirect the waveforms of the instruments through the synth pipe by selecting the "wav" option for the oscillator you're using for this synth instrument, samples can be used as wavetables to replace the stock signals. Sound banks like soundfont (sf2) or Kontakt2 are not supported at the moment ====DAW Audio Evolution 4==== Audio Evolution 4 gives you unsurpassed power for digital audio recording and editing on the Amiga. The latest release focusses on time-saving non-linear and non-destructive editing, as seen on other platforms. Besides editing, Audio Evolution 4 offers a wide range of realtime effects, including compression, noise gate, delays, reverb, chorus and 3-band EQ. Whether you put them as inserts on a channel or use them as auxillaries, the effect parameters are realtime adjustable and can be fully automated. Together with all other mixing parameters, they can even be controlled remotely, using more ergonomic MIDI hardware. Non-linear editing on the time line, including cut, copy, paste, move, split, trim and crossfade actions The number of tracks per project(s) is unlimited .... AHI limits you to recording only two at a time. i.e. not on 8 track sound cards like the Juli@ or Phase 88. sample file import is limited to 16bit AIFF (not AIFC, important distinction as some files from other sources can be AIFC with aiff file extention). and 16bit WAV (pcm only) Most apps use the Music Unit only but a few apps also use Unit (0-3) instead or as well. * Set up AHI prefs so that microphone is available. (Input option near the bottom) stereo++ allows the audio piece to be placed anywhere and the left-right adjusted to sound positionally right hifi best for music playback if driver supports this option Load 16bit .aif .aiff only sample(s) to use not AIFC which can have the same ending. AIFF stands for Audio Interchange File Format sox recital.wav recital.aiff sox recital.wav −b 16 recital.aiff channels 1 rate 16k fade 3 norm sox input.wav output.aiff bass −b 16 rate 48k performs the same format translation, but also applies four effects (down-mix to one channel, sample rate change, fade-in, nomalize), and stores the result at a bit-depth of 16. rec −c 2 radio.aiff trim 0 30:00 records half an hour of stereo audio play existing-file.wav 24bit PCM WAV or AIFF do not work *No stream format handling. So no way to pass on an AC3 encoded stream unmodified to the digital outputs through AHI. *No master volume handling. Each application has to set its own volume. So each driver implements its own custom driver-mixer interface for handling master volumes, mute and preamps. *Only one output stream. So all input gets mixed into one output. *No automatic handling of output direction based on connected cables. *No monitor input selection. Only monitor volume control. select the correct input (Don't mistake enabled sound for the correct input.) The monitor will feedback audio to the lineout and hp out no matter if you have selected the correct input to the ADC. The monitor will provide sound for any valid input. This will result in free mixing when recording from the monitor input instead of mic/line because the monitor itself will provide the hardware mixing for you. Be aware that MIC inputs will give two channel mono. Only Linein will give real stereo. Now for the not working part. Attempt to record from linein in the AE4 record window, the right channel is noise and the left channel is distorted. Even with the recommended HIFI 16bit Stereo++ mode at 48kHz. Channels Monitor Gain Inout Output Advanced settings - Debugging via serial port * Options -> Soundcard In/Out * Options -> SampleRate * Options -> Preferences F6 for Sample File List Setting a grid is easy as is measuring the BPM by marking a section of the sample. Is your kick drum track "not in time" ? If so, you're stumped in AE4 as it has no fancy variable time signatures and definitely no 'track this dodgy rhythm' function like software of the nature of Logic has. So if your drum beat is freeform you will need to work in freeform mode. (Real music is free form anyway). If the drum *is* accurate and you are just having trouble measuring the time, I usually measure over a range of bars and set the number of beats in range to say 16 as this is more accurate, Then you will need to shift the drum track to match your grid *before* applying the grid. (probably an iterative process as when the grid is active samples snap to it, and when inactive you cannot see it). AE4 does have ARexx but the functions are more for adding samples at set offsets and starting playback / recording. These are the usual features found in DAWs... * Recording digital audio, midi sequencer and mixer * virtual VST instruments and plug-ins * automation, group channels, MIDI channels, FX sends and returns, audio and MIDI editors and music notation editor * different track views * mixer and track layout (but not the same as below) * traditional two windows (track and mixer) Mixing - mixdown Could not figure out how to select what part I wanted to send to the aux, set it to echo and return. Pretty much the whole echo effect. Or any effect. Take look at page17 of the manual. When you open the EQ / Aux send popup window you will see 4 sends. Now from the menu choose the windows menu. Menus->Windows-> Aux Returns Window or press F5 You will see a small window with 4 volume controls and an effects button for each. Click a button and add an effects to that aux channel, then set it up as desired (note the reverb effect has a special AUX setting that improves its use with the aux channel, not compulsory but highly useful). You set the amount of 'return' on the main mix in the Aux Return window, and the amount sent from each main mixer channel in the popup for that channel. Again the aux sends are "prefade" so the volume faders on each channel do not affect them. Tracking Effects - fade in To add some echoes to some vocals, tried to add an effect on a track but did not come out. This is made more complicated as I wanted to mute a vocal but then make it echo at the muting point. Want to have one word of a vocal heard and then echoed off. But when the track is mute the echo is cancelled out. To correctly understand what is happening here you need to study the figure at the bottom of page 15 on the manual. You will see from that that the effects are applied 'prefade' So the automation you applied will naturally mute the entire signal. There would be a number of ways to achieve the goal, You have three real time effects slots, one for smoothing like so Sample -> Amplify -> Delay Then automate the gain of the amplify block so that it effectively mutes the sample just before the delay at the appropriate moment, the echo effect should then be heard. Getting the effects in the right order will require experimentation as they can only be added top down and it's not obvious which order they are applied to the signal, but there only two possibilities, so it wont take long to find out. Using MUTE can cause clicks to the Amplify can be used to mute more smoothly so that's a secondary advantage. Signal Processing - Overdub [[#top|...to the top]] ===Office=== ====Spreadsheet Leu==== Support for some xlsx, and ods functions ====Spreadsheet Ignition==== ; Needs ABIv1 to be completed before more can be done File formats supported * ascii #?.txt and #?.csv (single sheets with data only). * igs and TurboCalc(WIP) #?.tc for all sheets with data, formats and formulas. There is '''no''' support for xls, xlsx, ods or uos ([http://en.wikipedia.org/wiki/Uniform_Office_Format Uniform Unified Office Format]) at the moment. * Always use Esc key after editing Spreadsheet cells. * copy/paste seems to copy the first instance only so go to Edit -> Clipboard to manage the list of remembered actions. * Right mouse click on row (1 or 2 or 3) or column header (a or b or c) to access optimal height or width of the row or column respectively * Edit -> Insert -> Row seems to clear the spreadsheet or clears the rows after the inserted row until undo restores as it should be... Change Sheet name by Object -> Sheet -> Properties Click in the cell which will contain the result, and click '''down arrow button''' to the right of the formula box at the bottom of the spreadsheet and choose the function required from the list provided. Then click on the start cell and click on the bottom right corner, a '''very''' small blob, which allows stretching a bounding box (thick grey outlines) across many cells This grey bounding box can be used to '''copy a formula''' to other cells. Object -> Cell -> Properties to change cell format - Currency only covers DM and not $, Euro, Renminbi, Yen or Pound etc. Shift key and arrow keys selects a range of cells, so that '''formatting can be done to all highlighted cells'''. View -> Overview then select ALL with one click (in empty cell in the top left hand corner of the sheet). Default mode is relative cell referencing e.g. a1+a2 but absolute e.g. $a$1+$a$2 can be entered. * #sheet-name to '''absolute''' reference another sheet-name cell unless reference() function used. ;Graphs use shift key and arrow keys to select a bunch of cells to be graph'ed making sure that x axes represents and y axes represents * value() - 0 value, 1 percent, 2 date, 3 time, 4 unit ... ;Dates * Excel starts a running count from the 1st Jan 1900 and Ignition starts from 1st Jan 1AD '''(maybe this needs to change)''' Set formatting Object -> Cell -> Properties and put date in days ;Time Set formatting Object -> Cell -> Properties and put time in seconds taken ;Database (to be done by someone else) type - standard, reference (bezug), search criterion (suchkriterium), * select a bunch of cells and Object -> Database -> Define to set Datenbank (database) and Felder (fields not sure how?) * Neu (new) or loschen (delete) to add/remove database headings e.g. Personal, Start Date, Finish Date (one per row?) * Object -> Database -> Index to add fields (felder) like Surname, First Name, Employee ID, etc. to ? Filtering done with dbfilter(), dbproduct() and dbposition(). Activities with dbsum(), dbaverage(), dbmin() and dbmax(). Table sorting - ;Scripts (Arexx) ;Excel(TM) to Ignition - commas ''',''' replaced by semi-colons ''';''' to separate values within functions *SUM(), *AVERAGE(), MAX(), MIN(), INT(), PRODUCT(), MEDIAN(), VAR() becomes Variance(), Percentile(), *IF(), AND, OR, NOT *LEFT(), RIGHT(), MID() becomes MIDDLE(), LEN() becomes LENGTH(), *LOWER() becomes LOWERCASE(), UPPER() becomes UPPERCASE(), * DATE(yyyy,mm,dd) becomes COMPUTEDATE(dd;mm;yyyy), *TODAY(), DAY(),WEEK(), MONTH(),=YEAR(TODAY()), *EOMONTH() becomes MONTHLENGTH(), *NOW() should be date and time becomes time only, SECOND(), MINUTE(), HOUR(), *DBSUM() becomes DSUM(), ;Missing and possibly useful features/functions needed for ignition to have better support of Excel files There is no Merge and Join Text over many cells, no protect and/or freeze row or columns or books but can LOCK sheets, no define bunch of cells as a name, Macros (Arexx?), conditional formatting, no Solver, no Goal Seek, no Format Painter, no AutoFill, no AutoSum function button, no pivot tables, (30 argument limit applies to Excel) *HLOOKUP(), VLOOKUP(), [http://production-scheduling.com/excel-index-function-most-useful/ INDEX(), MATCH()], CHOOSE(), TEXT(), *TRIM(), FIND(), SUBSTITUTE(), CONCATENATE() or &, PROPER(), REPT(), *[https://acingexcel.com/excel-sumproduct-function/ SUMPRODUCT()], ROUND(), ROUNDUP(), *ROUNDDOWN(), COUNT(), COUNTA(), SUMIF(), COUNTIF(), COUNTBLANK(), TRUNC(), *PMT(), PV(), FV(), POWER(), SQRT(), MODE(), TRUE, FALSE, *MODE(), LARGE(), SMALL(), RANK(), STDEV(), *DCOUNT(), DCOUNTA(), WEEKDAY(), ;Excel Keyboard [http://dmcritchie.mvps.org/excel/shortx2k.htm shortcuts needed to aid usability in Ignition] <pre> Ctrl Z - Undo Ctrl D - Fill Down Ctrl R - Fill right Ctrl F - Find Ctrl H - Replace Ctrl 1 - Formatting of Cells CTRL SHIFT ~ Apply General Formatting ie a number Ctrl ; - Todays Date F2 - Edit cell F4 - toggle cell absolute / relative cell references </pre> ====Document Scanning - Scandal==== Scanner usually needs to be connected via a USB port and not via a hub or extension lead. Check in Trident Prefs -> Devices that the USB Scanner is not bound to anything (e.g. Bindings None) If not found then reboot the computer and recheck. Start Scandal, choose Settings from Menu strip at top of screen and in Scanner Driver choose the ?#.device of the scanner (e.g. epson2.device). The next two boxes - leave empty as they are for morphos SCSI use only or put ata.device (use the selection option in bigger box below) and Unit as 0 this is needed for gt68xx * gt68xx - no editing needed in s/gt68xx.conf but needs a firmware file that corresponds to the scanner [http://www.meier-geinitz.de/sane/gt68xx-backend/ gt68xx firmwares] in sys:s/gt68xx. * epson2 - Need to edit the file epson2.conf in sys/s that corresponds to the scanner being used '''Save''' the settings but do not press the Use button (aros freezes) Back to the Picture Scan window and the right-hand sections. Click on the '''Information''' tab and press Connect button and the scanner should now be detected. Go next to the '''Scanner''' tab next to Information Tab should have Color, Black and White, etc. and dpi settings now. Selecting an option Color, B/W etc. can cause dpi settings corruption (especially if the settings are in one line) so set '''dpi first'''. Make sure if Preview is set or not. In the '''Scan''' Tab, press Scan and the scanner will do its duty. Be aware that nothing is saved to disk yet. In the Save tab, change format JPEG, PNG or IFF DEEP. Tick incremental and base filename if necessary and then click the Save button. The image will now be saved to permanent storage. The driver ignores a device if it is already bond to another USB class, rejects it from being usable. However, open Trident prefs, select your device and use the right mouse button to open. Select "NONE" to prevent poseidon from touching the device. Now save settings. It should always work now. [[#top|...to the top]] ===Emulators=== ==== Amiberry ==== ==== Amiga Emu - Janus UAE ==== With Amibridge, AROS attempts to make the UAE emulator seem embedded within but it still is acting as an app There is no dynarec m68k for each hardware that Aros supports or direct patching of motorola calls to AROS hardware accelerated ones unless the emulator has that included Try starting Janus with a priority of -1 like this little script: <pre> cd sys:system/AmiBridge/emulator changetaskpri -1 run janus-uae -f my_uaerc.config >nil: cd sys:prefs endcli </pre> This stops Janus hogging all the CPU time. ===Miscellaneous=== ====Screensaver Blanker==== Most blankers on the amiga (i.e. aros) run as commodities (they are in the tools/commodities drawer). Double click on blanker. Control is with an app called Exchange, which you need to run first (double click on app) or run QUIET sys:tools/commodities/Exchange >NIL: but subsequently can use (Cntrl Alt h). Icon tool types (may be broken) or command line options <pre> seconds=number </pre> Once the timing is right then add the following to s:icaros-sequence or s:user-startup e.g. for 5 minutes run QUIET sys:tools/commodities/Blanker seconds=300 >NIL: *[http://archives.aros-exec.org/index.php?function=showfile&file=graphics/screenblanker/gblanker.i386-aros.zip Garshneblanker] can make Aros unstable or slow. Certain blankers crashes in Icaros 2.0.x like Dragon, Executor. *[ Acuario AROS version], the aquarium screen saver. Startup: extras:acuariofv-aros/acuario Kill: c:break name=extras:acuariofv-aros/acuario Managed to start Acuario by the Executor blanker. <pre> cx_priority= cx_popkey= ie CX_POPKEY="Shift F1" cx_popup=Yes or No </pre> <pre> Qualifier String Input Event Class ---------------- ----------------- "lshift" IEQUALIFIER_LSHIFT "rshift" IEQUALIFIER_RSHIFT "capslock" IEQUALIFIER_CAPSLOCK "control" IEQUALIFIER_CONTROL "lalt" IEQUALIFIER_LALT "ralt" IEQUALIFIER_RALT "lcommand" IEQUALIFIER_LCOMMAND "rcommand" IEQUALIFIER_RCOMMAND "numericpad" IEQUALIFIER_NUMERICPAD "repeat" IEQUALIFIER_REPEAT "midbutton" IEQUALIFIER_MIDBUTTON "rbutton" IEQUALIFIER_RBUTTON "leftbutton" IEQUALIFIER_LEFTBUTTON "relativemouse" IEQUALIFIER_RELATIVEMOUSE </pre> <pre> Synonym Synonym String Identifier ------- ---------- "shift" IXSYM_SHIFT /* look for either shift key */ "caps" IXSYM_CAPS /* look for either shift key or capslock */ "alt" IXSYM_ALT /* look for either alt key */ Highmap is one of the following strings: "space", "backspace", "tab", "enter", "return", "esc", "del", "up", "down", "right", "left", "f1", "f2", "f3", "f4", "f5", "f6", "f7", "f8", "f9", "f10", "help". </pre> [[#top|...to the top]] ==== World Construction Set WCS (Version 2.031) ==== WCS is a fractal landscape software such as Scenery Animator, Vista Pro and Panorama. Open sourced February 2022, World Construction Set [https://3dnature.com/downloads/legacy-software/ legally and for free] and [https://github.com/AlphaPixel/3DNature c source]. Announced August 1994 this version dates from April 1996 developed by Gary R. Huber and Chris "Xenon" Hanson" from Questar <pre> Assign "WCSProjects:" "Volume:Dir/Dir/WCSProjects" Assign "WCSFrames:" "Volume:Dir/Dir/WCSFrames" </pre> <pre> Load projects .proj by accessing pull down menu Project -> Open then click on CanyonSunset.proj OK to changing .par file and enlarge Status Log window to show what is happening Render by pull down menu Modules -> Render with End equal 1 not 300 then click bottom middle button Render </pre> [https://www.youtube.com/watch?v=CxQDmf1ZWG0 Youtube walkthrough of above], [], [], Also try working with the already built file ColoDemo - Then open with the drop-down menu: Project/Open, then WCSProject:ColoDemo.proj Which allows you to use altimetric DEM files already included and Loading scene parameters from ColoDemo.par Once this is done, save everything with a new name to start working exclusively on your project. Then drop-down menu and select Save As ("NewName".proj name), then drop-down menu to open parameter and select Save All ( .par name) After launching the software, there is a the Module Control Panel composed of five icons. It is a dock type shortcut of the first few functions of the drop-down menu *Database - Load (#?.proj), Append, Create, Edit, Save, Dir List (of WCSProject drawer), *Data Ops - Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats *Map View - Database file Loader leading to Map View Control with option to the Database Editor *Parameters - Editor for Motion, Color, Ecosystem, Clouds, Waves, management of altimeter files DEM, sclock settings etc *Render - rendering terrain These are more in the pull down menu but not in the dock *Motion Editor *Color Editor *Ecosys Editor Simple minimal workflow *Load database (1st icon - 1st) *Set parameters and save .par file (4th icon) *Render scene (5th icon) [https://www.youtube.com/watch?v=ZbTwwR2qcc4 Youtube], [], <pre> .proj new project name which creates a drawer of additional files .binary array, ascii array .xyz , z buffer, DTED .dt0, vista 1990s dem, iff conversion .Obj with .elev, .frd with .hdr maps, - digital elevation model (DEM) is a 3D representation of elevation data in various formats USGS 7.5MinDEM, .par </pre> Since for the time being no project is loaded, a query window indicates a procedural error when clicking on the rendering icon (right end of the bar). The menu is quite traditional; it varies according to the activity of the windows. To display any altimetric file in the "Mapview" (third icon of the panel), There are three possibilities: * Loading of a demonstration project. * The import of a DEM file, followed by texturing and packaging from the "Database-Editor" and the "Color-Editor". * The creation of an altimetric file in WCS format, then texturing. The altimeter file editing (display in the menu) is only made possible if the "Mapview" window is active. The software is made up of many windows and won't be able to describe them all. Know that "Color-Editor" and the "Data-Editor" comprise sufficient functions for obtaining an almost real rendering quality. You have the possibility of inserting vector objects in the "Data-Editor" (creation of roads, railways, etc.) The Map View (MapView) window *Database - Objects and Topos *View - Align, Center, Zoom, Pan, Move *Draw - Maps and distance *Object - Find, highlight, add points, conform topo, duplicate *Motion - Camera, Focus, path, elevation *Windows - DEM designer, Cloud (.cld) and wave (.wve) editor, You will notice that by selecting this window and simply moving the pointer to various points on the map you will see latitude and longitude values ​​change, along with the height. Drop-down menu and Modules, then select MapView and change the width of the window with the map to arrange it in the best way on the screen. With the Auto button the center. Window that then displays the contents of my DEM file, in this case the Grand Canyon. MapView allows you to observe the shape of the landscape from above ZOOM button Press the Zoom button and then with the pointer position on a point on the map, press the left mouse button and then move to the opposite corner to circumscribe the chosen area and press the left mouse button again, then we will see the enlarged area selected on the map. Would add that there is a box next to the Zoom button that allows the direct insertion of a value which, the larger it is, the smaller the magnification and the smaller the value, the stronger the magnification. At each numerical change you will need to press the DRAW button to update the view. PAN button Under Zoom you will find the PAN button which allows you to move the map at will in all directions by the amount you want. This is done by drawing a line in one direction, then press PAN and point to an area on the map with the pointer and press the left mouse button. At this point, leave it and move the pointer in one direction by drawing a line and press the left mouse button again to trigger the movement of the map on the screen (origin and end points). Do some experiments and then use the Auto button immediately below to recenter everything. There are parameters such as TOPO, VEC to be left checked and immediately below one that allows different views of the map with the Style command (Single, Multi, Surface, Emboss, Slope, Contour), each with its own particularities to highlight different details. Now you have the first basics to manage your project visually on the map. Close the MapView window and go further... Let's start working on ECOSYSTEMS If we select Emboss from the MapView Style command we will have a clear idea of ​​how the landscape appears, realizing that it is a predominantly desert region of our planet. Therefore we will begin to act on any vegetation present and the appearance of the landscape. With WCS we will begin to break down the elements of the landscape by assigning defined characteristics. It will be necessary to determine the classes of the ecosystem (Class) with parameters of Elevation Line (maximum altitude), Relative Elevation (arrangement on basins or convexities with respectively positive or negative parameters), Min Slope and Max Slope (slope). WCS offers the possibility of making ecosystems coexist on the same terrain with the UnderEco function, by setting a Density value. Ecosys Ecosystem Editor Let's open it from Modules, then Ecosys Editor. In the left pane you will find the list of ecosystems referring to the files present in our project. It will be necessary to clean up that box to leave only the Water and Snow landscapes and a few other predefined ones. We can do this by selecting the items and pressing the Remove button (be careful not for all elements the button is activated, therefore they cannot all be eliminated). Once this is done we can start adding new ecosystems. Scroll through the various Unused and as soon as the Name item at the top is activated allowing you to write, type the name of your ecosystem, adding the necessary parameters. <pre> Ecosystem1: Name: RockBase Class: Rock Density: 80 MinSlope: 15 UnderEco: Terrain Ecosystem2: Name: RockIncl Clss: Rock Density: 80 MinSlope: 30 UnderEco: Terrain Ecosystem3: Name: Grass Class Low Veg Density: 50 Height: 1 Elev Line : 1500 Rel El Eff: 5 Max Slope: 10 – Min Slope: 0 UnderEco: Terrain Ecosistema4: Name: Shrubs Class: Low Veg Density: 40 Height: 8 Elev Line: 3000 Rel El Eff: -2 Max Slope: 20 Min Slope : 5 UnderEco: Terrain Ecosistema5: Name: Terrain Class: Ground Density: 100 UnderEco: Terrain </pre> Now we need to identify an intermediate ecosystem that guarantees a smooth transition between all, therefore we select as Understory Ecosystem the one called Terrain in all ecosystems, except Snow and Water . Now we need to 'emerge' the Colorado River in the Canyon and we can do this by raising the sea level to 900 (Sea Level) in the Ecosystem called Water. Please note that the order of the ecosystem list gives priority to those that come after. So our list must have the following order: Water, Snow, Shrubs, RockIncl, RockBase, Terrain. It is possible to carry out all movements with the Swap button at the bottom. To put order you can also press Short List. Press Keep to confirm all the work done so far with Ecosystem Editor. Remember every now and then to save both the Project 'Modules/Save' and 'Parameter/Save All' EcoModels are made up of .etp .fgp .iff8 for each model Color Editor Now it's time to define the colors of our scene and we can do this by going to Modules and then Color Editor. In the list we focus on our ecosystems, created first. Let's go to the bottom of the list and select the first white space, assigning the name 'empty1', with a color we like and then we will find this element again in other environments... It could serve as an example for other situations! So we move to 'grass' which already exists and assign the following colors: R 60 G 70 B50 <pre> 'shrubs': R 60 G 80 B 30 'RockIncl' R 110 G 65 B 60 'RockBase' R 110 G 80 B 80 ' Terrain' R 150 G 30 B 30 <pre> Now we can work on pre-existing colors <pre> 'SunLight' R 150 G 130 B 130 'Haze and Fog' R 190 G 170 B 170 'Horizon' R 209 G 185 B 190 'Zenith' R 140 G 150 B 200 'Water' R 90 G 125 B 170 </pre> Ambient R 0 G 0 B 0 So don't forget to close Color Editor by pressing Keep. Go once again to Ecosystem Editor and assign the corresponding color to each environment by selecting it using the Ecosystem Color button. Press it several times until the correct one appears. Then save the project and parameters again, as done previously. Motion Editor Now it's time to take care of the framing, so let's go to Modules and then to Motion Editor. An extremely feature-rich window will open. Following is the list of parameters regarding the Camera, position and other characteristics: <pre> -Camera Altitude: 7.0 -Camera Latitude: 36.075 -Camera Longitude: 112.133 -Focus Attitude: -2.0 -Focus Latitude: 36.275 -Focus Longitude: 112.386 -Camera : 512 → rendering window -Camera Y: 384 → rendering window -View Arc: 80 → View width in degrees -Sun Longitude: 172 -Sun Latitude: -0.9 -Haze Start: 3.8 -Haze Range: 78, 5 </pre> As soon as the values ​​shown in the relevant sliders have been modified, we will be ready to open the CamView window to observe the wireframe preview. Let's not consider all the controls that will appear. Well from the Motion Editor if you have selected Camera Altitude and open the CamView panel, you can change the height of the camera by holding down the right mouse button and moving the mouse up and down. To update the view, press the Terrain button in the adjacent window. As soon as you are convinced of the position, confirm again with Keep. You can carry out the same work with the other functions of the camera, such as Focus Altitude... Let's now see the next positioning step on the Camera map, but let's leave the CamView preview window open while we go to Modules to open the window at the same time MapView. We will thus be able to take advantage of the view from the other together with a subjective one. From the MapView window, select with the left mouse button and while it is pressed, move the Camera as desired. To update the subjective preview, always click on Terrain. While with the same procedure you can intervene on the direction of the camera lens, by selecting the cross and with the left button pressed you can choose the desired view. So with the pressure of Terrain I update the Preview. Possibly can enlarge or reduce the Map View using the Zoom button, for greater precision. Also write that the circle around the cameras indicates the beginning of the haze, there are two types (haze and fog) linked to the altitude. Would also add that the camera height is editable through the Motion Editor panel. The sun Let's see that changing the position of the sun from the Motion Editor. Press the SUN button at the bottom right and set the time and the date. Longitude and latitude are automatically obtained by the program. Always open the View Arc command from the Motion Editor panel, an item present in the Parameter List box. Once again confirm everything with Keep and then save again. Animation The animation part is not left-back and also occupies a window. The settings possibilities are enormous. A time line with dragging functions ("slide", "drag"...) comparable to that of LightWave completes this window. A small window is available for positioning the stars as a function of a date, in order to vary the seasons and their various events (and yes...). At the bottom of the "Motion-Editor", a "cam-view" function will give you access to a control panel. Different preview modes are possible. The rendering is also accessible through a window. No less than nine pages compose it. At this level, you will be able to determine the backup name of your images ("path"), the type of texture to be calculated, the resolution of the images, activate or deactivate functions such as the depth buffer ("zbuffer"), the blur, the background image, etc. Once all these parameters have been set, all you have to do is click on the "Render" button. For rendering go to Modules and then Render. Select the resolution, then under IMA select the name of the image. Move to FRA and indicate the level of fractal detail which of 4 is quite good. Then Keep to confirm and then reopen the window, pressing Render you will see the result. The image will be opened with any viewing program. Strengths: * Multi-window. * Quality of rendering. * Accuracy. * Opening, preview and rendering on CyberGraphX screen. * Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats * The "zbuffer" function. Weaknesses: * No OpenGL management * Calculation time. * No network computing tool. ====Writing CD / DVD - Frying Pan==== Can be backup DVDs (4GB ISO size limit due to use of FileInfoBlock), create audio cds from mp3's, and put .iso files on discs If using for the first time - click Drive button and Device set to ata.device and unit to 0 (zero) Click Tracks Button - Drive 1 - Create New Disc or Import Existing Disc Image (iso bin/cue etc.) - Session File open cue file If you're making a data cd, with files and drawers from your hard drive, you should be using the ISO Builder.. which is the MUI page on the left. ("Data/Audio Tracks" is on the right). You should use the "Data/Audio tracks" page if you want to create music cds with AIFF/WAV/MP3 files, or if you download an .iso file, and you want to put it on a cd. Click WRITE Button - set write speed - click on long Write button Examples Easiest way would be to burn a DATA CD, simply go to "Tracks" page "ISO Builder" and "ADD" everything you need to burn. On the "Write" page i have "Masterize Disc (DAO)", "Close Disc" and "Eject after Write" set. One must not "Blank disc before write" if one uses a CDR AUDIO CD from MP3's are as easy but tricky to deal with. FP only understands one MP3 format, Layer II, everything else will just create empty tracks Burning bootable CD's works only with .iso files. Go to "Tracks" page and "Data/Audio Tracks" and add the .iso ====odf==== Every ODF file is a collection of several subdocuments within a package (ZIP file), each of which stores part of the complete document. * content.xml – Document content and automatic styles used in the content. * styles.xml – Styles used in the document content and automatic styles used in the styles themselves. * meta.xml – Document meta information, such as the author or the time of the last save action. * settings.xml – Application-specific settings, such as the window size or printer information. To read document follow these steps: * Extracting .ods file. * Getting content.xml file (which contains sheets data). * Creating XmlDocument object from content.xml file. * Creating DataSet (that represent Spreadsheet file). * With XmlDocument select “table:table” elements, and then create adequate DataTables. * Parse child’s of “table:table” element and fill DataTables with those data. * At the end, return DataSet and show it in application’s interface. To write document follow these steps: * Extracting template.ods file (.ods file that we use as template). * Getting content.xml file. * Creating XmlDocument object from content.xml file. * Erasing all “table:table” elements from the content.xml file. * Reading data from our DataSet and composing adequate “table:table” elements. * Adding “table:table” elements to content.xml file. * Zipping that file as new .ods file. XLS file format The XLS file format contains streams, substreams, and records. These sheet substreams include worksheets, macro sheets, chart sheets, dialog sheets, and VBA module sheets. All the records in an XLS document start with a 2-byte unsigned integer to specify Record Type (rt), and another for Count of Bytes (cb). A record cannot exceed 8224 bytes. If larger than the rest is stored in one or more continue records. * Workbook stream **Globals substream ***BoundSheet8 record - info for Worksheet substream i.e. name, location, type, and visibility. (4bytes the lbPlyPos FilePointer, specifies the position in the Workbook stream where the sheet substream starts) **Worksheet substream (sheet) - Cell Table - Row record - Cells (2byte=row 2byte=column 2byte=XF format) ***Blank cell record ***RK cell record 32-bit number. ***BoolErr cell record (2-byte Bes structure that may be either a Boolean value or an error code) ***Number cell record (64-bit floating-point number) ***LabelSst cell record (4-byte integer that specifies a string in the Shared Strings Table (SST). Specifically, the integer corresponds to the array index in the RGB field of the SST) ***Formula cell record (FormulaValue structure in the 8 bytes that follow the cell structure. The next 6 bytes can be ignored, and the rest of the record is a CellParsedFormula structure that contains the formula itself) ***MulBlank record (first 2 bytes give the row, and the next 2 bytes give the column that the series of blanks starts at. Next, a variable length array of cell structures follows to store formatting information, and the last 2 bytes show what column the series of blanks ends on) ***MulRK record ***Shared String Table (SST) contains all of the string values in the workbook. ACCRINT(), ACCRINTM(), AMORDEGRC(), AMORLINC(), COUPDAYBS(), COUPDAYS(), COUPDAYSNC(), COUPNCD(), COUPNUM(), COUPPCD(), CUMIPMT(), CUMPRINC(), DB(), DDB(), DISC(), DOLLARDE(), DOLLARFR(), DURATION(), EFFECT(), FV(), FVSCHEDULE(), INTRATE(), IPMT(), IRR(), ISPMT(), MDURATION(), MIRR(), NOMINAL(), NPER(), NPV(), ODDFPRICE(), ODDFYIELD(), ODDLPRICE(), ODDLYIELD(), PMT(), PPMT(), PRICE(), PRICEDISC(), PRICEMAT(), PV(), RATE(), RECEIVED(), SLN(), SYD(), TBILLEQ(), TBILLPRICE(), TBILLYIELD(), VDB(), XIRR(), XNPV(), YIELD(), YIELDDISC(), YIELDMAT(), <pre> </pre> <pre> </pre> <pre> </pre> {{BookCat}} 3mr2x812lh3gydnhxo4ja1b26580rdi 0 238420 4634216 4634008 2026-05-05T02:56:37Z Yqj3km 3579825 added a page 4634216 wikitext text/x-wiki __NOTOC__ [[Image:UVa Rotunda.jpg|thumb|196px|right|The Rotunda at The University of Virginia]] ''Lentis: The Social Interface of Technology'' is a guidebook to the realm where technological phenomena and social phenomena intersect. If we think of technology and society as circular domains that overlap, the common domain they share is a [[w:Lens (geometry)|lens]] in shape. Hence the short title of the book, ''Lentis,'' which is Latin for "of [or about] the lens." If the title (with its association with [[w:Lens|lenses]]) also suggests means of viewing, of examining, of magnifying, and of discovering, so much the better. The lens-shaped realm is called the "social interface of technology." The chief authors of ''Lentis'' are students at the University of Virginia's School of Engineering and Applied Science. The authors are engineers representing diverse fields of engineering. As a wikibook, ''Lentis'' will accept contributions from authors and editors all over the world, but the student authors will take particular responsibility to produce a complete, well documented, well written and useful book. This is a student project. Until December 20, 2024, would-be contributors who are not students in the class are asked to consider editing sparingly, but are invited to comment freely on discussion pages, where their suggestions and advice will be welcomed and appreciated. No one's right to edit is in question. ''Lentis'' is intended to serve a general purpose and a specific purpose. The general purpose is to present to interested readers worldwide illuminating cases with practical lessons for those who navigate the dangerous channels of the social interface of technology. The book begins with the premise that success in technological and social endeavors often depends upon the skillful negotiation of sociotechnical factors, where technological techniques alone, or social techniques alone, are insufficient. A second premise is that case studies offer generalizable lessons that can guide people who work where technology and society overlap. They are, in effect, "true fables" that offer "morals" of practical value in diverse endeavors. More specifically, ''Lentis'' is a book written by and for engineers. Here the premise is that engineers by definition are problem solvers whose instruments may include social as well as technological tools, whose work ultimately serves non-engineers, and who must therefore inevitably venture into the social interface of technology, where these non-engineers dwell. Too often, engineers have had to leave this territory to managers, policymakers, clients and others who lack the technical expertise for success in this zone. If engineers can develop the social expertise they need at the social interface of technology, they can lead there. If "those who cannot remember the past are condemned to repeat it," then those who recover the past can best lead us out of it. In the history of technology countless technological innovations succeeded until they met the social interface, where social phenomena interact with technological phenomena in surprising ways. This book will be a success if it helps engineers anticipate these effects. Most of the chapters in ''Lentis'' are examinations of cases. The authors will attempt to derive practical lessons from these cases; the most valuable lessons will be generalizable. If a lesson is generalizable, it is applicable in cases and situations that may be far removed in time, space or engineering field. A case from American transportation engineering in the 1990s, for example, may have lessons useful to biomedical engineers in 2024. The authors have endeavored to find such lessons in the cases they investigated. Because social theories are also useful navigational aids in the social interface of technology, some chapters examine such theories. The authors have sought not only to explain these theories, but to show how they can be of practical value. == Table of Contents == === '''Preliminaries''' === * [[/Chapters: Active and Candidates/]] === '''Lentis: The Social Interface of Technology''' === ==== Food and Energy ==== <div style="column-count:3"> * [[Lentis/Public Health, Sugary Drinks, and the US Beverage Lobby|Public Health, Sugary Drinks, and the US Beverage Lobby]] * [[/Biofuels Vs. Food in Developing Countries/]] * [[/Politics of Biofuels/]] * [[/Opposition to GMOs in Europe/]] * [[/Patenting of GM Seeds/]] * [[/Corn, Beef and Feedlots/]] * [[/Dakota Access Pipeline/]] * [[/High-Fructose Corn Syrup/]] * [[/The Organic Foods Movement/]] * [[/Local Food as a Case of Disintermediation/]] * [[/Local Food as a Social Movement/]] * [[/Marketing of Natural Foods/]] * [[/Corn Ethanol in the United States/]] * [[/Popular Perceptions of Nuclear Power/]] * [[/Nuclear Meltdown: Is Nuclear Energy Socially Viable Following the 2011 Japanese Earthquake?/]] * [[/Fracking/]] * [[/Wind Energy/]] * [[/Rare Earth Metals/]] * [[/Carbon Offsets/]] * [[/Clean Coal/]] * [[/Food Waste in the United States/]] * [[/Genetically Modified Food Controversy in the United States/]] *[[/Solar Energy Policy in Germany/]] *[[/Peak Oil/]] *[[/U.S. Arctic Oil Mining/]] *[[/How Energy Companies Rebrand Themselves/]] * [[/Gluten-Free: Nutritional Principle or Social Value/]] *[[/Vegan and Vegetarian Diets: Nutritional and Social Values/]] *[[/Energy from Trash/]] *[[/Life Off the Grid/]] * [[/Soylent/]] * [[/Expansion of Solar Farms in the Rural United States/]] * [[/Urban Farming/]] * [[/Oil Palm Plantations/]] * [[/Golden Rice/]] * [[/Miracle Rice/]] *[[/The Cavendish Banana, Monoculture, and Blight/]] *[[/Atlantic Coast Pipeline/]] * [[/Cooking with Wood Fuel/]] * [[Lentis/Solar Panel Recycling in the United States|Solar Panel Recycling in the United States]] * [[Lentis/Line 3 Pipeline Controversy|Line 3 Pipeline Controversy]] * [[/Data Centers and Energy/]] * [[/Conflicts of Interest in US Nutrition Research/]] </div> ==== Environmental Values and Climate Change ==== <div style="column-count:3"> * [[Lentis/8 House|8 House]] * [[Lentis/Plastic Bags|Plastic Bags]] * [[Lentis/Water Bottles|Water Bottles]] * [[Lentis/Competition for Water in California|Competition for Water in California]] * [[Lentis/Green Roofing|Green Roofing]] * [[Lentis/Hypoxic Zones|Hypoxic Zones]] * [[Lentis/Unnatural Selection: Explaining Strange Pet Breeds|Unnatural Selection: Explaining Strange Pet Breeds]] * [[Lentis/Masdar City|Masdar City]] * [[Lentis/World Trade as an Invasive Species Vector|World Trade as an Invasive Species Vector]] * [[Lentis/Noise pollution|Noise pollution]] * [[Lentis/Ecovillages|Ecovillages]] * [[Lentis/Climate Change Denial|Climate Change Denial]] * [[Lentis/Lawn Care in America: Intensive Agriculture, No Harvest|Lawn Care in America: Intensive Agriculture, No Harvest]] * [[Lentis/Marine Waste|Marine Waste]] * [[Lentis/Gold, Mercury, and Madre de Dios, Peru|Gold, Mercury, and Madre de Dios, Peru]] * [[Lentis/The Amazon Basin Fires of 2019|The Amazon Basin Fires of 2019]] * [[Lentis/Lithium-Ion Batteries in Electric Vehicles|Lithium-Ion Batteries in Electric Vehicles]] * [[Lentis/BedZED|BedZED]] * [[Lentis/Small Island Countries and Sea Level Rise|Small Island Countries and Sea Level Rise]] * [[Lentis/Light pollution|Light pollution]] * [[Lentis/The 2020 Western Wildfire Season in the U.S.|The 2020 Western Wildfire Season in the U.S.]] * [[Lentis/les Zadistes|les Zadistes]] *[[/Flight Shaming/]] *[[/Ecological Implications of Commercial Marine Fishing/]] *[[/Zero-Plastic Retailing/]] *[[/The PFAS Controversy/]] </div> ==== Health and Medicine ==== <div style="column-count:3"> * [[Lentis/Insurance Companies’ Influence in US Health Policy|Insurance Companies’ Influence in US Health Policy]] * [[Lentis/The Ebola Outbreak of 2014|The Ebola Outbreak of 2014]] * [[AI & Medical Imaging]] * [[Antimicrobial Agents in Consumer Products]] * [[Mental Health as a Pharmacological Growth Market]] * [[/Nicotine Addictions/]] * [[/Thinking Small: Appropriate Technology for Developing Countries/]] * [[/Water Supply, Sanitation, and Public Health in Haiti/]] * [[/Fluoridation/]] * [[/Medicine and Disgust/]] * [[/Popular Hygiene: Perceptions and Practices/]] * [[/Bedside Manner in the High-Tech Hospital/]] * [[/Technology and Quality of Life for the Terminally Ill/]] * [[/Ellie, the Microsoft Kinect, and Psychotherapy/]] * [[/Chatbots as Therapists/]] * [[/Placebos/]] * [[/Baby Formula/]] * [[/Sick Building Syndrome/]] * [[/Football and Concussions/]] * [[/The Dietary and Bodybuilding Supplement Industry in the United States /|The Dietary and Bodybuilding Supplement Industry in the United States]] * [[/Obesity and Diets in Economic Classes in the United States/]] * [[/Steroids and Baseball/]] * [[/Nanotechnology and Health/]] * [[/Dissociative Identity Disorder (Multiple Personality Disorder)/]] * [[/Malaria and Mosquito Nets/]] * [[/International Air Travel as a Disease Vector/]] * [[/Social Resistance to Vaccination: Thiomersal and Autism/]] * [[/Religious Opposition to Vaccination/]] * [[/Physician-Assisted Suicide/]] * [[/Power Balance, Magnetic Bracelets and Other Strange Cures/]] * [[/The D.A.R.E. Program/]] * [[/Social Obstacles to Public Health in Developing Countries/]] * [[/Athletes, Superstition, and Performance/]] * [[/Gattaca Revisited/]] * [[/Artificial Wombs/]] * [[/The Weight Loss Industry in the United States/]] * [[/Direct-to-Consumer Personal Genomics/]] * [[/Vaping/]] * [[/Neuroprosthetics/]] * [[/Detoxing as a Social Phenomenon/]] * [[/Antibiotics in India/]] * [[/Public Health: Fear Appeals vs Self-Efficacy and Social Norms Campaigns/]] * [[/Public Health Responds to Physical Inactivity/]] * [[/Mobility and Access for the Disabled/]] * [[/Power Lines and Public Health/]] * [[/The HPV Vaccine/]] * [[/Medication Overload/]] * [[/The 2020 Pandemic Response in Italy/]] * [[/Healthcare in U.S. Prisons/]] * [[/Antimaskers in the U.S. during the 2020 Pandemic/]] * [[/Pain Scales/]] * [[/Augmented Reality in Medicine/]] * [[/COVID-19 Vaccine Distribution/]] * [[/Chloramination of Drinking Water/]] * [[/Manual Water Collection in Developing Countries/]] * [[/The U.S. Pandemic Response: Influenza, 1918-1919/]] * [[/Robotic Pets for Psychosocial Therapeutics/]] * [[/Caffeine Addiction/]] * [[/The Cultural Politics of Obesity Drugs in the US/]] * [[/Pharma’s influence in FDA/]] </div> ==== Mobility and Land Use ==== <div style="column-count:3"> * [[/Cascadia Earthquake Preparation/]] * [[/Bicyclists in Cities/]] * [[/Drivers’ and Bicyclists’ Perceptions of Each Other/]] * [[/American Automobility and the Car Counter-Culture/]] * [[/Congestion Pricing/]] * [[/Urban Sprawl/]] * [[/Planned Communities/]] * [[/Slugging/]] * [[/Bicycling in the Netherlands/]] * [[/Tata Nano and Mobility in India/]] * [[/How Cars Became Dining Rooms: Drive-Thrus, Cupholders and American Culture/]] * [[/Autonomous Vehicles/]] * [[/The Disappearing American Streetcar/]] * [[/Pedestrians and Walkability in Cities and Suburbs/]] * [[/Real-time Ridesharing/]] * [[/Hitchhiking in the Digital Age /]] * [[/Arcology/]] * [[/Lowriding/]] * [[/California High Speed Rail/]] * [[/Self-Driving Cars/]] * [[/The Future of U.S. Civil Aviation in 1945/]] * [[/Road Rage/]] * [[/The Ogallala Aquifer/]] * [[/Rail in America/]] * [[/The Belt and Road Initiative/]] * [[/Car Dependency in the U.S./]] * [[/Guerrilla Urbanism/]] *[[/The Transformation of Times Square/]] *[[/David Engwicht and Street Reclaiming/]] *[[/Vision Zero/]] *[[/Shared Space and Woonerven/]] *[[/Eyjafjallajökull 2010/]] *[[Lentis/Driving Speed Enforcement|Driving Speed Enforcement]] *[[/E-bikes and Personal Mobility/]] *[[Lentis/Zoning Laws in the United States|Zoning Laws in the United States]] *[[Lentis/Carpooling|Carpooling]] *[[The Politics of Electric Vehicle Subsidies]] *[[Lentis/Freeway Removal Movements in US Cities|Freeway Removal Movements in US Cities]] *[[/New Urbanism/]] *Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad </div> ==== Computers and the Internet ==== <div style="column-count:3"> * [[/AI: More Human Than You Think/]] * [[/Antipiracy/]] * [[/Amazon and the Ecommerce Evolution/]] * [[/Compulsive Connectivity/]] * [[/Screen-Free Child Rearing/]] * [[/Crowdsourcing Higher Education/]] * [[/Cryptocurrency/]] * [[/"Data is the new oil"/]] * [[/Deepfakes/]] * [[/Fake Users/]] * [[/Hacker Culture/]] * [[/Human Flesh Search Engine/]] * [[/Social Engineering/]] * [[/Internet Memes/]] * [[/Internet Subcultures/]] * [[/The Open-Source Movement/]] * [[/Electronic Voting/]] * [[/Online Consumer Reviews/]] * [[/Online Dating Scams/]] * [[/Online Shopping/]] * [[/Online Reputation Management/]] * [[/Online Recruitment by Extremist Groups/]] * [[/Peer-to-Peer Media Sharing/]] * [[/Program and High Frequency Trading/]] * [[/Social Networks/]] * [[/Social Media and the Arab Spring/]] * [[/Social Norms in Virtual Worlds/]] * [[/Software Journalism: When Programs Write the News/]] * [[/Street View/]] * [[/Second Life/]] * [[/User-Generated Content in the Internet Age/]] * [[/password1234: Internet Security and Password Culture/]] * [[/Reddit: Anonymity and Social Norms/]] * [[/Wikipedia/]] * [[/Cyber-Attacks on Cyber-Physical Systems/]] * [[/Cyberterrorism and Cyberwarfare/]] * [[/Mass Collaboration/]] * [[/Net Neutrality/]] * [[/Mass Control of a Single Gamer/]] * [[/Harmonious Society: Internet Censorship in China/]] * [[/Web Induced Risk Taking/]] * [[/Where It Goes: Electronic Waste and Salvage/]] * [[/Working Conditions at Apple Hardware Factories in China/]] * [[/Facebook Cheating/]] * [[/Intellectual Property in the Internet Age/]] * [[/The Social Psychology of YouTube/]] * [[/Learning from a Distance/]] *[[Communication Technology and Interpersonal Relationships]] * [[/Identity Theft/]] * [[/Higher Education Online/]] * [[/The Culture of Instagram/]] * [[/New Media and the United States Presidential Election of 2008/]] * [[/Targeted Advertising/]] * [[/Viral Marketing/]] * [[/Web Tracking/]] * [[/Internet Anonymity/]] * [[/The Culture of Snapchat/]] * [[/Snopes, PolitiFact, and Other Fact-Checking Websites/]] * [[/Twitter and other social networks in the Iranian protests of 2009/]] * [[/The Internet Strategy of White Supremacists/]] * [[/Google Translate|Google Translate]] * [[/The Deep Web/]] * [[/Social Media Mining/]] * [[/Internet Witch Hunts/]] * [[/News Echo Chambers/]] * [[/Featuritis/]] * [[/Content Moderation/]] * [[/Virtual Reality/]] * [[/Social Media Shaming Campaigns/]] * [[Lentis/The Geopolitics of TikTok|The Geopolitics of TikTok]] * [[/AI Music, Creativity, and Intellectual Property/]] * [[/Texting in Japan/]] * [[/Social Media Influencers and Public Health/]] </div> ==== Portable Electronics ==== <div style="column-count:3"> * [[Lentis/Smartphones and Cognitive Offloading|Smartphones and Cognitive Offloading]] * [[Cell Phones and Cancer in Britain]] * [[/Driving while Texting/]] * [[/GPS and Driving/]] * [[/Sociology of Texting/]] * [[/The Text Effect/]] * [[/Norms of Handheld Device Use/]] * [[/Happy Slapping/]] * [[/The Walkman Effect/]] * [[/Electronically Enabled Test Cheating/]] * [[/Cell Phones versus Face-to-Face Interaction/]] * [[/Children and Cell Phones/]] * [[/Amazon, E-readers and the Future of the Publishing Industry/]] * [[/Social Aspects of Cell Phone Cameras/]] * [[/Airline Passengers and Portable Electronics/]] * [[/Pokémon Go/]] * [[/Phone Cinematography/]] * [[/Cell Phones in Developing Countries/]] * [[/Wearable Activity Trackers/]] * [[/Handheld Electronics in South Korean Society/]] * [[/The Looking Glass/]] </div> ==== Entertainment and Media ==== <div style="column-count:3"> * [[/Massively Multiplayer Online Role-Playing Games/]] * [[/Gambling/]] * [[/Game Addictions/]] * [[/The Psychology and Technology of Game Immersion/]] * [[/The Proliferation of Music Production Capability/]] * [[/Grand Theft Auto: Violent Video Games and Controversy/]] * [[/Doom: Violent Video Games and Controversy/]] * [[/Implementation of Technology in Sports: Historical Successes and Failures, and Modern Discussion/]] * [[/Portrayal of Women in Video Games/]] * [[/Children,Video Games and Obesity/]] * [[/Electronic Sports (eSports)/]] * [[/Electronic Music Popular/]] * [[/From Cronkite to Stewart: TV News during and after Network Hegemony/]] * [[/The Impact of Fans on Technological Innovation in the NFL/]] * [[/Gold Farming/]] * [[/Jackass: Media Driven Risk Propagation/]] * [[/Anti-TV Social Movements/]] * [[/Media Format Wars/]] * [[/Microtransactions in Videogames/]] * [[/Moe Anthropomorphism/]] * [[/Hello Kitty: Identity Crisis, Kawaii Culture, and More/]] * [[/Technology and Conventional Norms of Personal Beauty/]] * [[/Dance Dance Revolution/]] * [[/Super Smash Bros./]] * [[/Twitch/]] * [[/Instant Replay in International Soccer/]] * [[/Among Us: Social Behavior in a Virtual World/]] * [[Lentis/TikTok|TikTok]] </div> ==== Security, Official Violence, Freedom, Privacy ==== <div style="column-count:3"> * [[/JEDI Cloud/]] * [[/Digital Rights Management/]] * [[/Military Industrial Complex/]] * [[/Tasers and Stun Guns/]] * [[/Probation Technology/]] * [[/International Drug Trafficking and Law Enforcement/]] * [[/Air Travel Security/]] * [[/The United States - Mexico Border/]] * [[/Recording Police Activity/]] * [[/Video Surveillance/]] * [[/Shopkeepers and Shoplifters: Technology and the Changing Balance of Power/]] * [[/Cell Phones in Prison/]] * [[/Cell Phone Jamming in the United States/]] * [[/Freedom of Information: WikiLeaks/]] * [[/Playing Games at Work: Employees versus Employers, Surveillance and Stealth/]] * [[/Cyberslacking/]] * [[/Mashups and Remixes: Between Creativity and Theft/]] * [[/Video Surveillance in Great Britain/]] * [[/Technology and Incarceration in the United States/]] * [[/Additive Manufacturing/]] * [[/Law Enforcement Access to Encrypted Data/]] * [[/Amateurs with Drones/]] * [[/Body Cameras/]] * [[/Human Terrain System: Military Meets Cultural Mindfulness/]] * [[/Law Enforcement and Social Media/]] * [[/Cyber-attack Attribution/]] * [[/China’s Social Credit System/]] * [[/Technology in the 2019 Hong Kong Protests/]] * [[/8chan/]] * [[/Lockheed Martin F-35/]] * [[/Drone Warfare/]] *[[/Capital Punishment in the United States/]] * [[/The Yellow Vests Movement/]] * [[Lentis/The 2018 U.S. Prison Strike|The 2018 U.S. Prison Strike]] * [[Lentis/Office Productivity in the Changing Workplace|Office Productivity in the Changing Workplace]] * [[Lentis/The Geopolitics of Asymmetric War: The Case of Ukraine|The Geopolitics of Asymmetric War: The Case of Ukraine]] </div> ==== Systemic Racism in the U.S. ==== <div style="column-count:3"> * [[/Gentrification/]] * [[/Predictive Policing/]] *[[The Prison-Industrial Complex]] *[[/The War on Drugs/]] *[[Lentis/Algorithmic Bias|Algorithmic Bias]] *[[Lentis/The School to Prison Pipeline|The School to Prison Pipeline]] *[[Lentis/TheHBCURenaissance|The HBCU Renaissance]] </div> ==== Technology and Gender ==== * [[Lentis/Algorithmic_bias_by_gender|Algorithmic Bias by Gender]] ==== History of Technology ==== <div style="column-count:3"> * [[The Decline of Public Transport in the U.S., 1945-1975]] * [[/The Pill, the Vatican, and American Catholics/]] * [[/Education and the Space Race in the United States/]] * [[/Technology, Organized Crime, and Law Enforcement in the early 20th-Century United States/]] * [[/Disease Prevention in the First World War/]] * [[/Atomic Age Optimism: 1930s - 1960s/]] * [[/Abortion in America as a Sociotechnical Controversy/]] * [[/Phreaking/]] * [[/Rachel Carson, Silent Spring, and the Development of Environmental Values, 1950-1970/]] *[[/The Legacy of the Donora Smog of 1946/]] *[[/COINTELPRO: The FBI, Civil Rights, and Domestic Surveillance/]] </div> ==== Sociotechnical Theories and Movements ==== <div style="column-count:3"> * [[Lentis/Protection Motivation Theory|Protection Motivation Theory]] * [[/The Singularity/]] * [[/Conversion to the Metric Standard in the United States/]] * [[/Disintermediation/]] * [[/Jevons Paradox/]] * [[/Path Dependence/]] * [[/Neoluddism and Technophilia/]] * [[/Emergent Behavior/]] * [[/Free Range Kids/|Free Range Kids: Children's Independent Mobility]] * [[/User Trust/]] * [[/The Panopticon/]] * [[/Planned Obsolescence/]] * [[/Fake News/]] *[[/Iron Triangles in the U.S. Federal Government/]] *[[/Risk Compensation/]] </div> {{BookCat}} {{Shelves|general engineering|Class projects}} {{alphabetical|L}} {{status|100%}} fx0iql8zuoflqlqhp07r0b7m7gn1k2x 4634217 4634216 2026-05-05T02:57:35Z Yqj3km 3579825 added link to article 4634217 wikitext text/x-wiki __NOTOC__ [[Image:UVa Rotunda.jpg|thumb|196px|right|The Rotunda at The University of Virginia]] ''Lentis: The Social Interface of Technology'' is a guidebook to the realm where technological phenomena and social phenomena intersect. If we think of technology and society as circular domains that overlap, the common domain they share is a [[w:Lens (geometry)|lens]] in shape. Hence the short title of the book, ''Lentis,'' which is Latin for "of [or about] the lens." If the title (with its association with [[w:Lens|lenses]]) also suggests means of viewing, of examining, of magnifying, and of discovering, so much the better. The lens-shaped realm is called the "social interface of technology." The chief authors of ''Lentis'' are students at the University of Virginia's School of Engineering and Applied Science. The authors are engineers representing diverse fields of engineering. As a wikibook, ''Lentis'' will accept contributions from authors and editors all over the world, but the student authors will take particular responsibility to produce a complete, well documented, well written and useful book. This is a student project. Until December 20, 2024, would-be contributors who are not students in the class are asked to consider editing sparingly, but are invited to comment freely on discussion pages, where their suggestions and advice will be welcomed and appreciated. No one's right to edit is in question. ''Lentis'' is intended to serve a general purpose and a specific purpose. The general purpose is to present to interested readers worldwide illuminating cases with practical lessons for those who navigate the dangerous channels of the social interface of technology. The book begins with the premise that success in technological and social endeavors often depends upon the skillful negotiation of sociotechnical factors, where technological techniques alone, or social techniques alone, are insufficient. A second premise is that case studies offer generalizable lessons that can guide people who work where technology and society overlap. They are, in effect, "true fables" that offer "morals" of practical value in diverse endeavors. More specifically, ''Lentis'' is a book written by and for engineers. Here the premise is that engineers by definition are problem solvers whose instruments may include social as well as technological tools, whose work ultimately serves non-engineers, and who must therefore inevitably venture into the social interface of technology, where these non-engineers dwell. Too often, engineers have had to leave this territory to managers, policymakers, clients and others who lack the technical expertise for success in this zone. If engineers can develop the social expertise they need at the social interface of technology, they can lead there. If "those who cannot remember the past are condemned to repeat it," then those who recover the past can best lead us out of it. In the history of technology countless technological innovations succeeded until they met the social interface, where social phenomena interact with technological phenomena in surprising ways. This book will be a success if it helps engineers anticipate these effects. Most of the chapters in ''Lentis'' are examinations of cases. The authors will attempt to derive practical lessons from these cases; the most valuable lessons will be generalizable. If a lesson is generalizable, it is applicable in cases and situations that may be far removed in time, space or engineering field. A case from American transportation engineering in the 1990s, for example, may have lessons useful to biomedical engineers in 2024. The authors have endeavored to find such lessons in the cases they investigated. Because social theories are also useful navigational aids in the social interface of technology, some chapters examine such theories. The authors have sought not only to explain these theories, but to show how they can be of practical value. == Table of Contents == === '''Preliminaries''' === * [[/Chapters: Active and Candidates/]] === '''Lentis: The Social Interface of Technology''' === ==== Food and Energy ==== <div style="column-count:3"> * [[Lentis/Public Health, Sugary Drinks, and the US Beverage Lobby|Public Health, Sugary Drinks, and the US Beverage Lobby]] * [[/Biofuels Vs. Food in Developing Countries/]] * [[/Politics of Biofuels/]] * [[/Opposition to GMOs in Europe/]] * [[/Patenting of GM Seeds/]] * [[/Corn, Beef and Feedlots/]] * [[/Dakota Access Pipeline/]] * [[/High-Fructose Corn Syrup/]] * [[/The Organic Foods Movement/]] * [[/Local Food as a Case of Disintermediation/]] * [[/Local Food as a Social Movement/]] * [[/Marketing of Natural Foods/]] * [[/Corn Ethanol in the United States/]] * [[/Popular Perceptions of Nuclear Power/]] * [[/Nuclear Meltdown: Is Nuclear Energy Socially Viable Following the 2011 Japanese Earthquake?/]] * [[/Fracking/]] * [[/Wind Energy/]] * [[/Rare Earth Metals/]] * [[/Carbon Offsets/]] * [[/Clean Coal/]] * [[/Food Waste in the United States/]] * [[/Genetically Modified Food Controversy in the United States/]] *[[/Solar Energy Policy in Germany/]] *[[/Peak Oil/]] *[[/U.S. Arctic Oil Mining/]] *[[/How Energy Companies Rebrand Themselves/]] * [[/Gluten-Free: Nutritional Principle or Social Value/]] *[[/Vegan and Vegetarian Diets: Nutritional and Social Values/]] *[[/Energy from Trash/]] *[[/Life Off the Grid/]] * [[/Soylent/]] * [[/Expansion of Solar Farms in the Rural United States/]] * [[/Urban Farming/]] * [[/Oil Palm Plantations/]] * [[/Golden Rice/]] * [[/Miracle Rice/]] *[[/The Cavendish Banana, Monoculture, and Blight/]] *[[/Atlantic Coast Pipeline/]] * [[/Cooking with Wood Fuel/]] * [[Lentis/Solar Panel Recycling in the United States|Solar Panel Recycling in the United States]] * [[Lentis/Line 3 Pipeline Controversy|Line 3 Pipeline Controversy]] * [[/Data Centers and Energy/]] * [[/Conflicts of Interest in US Nutrition Research/]] </div> ==== Environmental Values and Climate Change ==== <div style="column-count:3"> * [[Lentis/8 House|8 House]] * [[Lentis/Plastic Bags|Plastic Bags]] * [[Lentis/Water Bottles|Water Bottles]] * [[Lentis/Competition for Water in California|Competition for Water in California]] * [[Lentis/Green Roofing|Green Roofing]] * [[Lentis/Hypoxic Zones|Hypoxic Zones]] * [[Lentis/Unnatural Selection: Explaining Strange Pet Breeds|Unnatural Selection: Explaining Strange Pet Breeds]] * [[Lentis/Masdar City|Masdar City]] * [[Lentis/World Trade as an Invasive Species Vector|World Trade as an Invasive Species Vector]] * [[Lentis/Noise pollution|Noise pollution]] * [[Lentis/Ecovillages|Ecovillages]] * [[Lentis/Climate Change Denial|Climate Change Denial]] * [[Lentis/Lawn Care in America: Intensive Agriculture, No Harvest|Lawn Care in America: Intensive Agriculture, No Harvest]] * [[Lentis/Marine Waste|Marine Waste]] * [[Lentis/Gold, Mercury, and Madre de Dios, Peru|Gold, Mercury, and Madre de Dios, Peru]] * [[Lentis/The Amazon Basin Fires of 2019|The Amazon Basin Fires of 2019]] * [[Lentis/Lithium-Ion Batteries in Electric Vehicles|Lithium-Ion Batteries in Electric Vehicles]] * [[Lentis/BedZED|BedZED]] * [[Lentis/Small Island Countries and Sea Level Rise|Small Island Countries and Sea Level Rise]] * [[Lentis/Light pollution|Light pollution]] * [[Lentis/The 2020 Western Wildfire Season in the U.S.|The 2020 Western Wildfire Season in the U.S.]] * [[Lentis/les Zadistes|les Zadistes]] *[[/Flight Shaming/]] *[[/Ecological Implications of Commercial Marine Fishing/]] *[[/Zero-Plastic Retailing/]] *[[/The PFAS Controversy/]] </div> ==== Health and Medicine ==== <div style="column-count:3"> * [[Lentis/Insurance Companies’ Influence in US Health Policy|Insurance Companies’ Influence in US Health Policy]] * [[Lentis/The Ebola Outbreak of 2014|The Ebola Outbreak of 2014]] * [[AI & Medical Imaging]] * [[Antimicrobial Agents in Consumer Products]] * [[Mental Health as a Pharmacological Growth Market]] * [[/Nicotine Addictions/]] * [[/Thinking Small: Appropriate Technology for Developing Countries/]] * [[/Water Supply, Sanitation, and Public Health in Haiti/]] * [[/Fluoridation/]] * [[/Medicine and Disgust/]] * [[/Popular Hygiene: Perceptions and Practices/]] * [[/Bedside Manner in the High-Tech Hospital/]] * [[/Technology and Quality of Life for the Terminally Ill/]] * [[/Ellie, the Microsoft Kinect, and Psychotherapy/]] * [[/Chatbots as Therapists/]] * [[/Placebos/]] * [[/Baby Formula/]] * [[/Sick Building Syndrome/]] * [[/Football and Concussions/]] * [[/The Dietary and Bodybuilding Supplement Industry in the United States /|The Dietary and Bodybuilding Supplement Industry in the United States]] * [[/Obesity and Diets in Economic Classes in the United States/]] * [[/Steroids and Baseball/]] * [[/Nanotechnology and Health/]] * [[/Dissociative Identity Disorder (Multiple Personality Disorder)/]] * [[/Malaria and Mosquito Nets/]] * [[/International Air Travel as a Disease Vector/]] * [[/Social Resistance to Vaccination: Thiomersal and Autism/]] * [[/Religious Opposition to Vaccination/]] * [[/Physician-Assisted Suicide/]] * [[/Power Balance, Magnetic Bracelets and Other Strange Cures/]] * [[/The D.A.R.E. Program/]] * [[/Social Obstacles to Public Health in Developing Countries/]] * [[/Athletes, Superstition, and Performance/]] * [[/Gattaca Revisited/]] * [[/Artificial Wombs/]] * [[/The Weight Loss Industry in the United States/]] * [[/Direct-to-Consumer Personal Genomics/]] * [[/Vaping/]] * [[/Neuroprosthetics/]] * [[/Detoxing as a Social Phenomenon/]] * [[/Antibiotics in India/]] * [[/Public Health: Fear Appeals vs Self-Efficacy and Social Norms Campaigns/]] * [[/Public Health Responds to Physical Inactivity/]] * [[/Mobility and Access for the Disabled/]] * [[/Power Lines and Public Health/]] * [[/The HPV Vaccine/]] * [[/Medication Overload/]] * [[/The 2020 Pandemic Response in Italy/]] * [[/Healthcare in U.S. Prisons/]] * [[/Antimaskers in the U.S. during the 2020 Pandemic/]] * [[/Pain Scales/]] * [[/Augmented Reality in Medicine/]] * [[/COVID-19 Vaccine Distribution/]] * [[/Chloramination of Drinking Water/]] * [[/Manual Water Collection in Developing Countries/]] * [[/The U.S. Pandemic Response: Influenza, 1918-1919/]] * [[/Robotic Pets for Psychosocial Therapeutics/]] * [[/Caffeine Addiction/]] * [[/The Cultural Politics of Obesity Drugs in the US/]] * [[/Pharma’s influence in FDA/]] </div> ==== Mobility and Land Use ==== <div style="column-count:3"> * [[/Cascadia Earthquake Preparation/]] * [[/Bicyclists in Cities/]] * [[/Drivers’ and Bicyclists’ Perceptions of Each Other/]] * [[/American Automobility and the Car Counter-Culture/]] * [[/Congestion Pricing/]] * [[/Urban Sprawl/]] * [[/Planned Communities/]] * [[/Slugging/]] * [[/Bicycling in the Netherlands/]] * [[/Tata Nano and Mobility in India/]] * [[/How Cars Became Dining Rooms: Drive-Thrus, Cupholders and American Culture/]] * [[/Autonomous Vehicles/]] * [[/The Disappearing American Streetcar/]] * [[/Pedestrians and Walkability in Cities and Suburbs/]] * [[/Real-time Ridesharing/]] * [[/Hitchhiking in the Digital Age /]] * [[/Arcology/]] * [[/Lowriding/]] * [[/California High Speed Rail/]] * [[/Self-Driving Cars/]] * [[/The Future of U.S. Civil Aviation in 1945/]] * [[/Road Rage/]] * [[/The Ogallala Aquifer/]] * [[/Rail in America/]] * [[/The Belt and Road Initiative/]] * [[/Car Dependency in the U.S./]] * [[/Guerrilla Urbanism/]] *[[/The Transformation of Times Square/]] *[[/David Engwicht and Street Reclaiming/]] *[[/Vision Zero/]] *[[/Shared Space and Woonerven/]] *[[/Eyjafjallajökull 2010/]] *[[Lentis/Driving Speed Enforcement|Driving Speed Enforcement]] *[[/E-bikes and Personal Mobility/]] *[[Lentis/Zoning Laws in the United States|Zoning Laws in the United States]] *[[Lentis/Carpooling|Carpooling]] *[[The Politics of Electric Vehicle Subsidies]] *[[Lentis/Freeway Removal Movements in US Cities|Freeway Removal Movements in US Cities]] *[[/New Urbanism/]] *[[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad|Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]] </div> ==== Computers and the Internet ==== <div style="column-count:3"> * [[/AI: More Human Than You Think/]] * [[/Antipiracy/]] * [[/Amazon and the Ecommerce Evolution/]] * [[/Compulsive Connectivity/]] * [[/Screen-Free Child Rearing/]] * [[/Crowdsourcing Higher Education/]] * [[/Cryptocurrency/]] * [[/"Data is the new oil"/]] * [[/Deepfakes/]] * [[/Fake Users/]] * [[/Hacker Culture/]] * [[/Human Flesh Search Engine/]] * [[/Social Engineering/]] * [[/Internet Memes/]] * [[/Internet Subcultures/]] * [[/The Open-Source Movement/]] * [[/Electronic Voting/]] * [[/Online Consumer Reviews/]] * [[/Online Dating Scams/]] * [[/Online Shopping/]] * [[/Online Reputation Management/]] * [[/Online Recruitment by Extremist Groups/]] * [[/Peer-to-Peer Media Sharing/]] * [[/Program and High Frequency Trading/]] * [[/Social Networks/]] * [[/Social Media and the Arab Spring/]] * [[/Social Norms in Virtual Worlds/]] * [[/Software Journalism: When Programs Write the News/]] * [[/Street View/]] * [[/Second Life/]] * [[/User-Generated Content in the Internet Age/]] * [[/password1234: Internet Security and Password Culture/]] * [[/Reddit: Anonymity and Social Norms/]] * [[/Wikipedia/]] * [[/Cyber-Attacks on Cyber-Physical Systems/]] * [[/Cyberterrorism and Cyberwarfare/]] * [[/Mass Collaboration/]] * [[/Net Neutrality/]] * [[/Mass Control of a Single Gamer/]] * [[/Harmonious Society: Internet Censorship in China/]] * [[/Web Induced Risk Taking/]] * [[/Where It Goes: Electronic Waste and Salvage/]] * [[/Working Conditions at Apple Hardware Factories in China/]] * [[/Facebook Cheating/]] * [[/Intellectual Property in the Internet Age/]] * [[/The Social Psychology of YouTube/]] * [[/Learning from a Distance/]] *[[Communication Technology and Interpersonal Relationships]] * [[/Identity Theft/]] * [[/Higher Education Online/]] * [[/The Culture of Instagram/]] * [[/New Media and the United States Presidential Election of 2008/]] * [[/Targeted Advertising/]] * [[/Viral Marketing/]] * [[/Web Tracking/]] * [[/Internet Anonymity/]] * [[/The Culture of Snapchat/]] * [[/Snopes, PolitiFact, and Other Fact-Checking Websites/]] * [[/Twitter and other social networks in the Iranian protests of 2009/]] * [[/The Internet Strategy of White Supremacists/]] * [[/Google Translate|Google Translate]] * [[/The Deep Web/]] * [[/Social Media Mining/]] * [[/Internet Witch Hunts/]] * [[/News Echo Chambers/]] * [[/Featuritis/]] * [[/Content Moderation/]] * [[/Virtual Reality/]] * [[/Social Media Shaming Campaigns/]] * [[Lentis/The Geopolitics of TikTok|The Geopolitics of TikTok]] * [[/AI Music, Creativity, and Intellectual Property/]] * [[/Texting in Japan/]] * [[/Social Media Influencers and Public Health/]] </div> ==== Portable Electronics ==== <div style="column-count:3"> * [[Lentis/Smartphones and Cognitive Offloading|Smartphones and Cognitive Offloading]] * [[Cell Phones and Cancer in Britain]] * [[/Driving while Texting/]] * [[/GPS and Driving/]] * [[/Sociology of Texting/]] * [[/The Text Effect/]] * [[/Norms of Handheld Device Use/]] * [[/Happy Slapping/]] * [[/The Walkman Effect/]] * [[/Electronically Enabled Test Cheating/]] * [[/Cell Phones versus Face-to-Face Interaction/]] * [[/Children and Cell Phones/]] * [[/Amazon, E-readers and the Future of the Publishing Industry/]] * [[/Social Aspects of Cell Phone Cameras/]] * [[/Airline Passengers and Portable Electronics/]] * [[/Pokémon Go/]] * [[/Phone Cinematography/]] * [[/Cell Phones in Developing Countries/]] * [[/Wearable Activity Trackers/]] * [[/Handheld Electronics in South Korean Society/]] * [[/The Looking Glass/]] </div> ==== Entertainment and Media ==== <div style="column-count:3"> * [[/Massively Multiplayer Online Role-Playing Games/]] * [[/Gambling/]] * [[/Game Addictions/]] * [[/The Psychology and Technology of Game Immersion/]] * [[/The Proliferation of Music Production Capability/]] * [[/Grand Theft Auto: Violent Video Games and Controversy/]] * [[/Doom: Violent Video Games and Controversy/]] * [[/Implementation of Technology in Sports: Historical Successes and Failures, and Modern Discussion/]] * [[/Portrayal of Women in Video Games/]] * [[/Children,Video Games and Obesity/]] * [[/Electronic Sports (eSports)/]] * [[/Electronic Music Popular/]] * [[/From Cronkite to Stewart: TV News during and after Network Hegemony/]] * [[/The Impact of Fans on Technological Innovation in the NFL/]] * [[/Gold Farming/]] * [[/Jackass: Media Driven Risk Propagation/]] * [[/Anti-TV Social Movements/]] * [[/Media Format Wars/]] * [[/Microtransactions in Videogames/]] * [[/Moe Anthropomorphism/]] * [[/Hello Kitty: Identity Crisis, Kawaii Culture, and More/]] * [[/Technology and Conventional Norms of Personal Beauty/]] * [[/Dance Dance Revolution/]] * [[/Super Smash Bros./]] * [[/Twitch/]] * [[/Instant Replay in International Soccer/]] * [[/Among Us: Social Behavior in a Virtual World/]] * [[Lentis/TikTok|TikTok]] </div> ==== Security, Official Violence, Freedom, Privacy ==== <div style="column-count:3"> * [[/JEDI Cloud/]] * [[/Digital Rights Management/]] * [[/Military Industrial Complex/]] * [[/Tasers and Stun Guns/]] * [[/Probation Technology/]] * [[/International Drug Trafficking and Law Enforcement/]] * [[/Air Travel Security/]] * [[/The United States - Mexico Border/]] * [[/Recording Police Activity/]] * [[/Video Surveillance/]] * [[/Shopkeepers and Shoplifters: Technology and the Changing Balance of Power/]] * [[/Cell Phones in Prison/]] * [[/Cell Phone Jamming in the United States/]] * [[/Freedom of Information: WikiLeaks/]] * [[/Playing Games at Work: Employees versus Employers, Surveillance and Stealth/]] * [[/Cyberslacking/]] * [[/Mashups and Remixes: Between Creativity and Theft/]] * [[/Video Surveillance in Great Britain/]] * [[/Technology and Incarceration in the United States/]] * [[/Additive Manufacturing/]] * [[/Law Enforcement Access to Encrypted Data/]] * [[/Amateurs with Drones/]] * [[/Body Cameras/]] * [[/Human Terrain System: Military Meets Cultural Mindfulness/]] * [[/Law Enforcement and Social Media/]] * [[/Cyber-attack Attribution/]] * [[/China’s Social Credit System/]] * [[/Technology in the 2019 Hong Kong Protests/]] * [[/8chan/]] * [[/Lockheed Martin F-35/]] * [[/Drone Warfare/]] *[[/Capital Punishment in the United States/]] * [[/The Yellow Vests Movement/]] * [[Lentis/The 2018 U.S. Prison Strike|The 2018 U.S. Prison Strike]] * [[Lentis/Office Productivity in the Changing Workplace|Office Productivity in the Changing Workplace]] * [[Lentis/The Geopolitics of Asymmetric War: The Case of Ukraine|The Geopolitics of Asymmetric War: The Case of Ukraine]] </div> ==== Systemic Racism in the U.S. ==== <div style="column-count:3"> * [[/Gentrification/]] * [[/Predictive Policing/]] *[[The Prison-Industrial Complex]] *[[/The War on Drugs/]] *[[Lentis/Algorithmic Bias|Algorithmic Bias]] *[[Lentis/The School to Prison Pipeline|The School to Prison Pipeline]] *[[Lentis/TheHBCURenaissance|The HBCU Renaissance]] </div> ==== Technology and Gender ==== * [[Lentis/Algorithmic_bias_by_gender|Algorithmic Bias by Gender]] ==== History of Technology ==== <div style="column-count:3"> * [[The Decline of Public Transport in the U.S., 1945-1975]] * [[/The Pill, the Vatican, and American Catholics/]] * [[/Education and the Space Race in the United States/]] * [[/Technology, Organized Crime, and Law Enforcement in the early 20th-Century United States/]] * [[/Disease Prevention in the First World War/]] * [[/Atomic Age Optimism: 1930s - 1960s/]] * [[/Abortion in America as a Sociotechnical Controversy/]] * [[/Phreaking/]] * [[/Rachel Carson, Silent Spring, and the Development of Environmental Values, 1950-1970/]] *[[/The Legacy of the Donora Smog of 1946/]] *[[/COINTELPRO: The FBI, Civil Rights, and Domestic Surveillance/]] </div> ==== Sociotechnical Theories and Movements ==== <div style="column-count:3"> * [[Lentis/Protection Motivation Theory|Protection Motivation Theory]] * [[/The Singularity/]] * [[/Conversion to the Metric Standard in the United States/]] * [[/Disintermediation/]] * [[/Jevons Paradox/]] * [[/Path Dependence/]] * [[/Neoluddism and Technophilia/]] * [[/Emergent Behavior/]] * [[/Free Range Kids/|Free Range Kids: Children's Independent Mobility]] * [[/User Trust/]] * [[/The Panopticon/]] * [[/Planned Obsolescence/]] * [[/Fake News/]] *[[/Iron Triangles in the U.S. Federal Government/]] *[[/Risk Compensation/]] </div> {{BookCat}} {{Shelves|general engineering|Class projects}} {{alphabetical|L}} {{status|100%}} ccbn01f2uep3nxqe2h4845qkbq5ou38 0 254431 4634204 4633831 2026-05-05T01:00:08Z JackBot 396820 Formatting, [[Special:UncategorizedPages]] 4634204 wikitext text/x-wiki "'''Cotton Fields'''" is a song written by blues musician Huddie Ledbetter, better known as Lead Belly. It was also a #13 pop hit for The Highwaymen in 1961. The song mentions that the fields are "down in Louisiana, just about a mile from Texarkana". This is geographically impossible, as Texarkana is about 30 miles north of the Louisiana border.<ref>http://www.mapquest.com/maps?1s=LA&1y=US&1l=31.07095&1g=-92.0028&1v=STATE&2c=Texarkana&2s=TX&2y=US&2l=33.424999&2g=-94.047501&2v=CITY#a/maps/l::US-71:Doddridge:AR::US:33.024314:-93.892311:::1/l:::Texarkana:TX::US:33.424999:-94.047501:city::1/m:::::0:::::::::/io:1:::::f:EN:M:/e </ref> This song line suggestions the writer had the widely-held mistaken belief that Texarkana is partially in Louisiana. While the meaning of the name is clear – a portmanteau of Texas, Arkansas, and Louisiana, Texarkana is actually not on the Louisiana border, as surveyers were off by 30 miles. See Texarkana, History Section <ref>http://en.wikipedia.org/wiki/Texarkana</ref> ==The Beach Boys version== {{Infobox single | Name = Cottonfields | Cover = Beach Boys - Cottonfields.jpg | Artist = The Beach Boys | from Album = 20/20 | Released = February 10, 1969 (album)<br />April 20, 1970 (single) | Format = Vinyl | Recorded = November 18, 1968 (album)<br />August 15, 1969 (single) | Genre = Country rock | Length = 2:21 (album)<br />3:05 (single) | Label = Capitol | Producer = Brian Wilson and Al Jardine (album)<br />The Beach Boys (single) | Last single = "Add Some Music to Your Day"/"Susie Cincinnati" <br />(1970) | This single = "'''Cottonfields'''"/"The Nearest Faraway Place" <br />(1970) | Next single = "Slip On Through"/"This Whole World" <br />(1970) }} American rock band The Beach Boys covered "Cotton Fields" in 1968. It was released on their 1969 album ''20/20'' with Al Jardine on lead vocals. The song was recorded on November 18, 1968. Dissatisfied with Brian Wilson's arrangement, Jardine later led the group to record a more country-rock style version. The remake was recorded on August 15, 1969, with Orville "Red" Rhodes on pedal steel guitar. Released as "Cottonfields", this remake, while not a hit in the U.S., was a Top 10 song around the world in the spring and summer of 1970. It was the group's last single for Capitol Records and the last released in mono. While barely making a dent in the U.S. (#95 Record World, #103 ''Billboard'') though promoted with an appearance on the network TV pop show ''Something Else'', the song succeeded across the Atlantic, reaching number two in the UK's ''Melody Maker'' chart and listed as the tenth biggest seller of the year by the ''New Musical Express''. Worldwide &mdash; outside North America &mdash; it virtually replicated the success of the group's "Do It Again" two years before. It was number 1 in Australia, South Africa, Sweden and Norway, number 2 in Denmark, number 3 in Ireland, similarly top 5 in Japan, Spain and Rhodesia; number 12 in Holland, number 13 in New Zealand and number 29 in Germany. Because of this popularity, it was placed on the international release of the group's ''Sunflower'' album. ===Details=== *''Album:'' 20/20 *''Time:'' 2 minutes 21 seconds (album version), 3 minutes 05 seconds (single version) *''Produced and Arranged by:'' Brian Wilson (album version) *''Produced by:'' The Beach Boys *''Arranged by:'' Al Jardine (single version) ====Performers==== *Al Jardine: Lead Vocals ==Cover versions== *Creedence Clearwater Revival on their (1969) album ''Willy and the Poor Boys''. This version hit #1 in Mexico in 1970. *Elvis Presley in the movie ''Elvis: That's the Way It Is''. *Esther Ofarim sang "Cottons Fields" live on television in 1969, with her then husband Abi Ofarim. They also recorded a German version, "Wenn ich bei Dir sein kann" in 1964. *Elton John on ''Reg Dwight's Piano Goes Pop'' *Harry Belafonte on his 1958 album ''Belafonte Sings the Blues'' and his 1959 album ''Belafonte at Carnegie Hall,'' attributing the song to C. C. Carter *Harry Dean Stanton, in one scene of the film ''Cool Hand Luke'', plays a sped-up version. *Joe Dassin on 1989 Sony Music compilation Vol.2 *Johnny Cash on his album ''The Sound of Johnny Cash'' *Johnny Mann Singers on the album ''Golden Folk Song Hits'' - Liberty LST-7253 *The New Christy Minstrels on the album ''Chim-Chim-Cheree'' - Columbia CS-9169 *The Carter Sisters on their album ''The Best of The Carter Family'' (1966). *Donna Douglas on her album ''Back on the Mountain''. *Odetta on her 1963 album ''One Grain Of Sand'' *Odetta and Larry on their 1954 album ''The Tin Angel'' *Petula Clark in French as "L'enfant do" on a French EP released by Disques Vogue *The Pogues on their 1989 album ''Peace and Love'' (while this version references the original in its lyrics, the song itself is not a cover per se) *The Seekers on their 1964 album ''The Seekers'' (also known as ''Roving With The Seekers''). *Teresa Brewer on ''The Muppet Show''{{citation needed|date=March 2010}} *The Springfields known as the launch pad for singer Dusty Springfield for a 1962 EP, their version is featured on the CD ''On An Island Of Dreams: The Best Of The Springfields'' *Udo Jürgens a 1968 single. *Webb Pierce on the 1966 Decca album ''Webb's Choice'' Marching band arrangement as popularised by Kansas State University Marching Band and the Texas Tech University Marching Band by Joel Leach. ==Spanish version== The melody of "Cotton Fields" is also used in the Mexican song "Cuando Yo Era Jovencito" by Los Apson and Ramón Ayala. The title is taken from the first line of "Cotton Fields" ==References== {{reflist}} no:Cotton Fields nn:Cotton Fields {{BookCat}} mvn1g4scdwgj5m758g2jc0uqjcf4lif 0 273030 4634097 4315688 2026-05-04T15:40:29Z ErrinDev 3581204 change to gender neutral wording 4634097 wikitext text/x-wiki <noinclude>{{Nav}}</noinclude> <br /> <div class="nonumtoc"> __TOC__ </div> == Benefit of Standardization == Like most other standards, the primary purpose of SQL is '''portability'''. Usually, software designers and application developers structure and solve problems in layers. Every abstraction level is realized in its own component or sub-component: presentation to end-user, business logic, data access, data storage, net, and operation system demands are typical representatives of such components. They are organized as a stack and every layer offers an interface to the upper layers to use its functionality. If one of those components is realized by two different providers and both offer the same interface (as an API, Web-Service, language specification, ...), it is possible to exchange them without changing the layers which are based on them. In essence, the software industry needs '''stable interfaces''' at the top of essential layers to avoid dependence on a single provider. SQL acts as such an interface to relational database systems. If an application uses only those SQL commands which are defined within standard SQL, it should be possible to exchange the underlying rDBMS with a different one without changing the source code of the application. In practice, this is a hard job, because concrete implementations offer numerous additional features and software engineers love to use them. A second aspect is the '''conservation of know-how'''. If a student learns SQL, they are in a position to develop applications that are based on an arbitrary database system. The situation is comparable with any other popular programming language. If one learns Java or C-Sharp, they can develop applications of any kind running on a lot of different hardware systems and even different hardware architectures. == Limits == Database systems consist of many components. Access to the data is an essential element but not the only component. Other components include: throughput optimization, physical design, backup, distributed databases, replication, 7x24 availability, ... . Standard SQL is focused mainly on data access and ignores typical DBA tasks. Even the <code>CREATE INDEX</code> statement as a widely used optimization strategy is not part of the standard. Nevertheless, the standard fills thousands of pages. But most of the DBA's daily work is highly specialized to every concrete implementation and must be done differently when switching to a different rDBMS. Mainly application developers benefit from SQL. == The Standardization Process == The standardization process is organized in two levels. The first level acts in a national context. Interested companies, universities and persons of one country work within their national standardization organization like [[w:ANSI|ANSI]], [[w:DIN|Deutsches Institut für Normung (DIN)]] or [[w:BSI_Group|British Standards Institution (BSI)]], where every member has one vote. The second level is the international stage. The national organizations are members of ISO, respectively IEC. In case of SQL there is a common committee of ISO and IEC named [[w:ISO/IEC_JTC_1/SC_32|Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange]], where every national body has one vote. This committee approves the standard under the name ''ISO/IEC 9075-n:yyyy'', where ''n'' is the part number and ''yyyy'' is the year of publication. The ten parts of the standard are described in short [[w:SQL#Interoperability_and_standardization|here]]. If the committee releases a new version, this may concern only some of the ten parts. So it is possible that the ''yyyy'' denomination differs from part to part. ''Core SQL'' is defined mainly by the second part: ''ISO/IEC 9075-2:yyyy Part 2: Foundation (SQL/Foundation)'' - but it also contains some features of other parts. Note: The API [[w:JDBC|JDBC]] is part of Java SE and Java EE but not part of the SQL standard. A second, closely related standard complements the standard: ''ISO/IEC 13249-n:yyyy SQL Multimedia and Application Packages'', which is developed by the same organizations and committee. This publication defines interfaces and packages based on SQL. They focus on particular kinds of applications: text, pictures, data mining, and spatial data applications. == Verification of Conformance to the Standard == Until 1996 the [[w:National Institute of Standards and Technology|National Institute of Standards and Technology (NIST)]] certified the compliance of the SQL implementation of rDBMS with the SQL standard. As NIST abandon this work, nowadays, vendors self-certify the compliance of their product. They must declare the degree of conformance in a special appendix of their documentation. This documentation may be voluminous as the standard defines not only a set of base features - called ''Core SQL:yyyy'' - but also a lot of additional features an implementation may conform to or not. == Implementations == To fulfill their clients' demands, all major vendors of rDBMS offers - among other data access ways - the language SQL within their product. The implementations cover ''Core SQL'', a bunch of additional standardized features, and a huge number of additional, not standardized features. The access to standardized features may use the regular syntax or an implementation-specific syntax. In essence, SQL is the clamp holding everything together, but typically there are a lot of detours around the official language. <br /> <noinclude>{{Nav}}</noinclude> 3scwkr5eqac39z3ca5hme6nqleo7q9c 0 274498 4634260 4611798 2026-05-05T11:39:29Z Jeff1138 301139 4634260 wikitext text/x-wiki {{ArosNav}} ==Introduction== AROS supports hard disks and optical drives attached to several interfaces: * [[#NVMe M.2 SSD (M key)]] on the pci-e bus * [[#SATA]] aka Serial ATA or AHCI (IDE compatibility mode used in most cases) * IDE (also known as ATA, [[#PATA]] or Parallel ATA) * USB * SCSI limited ==PCI-e== ===NVMe M.2 SSD (M key)=== *Controller and firmware *DRAM better having if heavy workloads but not necessary for gaming *Cache like SLC HMB techniques *NAND (Main storage area with MLC, TLC or QLC versions of varying life expectancy) SSDs, USB flash drive, SD and Micro SD Cards have a limited amount of write cycles, therefore guaranteed to fail randomly and suddenly at any time. All SSDs are prone to corrupt firmware due to poor quality NAND where both the data and the firmware resides. The drive tends to go read only when too many errors occur before complete failure. That is up to 10 years for things like memory cards and USB sticks. In general, unless there is a firmware design issue, cheap materials used, stress like bending or overheating causing cold solder joints, an SSD can last a long time if minimal writing activity takes place but eventually if flash isn't written to, it degrades. Catch 22. Dram and cache are not the same thing. Dram stores the ssds indexes and metadata for faster data retrieval and wear leveling. The cache keeps part of the nand memory as SLC storage which can be written to faster. Basically all ssds will have a dynamic SLC cache where it will decrease as the drive fills up. Cache controller designs that are DRAM less use the internal SRAM cache in the controller to cache the NAND mapping table. It just requires a different mapping table design since SRAM caches are much smaller than DRAM. Ultimately the mapping table is still stored in NAND. General rule of thumb: the cheaper an SSD, the higher the likelihood it uses lower quality flash chips so sudden failing NAND, problematic controller chips (e.g. SandForce), outsourced firmware. Generic brand like old SP, Corsair or Crucial may be recoverable whilst major brands Samsung, Intel and Western Digital are impossible due to firmware encryption and customizations. Recommend sticking with older Silicon Motion or Phison controllers if possible. A ssd isn't good because it has dram or bad because it doesn't. Other things should be taken into account like sustained writes so check the TPU write intensive usage See [https://www.techpowerup.com/ssd-specs/ here] for more information {| class="wikitable" width="100%" ! width="15%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="30%" |Tested Distribution |- | <!--Brand-->Unnamed | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 to - SM2259XT2 SM2263XT MAS0902 MAP1202 YS9082HP RM1135 RTS5765 PS3111 |- | <!--Brand-->Unnamed OEMs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 to date - Realtek RTS5765/66 controller + Micron 96L (B27A) |- | <!--Brand-->Acer Predator GM7 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Acer drives built by Biwin, that also supplies HP, Maxio MAP1602A no DRAM so HMB, YMTC 128L TLC, |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 NVME IM2P33F8, IM2S3168 SSD | <!--Model-->IM2P33F8-512GD | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - industrial 12L 3D TLC NAND flash Supports LDPC ECC, RAID Engine, and SLC Cache End-to-End (E2E) Data Path Protection with Host Memory Buffer (HMB) i.e. DRAMless |- | <!--Brand-->ADATA XPG SX8200 Pro M.2 nvme | <!--Model-->ASX8200PNP1TTC | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 NVM Express 1.3 SN2262G later SN2262EN chipset - |- | <!--Brand-->ADATA 256GB GEN4 x4 NVMe PCIe M2 2230 SSD | <!--Model-->SM2P41C3-256GC2 DP/N 0KM1Y6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 consumer |- | <!--Brand-->ADATA XPG GAMMIX S50 Lite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Silicon Motion SM2267XT dramless |- | <!--Brand-->ADATA XPG ATOM 50 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Innogrit RainierQX IG5220 |- | <!--Brand-->Adata Legend 710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->ADATA Legend 900 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->BiWin PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Innogrit IG5216 controller, no DRAM so HMB which appears to be the standard - |- | <!--Brand-->BiWin NV7200 PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SM2263XT |- | <!--Brand-->Biwin NV7400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force LE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Corsair Force Series MP500 MP510 M.2 NVMe PCIe Gen 3 x4 SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 PS5012-E12-27 from Phison, 64-layer TLC Toshiba BiCS flash, may have dram cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 on DRAM DDR4 with Micron 96L QLC - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Corsair MP600 Elite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E16 and Bics DDR4 DRAM buffer and TLC-based with SLC-mode cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair MP600 Pro XT, PRO LPX, PRO NH PCIe4 | <!--Model-->CSSD-F1000GBMP600ECS Elite, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 DRAMless SSD controller Phison PS5026-E26, BiCS6 162L QLC NAND |- | <!--Brand-->Corsair MP600 Core XT | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison and Bics QLC-based with SLC-mode cache - |- | <!--Brand-->Corsair MP700 Pro PCIe 5.0 | <!--Model-->CSSD-F1000GBMP700PNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial P1 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 QLC NAND but a controller with a DRAM cache - |- | <!--Brand-->Crucial P2 M.2 2280 Gen3 x4 NVM-express | <!--Model-->CT1000P2SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 dram-less Phison PS5013-E13-31 on 96-layer QLC NAND - |- | <!--Brand-->Crucial P3 Plus M.2 2280 | <!--Model-->CT1000P3PSSD8 CT2000P3PSSD801 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with Host Memory Buffer HMB tech to use a small bit of system RAM as DRAM cache and Micron 176-layer QLC NAND - |- | <!--Brand-->Crucial P3 M.2 nvme SSD | <!--Model-->CT2000P3SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron QLC (N48R) - |- | <!--Brand-->Crucial P5 m.2 nvme PCIe 4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 runs hot - Crucial NVMe with DRAM LPDDR4 and Micron 96L TLC |- | <!--Brand-->Crucial P5 Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 some have DRAM cache |- | <!--Brand-->Crucial T500 Gen4.0 nvme 2.0 | <!--Model-->CT1000T500SSD8, CT2000T500SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison PS5025-E25 with micron B58R 232-layer 3D TLC NAND and Micron LPDDR4 DRAM cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Crucial T700 Gen5 SSD | <!--Model-->CT1000T700SSD3, CT2000T700SSD3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 SSD controller Phison PS5026-E26, Micron 232-layer NAND with no dram as standard - |- | <!--Brand-->Crucial P310 M.2 2280 NVMe PCIe Gen4 SSD | <!--Model-->CT2000P310SSD801 (2Tb), | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 DRAM-less Phison E27T Micron 232-layer NAND - |- | <!--Brand-->Crucial T705 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 dramless Phison SSD controller |- | <!--Brand-->Crucial T710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 SMI SM2508 SSD controller dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN605 PCIe Gen3 x4 interface, NVMe 1.3 support | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Ediloca EN660 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN760 PCIe Gen4 x4 M.2 NVMe 1.4 interface | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 gets hot |- | <!--Brand-->Ediloca EN870 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 no dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca EN855 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S500 pro PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 MaxioTech MAP1202A-F1C with YMTC 128L and pseudo-SLC cache |- | <!--Brand-->Fanxiang S660 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S880/R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Fanxiang S770 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX550 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Fikwot FN501 Pro m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->FIKWOT FN950 FN955 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 MAP1602 (at 1600 MT/s) flash YMTC TLC no dram |- | <!--Brand-->Fikwot FX991 m.2 nvme | <!--Model-->FW-FX991-2TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FN960 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Fikwot FN970 m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Geil ZEN ITH m.2 nvme | <!--Model-->S3-240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Gigabyte Aorus Gen4 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash - DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Gigabyte Aorus 10000 PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->HP EX950 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HP FX900 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dram less |- | <!--Brand-->HP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Integral M2 Series NVME M.2 2280 PCIe Gen 3x4 | <!--Model-->INSSD500GM280NM2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Inland Professional TLC E12S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E18 |- | <!--Brand-->Inland Gaming performance Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash |- | <!--Brand-->Inland TD510 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM DDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->intel SSD Pro 7600p Series M.2 80mm 2280 PCIe 3.0 x4, 3D TLC | <!--Model-->SSDPEKKF512GB, SSDPEKKF256G8L, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel 660p m.2 nvme | <!--Model-->ssdpeknw010tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 SMI SM2263 controller with 1GB DRAM cache and 1TB of Intel QLC NAND similar to crucial P1 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] 670p | <!--Model-->SSDPEKNU010TZ | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 256 MB DDR3L cache and 12-140 GB SLC-Cache QLC NAND |- | <!--Brand-->Intel P4511 m.2 nvme PCIe3.1 x4 22110 110mm | <!--Model-->SSDPELKX020T8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 very long |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A1000 NVME PCIE M2 2280 SSD | <!--Model-->SA1000M8/480G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Kingston A2000 NVME PCIE M2 2280 SSD | <!--Model-->SA2000M8/250G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->Kingston KC3000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] PS5018-E18 PCIe 4.0 x4 NVMe controller and Micron’s 176L TLC NAND flash - |- | <!--Brand-->Kingston NV1 m.2 nvme pcie | <!--Model-->SNV1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 entry-level consumer DRAMless Phison E13T or Silicon Motion 4-channel SM2263XT - one brand TLC up to 1Tb and QLC after - |- | <!--Brand-->Kingston NV2 | <!--Model-->SNV2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 entry-level, first SMI SM2267XT or Phison E19T and later SMI SM2269XT or Phison E21T with various flash memory |- | <!--Brand-->Kingston FURY Renegade m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] Phison E18 controller, Micron 176L nand and ddr4 dram - |- | <!--Brand-->Kingston NV3 | <!--Model-->SNV3S/500G, SNV3S/1000G, SNV3S/2000G, SNV3S/4000G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 entry-level, SMI SM2268XT2 or Phison E27T controller with BiCS6 TLC or QLC flash - dramless so hmb - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia (Toshiba) XG4? M2 2280 NVMe PCIe SSD | <!--Model-->THNSF5512GPUK, THNSN51T02DUK, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 Phison has done custom controller work for Kioxia, and Kioxia has also worked with SMI and InnoGrit (the latter more recently). Kioxia label their controllers as their own but these are largely rebadged. |- | <!--Brand-->Kioxia (Toshiba) XG5 for Data Centres | <!--Model-->KXG5 KXG50ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 nanya ddr3 dram? with 64-layer BiCS 3D flash memory |- | <!--Brand-->Kioxia XG6 OEM m.2 nvme | <!--Model-->KXG60ZNV512G, KXG60ZNV1T02, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 TC58NCP090GSD with DRAM NANYA LPDDR3 and Toshiba BiCS FLASH 96-layer 3D TLC - |- | <!--Brand-->Kioxia (Toshiba) BG4 m.2 nvme | <!--Model--> *KBG40ZNS128G, KBG40ZNS256G, KBG40ZNS512G, KBG40ZNS1T02 *KBG40ZNT256G, *KBG40ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - no dram but NVMe's Host Memory Buffer (HMB) i.e. portion of the system's RAM for caching - Toshiba's 96-Layer BiCS FLASH - seems Windows UASP driver and the JMS583 chipset interacts badly with the Kioxia BG4 - early firmware upgrade to prevent overheating hot - |- | <!--Brand-->Kioxia XG7 | <!--Model-->KXG70ZNV1T0G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 - might need firmware update on early 2tb 4tb versions - controller with sk hynix dram and tlc nand |- | <!--Brand-->KIOXIA EXCERIA PLUS G2 SSD series PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5012-E12S-32 aka TC58NC1201GST 4-channel controller along with KIOXIA proprietary 96-layer 3D TLC and "MG2h" version has BiCS4.5 which is faster than launch BiCS4 - - |- | <!--Brand-->Kioxia XG8 OEM m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 TC58NC0L1XGSD with DRAM LPDDR4 and 112-Layer Kioxia BiCS5 TLC - |- | <!--Brand-->Kioxia (Toshiba) BG5 | <!--Model-->KGB50ZNV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 HMB buffer |- | <!--Brand-->Kioxia (Toshiba) BG6 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless |- | <!--Brand-->KIOXIA EXCERIA PLUS G3 SSD series PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 has hmb, like most dram-less nvmes KIOXIA |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar 1TB SSD M.2 NVME 1.4 Gen3x4 M.2 2280 | <!--Model-->NM610Pro | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Lexar NM620 *IG5216 (worse?) not great original 96L *MAP1202 YMTC up to 232L, or 176L Micron, TLC for the 1TB | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 a few versions all DRAM-less, |- | <!--Brand-->Lexar NM790 SSD M.2 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Maxio MAP1602 no DRAM so HMB with 232-Layer YMTC TLC |- | <!--Brand-->Lexar m.2 nvme | <!--Model-->EQ790 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Maxio MAP1602, no DRAM so HMB, Flash Memory 232-Layer YMTC TLC, |- | <!--Brand-->Lexar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Liteon M.2 NVME 512GB SSD 2280 | <!--Model-->CAZ-51282512-Q11 DP/N 0K64PG | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI controller |- | <!--Brand-->Micron 2200S m.2 nvme 2200 series | <!--Model-->MTFDHBA256TCK, MTFDHBA512TCK | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 for a time, Micron controller with 64L TLC 3D Nand [https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=3jg3g BSOD occurred as CRITICAL_PROCESS_DIED] before self applied firmware [https://support.lenovo.com/us/en/downloads/ds119265-nvme-solid-state-drive-firmware-update-utility-for-windows-10-64-bit-thinkpad apparently it is related to the power management that disconnects the Micron SSD] |- | <!--Brand-->Micron 2300 m.2 nvme Gen 3 x4 | <!--Model-->MTFDHBA256TDV P/N M02626-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Micron 3400 M.2 NVME SSD Gen4 | <!--Model-->MTFDKBA512TFH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no cache |- | <!--Brand-->Micron 2450 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 E19T |- | <!--Brand-->Micron 2600 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison's PS5029-E29T SSD controller with Micron 276-layer G9 QLC NAND in a DRAMless - Adaptive Write Technology (AWT) using various NAND modes (SLC, TLC, and QLC) as a dynamic cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium S270 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium M450 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV2000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico J10 J-10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Orico D10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Orico e3500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Orico O7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Patriot P300 m.2 nvme pcie 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Patriot Viper VP4300 Lite M.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS2230 Gen3 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->PNY CS2140 CS2342 Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Raydisk 1T 2280 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 no dram, Memory QLC Intel 144 layer. Chip Realtek |- | <!--Brand-->Raydisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket Nano 2242 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket 4.0 m.2 nvme | <!--Model-->SB-2130-512, SB-2280-1TB, SB-Rocket-NVME4-HTSK-2TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 4.0 PLUS m.2 nvme | <!--Model-->SB-RKT4P-1TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E1? controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Phison E25 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung PM951 m.2 nvme | <!--Model-->MZVLV1T | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 950 PRO PM961 M.2 2280 NVMe 1.3 PCI-Express 3.0 x4 | <!--Model--> *MZ-VKW5120 *MZ-VLW2560 MZVLW256HEHP-000L7, MZ-VLW5120, MZ-SLW1T00 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - possibly 512M LPDDR3 Samsung K4E4E324EE-ECCF cache - Polaris (S4LP077X01-8030) unit with Samsung 48-layer TLC V-NAND V3 flash Samsung K90MGY8S7M-CCK0 - |- | <!--Brand-->Samsung 960 Pro SM961 M.2 PCi-e NVMe SSD 2280 | <!--Model-->MZ-V6P1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 Polaris (S4LP077X01-8030) controller Samsung 48-layer multi-level cell (MLC) V-NAND, pseudo-SLC cache or LPDDR3-1866 Samsung K4E8E304EE-EGCF |- | <!--Brand-->Samsung PM981 2280 PCI-Express 3.0 x4 | <!--Model--> *Rev 0 MZ-VLB256A, MZ-VLB512A, MZ-VLB1T0A, *Rev 0 MZ-VLB2560, MZ-VLB5120 P/N MZVLB512HAJQ, MZ-VLB1T00, *Rev ? MZ-VLB256B, MZ-VLB512B, MZ-VLB1T0B, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache hybrid SLC Samsung’s TurboWrite - |- | <!--Brand-->Samsung PM981a 2280 PCI-Express 3.0 x4 | <!--Model-->MZ-VLB5120 P/N MZVLB512HBJQ-000L7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache |- | <!--Brand-->SAMSUNG PM991 NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ2560 MZVLQ256HBJD-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SAMSUNG PM991a NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ256B MZVLQ256HBJD-00BH1, MZ-9LQ256C, MZ-VLQ512B MZVLQ512HBLU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Samsung 970 EVO Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Samsung Phoenix on Samsung LPDDR4 dram and 2 Samsung 9x-layer V-NAND TLC |- | <!--Brand-->Samsung 980 EVO Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Samsung 980 Pro m.2 nvme | <!--Model-->MZ-V8P1T0BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 originally made in Korea ([https://semiconductor.samsung.com/consumer-storage/support/tools/ 2tb firmware issues] with versions starting with 3) and year later Vietnam - DRAM |- | <!--Brand-->Samsung 990 EVO m.2 nvme | <!--Model-->MZ-V9E2T0BW, MZ-V9E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo no DRAM so HMB Samsung 133-Layer TLC (V6P) and Samsung 133-Layer TLC (V6P) - |- | <!--Brand-->SAMSUNG PM9A1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model-->MZ-VL25120 MZVL2512HCJQ, MZVL21T00 MZVL21T0HCLR-00BL2, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 might be OEM variant of the 980 Pro |- | <!--Brand-->Samsung PM9B1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model--> *2023 MZ9L4256HCJQ-00BD1 MZ-9L4256A, , *2025 MZ-VL42560, MZ-VL45120, MZ-VL421T, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SSD controller is Marvell 88SS1322 Whistler Plus, no DRAM cache and Samsung 128-layer TLC NAND flash |- | <!--Brand-->Samsung 990 EVO Plus m.2 nvme2.0 | <!--Model-->MZ-V9S2T0BW, MZ-V9S1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo with no DRAM so HMB and Samsung 236-Layer (V8) TLC - |- | <!--Brand-->Samsung 990 Pro m.2 nvme | <!--Model-->MZ-V9P2T0BW, MZ-V9P1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 2tb early firmware issue - Samsung Pascal with DRAM LPDDR4 and 176-Layer V-NAND TLC - has had firmware design issues, causing premature failure - |- | <!--Brand-->Samsung 9100 PRO PCIe Gen5 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Seagate Firecuda 510 G3 x4 nvme | <!--Model--> *ZP1000GM30001, *ZP500GM30021 P/N 2NT308-300, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad early batch - Phison E12 STXYP0160031 on SK Hynix DRAM DDR4 with Kioxia BiCS3 64L TLC |- | <!--Brand-->Seagate Firecuda Q5 | <!--Model-->ZP500CV30001,ZP250CV30001,ZP1000CV30001 P/N 2ZK307-881,ZP2000CV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 PS5013-E13-31 from Phison, no DRAM cache and QLC nand |- | <!--Brand-->Seagate Firecuda 515 | <!--Model-->ZP500GV30001,ZP250GV30001,ZP1000GV30001,ZP2000GV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 no dram and qlc nand |- | <!--Brand-->Seagate FireCuda 520 SSD M.2 PCIe Gen4 ×4 NVMe 1.4 | <!--Model-->ZP2000GM30002, ZP1000GM30002, ZP500GM30002 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Seagate Firecuda 520N m.2 nvme | <!--Model-->ZP2000GV3A012, ZP1000GV3A012 and ZP500GV3A012 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 530 m.2 nvme | <!--Model-->ZP500GM3A013, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5018-E18 on DRAM DDR4 with Micron 176L TLC |- | <!--Brand-->Seagate | <!--Model-->ZP1000CV3A002, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 540 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand-->Seagate Firecuda 530R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power UD85 m.2 nvme PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 [http://vlo.name:3000/ssdtool/ firmware tools] |- | <!--Brand-->Silicon Power UD90 PCIe 4.0 nvme | <!--Model-->SP250GBP44UD9005, SP500GBP44UD9005, SP01KGBP44UD9005, SP02KGBP44UD9005, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron TLC (B47R) but later no name QLC nand instead - |- | <!--Brand-->Silicon Power A60 A80 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 various originally an E12 drive with 64L Toshiba NAND, then had variations with E12S and SM2262EN as well as random 64L/96L, now it comes with a MAP1001A controller by Maxio and some YMTC NAND - |- | <!--Brand-->Silicon Power US75 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix BC501 M.2 m.2 NVMe PCIe Gen3 SSD | <!--Model--> *Rev0 HFM256GDHTNG-8510B SSS0L24764, HFM256GDJTNG-8310A, *Rev1 HFM256GDHTNG-8310A SSS0Q68673, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 bad batch early - |- | <!--Brand-->SK Hynix BC511 512GB NVMe PCIe M2 2230 SSD | <!--Model-->HFM256GDJTNI-82A0A HFM512GDGTNI-82A0A D P/N 0TG8T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 no dram cache |- | <!--Brand-->SK hynix BC711 PCIe Gen3 x4 | <!--Model-->HFM001TD3JX013N, HFM512GD3JX013N, HFM256GD3JX013N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 okay but no dram cache |- | <!--Brand-->SK hynix PC711 m.2 2280 PCIe Gen3 x4 | <!--Model--> *HFS001TDE9X073N, HFS512GDE9X073N, HFS256GDE9X073N *HFS001TDE9X080N, HFS512GDE9X080N, HFS256GDE9X081N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->SK Hynix SC210 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SK Hynix PC601 PCIe 3.0 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - Cepheus Plus YCN34PTA0FR Controller and 48L TLC Flash, pseudo-SLC cache and LPDDR4-3733 SK Hynix H9HCNNN8KUMLHR-NME dram - |- | <!--Brand-->SK Hynix PC401 3rd gen PCIe | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad batch early - |- | <!--Brand-->SK hynix Gold P31 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 SK hynix’s proprietary Cepheus controller |- | <!--Brand-->Sk Hynix SK500 Gen 4 (x4) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SK hynix Platinum P41 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Aries SSD controller with 176-Layer TLC flash - SK hynix LPDDR4 dram - |- | <!--Brand-->Sk Hynix PC801 PCIe Gen4 x4 m.2 nvme | <!--Model-->HFS001TEJ9X101N, HFS512GEJ9X101N, HFS256GEJ9X101N, HFS002TEJ9X101N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->SK Hynix BC901 m.2 nvme PCIe Gen4 2230 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Silicon Motion SM2269XT with no DRAM so HMB buffer cache - SK Hynix 176-layer TLC NAND flash 1TB only - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team | <!--Model-->TM8PS7512G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TeamGroup MP34 | <!--Model-->MP34 256GB, MP34 512GB, MP34 1TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 good Phison E12 with DRAM NANYA DDR3L and Toshiba BiCS 3 64L TLC - |- | <!--Brand-->Team Group T-Force Cardea A440 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison PS5018-E18 NVMe 1.4 controller and Micron’s 96L TLC with SK hynix 8Gb DDR4 chips but not OPAL-compliant AES 256-bit |- | <!--Brand-->Team Group TForce Cardea A440 Lite PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 dram-less E27T controller and 162L TLC but not OPAL-compliant AES 256-bit |- | <!--Brand-->teamgroup Team Z44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand-->teamgroup Team MP44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E21T no DRAM so HMB with 176-Layer Micron TLC |- | <!--Brand-->Team MP33Q | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - dramless maxio MAP1202 with TLC (MP33) or QLC (MP33Q) - |- | <!--Brand-->Team Group QX GE Pro m.2 nvme PCIe5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 innogit IG5666 with QLC 3D 232L nand with DRAM - |- | <!--Brand-->Team Group T-Force G70 Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 InnoGrit IG5236 (Rainier) with DRAM and NAND YMTC TLC - |- | <!--Brand-->Team Group T-Force Cardea Z540 m.2 nvme PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison E26 controller and 232L TLC and DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE110S PCIe Gen3 x4 M.2 2280 TS128GMTE110S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND |- | <!--Brand-->Transcend MTE220S PCIe Gen3 x4 M.2 2280 TS2TMTE220S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND with DRAM Cache |- | <!--Brand-->Transcend MTE300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand-->Transcend MTE300S PCIe Gen3 x4 M.2 2230 TS256GMTE300S TS512GMTE300S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND, 1G and 2G get hot |- | <!--Brand-->Transcend | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE400S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 mlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Union Memory (Shenzhen) AM6672 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM6A0 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Verbatim V15000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->WD Blue SN500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western digital SN720 M.2 2280 NVME PCIE for Data Centers | <!--Model-->SDAQNTW-512G-1001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2021 |- | <!--Brand-->WDC SN520 2230 Gen3 x2 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2020 |- | <!--Brand-->Western digital ix sn530 M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 industrial sandisk controller and firmware, as well as 96-layer 3D TLC NAND memory that can work in TLC or SLC mode - |- | <!--Brand-->Western digital SN730 Gen3 x4 M.2 2280 M.2 NVME | <!--Model-->SDBPNTY-1T00, SDBPNTY-512G-1012, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 to 2021 DRAM Cache DDR4-2666 CL18 Micron MT40A512M16LY-075:E (D9WFH) with Controller WD 20-82-00705-A2 Triton MP28 and NAND Flash Toshiba BiCS4 60082 512G (Rebranded by SanDisk) TLC 96-layer |- | <!--Brand-->WD Black SN750 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 64-layer 3D stacked NAND with 3 bits per cell TLC (Triple Level Cell) with 256MB of skhynix DRAM cache for every 250GB |- | <!--Brand-->WD Black SN850 m.2 nvme Gen4 PHY | <!--Model-->WDS100T1X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Sandisk G2 controller with Micron DDR4 cache - new nCache 4.0 slc cache total dynamic capacity spans one-third (300GB on 1TB) with a small static SLC cache (12GB on 1TB) from the Kioxia BiCS4 96L TLC 96-layer NAND flash - |- | <!--Brand-->Western digital SN550 Blue M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - various controllers and NANDs |- | <!--Brand-->Western Digital SN810 NVMe SSD 2280 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 slc cache - laptop oem only no retail version - |- | <!--Brand-->WD SN850X | <!--Model-->WDS100T2X0E, WDS200T2X0E, WDS400T2X0E, WDS800T2X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 issues with early ssd firmware and AMD Zen 3 X570 and X670E chipsets - Sandisk A101000291-82 controller with 112-layer TLC and DDR4 DRAM cache |- | <!--Brand-->WD_Blue SN570 single-sided M.2 2280 (80mm) PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless - WD/SanDisk SSD controller with BiCS 5 3D NAND TLC 112-layer NAND flash memory - |- | <!--Brand-->WD_Black SN770 m.2 nvme | <!--Model-->WDS100T3X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless cache with TLC |- | <!--Brand-->WD Green SN350 m.2 NVMe SSD | <!--Model-->WDS100T3G0C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 DRAM-less cache with SanDisk controller and QLC (quad-level cell) NAND |- | <!--Brand-->WD_BLACK SN750 SE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Phison E19T, dramless |- | <!--Brand-->WD SN740 M.2 (2230) PCIe 4.0 x4 2280 | <!--Model-->SDDQTQD-1T00, SDDPNQD-, SDDPNQD-256G-2006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless with SSD controller WD Sandisk 20-82-10081-A1 Polaris MP16+ with Toshiba BiCS5 112-layer TLC NAND flash |- | <!--Brand-->WD_Blue SN580 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless SanDisk controller with (HMB) and 112-Layer Kioxia TLC (BiCS5) |- | <!--Brand-->WD Blue SN5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Black SN8100 / Sandisk Optimus GX Pro 8100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk Optimus GX 5100 7100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk Optimus GX Pro 850X | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Zhitai (Yangtze Memory) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === Mini SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Biwin PCIe 4×2 NVMe 1.3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 GPDwin5 and Oneplayer Superx hybrid - 3D TLC - LGA packaging - V1 slide tray mechanism - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- |} ==SATA== Advanced Host Controller Interface (AHCI), a programming interface for SATA host controllers. Platforms supporting AHCI may take advantage of performance features such as no master/slave designation for SATA devices — each device is treated as a master — and hardware-assisted native command queuing. AHCI may but not often also provides usability enhancements such as Hot-Plug (Desktop and Mobile Only). AHCI requires appropriate software support (e.g., an AHCI driver) AHCI, the underlying protocol for SATA, only supports one queue with 32 commands. The issue with AHCI is that it's going to take a pile of test hardware just to figure out all the different bugs in all the motherboard chipsets and add-on PCI cards that 'kinda' implement AHCI. Not to mention Silicon Image, which took a very different approach from Intel's AHCI in their SATA controllers. === SATA 7mm 2.5inch SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand-->ADATA 240GB Ultimate SU630 2.5" | <!--Model-->ASU630SS-240GQ-R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->ADATA Ultimate Su650 2.5in | <!--Model-->ASU650SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->ADATA Ultimate Su800 2.5in | <!--Model-->ASU800 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI SM2258 controller with Micron 3D TLC NAND but low performance when data fills the SLC cache - slow write speed - |- | <!--Brand-->ADATA Ultimate Su680 2.5in | <!--Model-->ASU680SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS340 Panther | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS350 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial M225 SSD 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2009 sata2 3gbp/s |- | <!--Brand-->Crucial C300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 sata3 6gbps - |- | <!--Brand-->Crucial M4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2011 Marvell 88SS9174-BKK2 processor, 25nm MLC NAND flash and 128MB dram cache |- | <!--Brand-->Crucial M500 120Gb to 960Gb | <!--Model-->CT250M500SSD1, CT500M500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 dram cache |- | <!--Brand-->Crucial M550 120G to 1T | <!--Model-->CT250M550SSD1, CT500M550SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dram cache |- | <!--Brand-->Crucial (Micron) BX100 | <!--Model-->CT500BX100SSD1, CT1000BX100SSD1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - no dram - Silicon Motion SM2246EN and ATA version ACS-2 - |- | <!--Brand-->Crucial (Micron) MX100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache Micron controller and nand - |- | <!--Brand-->Crucial MX200 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC NAND |- | <!--Brand-->Crucial (Micron) BX300 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dramless cache - Micron ex Tidal controller and TLC nand - |- | <!--Brand-->Crucial (Micron) MX300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand-->Crucial (Micron) bx500 2.5inch | <!--Model-->CT240BX500SSD1, CT480BX500SSD1, CT960BX500SSD1, CT1000BX500SSD1, CT2000BX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SM2258XT 4channel later SM2259XT paired with Micron’s latest 64-Layer 3D TLC flash but dramless SLC cache (part of the tlc flash) - |- | <!--Brand-->Crucial (Micron) MX500 | <!--Model-->CT250MX500SSD1, CT500MX500SSD1, CT1000MX500SSD1, CT2000MX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - dram cache from 256M to 2G - discontinued end of 2024 |- | <!--Brand-->Fanxiang S101 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no dram cache, Hynix memory 3dv7-176l 176 layer QLC (one chip), either raymx rm1135, SM2259XT controller or Realtek rts5735dlq |- | <!--Brand-->Fanxiang ranxiana S102 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - no dram - |- | <!--Brand-->Fanxiang S101Q 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fanxiang | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX815 Standard 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FS810 Ultra 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertec FirestormLite 2.5inch | <!--Model-->S240GHS3-M or SDSSD240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertech | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral V2 Plus 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel SSD 520 Series 2.5 inch SATA 6Gb/s 2.5" SSD Solid State Drive | <!--Model-->SSDSC2CW240A3, SSDSC2CW480A3, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 LSI SandForce SF2281, Flash Memory Intel Synchronous 25nm MLC - |- | <!--Brand-->Intel Pro Series 1500 | <!--Model-->SSDSC2BF180A4L SSD0E38417, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Intel S3610 Series 2.5" 400GB 6GBPS SATA SSD | <!--Model-->SSDSC2BX400G4R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 data center |- | <!--Brand-->Intel SSD Pro 5400s 512 GB | <!--Model-->SSDSC2KF512H6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3510 Series MLC 2.5" | <!--Model-->SSDS2BB400G6, SSDSC2BB480G6R, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3520 Series MLC 2.5" | <!--Model-->SSDSC2BB800G7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel SSD DC S3710 Series 800GB 2.5" | <!--Model-->SSDSC2BA800G4P, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 server |- | <!--Brand-->Intel SSD 545S Series 256GB 512GB | <!--Model-->SSDSC2KW256G8X1, SSDSC2KW512G8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] SSD DC S4500 240GB 2.5inch - HP Enterprise | <!--Model-->SSDSC2KB240G7P | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingspec P3-512 P3-1T0 P3-2TO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston SSDNow 300 | <!--Model-->SV300S37A/240G, SV300S37A/120G, SV300S37A/60G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dramless - lsi sandforce SF2281 or JMicron JMF662 controller with Toshiba MLC or Intel MLC |- | <!--Brand-->Kingston A400 120G to 960Gb 2.5inch | <!--Model-->SA400S37/240G SBFK61K1, SA400S37/480G, SA400S37/960G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 half case sized ssd 4 x FH64B08UCT1-60 64G - t6 security torx into metal case - dram less - poor write speeds - |- | <!--Brand-->Kingston | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia formerly Toshiba HG6 2.5in | <!--Model--> *9.5mm THNSNJ512GBSU, THNSNJ256GBSU, THNSNJ128GBSU *7mm THNSNJ512GCSU THNSNJ512GCSY, THNSNJ256GCSU THNSNJ256GCSY, THNSNJ128GCSU THNSNJ128GCSY | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar NS100 2.5 inch sata | <!--Model-->LNS100-1TRB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - Marvell 88NV1120 Artemis, a DRAM cache is not available and pseudo-SLC. Micron 64-layer TLC NAND flash 4 chips @ 512 Gbit TS7512G181 (Rebranded by Lexar) (256G) - 4 nand flash chips Lexar/TST22T181/ B1924 and one controller: Lexar DM918/NOD43 1907 (512G) - |- | <!--Brand-->Lexar NQ100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - DM928 controller which operates without a DRAM buffer. Two 128GB Micron NAND flash chips |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LiteOn | <!--Model-->LCS-128L9S-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 no dram - sata2 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Matrix 256Gb 512GB SATA 2.5in SSD | <!--Model-->MIS512GSDS, MIS256GSDS | <!--Work MSDos-->UP TO 550MB/S | <!--Work GPT-->UP TO 500MB/S | <!--Tested Distribution--> |- | <!--Brand-->Micron 1100 | <!--Model-->MTFDDAK2T0TBN-1AR1ZA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron 1300 2TB 1300 2.5" | <!--Model-->MTFDDAK2T0TDL-1AW1ZABHA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 - old sdd - TLC nand - |- | <!--Brand-->Micron RealSSD C400 2.5inch | <!--Model-->MTFDDAK256MAM-1K12 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Mushkin Reactor | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC flash |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac SA500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico Y-20 Y20 2.5 inch sata SHENZHEN ORICO TECHNOLOGIES CO.,LTD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 flash nand - |- | <!--Brand-->Orico S500-Pro s500pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Origin Storage Inception TLC830 Pro Series 2.5in SATA III SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D tlc flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand-->Patriot P210 2.5 inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> qlc flash nand - |- | <!--Brand-->Patriot P220 | <!--Model-->P220S2TB25 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Plextor M6V | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS900 2.5 in sata SSD | <!--Model-->SSD7CS900-480-PB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->PNY CS2311, CS3030 and Pro Elite SSDs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung SM PM | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->PM871a or PM871b? SM/PM = 2-bit or 3-bit MLC. PM = 3-bit MLC = TLC. 8 = generation = 8xx, 7 = model = 850 EVO (in this case), 1 = usage (e.g. 3 = datacenter). a/b = revision or type of flash, the 850 EVO had multiple revisions including at least three types of flash (32L, 48L, 64L) so a = 32/48L, b = 64L. At lower capacities it might use different flash, for example the 256GB SM951 utilizies 2D/planar while the higher capacities use 3D. OEM drives tend to have different, optimized firmware, so performance will not be the same |- | <!--Brand-->Samsung 840 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Samsung 840 EVO | <!--Model-->MZ-7TE120 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 |- | <!--Brand-->Samsung PM851 2.5in sata | <!--Model-->MZ-7TE5120 P/N MZ7TE512HMHP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Samsung 850 EVO | <!--Model-->MZ-75E120, MZ-75E500 (P/N MZ7LN500) to MZ-75E4T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 Samsung MGX controller (S4LN062X01) up to 500GB capacities whilst Samsung MEX controller (3-core) beyond - Samsung TLC 3D V‐NAND 48 and later 64 layers and possibility of 256MB, 512MB or 1GB LPDDR2-1066 DRAM chip - |- | <!--Brand-->Samsung 850 PRO | <!--Model-->MZ-7KE1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung PM871a 2.5 inch sata | <!--Model-->MZ-7LN512A P/N MZ7LN512HMJP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung PM883 1.92TB | <!--Model-->MZ-7LH1T90 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - - Samsung MJX Maru (S4LR030) - 1gb LPDDR4-1866 dram - |- | <!--Brand-->Samsung 860 EVO | <!--Model-->MZ-76E1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung 860 EVO PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 860 QVO | <!--Model-->MZ-76Q1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 870 QVO 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - MKX 8-channel controller |- | <!--Brand-->Samsung 870 EVO | <!--Model-->MZ-7LN56F, MZ-77E1T0 P/N MZ7L31TOHBLB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 beware of bad batch early death - uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand-->Samsung PM871b | <!--Model-->MZ7LN256HCHP-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Sandisk Ultra 3D/Extreme Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 SandForce SF-2281 dram |- | <!--Brand-->Sandisk Ultra Plus | <!--Model-->SDSSDHP-256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell SS889175 processor with SanDisk's 19nm NAND and 128MB Samsung DDR2 DRAM chip |- | <!--Brand-->Sandisk Z300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Marvell 88SS9188 Marvell 88SS9187 with SanDisk 64Gbit 19nm MLC - |- | <!--Brand-->Sandisk x300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Sandisk x300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk Plus | <!--Model-->SDSSDA-240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 pseudo SLC cache dramless |- | <!--Brand-->Sandisk Z400s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - Silicon Motion SM2246XT DRAM-less - budget end of market - |- | <!--Brand-->Sandisk x400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 4 NAND packages and marvell controller 88ss1074 on blue pcb - 512MB DDR3L-1600 Micron DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Seagate BarraCuda Q1 SSD | <!--Model-->ZA240CV10001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 dramless A55 started with the Phison S10 but later the S11 i.e. Phison PS3111-S11-13 controller and 96-layer TLC NAND flash memory with a pseudo-SLC cache - |- | <!--Brand-->Silicon Power Ace A55 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand-->sk hynix | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 sandforce controller - |- | <!--Brand-->sk Hynix SH910A | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Link_A_Media (LAMD) controller with eight 256Gbit H27QEGDVEBLR NAND 20nm hynix MLC - SK hynix H5PS1G83JFA DRAM - |- | <!--Brand-->sk Hynix SC300 | <!--Model-->HFS256G32MND-3210A, HFS256G32MND-3312A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - red strip around edges - 8-channel controller SK hynix LM87810AA-A0 with DDR2 buffer chip and four pieces of 16nm hynix MLC NAND - |- | <!--Brand-->Sk Hynix Canvas SL300 series 2.5in SSD *3110A SL301STD *3210A *3300A *3310A | <!--Model-->HFS500G32TND, HFS256G32TNE, HFS128G32TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC - consumer line red in corners - SK hynix LM878100AA (HFS256G32MND-3312A) later SH87820BB and NAND 16nm hynix TLC - 256mb dram |- | <!--Brand-->Sk Hynix Canvas SC3 series 2.5in SSD *N1A0A , , *N1A1A *N1A2A SC308STD, *N2A0A , , SC311STD | <!--Model-->HFS512G32TNF-N2A0A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - red in corners - no dram and no SLC cache - Hynix ex Link_A_Media Devices (LAMD) SH87820BB 2c but poor mixed workload ability MLC - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team EX2 GX2 Elite QX | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->TEAMGROUP AX2 2.5 Inch SATA III Solid State Drive SSD | <!--Model-->T253A3512G0C101, T253A3001T0C101, T253A3002T0C101, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 3D NAND TLC |- | <!--Brand-->TeamGroup TF Vulcan Z 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dramless smi2259xt 128L tlc nand - |- | <!--Brand-->TeamGroup T-Force Vulcan ZQLC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram-less smi2259xt qlc 144L nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Topesel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend 220S 2.5in | <!--Model-->TS120GSSD220S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 3D TLC without dram |- | <!--Brand-->Transcend SSD230S 2.5in | <!--Model-->TS256GSSD230S TS512GSSD230S TS1TSSD230S TS2TSSD230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 3D TLC NAND with DRAM Cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Viathan | <!--Model-->S001T3V | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red SA500 NAS | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->WD Blue SA510 250Gb to 4Tb | <!--Model-->WDS400T3B0A WDS200T3B0A WDS100T3B0A WDS500G3B0A WDS250G3B0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - |- | <!--Brand-->Western Digital WD Green SSD 2.5" | <!--Model-->WDS240G1G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Green 200Gb to 2Tb | <!--Model-->WDS200T2G0A WDS100T3G0A WDS480G2G0A WDS240G2G0A WDS120G2G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - cheap and slow ssd - |- | <!--Brand-->WD SA530 | <!--Model-->SDASB8Y-256G SD9SB8W, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->[https://www.xray-disk.com xraydisk] 2.5 inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> from the manufacturer only - Phsion/SMI(2258XT)/Realtek/Yeestor |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Xum | <!--Model-->hx256gssdsata3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Yottamaster | <!--Model-->Y3000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCie 3.0 |- | <!--Brand-->Yottamaster | <!--Model-->Y7000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCIe 4.0 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |} === SATA M.2 (M and B key) === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 2280 Sata | <!--Model-->AXNS381E-128GM-B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S201 m.2 sata 2280 | <!--Model-->S201 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot FN203 m.2 sata (oldtan, twipps, teexin aka Shenzhen Pingfan "Ordinary" Road Technology Co., Ltd) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 lifespan not long Maxio MAP + YMTC 128L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Foresee (Shenzhen Longsys) | <!--Model-->YSM80CD-128G YSDE128G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 88nv1120-bt22 T3WU030 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral 2242 120G | <!--Model-->INSSD120GM242 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral M.2 2280 | <!--Model-->INSSD256GM.26M2280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral 256GB/512GB/1TB/2TB | <!--Model-->INSSD1TM280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 netac rebrand - no dram cache - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel Pro ‎545S 2280 | <!--Model-->SSDSCKKF256G8H | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> no dram, TLC nand |- | <!--Brand-->Intel | <!--Model-->SSDSC2KF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intenso M.2 internalSSD SATA III 1 TB | <!--Model-->Top | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A400 m.2 | <!--Model-->SA400M8/240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 entry level ssd 4 x FH64B08UCT1-60 64G - |- | <!--Brand-->Kingston | <!--Model-->RBU-SNS8350DES3128GP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston V300 | <!--Model-->SV300S3505AG | <!--Work MSDos-->{{yes}} | <!--Work GPT--> | <!--Tested under-->Nightly Build 2014-09-18 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON SATA 128GB | <!--Model-->CV3-8D128-11 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON | <!--Model-->CV1-8B256-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lite-On | <!--Model-->L8H-256V2G-HP L8H-128V2G-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 2016 nanya nt5c864m16fp-dh |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LSI | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 SF37000 controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model-->M550 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell 88SS9189 SATA controller |- | <!--Brand-->Micron M600 enterprise m.2 sata up to 512GB | <!--Model-->MTFDDAV256MBF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 Marvell 88SS9189 SATA controller, DRAM chip 256MB 533MHz LPDDR2, NAND for the 256GB drive MT29F1T08CQCCBG2-10:C 16nm MLC NAND each 128GB package |- | <!--Brand-->MICRON 1100 M.2 SATA 6Gb/s 2280 | <!--Model-->MTFDDAV256TBN HP P/N 903109-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Orico Y20M-2242 | <!--Model-->Y20M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->PNY | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung PM841 M.2 sata3 2280 | <!--Model-->MZ-NTD2560/0L9 MZNTD256HAGL-000L9 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung CM871 Rev 0 | <!--Model-->MZNLF128HCHP-000H1 MZ-NLF1280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM871a m.2 Sata | <!--Model-->MZNLN256HMHQ, NLN512A P/N MZNLN512HMJP-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC |- | <!--Brand-->SAMSUNG PM871b | <!--Model-->MZNLN128HAHQ-000H1, MZNLN256HAJQ MZ-NLN256F MZ-NLN256C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM881 | <!--Model-->MZ-NLH1280 MZNLH128HBHQ-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SanDisk X300 M.2 sata 2280 80mm SSD Solid State Drive | <!--Model-->SD7SN6S-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk X400 SSD M.2 sata 2280 | <!--Model-->SD8SN8U-128G-1006, SD8SN8U-256G-1006, SD8SN8U-512-1006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 SSD controller Marvell 88SS1074 four channel supports variety of NAND and up to 512MB DDR3L-1600 Micron DRAM cache - |- | <!--Brand-->SanDisk X600 M.2 SSD Solid State Drive | <!--Model-->SD9SN8W-128G-1006 SD9TN8W-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SANDISK X110 DELL 6T4HK M.2 2260 | <!--Model-->SD6SP1M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix SC300 | <!--Model-->SC308M280S HFS128G39TND | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 SH87820BB controller - No dram buffer - multi-level cell (MLC) NAND |- | <!--Brand-->SK HYNIX | <!--Model-->SC311 HFS256G39TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK HYNIX | <!--Model-->SC401 HFS256G39TNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 M.2 sata 2280 | <!--Model-->A55 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TEAMGROUP Team MS30 SSD M.2 Sata 2280 | <!--Model-->TM8PS7001T0C101 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Toshiba RC100 (retail version of BG3) | <!--Model-->KBG30ZMV256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Toshiba HG6 m.2 | <!--Model-->THNSNJ512GDNU THNSNJ512G8NY, THNSNJ256GDNU THNSNJ256G8NY, THNSNJ128GDNU THNSNJ128G8NY, THNSNJ256GVNU THNSNJ128GVNU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TOSHIBA SSD M.2 2280 256GB | <!--Model-->KSG50ZMV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand-->Kioxia (Toshiba) BG6 | <!--Model-->KSG60ZMG256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend | <!--Model-->400 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend M.2 SSD 2242 TS32GMTS400S TS64GMTS400S TS128GMTS400S | <!--Model-->400S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> DDR3 dram cache and mlc nand |- | <!--Brand-->Transcend | <!--Model-->M.2 SSD 600 (2260), M.2 SSD 800S (2280) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> mlc nand |- | <!--Brand-->Transcend M.2 SSD 2242 TS120GMTS420S TS240GMTS420S TS480GMTS420S | <!--Model-->420S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> can run hot slc cache |- | <!--Brand-->Transcend M.2 SSD 2242 TS256GMTS430S TS512GMTS430S | <!--Model-->430S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache - 3d tlc nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS120GMTS820S TS240GMTS820S TS960GMTS820S | <!--Model-->820S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS256GMTS830S TS512GMTS830S TS1TMTS830S TS4TMTS830S | <!--Model-->830S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 120GB to 480Gb | <!--Model-->WDS480G2G0B WDS240G2G0B WDS120G2G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 made in malaysia |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 240Gb to | <!--Model-->WDS240G3G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 made in |- | <!--Brand-->WD Blue SA510 M.2 SATA 250Gb to 2Tb | <!--Model-->WDS200T3B0B WDS100T3B0B WDS500G3B0B WDS250G3B0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red 500GB 1TB 2TB | <!--Model-->SA500 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM610 m.2 sata | <!--Model-->SSS0R27339, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === mSATA SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fangxiang S301 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingchuxing | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model-->INSSD256GMSA MO-300 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc 3d nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron enterprise | <!--Model-->M600 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico ZH-10 ZH10 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Samsung 840 EVO 1.8inch msata | <!--Model-->MZ-M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung 850 EVO 1.8in | <!--Model-->MZ-M5E120BW, MZ-M5E250BW, MZ-M5E500BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM851 1.8" msata | <!--Model-->MZ-MTE256D P/N MZ-MTMTE256HMHP, MZ-MTE1T00, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 860 EVO 1.8inch msata | <!--Model-->MZ-MM6E250BW, MZ-M6E500BW, MZ-M6E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Transcend TS64GMSA370S | <!--Model-->MSA370S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC nand |- | <!--Brand-->Transcend TS64GMSA230S | <!--Model-->230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3d tlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === SATA 2.5inch Laptop Hard Disks === ====7mm==== {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP628230-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP552605-01 250Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP693440-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HGST Hitachi Z5K320 Z5K500-500 Z5K100 series * 2013 HTS545050A7E380 HTS * 2015 HTS545050A7E680 HTS | <!--Model-->HTS 320GB 500Gb 1Tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->HGST Hitachi Z7K320 Z7K500 series | <!--Model-->HTS725050A7E630 320Gb HTS725050A7E635 500Gb 7200rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> avoid if it does not have the DCM code |- | <!--Brand-->HGST 1T 5400rpm | <!--Model-->HTS541010B7E610 | <!--Work--> | <!--Tested under-->2017 128m cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Seagate Momentus Thin | <!--Model-->ST500LT012 ST320LT012. ST250LT012 500Gb 320gb 250gb 2014 5.4K rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Seagate Thin SSHD 5400RPM Sata 2.5" | <!--Model-->ST500LM000 500GB, ST500LM001, ST500LM020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 up to 64M cache and with 8GB NAND Flash |- | <!--Brand-->Seagate MomentusThin-B Video 2.5 HDD * 2014 * 2015 * 2016 * 2017 | <!--Model-->ST500VT000 500GB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->SEAGATE Baracuda 2.5 5400 | <!--Model-->ST2000LM015 (2Gb), ST1000LM049 (1Tb), ST500LM030 (500Gb) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Seagate Barracuda Pro | <!--Model-->ST1000LM048 ST1000LM035 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> up to 128MB cache |- | <!--Brand-->SEAGATE FireCuda Compute 2.5 | <!--Model-->ST500LX025 ST1000LX015 ST2000LX001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 8GB NAND Commercial Multilevel Cell (cMLC), 128MB buffer and 5400-RPM spindle speed up to 140 MB/s |- | <!--Brand-->Toshiba 2.5in | <!--Model-->MQ04ABF100 1TB 5400 RPM 2018 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TOSHIBA MQ01ACF | <!--Model-->MQ01ACF050 500GB 7200rpm 2020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->western digital wd blue 500G 8meg cache 5400rpm * 2014 Rev T0 * 2015 Rev T1 | <!--Model-->wd5000lpvx | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012-2015 sequential 2MB block transfers 110 MB/s reading and writing - |- | <!--Brand-->Western Digital 2.5" WD Blue Slim | <!--Model-->WD10SPCX 1TB Nov 2016 | <!--Work MSDos-->{{Yes|hdd under partition table msdos/pc, boots on bios machines, will not on uefi machine}} | <!--Work GPT-->{{Unk|untested hdd under gpt partition protocol scheme, not booting on uefi}} | <!--Tested under-->AROS One 1.8 USB |- | <!--Brand-->Western Digital WD | <!--Model-->WD5000LUCX 500Gb 5400rpm 16mb cache Rev Y0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 2017 Malaysia |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} ====9.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->MHW2040BH | <!--Work--> | <!--Tested under--> 40gig |- | <!--Brand-->Fujitsu | <!--Model-->MHY2080BH | <!--Work--> | <!--Tested under--> 80gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHW2120B | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS541010A9E662 type TS5SAF100 | <!--Work--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Hitachi Travelstar 5K500.B-320 | <!--Model-->HTS545025B9SA02 HTS545032B9A300 HTS545040B9A300 HTS545050B9A300 250Gb 320Gb 400Gb 500Gb 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST 1TB 7200rpm | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung bought by Seagate late 2011 | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung Spinpoint with Seagate HD REV A (Jan 2014) | <!--Model-->ST1000LM024 | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand-->Samsung Spinpoint with Seagate 9.5mm * 2013 Rev A HN-M500MBB/I * 2014 Rev B HN-M500MBB/SP4 * 2015 Rev B HN-M500MBB/P4C | <!--Model-->ST500LM012 (500M) | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Momentus 5400.3 | <!--Model-->ST9160821AS | <!--Work--> | <!--Tested under--> 160gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SSHD 1t | <!--Model-->ST1000LM014, ST1000LM028, ST1000LM015 | <!--Work--> | <!--Tested under--> 8g nand flash |- | <!--Brand-->Seagate SSHD 1T | <!--Model-->ST1000LX001 | <!--Work--> | <!--Tested under--> 32G nand flash |- | <!--Brand-->Toshiba | <!--Model-->MK2555GSX HDD2H24 | <!--Work--> | <!--Tested under--> 250g 5400rpm |- | <!--Brand-->Toshiba | <!--Model-->MK5065GSX - 500GB 5400RPM SATA 3Gb/s 8MB Cache 2.5-Inch | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MKxx59GSXP, eg Toshiba MK6459GSXP 640GB 2011 | <!--Work-->{{yes}} | <!--Tested under-->Icaros 2.2 with uses Advanced Format (AF) in 4,096 bytes per sector. Compatibility with legacy, 512 bytes through AF emulation techniques, called 512e |- | <!--Brand-->Toshiba (2013 to 2016) | <!--Model-->MQ01ABD100 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba (2015 to 2020) *2013 *2014 *2015 AA50/AX0D5A *2016 AA60/AX0E1A * *2017 AGM AA01/AX002V *2018 AGS AA70/AX0G1A *2020 AA71/AX0G1A | <!--Model-->MQ01ABD050 500meg | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MQ04ABF100 1TB 5400 RPM 2013 | <!--Work-->{{Yes}} | <!--Tested under--> |- | <!--Brand-->TOSHIBA | <!--Model-->MQ04ABD200 2TB 5400 RPM 128MB Cache SATA 6.0Gb/s | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD7500BPVX 2013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WESTERN DIGITAL 1TB 2.5" SATA DRIVE 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-80JC3T0 (OCT 2014) | <!--Work--> | <!--Tested under--> , uses Advanced Format (AF) |- | <!--Brand-->WDC Western Digital Blue 1TB SATA 2.5" Hard Drive 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-08JC3T6 (Jun 2017) | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD10JPCX 1Tb | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital * 2019 | <!--Model-->WD10JUCT 1TB (1000GB) 2019 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WD Western Digital Scorpio Black * 2010 * 2014 | <!--Model-->WD5000BEKT, WD5000BPKX-22HPJT0, WD5000BPKT, | <!--Work--> | <!--Tested under--> 16m cache, 7200rpm thailand then malaysia |- | <!--Brand-->WD Western Digital Black * 2016 | <!--Model-->WD2500LPLX, WD3200LPLX, WD5000LPLX SMR: WD5000LPSX, WD10SPSX | <!--Work--> | <!--Tested under--> 32m cache , 7200rpm SATA-III malaysia |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA 2.5in NON-Laptop Hard Disks === ====11mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu 160GB 250GB 300GB | <!--Model-->MHX2160BT, MHX2250BT, MHX2300BT | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model-->TP00640GB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====12.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====15mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 1TB IBM System X 15mm 2.5" SATA | <!--Model-->ST91000640NS 81Y9731 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT10N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 5v 12.7mm |- | <!--Brand-->Hitachi LG | <!--Model-->GT20L | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009/2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model-->GT30N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT50N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT90N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 5v 12.7mm |- | <!--Brand-->HP | <!--Model-->TS-L633 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->HP | <!--Model-->GU70N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 5v 1.8A 9.5mm |- | <!--Brand-->HP | <!--Model-->GUD0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.8A 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->GTA0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic | <!--Model-->Uj870a Uj880 UJ890 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->UJ8A0 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic MATSHITA 12.5mm SATA DVD burner inside Asus K53S | <!--Model-->UJ8B0 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 12.7mm 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8B1 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8C0 UJ8C1 UJ8C2 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.6a |- | <!--Brand-->Panasonic | <!--Model-->UJ8D0 UJ8D1 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 |- | <!--Brand-->Panasonic | <!--Model-->UJ8E2Q | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 9.5mm |- | <!--Brand-->Panasonic | <!--Model-->UJ8FB | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5a 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->DS-8A5LH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm |- | <!--Brand-->HP | <!--Model-->DU-8A6SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5A 9.5mm |- | <!--Brand-->Philips and LiteOn | <!--Model-->DS-8A8SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5a 12.7mm |- | <!--Brand-->PLSD | <!--Model-->DS-8A9SH DS8A9SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7561S, AD-7560S Thickness: 12.7 MM Interface: SATA | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 |- | <!--Brand-->Sony | <!--Model-->AD-7580s, AD-7581s, AD-7583s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7585H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm cleaning the laser lens inside the drive with a liquid lens cleaner. Also check the lens carrier slides freely from one extreme to the other inside the drive without sticking |- | <!--Brand-->Sony | <!--Model-->AD7590s, AD-7591s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7700s, AD-7710h, AD-7701H, AD-7703S | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7760H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5A 12.7mm |- | <!--Brand--> | <!--Model-->AD-7711H AD-7740H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->Toshiba Samsung | <!--Model-->SN-S208B Ver BB Rev 00 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm |- | <!--Brand-->Toshiba TSSTCorp Samsung | <!--Model-->SN-S083C Ver C Rev 03 /BEBE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.5a 12.7 mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} === [https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data SATA Desktop 3.5inch Hard Disks] === Datasheets with the SMR (overlapped packing Shingled Magnetic Recording) and CMR (faster Conventional Magnetic Recording) parts <pre> WD: https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/internal-drives/wd-blue-hdd/product-brief-western-digital-wd-blue-pc-hdd.pdf Seagate: https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/datasheets/pdfs/3-5-barracudaDS1900-14-2007US-en_US.pdf Toshiba: https://storage.toshiba.com/docs/support-docs/P300-SalesSheet_English_Web_r2.pdf </pre> {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Seagate Barracuda 7200.9 | ST3160812AS, ST3160212AS | {{yes}} | Icaros Desktop 1.5.2 - Capacity: 160 GB - Speed: 7200RPM - Cache: 8 MB - Interface: SATA2 |- | <!--Brand-->Seagate Barracuda LP Green 5400rpm | <!--Model-->ST1000DL002 1TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SkyHawk Surveillance HDD ST4000VX000 Series | <!--Model-->ST4000VX013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Baracuda Compute | <!--Model-->ST500DM009 2F110A-500 / 02PKVY / 2PKVY (500m), | <!--Work--> | <!--Tested under--> - SATA III (6Gb/s) - Format 3.5" - 32MB Cache |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate CMR | <!--Model-->ST1000DM010 ST500DM009 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 2TB SMR | <!--Model-->ST2000DM008 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SMR | <!--Model-->ST8000DM004 ST6000DM003 ST4000DM004 ST3000DM007 ST2000DM005 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 5400rpm | <!--Model-->HDWD220 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 7200rpm | <!--Model-->HDWD320 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba P300 CMR | <!--Model-->HDWD130XZSTA HDWD130UZSVA, HDWD120XZSTA HDWD120UZSVA, HDWD110XZSTA HDWD110UZSVA | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital 2010 | <!--Model-->WD20EARS Green 2TB 5400rpm 64mb cache | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD20EFRX WD40EFRX 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital | <!--Model-->WD4002FFWD | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD80EAAZ WD80EAZZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD20EARZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD40EZAZ, WD60EZAZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD20EARZ, WD20EZAZ - 2TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD40EZAX - 4TB, WD60EZAX - 6TB, WD80EZAX - 8TB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- |} ==PATA== === IDE Desktop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | M1624TAU | {{yes}} | Icaros Desktop 1.5.2 |- | IBM | DHEA-38451 | {{yes}} | Icaros Desktop 1.5.2 |- | Samsung | SP40A2H | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST3160215ACE | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST32122A | {{maybe}} | Icaros Desktop 1.5.2 |- | Western Digital | WD102AA | {{yes}} | Icaros Desktop 1.5.2 |- | Western Digital | WD200 | {{maybe}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Laptop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHV2040AH | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->HGST Hitachi Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Toshiba | MK2011GAP | {{yes}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | Compaq | CR-594-BCQ | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8322B(CP1) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8484B(AM2A) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | LTN-485 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Creative | CD220E | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Hitachi-LG | GDA-4120B | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | LG | CRD-8400B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Lite-On | LTN486S | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Mitsumi | CRMC-FX4830T | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | CDR-1700B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | DV-5800A | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | ND-2100A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | NEC | NR-7900A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | Philips | DVD8631 | {{no}} | {{no}} | Icaros Desktop 2.2 |- | Samsung | SC-148 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SCR-2030 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SM-348B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU601 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU611-25 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Toshiba | SD-M1202 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |} === IDE Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->H-L Hitachi LG | <!--Model-->GCC-4244N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2006 |- | Hitachi-LG | GCCT10N | {{yes}} | {{Maybe|FryingPan WRITE seems to have no problem with data sections (track 1) - combos with audio sections (track 2) white screens aros eventually}} | AspireOS Xenon with 25th Jan 2014 self update kernel |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Philips | SDR089 | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | TSSTcorp | TS-L462C TS-L462D | {{yes}} | {{unk}} | 2005 Icaros Desktop 2.2 |- | TSSTcorp | TS-L632H | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Sony | DW-Q58A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | Sony Optiarc | AD-7540A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | <!--Brand-->Sony | <!--Model-->Optiarc DVD RW AD-7560A IDE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7590A | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} == SCSI == {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} NVMe accepts up to 64,000 queues with up to 64,000 commands each. 23qhqklww6863oco6d6ctmwp43yxscy 4634261 4634260 2026-05-05T11:47:00Z Jeff1138 301139 4634261 wikitext text/x-wiki {{ArosNav}} ==Introduction== AROS supports hard disks and optical drives attached to several interfaces: * [[#NVMe M.2 SSD (M key)]] on the pci-e bus * [[#SATA]] aka Serial ATA or AHCI (IDE compatibility mode used in most cases) * IDE (also known as ATA, [[#PATA]] or Parallel ATA) * USB * SCSI limited ==PCI-e== ===NVMe M.2 SSD (M key)=== *Controller and firmware *DRAM better having if heavy workloads but not necessary for gaming *Cache like SLC HMB techniques *NAND (Main storage area with MLC, TLC or QLC versions of varying life expectancy) SSDs, USB flash drive, SD and Micro SD Cards have a limited amount of write cycles, therefore guaranteed to fail randomly and suddenly at any time. All SSDs are prone to corrupt firmware due to poor quality NAND where both the data and the firmware resides. The drive tends to go read only when too many errors occur before complete failure. That is up to 10 years for things like memory cards and USB sticks. In general, unless there is a firmware design issue, cheap materials used, stress like bending or overheating causing cold solder joints, an SSD can last a long time if minimal writing activity takes place but eventually if flash isn't written to, it degrades. Catch 22. Dram and cache are not the same thing. Dram stores the ssds indexes and metadata for faster data retrieval and wear leveling. The cache keeps part of the nand memory as SLC storage which can be written to faster. Basically all ssds will have a dynamic SLC cache where it will decrease as the drive fills up. Cache controller designs that are DRAM less use the internal SRAM cache in the controller to cache the NAND mapping table. It just requires a different mapping table design since SRAM caches are much smaller than DRAM. Ultimately the mapping table is still stored in NAND. General rule of thumb: the cheaper an SSD, the higher the likelihood it uses lower quality flash chips so sudden failing NAND, problematic controller chips (e.g. SandForce), outsourced firmware. Generic brand like old SP, Corsair or Crucial may be recoverable whilst major brands Samsung, Intel and Western Digital are impossible due to firmware encryption and customizations. Recommend sticking with older Silicon Motion or Phison controllers if possible. A ssd isn't good because it has dram or bad because it doesn't. Other things should be taken into account like sustained writes so check the TPU write intensive usage See [https://www.techpowerup.com/ssd-specs/ here] for more information {| class="wikitable" width="100%" ! width="15%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="30%" |Tested Distribution |- | <!--Brand-->Unnamed | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 to - SM2259XT2 SM2263XT MAS0902 MAP1202 YS9082HP RM1135 RTS5765 PS3111 |- | <!--Brand-->Unnamed OEMs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 to date - Realtek RTS5765/66 controller + Micron 96L (B27A) |- | <!--Brand-->Acer Predator GM7 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Acer drives built by Biwin, that also supplies HP, Maxio MAP1602A no DRAM so HMB, YMTC 128L TLC, |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 NVME IM2P33F8, IM2S3168 SSD | <!--Model-->IM2P33F8-512GD | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - industrial 12L 3D TLC NAND flash Supports LDPC ECC, RAID Engine, and SLC Cache End-to-End (E2E) Data Path Protection with Host Memory Buffer (HMB) i.e. DRAMless |- | <!--Brand-->ADATA XPG SX8200 Pro M.2 nvme | <!--Model-->ASX8200PNP1TTC | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 NVM Express 1.3 SN2262G later SN2262EN chipset - |- | <!--Brand-->ADATA 256GB GEN4 x4 NVMe PCIe M2 2230 SSD | <!--Model-->SM2P41C3-256GC2 DP/N 0KM1Y6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 consumer |- | <!--Brand-->ADATA XPG GAMMIX S50 Lite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Silicon Motion SM2267XT dramless |- | <!--Brand-->ADATA XPG ATOM 50 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Innogrit RainierQX IG5220 |- | <!--Brand-->Adata Legend 710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->ADATA Legend 900 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->BiWin PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Innogrit IG5216 controller, no DRAM so HMB which appears to be the standard - |- | <!--Brand-->BiWin NV7200 PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SM2263XT |- | <!--Brand-->Biwin NV7400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force LE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Corsair Force Series MP500 MP510 M.2 NVMe PCIe Gen 3 x4 SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 PS5012-E12-27 from Phison, 64-layer TLC Toshiba BiCS flash, may have dram cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 on DRAM DDR4 with Micron 96L QLC - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Corsair MP600 Elite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E16 and Bics DDR4 DRAM buffer and TLC-based with SLC-mode cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair MP600 Pro XT, PRO LPX, PRO NH PCIe4 | <!--Model-->CSSD-F1000GBMP600ECS Elite, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 DRAMless SSD controller Phison PS5026-E26, BiCS6 162L QLC NAND |- | <!--Brand-->Corsair MP600 Core XT | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison and Bics QLC-based with SLC-mode cache - |- | <!--Brand-->Corsair MP700 Pro PCIe 5.0 | <!--Model-->CSSD-F1000GBMP700PNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial P1 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 QLC NAND but a controller with a DRAM cache - |- | <!--Brand-->Crucial P2 M.2 2280 Gen3 x4 NVM-express | <!--Model-->CT1000P2SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 dram-less Phison PS5013-E13-31 on 96-layer QLC NAND - |- | <!--Brand-->Crucial P3 Plus M.2 2280 | <!--Model-->CT1000P3PSSD8 CT2000P3PSSD801 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with Host Memory Buffer HMB tech to use a small bit of system RAM as DRAM cache and Micron 176-layer QLC NAND - |- | <!--Brand-->Crucial P3 M.2 nvme SSD | <!--Model-->CT2000P3SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron QLC (N48R) - |- | <!--Brand-->Crucial P5 m.2 nvme PCIe 4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 runs hot - Crucial NVMe with DRAM LPDDR4 and Micron 96L TLC |- | <!--Brand-->Crucial P5 Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 some have DRAM cache |- | <!--Brand-->Crucial T500 Gen4.0 nvme 2.0 | <!--Model-->CT1000T500SSD8, CT2000T500SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison PS5025-E25 with micron B58R 232-layer 3D TLC NAND and Micron LPDDR4 DRAM cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Crucial T700 Gen5 SSD | <!--Model-->CT1000T700SSD3, CT2000T700SSD3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 SSD controller Phison PS5026-E26, Micron 232-layer NAND with no dram as standard - |- | <!--Brand-->Crucial P310 M.2 2280 NVMe PCIe Gen4 SSD | <!--Model-->CT2000P310SSD801 (2Tb), | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 DRAM-less Phison E27T Micron 232-layer NAND - |- | <!--Brand-->Crucial T705 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 dramless Phison SSD controller |- | <!--Brand-->Crucial T710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 SMI SM2508 SSD controller dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN605 PCIe Gen3 x4 interface, NVMe 1.3 support | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Ediloca EN660 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN760 PCIe Gen4 x4 M.2 NVMe 1.4 interface | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 gets hot |- | <!--Brand-->Ediloca EN870 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 no dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca EN855 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S500 pro PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 MaxioTech MAP1202A-F1C with YMTC 128L and pseudo-SLC cache |- | <!--Brand-->Fanxiang S660 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S880/R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Fanxiang S770 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX550 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Fikwot FN501 Pro m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->FIKWOT FN950 FN955 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 MAP1602 (at 1600 MT/s) flash YMTC TLC no dram |- | <!--Brand-->Fikwot FX991 m.2 nvme | <!--Model-->FW-FX991-2TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FN960 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Fikwot FN970 m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Geil ZEN ITH m.2 nvme | <!--Model-->S3-240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Gigabyte Aorus Gen4 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash - DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Gigabyte Aorus 10000 PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->HP EX950 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HP FX900 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dram less |- | <!--Brand-->HP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Integral M2 Series NVME M.2 2280 PCIe Gen 3x4 | <!--Model-->INSSD500GM280NM2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Inland Professional TLC E12S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E18 |- | <!--Brand-->Inland Gaming performance Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash |- | <!--Brand-->Inland TD510 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM DDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->intel SSD Pro 7600p Series M.2 80mm 2280 PCIe 3.0 x4, 3D TLC | <!--Model-->SSDPEKKF512GB, SSDPEKKF256G8L, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel 660p m.2 nvme | <!--Model-->ssdpeknw010tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 SMI SM2263 controller with 1GB DRAM cache and 1TB of Intel QLC NAND similar to crucial P1 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] 670p | <!--Model-->SSDPEKNU010TZ | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 256 MB DDR3L cache and 12-140 GB SLC-Cache QLC NAND |- | <!--Brand-->Intel P4511 m.2 nvme PCIe3.1 x4 22110 110mm | <!--Model-->SSDPELKX020T8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 very long |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A1000 NVME PCIE M2 2280 SSD | <!--Model-->SA1000M8/480G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Kingston A2000 NVME PCIE M2 2280 SSD | <!--Model-->SA2000M8/250G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->Kingston KC3000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] PS5018-E18 PCIe 4.0 x4 NVMe controller and Micron’s 176L TLC NAND flash - |- | <!--Brand-->Kingston NV1 m.2 nvme pcie | <!--Model-->SNV1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 entry-level consumer DRAMless Phison E13T or Silicon Motion 4-channel SM2263XT - one brand TLC up to 1Tb and QLC after - |- | <!--Brand-->Kingston NV2 | <!--Model-->SNV2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 entry-level, first SMI SM2267XT or Phison E19T and later SMI SM2269XT or Phison E21T with various flash memory |- | <!--Brand-->Kingston FURY Renegade m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] Phison E18 controller, Micron 176L nand and ddr4 dram - |- | <!--Brand-->Kingston NV3 | <!--Model-->SNV3S/500G, SNV3S/1000G, SNV3S/2000G, SNV3S/4000G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 entry-level, SMI SM2268XT2 or Phison E27T controller with BiCS6 TLC or QLC flash - dramless so hmb - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia (Toshiba) XG4? M2 2280 NVMe PCIe SSD | <!--Model-->THNSF5512GPUK, THNSN51T02DUK, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 Phison has done custom controller work for Kioxia, and Kioxia has also worked with SMI and InnoGrit (the latter more recently). Kioxia label their controllers as their own but these are largely rebadged. |- | <!--Brand-->Kioxia (Toshiba) XG5 for Data Centres | <!--Model-->KXG5 KXG50ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 nanya ddr3 dram? with 64-layer BiCS 3D flash memory |- | <!--Brand-->Kioxia XG6 OEM m.2 nvme | <!--Model-->KXG60ZNV512G, KXG60ZNV1T02, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 TC58NCP090GSD with DRAM NANYA LPDDR3 and Toshiba BiCS FLASH 96-layer 3D TLC - |- | <!--Brand-->Kioxia (Toshiba) BG4 m.2 nvme | <!--Model--> *KBG40ZNS128G, KBG40ZNS256G, KBG40ZNS512G, KBG40ZNS1T02 *KBG40ZNT256G, *KBG40ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - no dram but NVMe's Host Memory Buffer (HMB) i.e. portion of the system's RAM for caching - Toshiba's 96-Layer BiCS FLASH - seems Windows UASP driver and the JMS583 chipset interacts badly with the Kioxia BG4 - early firmware upgrade to prevent overheating hot - |- | <!--Brand-->Kioxia XG7 | <!--Model-->KXG70ZNV1T0G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 - might need firmware update on early 2tb 4tb versions - controller with sk hynix dram and tlc nand |- | <!--Brand-->KIOXIA EXCERIA PLUS G2 SSD series PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5012-E12S-32 aka TC58NC1201GST 4-channel controller along with KIOXIA proprietary 96-layer 3D TLC and "MG2h" version has BiCS4.5 which is faster than launch BiCS4 - - |- | <!--Brand-->Kioxia XG8 OEM m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 TC58NC0L1XGSD with DRAM LPDDR4 and 112-Layer Kioxia BiCS5 TLC - |- | <!--Brand-->Kioxia (Toshiba) BG5 | <!--Model-->KGB50ZNV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 HMB buffer |- | <!--Brand-->Kioxia (Toshiba) BG6 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless |- | <!--Brand-->KIOXIA EXCERIA PLUS G3 SSD series PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 has hmb, like most dram-less nvmes KIOXIA |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar 1TB SSD M.2 NVME 1.4 Gen3x4 M.2 2280 | <!--Model-->NM610Pro | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Lexar NM620 *IG5216 (worse?) not great original 96L *MAP1202 YMTC up to 232L, or 176L Micron, TLC for the 1TB | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 a few versions all DRAM-less, |- | <!--Brand-->Lexar NM790 SSD M.2 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Maxio MAP1602 no DRAM so HMB with 232-Layer YMTC TLC |- | <!--Brand-->Lexar m.2 nvme | <!--Model-->EQ790 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Maxio MAP1602, no DRAM so HMB, Flash Memory 232-Layer YMTC TLC, |- | <!--Brand-->Lexar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Liteon M.2 NVME 512GB SSD 2280 | <!--Model-->CAZ-51282512-Q11 DP/N 0K64PG | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI controller |- | <!--Brand-->Micron 2200S m.2 nvme 2200 series | <!--Model-->MTFDHBA256TCK, MTFDHBA512TCK | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 for a time, Micron controller with 64L TLC 3D Nand [https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=3jg3g BSOD occurred as CRITICAL_PROCESS_DIED] before self applied firmware [https://support.lenovo.com/us/en/downloads/ds119265-nvme-solid-state-drive-firmware-update-utility-for-windows-10-64-bit-thinkpad apparently it is related to the power management that disconnects the Micron SSD] |- | <!--Brand-->Micron 2300 m.2 nvme Gen 3 x4 | <!--Model-->MTFDHBA256TDV P/N M02626-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Micron 3400 M.2 NVME SSD Gen4 | <!--Model-->MTFDKBA512TFH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no cache |- | <!--Brand-->Micron 2450 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 E19T |- | <!--Brand-->Micron 2600 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison's PS5029-E29T SSD controller with Micron 276-layer G9 QLC NAND in a DRAMless - Adaptive Write Technology (AWT) using various NAND modes (SLC, TLC, and QLC) as a dynamic cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium S270 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium M450 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV2000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico J10 J-10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Orico D10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Orico e3500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Orico O7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Patriot P300 m.2 nvme pcie 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Patriot Viper VP4300 Lite M.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS2230 Gen3 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->PNY CS2140 CS2342 Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Raydisk 1T 2280 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 no dram, Memory QLC Intel 144 layer. Chip Realtek |- | <!--Brand-->Raydisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket Nano 2242 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket 4.0 m.2 nvme | <!--Model-->SB-2130-512, SB-2280-1TB, SB-Rocket-NVME4-HTSK-2TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 4.0 PLUS m.2 nvme | <!--Model-->SB-RKT4P-1TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E1? controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Phison E25 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung PM951 m.2 nvme | <!--Model-->MZVLV1T | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 950 PRO PM961 M.2 2280 NVMe 1.3 PCI-Express 3.0 x4 | <!--Model--> *MZ-VKW5120 *MZ-VLW2560 MZVLW256HEHP-000L7, MZ-VLW5120, MZ-SLW1T00 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - possibly 512M LPDDR3 Samsung K4E4E324EE-ECCF cache - Polaris (S4LP077X01-8030) unit with Samsung 48-layer TLC V-NAND V3 flash Samsung K90MGY8S7M-CCK0 - |- | <!--Brand-->Samsung 960 Pro SM961 M.2 PCi-e NVMe SSD 2280 | <!--Model-->MZ-V6P1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 Polaris (S4LP077X01-8030) controller Samsung 48-layer multi-level cell (MLC) V-NAND, pseudo-SLC cache or LPDDR3-1866 Samsung K4E8E304EE-EGCF |- | <!--Brand-->Samsung PM981 2280 PCI-Express 3.0 x4 | <!--Model--> *Rev 0 MZ-VLB256A, MZ-VLB512A, MZ-VLB1T0A, *Rev 0 MZ-VLB2560, MZ-VLB5120 P/N MZVLB512HAJQ, MZ-VLB1T00, *Rev ? MZ-VLB256B, MZ-VLB512B, MZ-VLB1T0B, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache hybrid SLC Samsung’s TurboWrite - |- | <!--Brand-->Samsung PM981a 2280 PCI-Express 3.0 x4 | <!--Model-->MZ-VLB5120 P/N MZVLB512HBJQ-000L7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache |- | <!--Brand-->SAMSUNG PM991 NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ2560 MZVLQ256HBJD-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SAMSUNG PM991a NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ256B MZVLQ256HBJD-00BH1, MZ-9LQ256C, MZ-VLQ512B MZVLQ512HBLU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Samsung 970 EVO Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Samsung Phoenix on Samsung LPDDR4 dram and 2 Samsung 9x-layer V-NAND TLC |- | <!--Brand-->Samsung 980 EVO Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Samsung 980 Pro m.2 nvme | <!--Model-->MZ-V8P1T0BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 originally made in Korea ([https://semiconductor.samsung.com/consumer-storage/support/tools/ 2tb firmware issues] with versions starting with 3) and year later Vietnam - DRAM |- | <!--Brand-->Samsung 990 EVO m.2 nvme | <!--Model-->MZ-V9E2T0BW, MZ-V9E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo no DRAM so HMB Samsung 133-Layer TLC (V6P) and Samsung 133-Layer TLC (V6P) - |- | <!--Brand-->SAMSUNG PM9A1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model-->MZ-VL25120 MZVL2512HCJQ, MZVL21T00 MZVL21T0HCLR-00BL2, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 might be OEM variant of the 980 Pro |- | <!--Brand-->Samsung PM9B1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model--> *2023 MZ9L4256HCJQ-00BD1 MZ-9L4256A, , *2025 MZ-VL42560, MZ-VL45120, MZ-VL421T, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SSD controller is Marvell 88SS1322 Whistler Plus, no DRAM cache and Samsung 128-layer TLC NAND flash |- | <!--Brand-->Samsung 990 EVO Plus m.2 nvme2.0 | <!--Model-->MZ-V9S2T0BW, MZ-V9S1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo with no DRAM so HMB and Samsung 236-Layer (V8) TLC - |- | <!--Brand-->Samsung 990 Pro m.2 nvme | <!--Model-->MZ-V9P2T0BW, MZ-V9P1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 2tb early firmware issue - Samsung Pascal with DRAM LPDDR4 and 176-Layer V-NAND TLC - has had firmware design issues, causing premature failure - |- | <!--Brand-->Samsung 9100 PRO PCIe Gen5 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Seagate Firecuda 510 G3 x4 nvme | <!--Model--> *ZP1000GM30001, *ZP500GM30021 P/N 2NT308-300, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad early batch - Phison E12 STXYP0160031 on SK Hynix DRAM DDR4 with Kioxia BiCS3 64L TLC |- | <!--Brand-->Seagate Firecuda Q5 | <!--Model-->ZP500CV30001,ZP250CV30001,ZP1000CV30001 P/N 2ZK307-881,ZP2000CV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 PS5013-E13-31 from Phison, no DRAM cache and QLC nand |- | <!--Brand-->Seagate Firecuda 515 | <!--Model-->ZP500GV30001,ZP250GV30001,ZP1000GV30001,ZP2000GV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 no dram and qlc nand |- | <!--Brand-->Seagate FireCuda 520 SSD M.2 PCIe Gen4 ×4 NVMe 1.4 | <!--Model-->ZP2000GM30002, ZP1000GM30002, ZP500GM30002 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Seagate Firecuda 520N m.2 nvme | <!--Model-->ZP2000GV3A012, ZP1000GV3A012 and ZP500GV3A012 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 530 m.2 nvme | <!--Model-->ZP500GM3A013, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5018-E18 on DRAM DDR4 with Micron 176L TLC |- | <!--Brand-->Seagate | <!--Model-->ZP1000CV3A002, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 540 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand-->Seagate Firecuda 530R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power UD85 m.2 nvme PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 [http://vlo.name:3000/ssdtool/ firmware tools] |- | <!--Brand-->Silicon Power UD90 PCIe 4.0 nvme | <!--Model-->SP250GBP44UD9005, SP500GBP44UD9005, SP01KGBP44UD9005, SP02KGBP44UD9005, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron TLC (B47R) but later no name QLC nand instead - |- | <!--Brand-->Silicon Power A60 A80 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 various originally an E12 drive with 64L Toshiba NAND, then had variations with E12S and SM2262EN as well as random 64L/96L, now it comes with a MAP1001A controller by Maxio and some YMTC NAND - |- | <!--Brand-->Silicon Power US75 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix BC501 M.2 m.2 NVMe PCIe Gen3 SSD | <!--Model--> *Rev0 HFM256GDHTNG-8510B SSS0L24764, HFM256GDJTNG-8310A, *Rev1 HFM256GDHTNG-8310A SSS0Q68673, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 bad batch early - |- | <!--Brand-->SK Hynix BC511 512GB NVMe PCIe M2 2230 SSD | <!--Model-->HFM256GDJTNI-82A0A HFM512GDGTNI-82A0A D P/N 0TG8T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 no dram cache |- | <!--Brand-->SK hynix BC711 PCIe Gen3 x4 | <!--Model-->HFM001TD3JX013N, HFM512GD3JX013N, HFM256GD3JX013N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 okay but no dram cache |- | <!--Brand-->SK hynix PC711 m.2 2280 PCIe Gen3 x4 | <!--Model--> *HFS001TDE9X073N, HFS512GDE9X073N, HFS256GDE9X073N *HFS001TDE9X080N, HFS512GDE9X080N, HFS256GDE9X081N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->SK Hynix SC210 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SK Hynix PC601 PCIe 3.0 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - Cepheus Plus YCN34PTA0FR Controller and 48L TLC Flash, pseudo-SLC cache and LPDDR4-3733 SK Hynix H9HCNNN8KUMLHR-NME dram - |- | <!--Brand-->SK Hynix PC401 3rd gen PCIe | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad batch early - |- | <!--Brand-->SK hynix Gold P31 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 SK hynix’s proprietary Cepheus controller |- | <!--Brand-->Sk Hynix SK500 Gen 4 (x4) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SK hynix Platinum P41 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Aries SSD controller with 176-Layer TLC flash - SK hynix LPDDR4 dram - |- | <!--Brand-->Sk Hynix PC801 PCIe Gen4 x4 m.2 nvme | <!--Model-->HFS001TEJ9X101N, HFS512GEJ9X101N, HFS256GEJ9X101N, HFS002TEJ9X101N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->SK Hynix BC901 m.2 nvme PCIe Gen4 2230 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Silicon Motion SM2269XT with no DRAM so HMB buffer cache - SK Hynix 176-layer TLC NAND flash 1TB only - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team | <!--Model-->TM8PS7512G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TeamGroup MP34 | <!--Model-->MP34 256GB, MP34 512GB, MP34 1TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 good Phison E12 with DRAM NANYA DDR3L and Toshiba BiCS 3 64L TLC - |- | <!--Brand-->Team Group T-Force Cardea A440 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison PS5018-E18 NVMe 1.4 controller and Micron’s 96L TLC with SK hynix 8Gb DDR4 chips but not OPAL-compliant AES 256-bit |- | <!--Brand-->Team Group TForce Cardea A440 Lite PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 dram-less E27T controller and 162L TLC but not OPAL-compliant AES 256-bit |- | <!--Brand-->teamgroup Team Z44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand-->teamgroup Team MP44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E21T no DRAM so HMB with 176-Layer Micron TLC |- | <!--Brand-->Team MP33Q | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - dramless maxio MAP1202 with TLC (MP33) or QLC (MP33Q) - |- | <!--Brand-->Team Group QX GE Pro m.2 nvme PCIe5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 innogit IG5666 with QLC 3D 232L nand with DRAM - |- | <!--Brand-->Team Group T-Force G70 Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 InnoGrit IG5236 (Rainier) with DRAM and NAND YMTC TLC - |- | <!--Brand-->Team Group T-Force Cardea Z540 m.2 nvme PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison E26 controller and 232L TLC and DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE110S PCIe Gen3 x4 M.2 2280 TS128GMTE110S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND |- | <!--Brand-->Transcend MTE220S PCIe Gen3 x4 M.2 2280 TS2TMTE220S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND with DRAM Cache |- | <!--Brand-->Transcend MTE300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand-->Transcend MTE300S PCIe Gen3 x4 M.2 2230 TS256GMTE300S TS512GMTE300S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND, 1G and 2G get hot |- | <!--Brand-->Transcend | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE400S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 mlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Union Memory (Shenzhen) AM6672 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM6A0 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Verbatim V15000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->WD Blue SN500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western digital SN720 M.2 2280 NVME PCIE for Data Centers | <!--Model-->SDAQNTW-512G-1001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2021 |- | <!--Brand-->WDC SN520 2230 Gen3 x2 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2020 |- | <!--Brand-->Western digital ix sn530 M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 industrial sandisk controller and firmware, as well as 96-layer 3D TLC NAND memory that can work in TLC or SLC mode - |- | <!--Brand-->Western digital SN730 Gen3 x4 M.2 2280 M.2 NVME | <!--Model-->SDBPNTY-1T00, SDBPNTY-512G-1012, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 to 2021 DRAM Cache DDR4-2666 CL18 Micron MT40A512M16LY-075:E (D9WFH) with Controller WD 20-82-00705-A2 Triton MP28 and NAND Flash Toshiba BiCS4 60082 512G (Rebranded by SanDisk) TLC 96-layer |- | <!--Brand-->WD Black SN750 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 64-layer 3D stacked NAND with 3 bits per cell TLC (Triple Level Cell) with 256MB of skhynix DRAM cache for every 250GB |- | <!--Brand-->WD Black SN850 m.2 nvme Gen4 PHY | <!--Model-->WDS100T1X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Sandisk G2 controller with Micron DDR4 cache - new nCache 4.0 slc cache total dynamic capacity spans one-third (300GB on 1TB) with a small static SLC cache (12GB on 1TB) from the Kioxia BiCS4 96L TLC 96-layer NAND flash - |- | <!--Brand-->Western digital SN550 Blue M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - various controllers and NANDs |- | <!--Brand-->Western Digital SN810 NVMe SSD 2280 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 slc cache - laptop oem only no retail version - |- | <!--Brand-->WD SN850X | <!--Model-->WDS100T2X0E, WDS200T2X0E, WDS400T2X0E, WDS800T2X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 issues with early ssd firmware and AMD Zen 3 X570 and X670E chipsets - Sandisk A101000291-82 controller with 112-layer TLC and DDR4 DRAM cache |- | <!--Brand-->WD_Blue SN570 single-sided M.2 2280 (80mm) PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless - WD/SanDisk SSD controller with BiCS 5 3D NAND TLC 112-layer NAND flash memory - |- | <!--Brand-->WD_Black SN770 m.2 nvme | <!--Model-->WDS100T3X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless cache with TLC |- | <!--Brand-->WD Green SN350 m.2 NVMe SSD | <!--Model-->WDS100T3G0C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 DRAM-less cache with SanDisk controller and QLC (quad-level cell) NAND |- | <!--Brand-->WD_BLACK SN750 SE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Phison E19T, dramless |- | <!--Brand-->WD SN740 M.2 (2230) PCIe 4.0 x4 2280 | <!--Model-->SDDQTQD-1T00, SDDPNQD-, SDDPNQD-256G-2006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless with SSD controller WD Sandisk 20-82-10081-A1 Polaris MP16+ with Toshiba BiCS5 112-layer TLC NAND flash |- | <!--Brand-->WD_Blue SN580 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless SanDisk controller with (HMB) and 112-Layer Kioxia TLC (BiCS5) |- | <!--Brand-->WD Blue SN5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Black SN8100 / Sandisk Optimus GX Pro 8100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk Optimus GX 5100 7100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk Optimus GX Pro 850X | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Zhitai (Yangtze Memory) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === Mini SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Biwin PCIe 4×2 NVMe 1.3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 GPDwin5 and Oneplayer Superx hybrid - 3D TLC - LGA packaging - V1 slide tray mechanism - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- |} ==SATA== Advanced Host Controller Interface (AHCI), a programming interface for SATA host controllers. Platforms supporting AHCI may take advantage of performance features such as no master/slave designation for SATA devices — each device is treated as a master — and hardware-assisted native command queuing. AHCI may but not often also provides usability enhancements such as Hot-Plug (Desktop and Mobile Only). AHCI requires appropriate software support (e.g., an AHCI driver) AHCI, the underlying protocol for SATA, only supports one queue with 32 commands. The issue with AHCI is that it's going to take a pile of test hardware just to figure out all the different bugs in all the motherboard chipsets and add-on PCI cards that 'kinda' implement AHCI. Not to mention Silicon Image, which took a very different approach from Intel's AHCI in their SATA controllers. === SATA 7mm 2.5inch SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand-->ADATA 240GB Ultimate SU630 2.5" | <!--Model-->ASU630SS-240GQ-R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->ADATA Ultimate Su650 2.5in | <!--Model-->ASU650SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->ADATA Ultimate Su800 2.5in | <!--Model-->ASU800 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI SM2258 controller with Micron 3D TLC NAND but low performance when data fills the SLC cache - slow write speed - |- | <!--Brand-->ADATA Ultimate Su680 2.5in | <!--Model-->ASU680SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS340 Panther | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS350 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial M225 SSD 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2009 sata2 3gbp/s |- | <!--Brand-->Crucial C300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 sata3 6gbps - |- | <!--Brand-->Crucial M4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2011 Marvell 88SS9174-BKK2 processor, 25nm MLC NAND flash and 128MB dram cache |- | <!--Brand-->Crucial M500 120Gb to 960Gb | <!--Model-->CT250M500SSD1, CT500M500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 dram cache |- | <!--Brand-->Crucial M550 120G to 1T | <!--Model-->CT250M550SSD1, CT500M550SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dram cache |- | <!--Brand-->Crucial (Micron) BX100 | <!--Model-->CT500BX100SSD1, CT1000BX100SSD1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - no dram - Silicon Motion SM2246EN and ATA version ACS-2 - |- | <!--Brand-->Crucial (Micron) MX100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache Micron controller and nand - |- | <!--Brand-->Crucial MX200 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC NAND |- | <!--Brand-->Crucial (Micron) BX300 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dramless cache - Micron ex Tidal controller and TLC nand - |- | <!--Brand-->Crucial (Micron) MX300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand-->Crucial (Micron) bx500 2.5inch | <!--Model-->CT240BX500SSD1, CT480BX500SSD1, CT960BX500SSD1, CT1000BX500SSD1, CT2000BX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SM2258XT 4channel later SM2259XT paired with Micron’s latest 64-Layer 3D TLC flash but dramless SLC cache (part of the tlc flash) - |- | <!--Brand-->Crucial (Micron) MX500 | <!--Model-->CT250MX500SSD1, CT500MX500SSD1, CT1000MX500SSD1, CT2000MX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - dram cache from 256M to 2G - discontinued end of 2024 |- | <!--Brand-->Fanxiang S101 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no dram cache, Hynix memory 3dv7-176l 176 layer QLC (one chip), either raymx rm1135, SM2259XT controller or Realtek rts5735dlq |- | <!--Brand-->Fanxiang ranxiana S102 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - no dram - |- | <!--Brand-->Fanxiang S101Q 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fanxiang | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX815 Standard 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FS810 Ultra 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertec FirestormLite 2.5inch | <!--Model-->S240GHS3-M or SDSSD240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertech | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral V2 Plus 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel SSD 520 Series 2.5 inch SATA 6Gb/s 2.5" SSD Solid State Drive | <!--Model-->SSDSC2CW240A3, SSDSC2CW480A3, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 LSI SandForce SF2281, Flash Memory Intel Synchronous 25nm MLC - |- | <!--Brand-->Intel Pro Series 1500 | <!--Model-->SSDSC2BF180A4L SSD0E38417, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Intel S3610 Series 2.5" 400GB 6GBPS SATA SSD | <!--Model-->SSDSC2BX400G4R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 data center |- | <!--Brand-->Intel SSD Pro 5400s 512 GB | <!--Model-->SSDSC2KF512H6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3510 Series MLC 2.5" | <!--Model-->SSDS2BB400G6, SSDSC2BB480G6R, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3520 Series MLC 2.5" | <!--Model-->SSDSC2BB800G7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel SSD DC S3710 Series 800GB 2.5" | <!--Model-->SSDSC2BA800G4P, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 server |- | <!--Brand-->Intel SSD 545S Series 256GB 512GB | <!--Model-->SSDSC2KW256G8X1, SSDSC2KW512G8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] SSD DC S4500 240GB 2.5inch - HP Enterprise | <!--Model-->SSDSC2KB240G7P | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingspec P3-512 P3-1T0 P3-2TO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston SSDNow 300 | <!--Model-->SV300S37A/240G, SV300S37A/120G, SV300S37A/60G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dramless - lsi sandforce SF2281 or JMicron JMF662 controller with Toshiba MLC or Intel MLC |- | <!--Brand-->Kingston A400 120G to 960Gb 2.5inch | <!--Model-->SA400S37/240G SBFK61K1, SA400S37/480G, SA400S37/960G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 half case sized ssd 4 x FH64B08UCT1-60 64G - t6 security torx into metal case - dram less - poor write speeds - |- | <!--Brand-->Kingston | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia formerly Toshiba HG6 2.5in | <!--Model--> *9.5mm THNSNJ512GBSU, THNSNJ256GBSU, THNSNJ128GBSU *7mm THNSNJ512GCSU THNSNJ512GCSY, THNSNJ256GCSU THNSNJ256GCSY, THNSNJ128GCSU THNSNJ128GCSY | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar NS100 2.5 inch sata | <!--Model-->LNS100-1TRB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - Marvell 88NV1120 Artemis, a DRAM cache is not available and pseudo-SLC. Micron 64-layer TLC NAND flash 4 chips @ 512 Gbit TS7512G181 (Rebranded by Lexar) (256G) - 4 nand flash chips Lexar/TST22T181/ B1924 and one controller: Lexar DM918/NOD43 1907 (512G) - |- | <!--Brand-->Lexar NQ100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - DM928 controller which operates without a DRAM buffer. Two 128GB Micron NAND flash chips |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LiteOn | <!--Model-->LCS-128L9S-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 no dram - sata2 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Matrix 256Gb 512GB SATA 2.5in SSD | <!--Model-->MIS512GSDS, MIS256GSDS | <!--Work MSDos-->UP TO 550MB/S | <!--Work GPT-->UP TO 500MB/S | <!--Tested Distribution--> |- | <!--Brand-->Micron 1100 | <!--Model-->MTFDDAK2T0TBN-1AR1ZA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron 1300 2TB 1300 2.5" | <!--Model-->MTFDDAK2T0TDL-1AW1ZABHA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 - old sdd - TLC nand - |- | <!--Brand-->Micron RealSSD C400 2.5inch | <!--Model-->MTFDDAK256MAM-1K12 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Mushkin Reactor | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC flash |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac SA500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico Y-20 Y20 2.5 inch sata SHENZHEN ORICO TECHNOLOGIES CO.,LTD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 flash nand - |- | <!--Brand-->Orico S500-Pro s500pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Origin Storage Inception TLC830 Pro Series 2.5in SATA III SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D tlc flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand-->Patriot P210 2.5 inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> qlc flash nand - |- | <!--Brand-->Patriot P220 | <!--Model-->P220S2TB25 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Plextor M6V | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS900 2.5 in sata SSD | <!--Model-->SSD7CS900-480-PB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->PNY CS2311, CS3030 and Pro Elite SSDs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung SM PM | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->PM871a or PM871b? SM/PM = 2-bit or 3-bit MLC. PM = 3-bit MLC = TLC. 8 = generation = 8xx, 7 = model = 850 EVO (in this case), 1 = usage (e.g. 3 = datacenter). a/b = revision or type of flash, the 850 EVO had multiple revisions including at least three types of flash (32L, 48L, 64L) so a = 32/48L, b = 64L. At lower capacities it might use different flash, for example the 256GB SM951 utilizies 2D/planar while the higher capacities use 3D. OEM drives tend to have different, optimized firmware, so performance will not be the same |- | <!--Brand-->Samsung 840 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Samsung 840 EVO | <!--Model-->MZ-7TE120 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 |- | <!--Brand-->Samsung PM851 2.5in sata | <!--Model-->MZ-7TE5120 P/N MZ7TE512HMHP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Samsung 850 EVO | <!--Model-->MZ-75E120, MZ-75E500 (P/N MZ7LN500) to MZ-75E4T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 Samsung MGX controller (S4LN062X01) up to 500GB capacities whilst Samsung MEX controller (3-core) beyond - Samsung TLC 3D V‐NAND 48 and later 64 layers and possibility of 256MB, 512MB or 1GB LPDDR2-1066 DRAM chip - |- | <!--Brand-->Samsung 850 PRO | <!--Model-->MZ-7KE1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung PM871a 2.5 inch sata | <!--Model-->MZ-7LN512A P/N MZ7LN512HMJP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung PM883 1.92TB | <!--Model-->MZ-7LH1T90 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - - Samsung MJX Maru (S4LR030) - 1gb LPDDR4-1866 dram - |- | <!--Brand-->Samsung 860 EVO | <!--Model-->MZ-76E1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung 860 EVO PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 860 QVO | <!--Model-->MZ-76Q1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 870 QVO 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - MKX 8-channel controller |- | <!--Brand-->Samsung 870 EVO | <!--Model-->MZ-7LN56F, MZ-77E1T0 P/N MZ7L31TOHBLB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 beware of bad batch early death - uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand-->Samsung PM871b | <!--Model-->MZ7LN256HCHP-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Sandisk Ultra 3D/Extreme Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 SandForce SF-2281 dram |- | <!--Brand-->Sandisk Ultra Plus | <!--Model-->SDSSDHP-256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell SS889175 processor with SanDisk's 19nm NAND and 128MB Samsung DDR2 DRAM chip |- | <!--Brand-->Sandisk Z300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Marvell 88SS9188 Marvell 88SS9187 with SanDisk 64Gbit 19nm MLC - |- | <!--Brand-->Sandisk x300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Sandisk x300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk Plus | <!--Model-->SDSSDA-240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 pseudo SLC cache dramless |- | <!--Brand-->Sandisk Z400s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - Silicon Motion SM2246XT DRAM-less - budget end of market - |- | <!--Brand-->Sandisk x400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 4 NAND packages and marvell controller 88ss1074 on blue pcb - 512MB DDR3L-1600 Micron DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Seagate BarraCuda Q1 SSD | <!--Model-->ZA240CV10001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 dramless A55 started with the Phison S10 but later the S11 i.e. Phison PS3111-S11-13 controller and 96-layer TLC NAND flash memory with a pseudo-SLC cache - |- | <!--Brand-->Silicon Power Ace A55 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand-->sk hynix | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 sandforce controller - |- | <!--Brand-->sk Hynix SH910A | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Link_A_Media (LAMD) controller with eight 256Gbit H27QEGDVEBLR NAND 20nm hynix MLC - SK hynix H5PS1G83JFA DRAM - |- | <!--Brand-->sk Hynix SC300 | <!--Model-->HFS256G32MND-3210A, HFS256G32MND-3312A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - red strip around edges - 8-channel controller SK hynix LM87810AA-A0 with DDR2 buffer chip and four pieces of 16nm hynix MLC NAND - |- | <!--Brand-->Sk Hynix Canvas SL300 series 2.5in SSD *3110A SL301STD *3210A *3300A *3310A | <!--Model-->HFS500G32TND, HFS256G32TNE, HFS128G32TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC - consumer line red in corners - SK hynix LM878100AA (HFS256G32MND-3312A) later SH87820BB and NAND 16nm hynix TLC - 256mb dram |- | <!--Brand-->Sk Hynix Canvas SC3 series 2.5in SSD *N1A0A , , *N1A1A *N1A2A SC308STD, *N2A0A , , SC311STD | <!--Model-->HFS512G32TNF-N2A0A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - red in corners - no dram and no SLC cache - Hynix ex Link_A_Media Devices (LAMD) SH87820BB 2c but poor mixed workload ability MLC - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team EX2 GX2 Elite QX | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->TEAMGROUP AX2 2.5 Inch SATA III Solid State Drive SSD | <!--Model-->T253A3512G0C101, T253A3001T0C101, T253A3002T0C101, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 3D NAND TLC |- | <!--Brand-->TeamGroup TF Vulcan Z 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dramless smi2259xt 128L tlc nand - |- | <!--Brand-->TeamGroup T-Force Vulcan ZQLC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram-less smi2259xt qlc 144L nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Topesel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend 220S 2.5in | <!--Model-->TS120GSSD220S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 3D TLC without dram |- | <!--Brand-->Transcend SSD230S 2.5in | <!--Model-->TS256GSSD230S TS512GSSD230S TS1TSSD230S TS2TSSD230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 3D TLC NAND with DRAM Cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Viathan | <!--Model-->S001T3V | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red SA500 NAS | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->WD Blue SA510 250Gb to 4Tb | <!--Model-->WDS400T3B0A WDS200T3B0A WDS100T3B0A WDS500G3B0A WDS250G3B0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - |- | <!--Brand-->Western Digital WD Green SSD 2.5" | <!--Model-->WDS240G1G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Green 200Gb to 2Tb | <!--Model-->WDS200T2G0A WDS100T3G0A WDS480G2G0A WDS240G2G0A WDS120G2G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - cheap and slow ssd - |- | <!--Brand-->WD SA530 | <!--Model-->SDASB8Y-256G SD9SB8W, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->[https://www.xray-disk.com xraydisk] 2.5 inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> from the manufacturer only - Phsion/SMI(2258XT)/Realtek/Yeestor |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Xum | <!--Model-->hx256gssdsata3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Yottamaster | <!--Model-->Y3000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCie 3.0 |- | <!--Brand-->Yottamaster | <!--Model-->Y7000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCIe 4.0 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |} === SATA M.2 (M and B key) === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 2280 Sata | <!--Model-->AXNS381E-128GM-B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S201 m.2 sata 2280 | <!--Model-->S201 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot FN203 m.2 sata (oldtan, twipps, teexin aka Shenzhen Pingfan "Ordinary" Road Technology Co., Ltd) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 lifespan not long Maxio MAP + YMTC 128L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Foresee (Shenzhen Longsys) | <!--Model-->YSM80CD-128G YSDE128G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 88nv1120-bt22 T3WU030 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral 2242 120G | <!--Model-->INSSD120GM242 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral M.2 2280 | <!--Model-->INSSD256GM.26M2280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral 256GB/512GB/1TB/2TB | <!--Model-->INSSD1TM280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 netac rebrand - no dram cache - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel Pro ‎545S 2280 | <!--Model-->SSDSCKKF256G8H | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> no dram, TLC nand |- | <!--Brand-->Intel | <!--Model-->SSDSC2KF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intenso M.2 internalSSD SATA III 1 TB | <!--Model-->Top | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A400 m.2 | <!--Model-->SA400M8/240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 entry level ssd 4 x FH64B08UCT1-60 64G - |- | <!--Brand-->Kingston | <!--Model-->RBU-SNS8350DES3128GP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston V300 | <!--Model-->SV300S3505AG | <!--Work MSDos-->{{yes}} | <!--Work GPT--> | <!--Tested under-->Nightly Build 2014-09-18 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON SATA 128GB | <!--Model-->CV3-8D128-11 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON | <!--Model-->CV1-8B256-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lite-On | <!--Model-->L8H-256V2G-HP L8H-128V2G-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 2016 nanya nt5c864m16fp-dh |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LSI | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 SF37000 controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model-->M550 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell 88SS9189 SATA controller |- | <!--Brand-->Micron M600 enterprise m.2 sata up to 512GB | <!--Model-->MTFDDAV256MBF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 Marvell 88SS9189 SATA controller, DRAM chip 256MB 533MHz LPDDR2, NAND for the 256GB drive MT29F1T08CQCCBG2-10:C 16nm MLC NAND each 128GB package |- | <!--Brand-->MICRON 1100 M.2 SATA 6Gb/s 2280 | <!--Model-->MTFDDAV256TBN HP P/N 903109-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Orico Y20M-2242 | <!--Model-->Y20M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->PNY | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung PM841 M.2 sata3 2280 | <!--Model-->MZ-NTD2560/0L9 MZNTD256HAGL-000L9 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung CM871 Rev 0 | <!--Model-->MZNLF128HCHP-000H1 MZ-NLF1280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM871a m.2 Sata | <!--Model-->MZNLN256HMHQ, NLN512A P/N MZNLN512HMJP-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC |- | <!--Brand-->SAMSUNG PM871b | <!--Model-->MZNLN128HAHQ-000H1, MZNLN256HAJQ MZ-NLN256F MZ-NLN256C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM881 | <!--Model-->MZ-NLH1280 MZNLH128HBHQ-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SanDisk X300 M.2 sata 2280 80mm SSD Solid State Drive | <!--Model-->SD7SN6S-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk X400 SSD M.2 sata 2280 | <!--Model-->SD8SN8U-128G-1006, SD8SN8U-256G-1006, SD8SN8U-512-1006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 SSD controller Marvell 88SS1074 four channel supports variety of NAND and up to 512MB DDR3L-1600 Micron DRAM cache - |- | <!--Brand-->SanDisk X600 M.2 SSD Solid State Drive | <!--Model-->SD9SN8W-128G-1006 SD9TN8W-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SANDISK X110 DELL 6T4HK M.2 2260 | <!--Model-->SD6SP1M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix SC300 | <!--Model-->SC308M280S HFS128G39TND | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 SH87820BB controller - No dram buffer - multi-level cell (MLC) NAND |- | <!--Brand-->SK HYNIX | <!--Model-->SC311 HFS256G39TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK HYNIX | <!--Model-->SC401 HFS256G39TNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 M.2 sata 2280 | <!--Model-->A55 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TEAMGROUP Team MS30 SSD M.2 Sata 2280 | <!--Model-->TM8PS7001T0C101 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Toshiba RC100 (retail version of BG3) | <!--Model-->KBG30ZMV256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Toshiba HG6 m.2 | <!--Model-->THNSNJ512GDNU THNSNJ512G8NY, THNSNJ256GDNU THNSNJ256G8NY, THNSNJ128GDNU THNSNJ128G8NY, THNSNJ256GVNU THNSNJ128GVNU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TOSHIBA SSD M.2 2280 256GB | <!--Model-->KSG50ZMV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand-->Kioxia (Toshiba) BG6 | <!--Model-->KSG60ZMG256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend | <!--Model-->400 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend M.2 SSD 2242 TS32GMTS400S TS64GMTS400S TS128GMTS400S | <!--Model-->400S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> DDR3 dram cache and mlc nand |- | <!--Brand-->Transcend | <!--Model-->M.2 SSD 600 (2260), M.2 SSD 800S (2280) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> mlc nand |- | <!--Brand-->Transcend M.2 SSD 2242 TS120GMTS420S TS240GMTS420S TS480GMTS420S | <!--Model-->420S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> can run hot slc cache |- | <!--Brand-->Transcend M.2 SSD 2242 TS256GMTS430S TS512GMTS430S | <!--Model-->430S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache - 3d tlc nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS120GMTS820S TS240GMTS820S TS960GMTS820S | <!--Model-->820S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS256GMTS830S TS512GMTS830S TS1TMTS830S TS4TMTS830S | <!--Model-->830S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 120GB to 480Gb | <!--Model-->WDS480G2G0B WDS240G2G0B WDS120G2G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 made in malaysia |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 240Gb to | <!--Model-->WDS240G3G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 made in |- | <!--Brand-->WD Blue SA510 M.2 SATA 250Gb to 2Tb | <!--Model-->WDS200T3B0B WDS100T3B0B WDS500G3B0B WDS250G3B0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red 500GB 1TB 2TB | <!--Model-->SA500 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM610 m.2 sata | <!--Model-->SSS0R27339, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === mSATA SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fangxiang S301 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingchuxing | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model-->INSSD256GMSA MO-300 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc 3d nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron enterprise | <!--Model-->M600 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico ZH-10 ZH10 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Samsung 840 EVO 1.8inch msata | <!--Model-->MZ-M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung 850 EVO 1.8in | <!--Model-->MZ-M5E120BW, MZ-M5E250BW, MZ-M5E500BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM851 1.8" msata | <!--Model-->MZ-MTE256D P/N MZ-MTMTE256HMHP, MZ-MTE1T00, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 860 EVO 1.8inch msata | <!--Model-->MZ-MM6E250BW, MZ-M6E500BW, MZ-M6E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Transcend TS64GMSA370S | <!--Model-->MSA370S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC nand |- | <!--Brand-->Transcend TS64GMSA230S | <!--Model-->230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3d tlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === SATA 2.5inch Laptop Hard Disks === ====7mm==== {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP628230-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP552605-01 250Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP693440-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HGST Hitachi Z5K320 Z5K500-500 Z5K100 series * 2013 HTS545050A7E380 HTS * 2015 HTS545050A7E680 HTS | <!--Model-->HTS 320GB 500Gb 1Tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->HGST Hitachi Z7K320 Z7K500 series | <!--Model-->HTS725050A7E630 320Gb HTS725050A7E635 500Gb 7200rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> avoid if it does not have the DCM code |- | <!--Brand-->HGST 1T 5400rpm | <!--Model-->HTS541010B7E610 | <!--Work--> | <!--Tested under-->2017 128m cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Seagate Momentus Thin | <!--Model-->ST500LT012 ST320LT012. ST250LT012 500Gb 320gb 250gb 2014 5.4K rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Seagate Thin SSHD 5400RPM Sata 2.5" | <!--Model-->ST500LM000 500GB, ST500LM001, ST500LM020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 up to 64M cache and with 8GB NAND Flash |- | <!--Brand-->Seagate MomentusThin-B Video 2.5 HDD * 2014 * 2015 * 2016 * 2017 | <!--Model-->ST500VT000 500GB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->SEAGATE Baracuda 2.5 5400 | <!--Model-->ST2000LM015 (2Gb), ST1000LM049 (1Tb), ST500LM030 (500Gb) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Seagate Barracuda Pro | <!--Model-->ST1000LM048 ST1000LM035 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> up to 128MB cache |- | <!--Brand-->SEAGATE FireCuda Compute 2.5 | <!--Model-->ST500LX025 ST1000LX015 ST2000LX001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 8GB NAND Commercial Multilevel Cell (cMLC), 128MB buffer and 5400-RPM spindle speed up to 140 MB/s |- | <!--Brand-->Toshiba 2.5in | <!--Model-->MQ04ABF100 1TB 5400 RPM 2018 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TOSHIBA MQ01ACF | <!--Model-->MQ01ACF050 500GB 7200rpm 2020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->western digital wd blue 500G 8meg cache 5400rpm * 2014 Rev T0 * 2015 Rev T1 | <!--Model-->wd5000lpvx | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012-2015 sequential 2MB block transfers 110 MB/s reading and writing - |- | <!--Brand-->Western Digital 2.5" WD Blue Slim | <!--Model-->WD10SPCX 1TB Nov 2016 | <!--Work MSDos-->{{Yes|hdd under partition table msdos/pc, boots on bios machines, will not on uefi machine}} | <!--Work GPT-->{{Unk|untested hdd under gpt partition protocol scheme, not booting on uefi}} | <!--Tested under-->AROS One 1.8 USB |- | <!--Brand-->Western Digital WD | <!--Model-->WD5000LUCX 500Gb 5400rpm 16mb cache Rev Y0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 2017 Malaysia |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} ====9.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->MHW2040BH | <!--Work--> | <!--Tested under--> 40gig |- | <!--Brand-->Fujitsu | <!--Model-->MHY2080BH | <!--Work--> | <!--Tested under--> 80gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHW2120B | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS541010A9E662 type TS5SAF100 | <!--Work--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Hitachi Travelstar 5K500.B-320 | <!--Model-->HTS545025B9SA02 HTS545032B9A300 HTS545040B9A300 HTS545050B9A300 250Gb 320Gb 400Gb 500Gb 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST 1TB 7200rpm | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung bought by Seagate late 2011 | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung Spinpoint with Seagate HD REV A (Jan 2014) | <!--Model-->ST1000LM024 | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand-->Samsung Spinpoint with Seagate 9.5mm * 2013 Rev A HN-M500MBB/I * 2014 Rev B HN-M500MBB/SP4 * 2015 Rev B HN-M500MBB/P4C | <!--Model-->ST500LM012 (500M) | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Momentus 5400.3 | <!--Model-->ST9160821AS | <!--Work--> | <!--Tested under--> 160gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SSHD 1t | <!--Model-->ST1000LM014, ST1000LM028, ST1000LM015 | <!--Work--> | <!--Tested under--> 8g nand flash |- | <!--Brand-->Seagate SSHD 1T | <!--Model-->ST1000LX001 | <!--Work--> | <!--Tested under--> 32G nand flash |- | <!--Brand-->Toshiba | <!--Model-->MK2555GSX HDD2H24 | <!--Work--> | <!--Tested under--> 250g 5400rpm |- | <!--Brand-->Toshiba | <!--Model-->MK5065GSX - 500GB 5400RPM SATA 3Gb/s 8MB Cache 2.5-Inch | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MKxx59GSXP, eg Toshiba MK6459GSXP 640GB 2011 | <!--Work-->{{yes}} | <!--Tested under-->Icaros 2.2 with uses Advanced Format (AF) in 4,096 bytes per sector. Compatibility with legacy, 512 bytes through AF emulation techniques, called 512e |- | <!--Brand-->Toshiba (2013 to 2016) | <!--Model-->MQ01ABD100 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba (2015 to 2020) *2013 *2014 *2015 AA50/AX0D5A *2016 AA60/AX0E1A * *2017 AGM AA01/AX002V *2018 AGS AA70/AX0G1A *2020 AA71/AX0G1A | <!--Model-->MQ01ABD050 500meg | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MQ04ABF100 1TB 5400 RPM 2013 | <!--Work-->{{Yes}} | <!--Tested under--> |- | <!--Brand-->TOSHIBA | <!--Model-->MQ04ABD200 2TB 5400 RPM 128MB Cache SATA 6.0Gb/s | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD7500BPVX 2013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WESTERN DIGITAL 1TB 2.5" SATA DRIVE 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-80JC3T0 (OCT 2014) | <!--Work--> | <!--Tested under--> , uses Advanced Format (AF) |- | <!--Brand-->WDC Western Digital Blue 1TB SATA 2.5" Hard Drive 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-08JC3T6 (Jun 2017) | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD10JPCX 1Tb | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital * 2019 | <!--Model-->WD10JUCT 1TB (1000GB) 2019 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WD Western Digital Scorpio Black * 2010 * 2014 | <!--Model-->WD5000BEKT, WD5000BPKX-22HPJT0, WD5000BPKT, | <!--Work--> | <!--Tested under--> 16m cache, 7200rpm thailand then malaysia |- | <!--Brand-->WD Western Digital Black * 2016 | <!--Model-->WD2500LPLX, WD3200LPLX, WD5000LPLX SMR: WD5000LPSX, WD10SPSX | <!--Work--> | <!--Tested under--> 32m cache , 7200rpm SATA-III malaysia |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA 2.5in NON-Laptop Hard Disks === ====11mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu 160GB 250GB 300GB | <!--Model-->MHX2160BT, MHX2250BT, MHX2300BT | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model-->TP00640GB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====12.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====15mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 1TB IBM System X 15mm 2.5" SATA | <!--Model-->ST91000640NS 81Y9731 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT10N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 5v 12.7mm |- | <!--Brand-->HL Data Storage BD-Rom DVD Rewriter | <!--Model-->CT10N AFCK101 LGE-DMCT10A(B) | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 5v 12.7mm fails early |- | <!--Brand-->Hitachi LG | <!--Model-->GT20L | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009/2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model-->GT30N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT50N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT90N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 5v 12.7mm |- | <!--Brand-->HP | <!--Model-->TS-L633 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->HP | <!--Model-->GU70N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 5v 1.8A 9.5mm |- | <!--Brand-->HP | <!--Model-->GUD0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.8A 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->GTA0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic | <!--Model-->Uj870a Uj880 UJ890 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->UJ8A0 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic MATSHITA 12.5mm SATA DVD burner inside Asus K53S | <!--Model-->UJ8B0 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 12.7mm 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8B1 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8C0 UJ8C1 UJ8C2 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.6a |- | <!--Brand-->Panasonic | <!--Model-->UJ8D0 UJ8D1 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 |- | <!--Brand-->Panasonic | <!--Model-->UJ8E2Q | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 9.5mm |- | <!--Brand-->Panasonic | <!--Model-->UJ8FB | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5a 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->DS-8A5LH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm |- | <!--Brand-->HP | <!--Model-->DU-8A6SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5A 9.5mm |- | <!--Brand-->Philips and LiteOn | <!--Model-->DS-8A8SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5a 12.7mm |- | <!--Brand-->PLSD | <!--Model-->DS-8A9SH DS8A9SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7561S, AD-7560S Thickness: 12.7 MM Interface: SATA | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 |- | <!--Brand-->Sony | <!--Model-->AD-7580s, AD-7581s, AD-7583s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7585H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm cleaning the laser lens inside the drive with a liquid lens cleaner. Also check the lens carrier slides freely from one extreme to the other inside the drive without sticking |- | <!--Brand-->Sony | <!--Model-->AD7590s, AD-7591s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7700s, AD-7710h, AD-7701H, AD-7703S | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7760H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5A 12.7mm |- | <!--Brand--> | <!--Model-->AD-7711H AD-7740H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->Toshiba Samsung | <!--Model-->SN-S208B Ver BB Rev 00 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm |- | <!--Brand-->Toshiba TSSTCorp Samsung | <!--Model-->SN-S083C Ver C Rev 03 /BEBE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.5a 12.7 mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} === [https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data SATA Desktop 3.5inch Hard Disks] === Datasheets with the SMR (overlapped packing Shingled Magnetic Recording) and CMR (faster Conventional Magnetic Recording) parts <pre> WD: https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/internal-drives/wd-blue-hdd/product-brief-western-digital-wd-blue-pc-hdd.pdf Seagate: https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/datasheets/pdfs/3-5-barracudaDS1900-14-2007US-en_US.pdf Toshiba: https://storage.toshiba.com/docs/support-docs/P300-SalesSheet_English_Web_r2.pdf </pre> {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Seagate Barracuda 7200.9 | ST3160812AS, ST3160212AS | {{yes}} | Icaros Desktop 1.5.2 - Capacity: 160 GB - Speed: 7200RPM - Cache: 8 MB - Interface: SATA2 |- | <!--Brand-->Seagate Barracuda LP Green 5400rpm | <!--Model-->ST1000DL002 1TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SkyHawk Surveillance HDD ST4000VX000 Series | <!--Model-->ST4000VX013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Baracuda Compute | <!--Model-->ST500DM009 2F110A-500 / 02PKVY / 2PKVY (500m), | <!--Work--> | <!--Tested under--> - SATA III (6Gb/s) - Format 3.5" - 32MB Cache |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate CMR | <!--Model-->ST1000DM010 ST500DM009 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 2TB SMR | <!--Model-->ST2000DM008 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SMR | <!--Model-->ST8000DM004 ST6000DM003 ST4000DM004 ST3000DM007 ST2000DM005 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 5400rpm | <!--Model-->HDWD220 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 7200rpm | <!--Model-->HDWD320 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba P300 CMR | <!--Model-->HDWD130XZSTA HDWD130UZSVA, HDWD120XZSTA HDWD120UZSVA, HDWD110XZSTA HDWD110UZSVA | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital 2010 | <!--Model-->WD20EARS Green 2TB 5400rpm 64mb cache | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD20EFRX WD40EFRX 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital | <!--Model-->WD4002FFWD | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD80EAAZ WD80EAZZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD20EARZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD40EZAZ, WD60EZAZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD20EARZ, WD20EZAZ - 2TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD40EZAX - 4TB, WD60EZAX - 6TB, WD80EZAX - 8TB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- |} ==PATA== === IDE Desktop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | M1624TAU | {{yes}} | Icaros Desktop 1.5.2 |- | IBM | DHEA-38451 | {{yes}} | Icaros Desktop 1.5.2 |- | Samsung | SP40A2H | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST3160215ACE | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST32122A | {{maybe}} | Icaros Desktop 1.5.2 |- | Western Digital | WD102AA | {{yes}} | Icaros Desktop 1.5.2 |- | Western Digital | WD200 | {{maybe}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Laptop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHV2040AH | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->HGST Hitachi Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Toshiba | MK2011GAP | {{yes}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | Compaq | CR-594-BCQ | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8322B(CP1) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8484B(AM2A) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | LTN-485 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Creative | CD220E | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Hitachi-LG | GDA-4120B | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | LG | CRD-8400B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Lite-On | LTN486S | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Mitsumi | CRMC-FX4830T | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | CDR-1700B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | DV-5800A | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | ND-2100A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | NEC | NR-7900A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | Philips | DVD8631 | {{no}} | {{no}} | Icaros Desktop 2.2 |- | Samsung | SC-148 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SCR-2030 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SM-348B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU601 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU611-25 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Toshiba | SD-M1202 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |} === IDE Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->H-L Hitachi LG | <!--Model-->GCC-4244N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2006 |- | Hitachi-LG | GCCT10N | {{yes}} | {{Maybe|FryingPan WRITE seems to have no problem with data sections (track 1) - combos with audio sections (track 2) white screens aros eventually}} | AspireOS Xenon with 25th Jan 2014 self update kernel |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Philips | SDR089 | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | TSSTcorp | TS-L462C TS-L462D | {{yes}} | {{unk}} | 2005 Icaros Desktop 2.2 |- | TSSTcorp | TS-L632H | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Sony | DW-Q58A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | Sony Optiarc | AD-7540A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | <!--Brand-->Sony | <!--Model-->Optiarc DVD RW AD-7560A IDE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7590A | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} == SCSI == {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} NVMe accepts up to 64,000 queues with up to 64,000 commands each. ev6xghhzm73b68ri55ishr8phjshoy8 4634262 4634261 2026-05-05T11:52:18Z Jeff1138 301139 4634262 wikitext text/x-wiki {{ArosNav}} ==Introduction== AROS supports hard disks and optical drives attached to several interfaces: * [[#NVMe M.2 SSD (M key)]] on the pci-e bus * [[#SATA]] aka Serial ATA or AHCI (IDE compatibility mode used in most cases) * IDE (also known as ATA, [[#PATA]] or Parallel ATA) * USB * SCSI limited ==PCI-e== ===NVMe M.2 SSD (M key)=== *Controller and firmware *DRAM better having if heavy workloads but not necessary for gaming *Cache like SLC HMB techniques *NAND (Main storage area with MLC, TLC or QLC versions of varying life expectancy) SSDs, USB flash drive, SD and Micro SD Cards have a limited amount of write cycles, therefore guaranteed to fail randomly and suddenly at any time. All SSDs are prone to corrupt firmware due to poor quality NAND where both the data and the firmware resides. The drive tends to go read only when too many errors occur before complete failure. That is up to 10 years for things like memory cards and USB sticks. In general, unless there is a firmware design issue, cheap materials used, stress like bending or overheating causing cold solder joints, an SSD can last a long time if minimal writing activity takes place but eventually if flash isn't written to, it degrades. Catch 22. Dram and cache are not the same thing. Dram stores the ssds indexes and metadata for faster data retrieval and wear leveling. The cache keeps part of the nand memory as SLC storage which can be written to faster. Basically all ssds will have a dynamic SLC cache where it will decrease as the drive fills up. Cache controller designs that are DRAM less use the internal SRAM cache in the controller to cache the NAND mapping table. It just requires a different mapping table design since SRAM caches are much smaller than DRAM. Ultimately the mapping table is still stored in NAND. General rule of thumb: the cheaper an SSD, the higher the likelihood it uses lower quality flash chips so sudden failing NAND, problematic controller chips (e.g. SandForce), outsourced firmware. Generic brand like old SP, Corsair or Crucial may be recoverable whilst major brands Samsung, Intel and Western Digital are impossible due to firmware encryption and customizations. Recommend sticking with older Silicon Motion or Phison controllers if possible. A ssd isn't good because it has dram or bad because it doesn't. Other things should be taken into account like sustained writes so check the TPU write intensive usage See [https://www.techpowerup.com/ssd-specs/ here] for more information {| class="wikitable" width="100%" ! width="15%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="30%" |Tested Distribution |- | <!--Brand-->Unnamed | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 to - SM2259XT2 SM2263XT MAS0902 MAP1202 YS9082HP RM1135 RTS5765 PS3111 |- | <!--Brand-->Unnamed OEMs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 to date - Realtek RTS5765/66 controller + Micron 96L (B27A) |- | <!--Brand-->Acer Predator GM7 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Acer drives built by Biwin, that also supplies HP, Maxio MAP1602A no DRAM so HMB, YMTC 128L TLC, |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 NVME IM2P33F8, IM2S3168 SSD | <!--Model-->IM2P33F8-512GD | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - industrial 12L 3D TLC NAND flash Supports LDPC ECC, RAID Engine, and SLC Cache End-to-End (E2E) Data Path Protection with Host Memory Buffer (HMB) i.e. DRAMless |- | <!--Brand-->ADATA XPG SX8200 Pro M.2 nvme | <!--Model-->ASX8200PNP1TTC | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 NVM Express 1.3 SN2262G later SN2262EN chipset - |- | <!--Brand-->ADATA 256GB GEN4 x4 NVMe PCIe M2 2230 SSD | <!--Model-->SM2P41C3-256GC2 DP/N 0KM1Y6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 consumer |- | <!--Brand-->ADATA XPG GAMMIX S50 Lite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Silicon Motion SM2267XT dramless |- | <!--Brand-->ADATA XPG ATOM 50 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Innogrit RainierQX IG5220 |- | <!--Brand-->Adata Legend 710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->ADATA Legend 900 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->BiWin PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Innogrit IG5216 controller, no DRAM so HMB which appears to be the standard - |- | <!--Brand-->BiWin NV7200 PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SM2263XT |- | <!--Brand-->Biwin NV7400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force LE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Corsair Force Series MP500 MP510 M.2 NVMe PCIe Gen 3 x4 SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 PS5012-E12-27 from Phison, 64-layer TLC Toshiba BiCS flash, may have dram cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 on DRAM DDR4 with Micron 96L QLC - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Corsair MP600 Elite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E16 and Bics DDR4 DRAM buffer and TLC-based with SLC-mode cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair MP600 Pro XT, PRO LPX, PRO NH PCIe4 | <!--Model-->CSSD-F1000GBMP600ECS Elite, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 DRAMless SSD controller Phison PS5026-E26, BiCS6 162L QLC NAND |- | <!--Brand-->Corsair MP600 Core XT | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison and Bics QLC-based with SLC-mode cache - |- | <!--Brand-->Corsair MP700 Pro PCIe 5.0 | <!--Model-->CSSD-F1000GBMP700PNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial P1 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 QLC NAND but a controller with a DRAM cache - |- | <!--Brand-->Crucial P2 M.2 2280 Gen3 x4 NVM-express | <!--Model-->CT1000P2SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 dram-less Phison PS5013-E13-31 on 96-layer QLC NAND - |- | <!--Brand-->Crucial P3 Plus M.2 2280 | <!--Model-->CT1000P3PSSD8 CT2000P3PSSD801 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with Host Memory Buffer HMB tech to use a small bit of system RAM as DRAM cache and Micron 176-layer QLC NAND - |- | <!--Brand-->Crucial P3 M.2 nvme SSD | <!--Model-->CT2000P3SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron QLC (N48R) - |- | <!--Brand-->Crucial P5 m.2 nvme PCIe 4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 runs hot - Crucial NVMe with DRAM LPDDR4 and Micron 96L TLC |- | <!--Brand-->Crucial P5 Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 some have DRAM cache |- | <!--Brand-->Crucial T500 Gen4.0 nvme 2.0 | <!--Model-->CT1000T500SSD8, CT2000T500SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison PS5025-E25 with micron B58R 232-layer 3D TLC NAND and Micron LPDDR4 DRAM cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Crucial T700 Gen5 SSD | <!--Model-->CT1000T700SSD3, CT2000T700SSD3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 SSD controller Phison PS5026-E26, Micron 232-layer NAND with no dram as standard - |- | <!--Brand-->Crucial P310 M.2 2280 NVMe PCIe Gen4 SSD | <!--Model-->CT2000P310SSD801 (2Tb), | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 DRAM-less Phison E27T Micron 232-layer NAND - |- | <!--Brand-->Crucial T705 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 dramless Phison SSD controller |- | <!--Brand-->Crucial T710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 SMI SM2508 SSD controller dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN605 PCIe Gen3 x4 interface, NVMe 1.3 support | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Ediloca EN660 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN760 PCIe Gen4 x4 M.2 NVMe 1.4 interface | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 gets hot |- | <!--Brand-->Ediloca EN870 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 no dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca EN855 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S500 pro PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 MaxioTech MAP1202A-F1C with YMTC 128L and pseudo-SLC cache |- | <!--Brand-->Fanxiang S660 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S880/R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Fanxiang S770 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX550 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Fikwot FN501 Pro m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->FIKWOT FN950 FN955 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 MAP1602 (at 1600 MT/s) flash YMTC TLC no dram |- | <!--Brand-->Fikwot FX991 m.2 nvme | <!--Model-->FW-FX991-2TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FN960 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Fikwot FN970 m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Geil ZEN ITH m.2 nvme | <!--Model-->S3-240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Gigabyte Aorus Gen4 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash - DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Gigabyte Aorus 10000 PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->HP EX950 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HP FX900 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dram less |- | <!--Brand-->HP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Integral M2 Series NVME M.2 2280 PCIe Gen 3x4 | <!--Model-->INSSD500GM280NM2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Inland Professional TLC E12S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E18 |- | <!--Brand-->Inland Gaming performance Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash |- | <!--Brand-->Inland TD510 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM DDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->intel SSD Pro 7600p Series M.2 80mm 2280 PCIe 3.0 x4, 3D TLC | <!--Model-->SSDPEKKF512GB, SSDPEKKF256G8L, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel 660p m.2 nvme | <!--Model-->ssdpeknw010tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 SMI SM2263 controller with 1GB DRAM cache and 1TB of Intel QLC NAND similar to crucial P1 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] 670p | <!--Model-->SSDPEKNU010TZ | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 256 MB DDR3L cache and 12-140 GB SLC-Cache QLC NAND |- | <!--Brand-->Intel P4511 m.2 nvme PCIe3.1 x4 22110 110mm | <!--Model-->SSDPELKX020T8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 very long |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A1000 NVME PCIE M2 2280 SSD | <!--Model-->SA1000M8/480G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Kingston A2000 NVME PCIE M2 2280 SSD | <!--Model-->SA2000M8/250G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->Kingston KC3000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] PS5018-E18 PCIe 4.0 x4 NVMe controller and Micron’s 176L TLC NAND flash - |- | <!--Brand-->Kingston NV1 m.2 nvme pcie | <!--Model-->SNV1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 entry-level consumer DRAMless Phison E13T or Silicon Motion 4-channel SM2263XT - one brand TLC up to 1Tb and QLC after - |- | <!--Brand-->Kingston NV2 | <!--Model-->SNV2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 entry-level, first SMI SM2267XT or Phison E19T and later SMI SM2269XT or Phison E21T with various flash memory |- | <!--Brand-->Kingston FURY Renegade m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] Phison E18 controller, Micron 176L nand and ddr4 dram - |- | <!--Brand-->Kingston NV3 | <!--Model-->SNV3S/500G, SNV3S/1000G, SNV3S/2000G, SNV3S/4000G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 entry-level, SMI SM2268XT2 or Phison E27T controller with BiCS6 TLC or QLC flash - dramless so hmb - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia (Toshiba) XG4? M2 2280 NVMe PCIe SSD | <!--Model-->THNSF5512GPUK, THNSN51T02DUK, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 Phison has done custom controller work for Kioxia, and Kioxia has also worked with SMI and InnoGrit (the latter more recently). Kioxia label their controllers as their own but these are largely rebadged. |- | <!--Brand-->Kioxia (Toshiba) XG5 for Data Centres | <!--Model-->KXG5 KXG50ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 nanya ddr3 dram? with 64-layer BiCS 3D flash memory |- | <!--Brand-->Kioxia XG6 OEM m.2 nvme | <!--Model-->KXG60ZNV512G, KXG60ZNV1T02, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 TC58NCP090GSD with DRAM NANYA LPDDR3 and Toshiba BiCS FLASH 96-layer 3D TLC - |- | <!--Brand-->Kioxia (Toshiba) BG4 m.2 nvme | <!--Model--> *KBG40ZNS128G, KBG40ZNS256G, KBG40ZNS512G, KBG40ZNS1T02 *KBG40ZNT256G, *KBG40ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - no dram but NVMe's Host Memory Buffer (HMB) i.e. portion of the system's RAM for caching - Toshiba's 96-Layer BiCS FLASH - seems Windows UASP driver and the JMS583 chipset interacts badly with the Kioxia BG4 - early firmware upgrade to prevent overheating hot - |- | <!--Brand-->Kioxia XG7 | <!--Model-->KXG70ZNV1T0G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 - might need firmware update on early 2tb 4tb versions - controller with sk hynix dram and tlc nand |- | <!--Brand-->KIOXIA EXCERIA PLUS G2 SSD series PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5012-E12S-32 aka TC58NC1201GST 4-channel controller along with KIOXIA proprietary 96-layer 3D TLC and "MG2h" version has BiCS4.5 which is faster than launch BiCS4 - - |- | <!--Brand-->Kioxia XG8 OEM m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 TC58NC0L1XGSD with DRAM LPDDR4 and 112-Layer Kioxia BiCS5 TLC - |- | <!--Brand-->Kioxia (Toshiba) BG5 | <!--Model-->KGB50ZNV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 HMB buffer |- | <!--Brand-->Kioxia (Toshiba) BG6 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless |- | <!--Brand-->KIOXIA EXCERIA PLUS G3 SSD series PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 has hmb, like most dram-less nvmes KIOXIA |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar 1TB SSD M.2 NVME 1.4 Gen3x4 M.2 2280 | <!--Model-->NM610Pro | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Lexar NM620 *IG5216 (worse?) not great original 96L *MAP1202 YMTC up to 232L, or 176L Micron, TLC for the 1TB | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 a few versions all DRAM-less, |- | <!--Brand-->Lexar NM790 SSD M.2 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Maxio MAP1602 no DRAM so HMB with 232-Layer YMTC TLC |- | <!--Brand-->Lexar m.2 nvme | <!--Model-->EQ790 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Maxio MAP1602, no DRAM so HMB, Flash Memory 232-Layer YMTC TLC, |- | <!--Brand-->Lexar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Liteon M.2 NVME 512GB SSD 2280 | <!--Model-->CAZ-51282512-Q11 DP/N 0K64PG | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI controller |- | <!--Brand-->Micron 2200S m.2 nvme 2200 series | <!--Model-->MTFDHBA256TCK, MTFDHBA512TCK | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 for a time, Micron controller with 64L TLC 3D Nand [https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=3jg3g BSOD occurred as CRITICAL_PROCESS_DIED] before self applied firmware [https://support.lenovo.com/us/en/downloads/ds119265-nvme-solid-state-drive-firmware-update-utility-for-windows-10-64-bit-thinkpad apparently it is related to the power management that disconnects the Micron SSD] |- | <!--Brand-->Micron 2300 m.2 nvme Gen 3 x4 | <!--Model-->MTFDHBA256TDV P/N M02626-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Micron 3400 M.2 NVME SSD Gen4 | <!--Model-->MTFDKBA512TFH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no cache |- | <!--Brand-->Micron 2450 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 E19T |- | <!--Brand-->Micron 2600 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison's PS5029-E29T SSD controller with Micron 276-layer G9 QLC NAND in a DRAMless - Adaptive Write Technology (AWT) using various NAND modes (SLC, TLC, and QLC) as a dynamic cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium S270 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium M450 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV2000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico J10 J-10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Orico D10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Orico e3500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Orico O7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Patriot P300 m.2 nvme pcie 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Patriot Viper VP4300 Lite M.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS2230 Gen3 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->PNY CS2140 CS2342 Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Raydisk 1T 2280 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 no dram, Memory QLC Intel 144 layer. Chip Realtek |- | <!--Brand-->Raydisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket Nano 2242 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket 4.0 m.2 nvme | <!--Model-->SB-2130-512, SB-2280-1TB, SB-Rocket-NVME4-HTSK-2TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 4.0 PLUS m.2 nvme | <!--Model-->SB-RKT4P-1TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E1? controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Phison E25 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung PM951 m.2 nvme | <!--Model-->MZVLV1T | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 950 PRO PM961 M.2 2280 NVMe 1.3 PCI-Express 3.0 x4 | <!--Model--> *MZ-VKW5120 *MZ-VLW2560 MZVLW256HEHP-000L7, MZ-VLW5120, MZ-SLW1T00 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - possibly 512M LPDDR3 Samsung K4E4E324EE-ECCF cache - Polaris (S4LP077X01-8030) unit with Samsung 48-layer TLC V-NAND V3 flash Samsung K90MGY8S7M-CCK0 - |- | <!--Brand-->Samsung 960 Pro SM961 M.2 PCi-e NVMe SSD 2280 | <!--Model-->MZ-V6P1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 Polaris (S4LP077X01-8030) controller Samsung 48-layer multi-level cell (MLC) V-NAND, pseudo-SLC cache or LPDDR3-1866 Samsung K4E8E304EE-EGCF |- | <!--Brand-->Samsung PM981 2280 PCI-Express 3.0 x4 | <!--Model--> *Rev 0 MZ-VLB256A, MZ-VLB512A, MZ-VLB1T0A, *Rev 0 MZ-VLB2560, MZ-VLB5120 P/N MZVLB512HAJQ, MZ-VLB1T00, *Rev ? MZ-VLB256B, MZ-VLB512B, MZ-VLB1T0B, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache hybrid SLC Samsung’s TurboWrite - |- | <!--Brand-->Samsung PM981a 2280 PCI-Express 3.0 x4 | <!--Model-->MZ-VLB5120 P/N MZVLB512HBJQ-000L7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache |- | <!--Brand-->SAMSUNG PM991 NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ2560 MZVLQ256HBJD-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SAMSUNG PM991a NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ256B MZVLQ256HBJD-00BH1, MZ-9LQ256C, MZ-VLQ512B MZVLQ512HBLU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Samsung 970 EVO Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Samsung Phoenix on Samsung LPDDR4 dram and 2 Samsung 9x-layer V-NAND TLC |- | <!--Brand-->Samsung 980 EVO Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Samsung 980 Pro m.2 nvme | <!--Model-->MZ-V8P1T0BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 originally made in Korea ([https://semiconductor.samsung.com/consumer-storage/support/tools/ 2tb firmware issues] with versions starting with 3) and year later Vietnam - DRAM |- | <!--Brand-->Samsung 990 EVO m.2 nvme | <!--Model-->MZ-V9E2T0BW, MZ-V9E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo no DRAM so HMB Samsung 133-Layer TLC (V6P) and Samsung 133-Layer TLC (V6P) - |- | <!--Brand-->SAMSUNG PM9A1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model-->MZ-VL25120 MZVL2512HCJQ, MZVL21T00 MZVL21T0HCLR-00BL2, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 might be OEM variant of the 980 Pro |- | <!--Brand-->Samsung PM9B1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model--> *2023 MZ9L4256HCJQ-00BD1 MZ-9L4256A, , *2025 MZ-VL42560, MZ-VL45120, MZ-VL421T, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SSD controller is Marvell 88SS1322 Whistler Plus, no DRAM cache and Samsung 128-layer TLC NAND flash |- | <!--Brand-->Samsung 990 EVO Plus m.2 nvme2.0 | <!--Model-->MZ-V9S2T0BW, MZ-V9S1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo with no DRAM so HMB and Samsung 236-Layer (V8) TLC - |- | <!--Brand-->Samsung 990 Pro m.2 nvme | <!--Model-->MZ-V9P2T0BW, MZ-V9P1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 2tb early firmware issue - Samsung Pascal with DRAM LPDDR4 and 176-Layer V-NAND TLC - has had firmware design issues, causing premature failure - |- | <!--Brand-->Samsung 9100 PRO PCIe Gen5 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Seagate Firecuda 510 G3 x4 nvme | <!--Model--> *ZP1000GM30001, *ZP500GM30021 P/N 2NT308-300, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad early batch - Phison E12 STXYP0160031 on SK Hynix DRAM DDR4 with Kioxia BiCS3 64L TLC |- | <!--Brand-->Seagate Firecuda Q5 | <!--Model-->ZP500CV30001,ZP250CV30001,ZP1000CV30001 P/N 2ZK307-881,ZP2000CV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 PS5013-E13-31 from Phison, no DRAM cache and QLC nand |- | <!--Brand-->Seagate Firecuda 515 | <!--Model-->ZP500GV30001,ZP250GV30001,ZP1000GV30001,ZP2000GV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 no dram and qlc nand |- | <!--Brand-->Seagate FireCuda 520 SSD M.2 PCIe Gen4 ×4 NVMe 1.4 | <!--Model-->ZP2000GM30002, ZP1000GM30002, ZP500GM30002 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Seagate Firecuda 520N m.2 nvme | <!--Model-->ZP2000GV3A012, ZP1000GV3A012 and ZP500GV3A012 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 530 m.2 nvme | <!--Model-->ZP500GM3A013, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5018-E18 on DRAM DDR4 with Micron 176L TLC |- | <!--Brand-->Seagate | <!--Model-->ZP1000CV3A002, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 540 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand-->Seagate Firecuda 530R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power UD85 m.2 nvme PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 [http://vlo.name:3000/ssdtool/ firmware tools] |- | <!--Brand-->Silicon Power UD90 PCIe 4.0 nvme | <!--Model-->SP250GBP44UD9005, SP500GBP44UD9005, SP01KGBP44UD9005, SP02KGBP44UD9005, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron TLC (B47R) but later no name QLC nand instead - |- | <!--Brand-->Silicon Power A60 A80 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 various originally an E12 drive with 64L Toshiba NAND, then had variations with E12S and SM2262EN as well as random 64L/96L, now it comes with a MAP1001A controller by Maxio and some YMTC NAND - |- | <!--Brand-->Silicon Power US75 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix BC501 M.2 m.2 NVMe PCIe Gen3 SSD | <!--Model--> *Rev0 HFM256GDHTNG-8510B SSS0L24764, HFM256GDJTNG-8310A, *Rev1 HFM256GDHTNG-8310A SSS0Q68673, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 bad batch early - |- | <!--Brand-->SK Hynix BC511 512GB NVMe PCIe M2 2230 SSD | <!--Model-->HFM256GDJTNI-82A0A HFM512GDGTNI-82A0A D P/N 0TG8T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 no dram cache |- | <!--Brand-->SK hynix BC711 PCIe Gen3 x4 | <!--Model-->HFM001TD3JX013N, HFM512GD3JX013N, HFM256GD3JX013N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 okay but no dram cache |- | <!--Brand-->SK hynix PC711 m.2 2280 PCIe Gen3 x4 | <!--Model--> *HFS001TDE9X073N, HFS512GDE9X073N, HFS256GDE9X073N *HFS001TDE9X080N, HFS512GDE9X080N, HFS256GDE9X081N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->SK Hynix SC210 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SK Hynix PC601 PCIe 3.0 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - Cepheus Plus YCN34PTA0FR Controller and 48L TLC Flash, pseudo-SLC cache and LPDDR4-3733 SK Hynix H9HCNNN8KUMLHR-NME dram - |- | <!--Brand-->SK Hynix PC401 3rd gen PCIe | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad batch early - |- | <!--Brand-->SK hynix Gold P31 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 SK hynix’s proprietary Cepheus controller |- | <!--Brand-->Sk Hynix SK500 Gen 4 (x4) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SK hynix Platinum P41 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Aries SSD controller with 176-Layer TLC flash - SK hynix LPDDR4 dram - |- | <!--Brand-->Sk Hynix PC801 PCIe Gen4 x4 m.2 nvme | <!--Model-->HFS001TEJ9X101N, HFS512GEJ9X101N, HFS256GEJ9X101N, HFS002TEJ9X101N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->SK Hynix BC901 m.2 nvme PCIe Gen4 2230 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Silicon Motion SM2269XT with no DRAM so HMB buffer cache - SK Hynix 176-layer TLC NAND flash 1TB only - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team | <!--Model-->TM8PS7512G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TeamGroup MP34 | <!--Model-->MP34 256GB, MP34 512GB, MP34 1TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 good Phison E12 with DRAM NANYA DDR3L and Toshiba BiCS 3 64L TLC - |- | <!--Brand-->Team Group T-Force Cardea A440 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison PS5018-E18 NVMe 1.4 controller and Micron’s 96L TLC with SK hynix 8Gb DDR4 chips but not OPAL-compliant AES 256-bit |- | <!--Brand-->Team Group TForce Cardea A440 Lite PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 dram-less E27T controller and 162L TLC but not OPAL-compliant AES 256-bit |- | <!--Brand-->teamgroup Team Z44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand-->teamgroup Team MP44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E21T no DRAM so HMB with 176-Layer Micron TLC |- | <!--Brand-->Team MP33Q | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - dramless maxio MAP1202 with TLC (MP33) or QLC (MP33Q) - |- | <!--Brand-->Team Group QX GE Pro m.2 nvme PCIe5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 innogit IG5666 with QLC 3D 232L nand with DRAM - |- | <!--Brand-->Team Group T-Force G70 Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 InnoGrit IG5236 (Rainier) with DRAM and NAND YMTC TLC - |- | <!--Brand-->Team Group T-Force Cardea Z540 m.2 nvme PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison E26 controller and 232L TLC and DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE110S PCIe Gen3 x4 M.2 2280 TS128GMTE110S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND |- | <!--Brand-->Transcend MTE220S PCIe Gen3 x4 M.2 2280 TS2TMTE220S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND with DRAM Cache |- | <!--Brand-->Transcend MTE300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand-->Transcend MTE300S PCIe Gen3 x4 M.2 2230 TS256GMTE300S TS512GMTE300S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND, 1G and 2G get hot |- | <!--Brand-->Transcend | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE400S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 mlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Union Memory (Shenzhen) AM6672 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM6A0 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Verbatim V15000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->WD Blue SN500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western digital SN720 M.2 2280 NVME PCIE for Data Centers | <!--Model-->SDAQNTW-512G-1001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2021 |- | <!--Brand-->WDC SN520 2230 Gen3 x2 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2020 |- | <!--Brand-->Western digital ix sn530 M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 industrial sandisk controller and firmware, as well as 96-layer 3D TLC NAND memory that can work in TLC or SLC mode - |- | <!--Brand-->Western digital SN730 Gen3 x4 M.2 2280 M.2 NVME | <!--Model-->SDBPNTY-1T00, SDBPNTY-512G-1012, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 to 2021 DRAM Cache DDR4-2666 CL18 Micron MT40A512M16LY-075:E (D9WFH) with Controller WD 20-82-00705-A2 Triton MP28 and NAND Flash Toshiba BiCS4 60082 512G (Rebranded by SanDisk) TLC 96-layer |- | <!--Brand-->WD Black SN750 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 64-layer 3D stacked NAND with 3 bits per cell TLC (Triple Level Cell) with 256MB of skhynix DRAM cache for every 250GB |- | <!--Brand-->WD Black SN850 m.2 nvme Gen4 PHY | <!--Model-->WDS100T1X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Sandisk G2 controller with Micron DDR4 cache - new nCache 4.0 slc cache total dynamic capacity spans one-third (300GB on 1TB) with a small static SLC cache (12GB on 1TB) from the Kioxia BiCS4 96L TLC 96-layer NAND flash - |- | <!--Brand-->Western digital SN550 Blue M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - various controllers and NANDs |- | <!--Brand-->Western Digital SN810 NVMe SSD 2280 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 slc cache - laptop oem only no retail version - |- | <!--Brand-->WD SN850X | <!--Model-->WDS100T2X0E, WDS200T2X0E, WDS400T2X0E, WDS800T2X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 issues with early ssd firmware and AMD Zen 3 X570 and X670E chipsets - Sandisk A101000291-82 controller with 112-layer TLC and DDR4 DRAM cache |- | <!--Brand-->WD_Blue SN570 single-sided M.2 2280 (80mm) PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless - WD/SanDisk SSD controller with BiCS 5 3D NAND TLC 112-layer NAND flash memory - |- | <!--Brand-->WD_Black SN770 m.2 nvme | <!--Model-->WDS100T3X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless cache with TLC |- | <!--Brand-->WD Green SN350 m.2 NVMe SSD | <!--Model-->WDS100T3G0C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 DRAM-less cache with SanDisk controller and QLC (quad-level cell) NAND |- | <!--Brand-->WD_BLACK SN750 SE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Phison E19T, dramless |- | <!--Brand-->WD SN740 M.2 (2230) PCIe 4.0 x4 2280 | <!--Model-->SDDQTQD-1T00, SDDPNQD-, SDDPNQD-256G-2006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless with SSD controller WD Sandisk 20-82-10081-A1 Polaris MP16+ with Toshiba BiCS5 112-layer TLC NAND flash |- | <!--Brand-->WD_Blue SN580 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless SanDisk controller with (HMB) and 112-Layer Kioxia TLC (BiCS5) |- | <!--Brand-->WD Blue SN5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Black SN8100 / Sandisk Optimus GX Pro 8100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk Optimus GX 5100 7100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk Optimus GX Pro 850X | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Zhitai (Yangtze Memory) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === Mini SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Biwin PCIe 4×2 NVMe 1.3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 GPDwin5 and Oneplayer Superx hybrid - 3D TLC - LGA packaging - V1 slide tray mechanism - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- |} ==SATA== Advanced Host Controller Interface (AHCI), a programming interface for SATA host controllers. Platforms supporting AHCI may take advantage of performance features such as no master/slave designation for SATA devices — each device is treated as a master — and hardware-assisted native command queuing. AHCI may but not often also provides usability enhancements such as Hot-Plug (Desktop and Mobile Only). AHCI requires appropriate software support (e.g., an AHCI driver) AHCI, the underlying protocol for SATA, only supports one queue with 32 commands. The issue with AHCI is that it's going to take a pile of test hardware just to figure out all the different bugs in all the motherboard chipsets and add-on PCI cards that 'kinda' implement AHCI. Not to mention Silicon Image, which took a very different approach from Intel's AHCI in their SATA controllers. === SATA 7mm 2.5inch SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand-->ADATA 240GB Ultimate SU630 2.5" | <!--Model-->ASU630SS-240GQ-R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->ADATA Ultimate Su650 2.5in | <!--Model-->ASU650SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->ADATA Ultimate Su800 2.5in | <!--Model-->ASU800 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI SM2258 controller with Micron 3D TLC NAND but low performance when data fills the SLC cache - slow write speed - |- | <!--Brand-->ADATA Ultimate Su680 2.5in | <!--Model-->ASU680SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS340 Panther | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS350 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial M225 SSD 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2009 sata2 3gbp/s |- | <!--Brand-->Crucial C300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 sata3 6gbps - |- | <!--Brand-->Crucial M4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2011 Marvell 88SS9174-BKK2 processor, 25nm MLC NAND flash and 128MB dram cache |- | <!--Brand-->Crucial M500 120Gb to 960Gb | <!--Model-->CT250M500SSD1, CT500M500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 dram cache |- | <!--Brand-->Crucial M550 120G to 1T | <!--Model-->CT250M550SSD1, CT500M550SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dram cache |- | <!--Brand-->Crucial (Micron) BX100 | <!--Model-->CT500BX100SSD1, CT1000BX100SSD1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - no dram - Silicon Motion SM2246EN and ATA version ACS-2 - |- | <!--Brand-->Crucial (Micron) MX100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache Micron controller and nand - |- | <!--Brand-->Crucial MX200 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC NAND |- | <!--Brand-->Crucial (Micron) BX300 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dramless cache - Micron ex Tidal controller and TLC nand - |- | <!--Brand-->Crucial (Micron) MX300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand-->Crucial (Micron) bx500 2.5inch | <!--Model-->CT240BX500SSD1, CT480BX500SSD1, CT960BX500SSD1, CT1000BX500SSD1, CT2000BX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SM2258XT 4channel later SM2259XT paired with Micron’s latest 64-Layer 3D TLC flash but dramless SLC cache (part of the tlc flash) - |- | <!--Brand-->Crucial (Micron) MX500 | <!--Model-->CT250MX500SSD1, CT500MX500SSD1, CT1000MX500SSD1, CT2000MX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - dram cache from 256M to 2G - discontinued end of 2024 |- | <!--Brand-->Fanxiang S101 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no dram cache, Hynix memory 3dv7-176l 176 layer QLC (one chip), either raymx rm1135, SM2259XT controller or Realtek rts5735dlq |- | <!--Brand-->Fanxiang ranxiana S102 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - no dram - |- | <!--Brand-->Fanxiang S101Q 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fanxiang | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX815 Standard 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FS810 Ultra 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertec FirestormLite 2.5inch | <!--Model-->S240GHS3-M or SDSSD240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertech | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral V2 Plus 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel SSD 520 Series 2.5 inch SATA 6Gb/s 2.5" SSD Solid State Drive | <!--Model-->SSDSC2CW240A3, SSDSC2CW480A3, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 LSI SandForce SF2281, Flash Memory Intel Synchronous 25nm MLC - |- | <!--Brand-->Intel Pro Series 1500 | <!--Model-->SSDSC2BF180A4L SSD0E38417, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Intel S3610 Series 2.5" 400GB 6GBPS SATA SSD | <!--Model-->SSDSC2BX400G4R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 data center |- | <!--Brand-->Intel SSD Pro 5400s 512 GB | <!--Model-->SSDSC2KF512H6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3510 Series MLC 2.5" | <!--Model-->SSDS2BB400G6, SSDSC2BB480G6R, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3520 Series MLC 2.5" | <!--Model-->SSDSC2BB800G7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel SSD DC S3710 Series 800GB 2.5" | <!--Model-->SSDSC2BA800G4P, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 server |- | <!--Brand-->Intel SSD 545S Series 256GB 512GB | <!--Model-->SSDSC2KW256G8X1, SSDSC2KW512G8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] SSD DC S4500 240GB 2.5inch - HP Enterprise | <!--Model-->SSDSC2KB240G7P | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingspec P3-512 P3-1T0 P3-2TO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston SSDNow 300 | <!--Model-->SV300S37A/240G, SV300S37A/120G, SV300S37A/60G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dramless - lsi sandforce SF2281 or JMicron JMF662 controller with Toshiba MLC or Intel MLC |- | <!--Brand-->Kingston A400 120G to 960Gb 2.5inch | <!--Model-->SA400S37/240G SBFK61K1, SA400S37/480G, SA400S37/960G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 half case sized ssd 4 x FH64B08UCT1-60 64G - t6 security torx into metal case - dram less - poor write speeds - |- | <!--Brand-->Kingston | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia formerly Toshiba HG6 2.5in | <!--Model--> *9.5mm THNSNJ512GBSU, THNSNJ256GBSU, THNSNJ128GBSU *7mm THNSNJ512GCSU THNSNJ512GCSY, THNSNJ256GCSU THNSNJ256GCSY, THNSNJ128GCSU THNSNJ128GCSY | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar NS100 2.5 inch sata | <!--Model-->LNS100-1TRB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - Marvell 88NV1120 Artemis, a DRAM cache is not available and pseudo-SLC. Micron 64-layer TLC NAND flash 4 chips @ 512 Gbit TS7512G181 (Rebranded by Lexar) (256G) - 4 nand flash chips Lexar/TST22T181/ B1924 and one controller: Lexar DM918/NOD43 1907 (512G) - |- | <!--Brand-->Lexar NQ100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - DM928 controller which operates without a DRAM buffer. Two 128GB Micron NAND flash chips |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LiteOn | <!--Model-->LCS-128L9S-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 no dram - sata2 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Matrix 256Gb 512GB SATA 2.5in SSD | <!--Model-->MIS512GSDS, MIS256GSDS | <!--Work MSDos-->UP TO 550MB/S | <!--Work GPT-->UP TO 500MB/S | <!--Tested Distribution--> |- | <!--Brand-->Micron 1100 | <!--Model-->MTFDDAK2T0TBN-1AR1ZA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron 1300 2TB 1300 2.5" | <!--Model-->MTFDDAK2T0TDL-1AW1ZABHA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 - old sdd - TLC nand - |- | <!--Brand-->Micron RealSSD C400 2.5inch | <!--Model-->MTFDDAK256MAM-1K12 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Mushkin Reactor | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC flash |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac SA500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico Y-20 Y20 2.5 inch sata SHENZHEN ORICO TECHNOLOGIES CO.,LTD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 flash nand - |- | <!--Brand-->Orico S500-Pro s500pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Origin Storage Inception TLC830 Pro Series 2.5in SATA III SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D tlc flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand-->Patriot P210 2.5 inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> qlc flash nand - |- | <!--Brand-->Patriot P220 | <!--Model-->P220S2TB25 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Plextor M6V | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS900 2.5 in sata SSD | <!--Model-->SSD7CS900-480-PB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->PNY CS2311, CS3030 and Pro Elite SSDs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung SM PM | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->PM871a or PM871b? SM/PM = 2-bit or 3-bit MLC. PM = 3-bit MLC = TLC. 8 = generation = 8xx, 7 = model = 850 EVO (in this case), 1 = usage (e.g. 3 = datacenter). a/b = revision or type of flash, the 850 EVO had multiple revisions including at least three types of flash (32L, 48L, 64L) so a = 32/48L, b = 64L. At lower capacities it might use different flash, for example the 256GB SM951 utilizies 2D/planar while the higher capacities use 3D. OEM drives tend to have different, optimized firmware, so performance will not be the same |- | <!--Brand-->Samsung 840 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Samsung 840 EVO | <!--Model-->MZ-7TE120 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 |- | <!--Brand-->Samsung PM851 2.5in sata | <!--Model-->MZ-7TE5120 P/N MZ7TE512HMHP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Samsung 850 EVO | <!--Model-->MZ-75E120, MZ-75E500 (P/N MZ7LN500) to MZ-75E4T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 Samsung MGX controller (S4LN062X01) up to 500GB capacities whilst Samsung MEX controller (3-core) beyond - Samsung TLC 3D V‐NAND 48 and later 64 layers and possibility of 256MB, 512MB or 1GB LPDDR2-1066 DRAM chip - |- | <!--Brand-->Samsung 850 PRO | <!--Model-->MZ-7KE1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung PM871a 2.5 inch sata | <!--Model-->MZ-7LN512A P/N MZ7LN512HMJP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung PM883 1.92TB | <!--Model-->MZ-7LH1T90 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - - Samsung MJX Maru (S4LR030) - 1gb LPDDR4-1866 dram - |- | <!--Brand-->Samsung 860 EVO | <!--Model-->MZ-76E1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung 860 EVO PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 860 QVO | <!--Model-->MZ-76Q1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 870 QVO 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - MKX 8-channel controller |- | <!--Brand-->Samsung 870 EVO | <!--Model-->MZ-7LN56F, MZ-77E1T0 P/N MZ7L31TOHBLB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 beware of bad batch early death - uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand-->Samsung PM871b | <!--Model-->MZ7LN256HCHP-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Sandisk Ultra 3D/Extreme Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 SandForce SF-2281 dram |- | <!--Brand-->Sandisk Ultra Plus | <!--Model-->SDSSDHP-256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell SS889175 processor with SanDisk's 19nm NAND and 128MB Samsung DDR2 DRAM chip |- | <!--Brand-->Sandisk Z300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Marvell 88SS9188 Marvell 88SS9187 with SanDisk 64Gbit 19nm MLC - |- | <!--Brand-->Sandisk x300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Sandisk x300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk Plus | <!--Model-->SDSSDA-240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 pseudo SLC cache dramless |- | <!--Brand-->Sandisk Z400s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - Silicon Motion SM2246XT DRAM-less - budget end of market - |- | <!--Brand-->Sandisk x400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 4 NAND packages and marvell controller 88ss1074 on blue pcb - 512MB DDR3L-1600 Micron DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Seagate BarraCuda Q1 SSD | <!--Model-->ZA240CV10001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 dramless A55 started with the Phison S10 but later the S11 i.e. Phison PS3111-S11-13 controller and 96-layer TLC NAND flash memory with a pseudo-SLC cache - |- | <!--Brand-->Silicon Power Ace A55 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand-->sk hynix | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 sandforce controller - |- | <!--Brand-->sk Hynix SH910A | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Link_A_Media (LAMD) controller with eight 256Gbit H27QEGDVEBLR NAND 20nm hynix MLC - SK hynix H5PS1G83JFA DRAM - |- | <!--Brand-->sk Hynix SC300 | <!--Model-->HFS256G32MND-3210A, HFS256G32MND-3312A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - red strip around edges - 8-channel controller SK hynix LM87810AA-A0 with DDR2 buffer chip and four pieces of 16nm hynix MLC NAND - |- | <!--Brand-->Sk Hynix Canvas SL300 series 2.5in SSD *3110A SL301STD *3210A *3300A *3310A | <!--Model-->HFS500G32TND, HFS256G32TNE, HFS128G32TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC - consumer line red in corners - SK hynix LM878100AA (HFS256G32MND-3312A) later SH87820BB and NAND 16nm hynix TLC - 256mb dram |- | <!--Brand-->Sk Hynix Canvas SC3 series 2.5in SSD *N1A0A , , *N1A1A *N1A2A SC308STD, *N2A0A , , SC311STD | <!--Model-->HFS512G32TNF-N2A0A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - red in corners - no dram and no SLC cache - Hynix ex Link_A_Media Devices (LAMD) SH87820BB 2c but poor mixed workload ability MLC - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team EX2 GX2 Elite QX | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->TEAMGROUP AX2 2.5 Inch SATA III Solid State Drive SSD | <!--Model-->T253A3512G0C101, T253A3001T0C101, T253A3002T0C101, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 3D NAND TLC |- | <!--Brand-->TeamGroup TF Vulcan Z 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dramless smi2259xt 128L tlc nand - |- | <!--Brand-->TeamGroup T-Force Vulcan ZQLC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram-less smi2259xt qlc 144L nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Topesel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend 220S 2.5in | <!--Model-->TS120GSSD220S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 3D TLC without dram |- | <!--Brand-->Transcend SSD230S 2.5in | <!--Model-->TS256GSSD230S TS512GSSD230S TS1TSSD230S TS2TSSD230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 3D TLC NAND with DRAM Cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Viathan | <!--Model-->S001T3V | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red SA500 NAS | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->WD Blue SA510 250Gb to 4Tb | <!--Model-->WDS400T3B0A WDS200T3B0A WDS100T3B0A WDS500G3B0A WDS250G3B0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - |- | <!--Brand-->Western Digital WD Green SSD 2.5" | <!--Model-->WDS240G1G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Green 200Gb to 2Tb | <!--Model-->WDS200T2G0A WDS100T3G0A WDS480G2G0A WDS240G2G0A WDS120G2G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - cheap and slow ssd - |- | <!--Brand-->WD SA530 | <!--Model-->SDASB8Y-256G SD9SB8W, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->[https://www.xray-disk.com xraydisk] 2.5 inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> from the manufacturer only - Phsion/SMI(2258XT)/Realtek/Yeestor |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Xum | <!--Model-->hx256gssdsata3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Yottamaster | <!--Model-->Y3000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCie 3.0 |- | <!--Brand-->Yottamaster | <!--Model-->Y7000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCIe 4.0 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |} === SATA M.2 (M and B key) === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 2280 Sata | <!--Model-->AXNS381E-128GM-B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S201 m.2 sata 2280 | <!--Model-->S201 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot FN203 m.2 sata (oldtan, twipps, teexin aka Shenzhen Pingfan "Ordinary" Road Technology Co., Ltd) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 lifespan not long Maxio MAP + YMTC 128L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Foresee (Shenzhen Longsys) | <!--Model-->YSM80CD-128G YSDE128G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 88nv1120-bt22 T3WU030 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral 2242 120G | <!--Model-->INSSD120GM242 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral M.2 2280 | <!--Model-->INSSD256GM.26M2280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral 256GB/512GB/1TB/2TB | <!--Model-->INSSD1TM280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 netac rebrand - no dram cache - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel Pro ‎545S 2280 | <!--Model-->SSDSCKKF256G8H | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> no dram, TLC nand |- | <!--Brand-->Intel | <!--Model-->SSDSC2KF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intenso M.2 internalSSD SATA III 1 TB | <!--Model-->Top | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A400 m.2 | <!--Model-->SA400M8/240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 entry level ssd 4 x FH64B08UCT1-60 64G - |- | <!--Brand-->Kingston | <!--Model-->RBU-SNS8350DES3128GP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston V300 | <!--Model-->SV300S3505AG | <!--Work MSDos-->{{yes}} | <!--Work GPT--> | <!--Tested under-->Nightly Build 2014-09-18 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON SATA 128GB | <!--Model-->CV3-8D128-11 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON | <!--Model-->CV1-8B256-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lite-On | <!--Model-->L8H-256V2G-HP L8H-128V2G-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 2016 nanya nt5c864m16fp-dh |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LSI | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 SF37000 controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model-->M550 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell 88SS9189 SATA controller |- | <!--Brand-->Micron M600 enterprise m.2 sata up to 512GB | <!--Model-->MTFDDAV256MBF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 Marvell 88SS9189 SATA controller, DRAM chip 256MB 533MHz LPDDR2, NAND for the 256GB drive MT29F1T08CQCCBG2-10:C 16nm MLC NAND each 128GB package |- | <!--Brand-->MICRON 1100 M.2 SATA 6Gb/s 2280 | <!--Model-->MTFDDAV256TBN HP P/N 903109-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Orico Y20M-2242 | <!--Model-->Y20M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->PNY | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung PM841 M.2 sata3 2280 | <!--Model-->MZ-NTD2560/0L9 MZNTD256HAGL-000L9 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung CM871 Rev 0 | <!--Model-->MZNLF128HCHP-000H1 MZ-NLF1280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM871a m.2 Sata | <!--Model-->MZNLN256HMHQ, NLN512A P/N MZNLN512HMJP-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC |- | <!--Brand-->SAMSUNG PM871b | <!--Model-->MZNLN128HAHQ-000H1, MZNLN256HAJQ MZ-NLN256F MZ-NLN256C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM881 | <!--Model-->MZ-NLH1280 MZNLH128HBHQ-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SanDisk X300 M.2 sata 2280 80mm SSD Solid State Drive | <!--Model-->SD7SN6S-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk X400 SSD M.2 sata 2280 | <!--Model-->SD8SN8U-128G-1006, SD8SN8U-256G-1006, SD8SN8U-512-1006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 SSD controller Marvell 88SS1074 four channel supports variety of NAND and up to 512MB DDR3L-1600 Micron DRAM cache - |- | <!--Brand-->SanDisk X600 M.2 SSD Solid State Drive | <!--Model-->SD9SN8W-128G-1006 SD9TN8W-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SANDISK X110 DELL 6T4HK M.2 2260 | <!--Model-->SD6SP1M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix SC300 | <!--Model-->SC308M280S HFS128G39TND | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 SH87820BB controller - No dram buffer - multi-level cell (MLC) NAND |- | <!--Brand-->SK HYNIX | <!--Model-->SC311 HFS256G39TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK HYNIX | <!--Model-->SC401 HFS256G39TNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 M.2 sata 2280 | <!--Model-->A55 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TEAMGROUP Team MS30 SSD M.2 Sata 2280 | <!--Model-->TM8PS7001T0C101 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Toshiba RC100 (retail version of BG3) | <!--Model-->KBG30ZMV256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Toshiba HG6 m.2 | <!--Model-->THNSNJ512GDNU THNSNJ512G8NY, THNSNJ256GDNU THNSNJ256G8NY, THNSNJ128GDNU THNSNJ128G8NY, THNSNJ256GVNU THNSNJ128GVNU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TOSHIBA SSD M.2 2280 256GB | <!--Model-->KSG50ZMV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand-->Kioxia (Toshiba) BG6 | <!--Model-->KSG60ZMG256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend | <!--Model-->400 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend M.2 SSD 2242 TS32GMTS400S TS64GMTS400S TS128GMTS400S | <!--Model-->400S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> DDR3 dram cache and mlc nand |- | <!--Brand-->Transcend | <!--Model-->M.2 SSD 600 (2260), M.2 SSD 800S (2280) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> mlc nand |- | <!--Brand-->Transcend M.2 SSD 2242 TS120GMTS420S TS240GMTS420S TS480GMTS420S | <!--Model-->420S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> can run hot slc cache |- | <!--Brand-->Transcend M.2 SSD 2242 TS256GMTS430S TS512GMTS430S | <!--Model-->430S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache - 3d tlc nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS120GMTS820S TS240GMTS820S TS960GMTS820S | <!--Model-->820S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS256GMTS830S TS512GMTS830S TS1TMTS830S TS4TMTS830S | <!--Model-->830S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 120GB to 480Gb | <!--Model-->WDS480G2G0B WDS240G2G0B WDS120G2G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 made in malaysia |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 240Gb to | <!--Model-->WDS240G3G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 made in |- | <!--Brand-->WD Blue SA510 M.2 SATA 250Gb to 2Tb | <!--Model-->WDS200T3B0B WDS100T3B0B WDS500G3B0B WDS250G3B0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red 500GB 1TB 2TB | <!--Model-->SA500 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM610 m.2 sata | <!--Model-->SSS0R27339, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === mSATA SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fangxiang S301 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingchuxing | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model-->INSSD256GMSA MO-300 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc 3d nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron enterprise | <!--Model-->M600 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico ZH-10 ZH10 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Samsung 840 EVO 1.8inch msata | <!--Model-->MZ-M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung 850 EVO 1.8in | <!--Model-->MZ-M5E120BW, MZ-M5E250BW, MZ-M5E500BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM851 1.8" msata | <!--Model-->MZ-MTE256D P/N MZ-MTMTE256HMHP, MZ-MTE1T00, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 860 EVO 1.8inch msata | <!--Model-->MZ-MM6E250BW, MZ-M6E500BW, MZ-M6E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Transcend TS64GMSA370S | <!--Model-->MSA370S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC nand |- | <!--Brand-->Transcend TS64GMSA230S | <!--Model-->230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3d tlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === SATA 2.5inch Laptop Hard Disks === ====7mm==== {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP628230-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP552605-01 250Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP693440-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HGST Hitachi Z5K320 Z5K500-500 Z5K100 series * 2013 HTS545050A7E380 HTS * 2015 HTS545050A7E680 HTS | <!--Model-->HTS 320GB 500Gb 1Tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->HGST Hitachi Z7K320 Z7K500 series | <!--Model-->HTS725050A7E630 320Gb HTS725050A7E635 500Gb 7200rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> avoid if it does not have the DCM code |- | <!--Brand-->HGST 1T 5400rpm | <!--Model-->HTS541010B7E610 | <!--Work--> | <!--Tested under-->2017 128m cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Seagate Momentus Thin | <!--Model-->ST500LT012 ST320LT012. ST250LT012 500Gb 320gb 250gb 2014 5.4K rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Seagate Thin SSHD 5400RPM Sata 2.5" | <!--Model-->ST500LM000 500GB, ST500LM001, ST500LM020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 up to 64M cache and with 8GB NAND Flash |- | <!--Brand-->Seagate MomentusThin-B Video 2.5 HDD * 2014 * 2015 * 2016 * 2017 | <!--Model-->ST500VT000 500GB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->SEAGATE Baracuda 2.5 5400 | <!--Model-->ST2000LM015 (2Gb), ST1000LM049 (1Tb), ST500LM030 (500Gb) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Seagate Barracuda Pro | <!--Model-->ST1000LM048 ST1000LM035 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> up to 128MB cache |- | <!--Brand-->SEAGATE FireCuda Compute 2.5 | <!--Model-->ST500LX025 ST1000LX015 ST2000LX001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 8GB NAND Commercial Multilevel Cell (cMLC), 128MB buffer and 5400-RPM spindle speed up to 140 MB/s |- | <!--Brand-->Toshiba 2.5in | <!--Model-->MQ04ABF100 1TB 5400 RPM 2018 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TOSHIBA MQ01ACF | <!--Model-->MQ01ACF050 500GB 7200rpm 2020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->western digital wd blue 500G 8meg cache 5400rpm * 2014 Rev T0 * 2015 Rev T1 | <!--Model-->wd5000lpvx | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012-2015 sequential 2MB block transfers 110 MB/s reading and writing - |- | <!--Brand-->Western Digital 2.5" WD Blue Slim | <!--Model-->WD10SPCX 1TB Nov 2016 | <!--Work MSDos-->{{Yes|hdd under partition table msdos/pc, boots on bios machines, will not on uefi machine}} | <!--Work GPT-->{{Unk|untested hdd under gpt partition protocol scheme, not booting on uefi}} | <!--Tested under-->AROS One 1.8 USB |- | <!--Brand-->Western Digital WD | <!--Model-->WD5000LUCX 500Gb 5400rpm 16mb cache Rev Y0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 2017 Malaysia |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} ====9.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->MHW2040BH | <!--Work--> | <!--Tested under--> 40gig |- | <!--Brand-->Fujitsu | <!--Model-->MHY2080BH | <!--Work--> | <!--Tested under--> 80gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHW2120B | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS541010A9E662 type TS5SAF100 | <!--Work--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Hitachi Travelstar 5K500.B-320 | <!--Model-->HTS545025B9SA02 HTS545032B9A300 HTS545040B9A300 HTS545050B9A300 250Gb 320Gb 400Gb 500Gb 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST 1TB 7200rpm | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung bought by Seagate late 2011 | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung Spinpoint with Seagate HD REV A (Jan 2014) | <!--Model-->ST1000LM024 | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand-->Samsung Spinpoint with Seagate 9.5mm * 2013 Rev A HN-M500MBB/I * 2014 Rev B HN-M500MBB/SP4 * 2015 Rev B HN-M500MBB/P4C | <!--Model-->ST500LM012 (500M) | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Momentus 5400.3 | <!--Model-->ST9160821AS | <!--Work--> | <!--Tested under--> 160gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SSHD 1t | <!--Model-->ST1000LM014, ST1000LM028, ST1000LM015 | <!--Work--> | <!--Tested under--> 8g nand flash |- | <!--Brand-->Seagate SSHD 1T | <!--Model-->ST1000LX001 | <!--Work--> | <!--Tested under--> 32G nand flash |- | <!--Brand-->Toshiba | <!--Model-->MK2555GSX HDD2H24 | <!--Work--> | <!--Tested under--> 250g 5400rpm |- | <!--Brand-->Toshiba | <!--Model-->MK5065GSX - 500GB 5400RPM SATA 3Gb/s 8MB Cache 2.5-Inch | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MKxx59GSXP, eg Toshiba MK6459GSXP 640GB 2011 | <!--Work-->{{yes}} | <!--Tested under-->Icaros 2.2 with uses Advanced Format (AF) in 4,096 bytes per sector. Compatibility with legacy, 512 bytes through AF emulation techniques, called 512e |- | <!--Brand-->Toshiba (2013 to 2016) | <!--Model-->MQ01ABD100 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba (2015 to 2020) *2013 *2014 *2015 AA50/AX0D5A *2016 AA60/AX0E1A * *2017 AGM AA01/AX002V *2018 AGS AA70/AX0G1A *2020 AA71/AX0G1A | <!--Model-->MQ01ABD050 500meg | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MQ04ABF100 1TB 5400 RPM 2013 | <!--Work-->{{Yes}} | <!--Tested under--> |- | <!--Brand-->TOSHIBA | <!--Model-->MQ04ABD200 2TB 5400 RPM 128MB Cache SATA 6.0Gb/s | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD7500BPVX 2013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WESTERN DIGITAL 1TB 2.5" SATA DRIVE 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-80JC3T0 (OCT 2014) | <!--Work--> | <!--Tested under--> , uses Advanced Format (AF) |- | <!--Brand-->WDC Western Digital Blue 1TB SATA 2.5" Hard Drive 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-08JC3T6 (Jun 2017) | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD10JPCX 1Tb | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital * 2019 | <!--Model-->WD10JUCT 1TB (1000GB) 2019 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WD Western Digital Scorpio Black * 2010 * 2014 | <!--Model-->WD5000BEKT, WD5000BPKX-22HPJT0, WD5000BPKT, | <!--Work--> | <!--Tested under--> 16m cache, 7200rpm thailand then malaysia |- | <!--Brand-->WD Western Digital Black * 2016 | <!--Model-->WD2500LPLX, WD3200LPLX, WD5000LPLX SMR: WD5000LPSX, WD10SPSX | <!--Work--> | <!--Tested under--> 32m cache , 7200rpm SATA-III malaysia |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA 2.5in NON-Laptop Hard Disks === ====11mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu 160GB 250GB 300GB | <!--Model-->MHX2160BT, MHX2250BT, MHX2300BT | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model-->TP00640GB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====12.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====15mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 1TB IBM System X 15mm 2.5" SATA | <!--Model-->ST91000640NS 81Y9731 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT10N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 5v 12.7mm |- | <!--Brand-->HL Data Storage BD-Rom DVD Rewriter | <!--Model-->CT10N AFCK101 LGE-DMCT10A(B) | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 5v 12.7mm fails early |- | <!--Brand-->Hitachi LG | <!--Model-->GT20L | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009/2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model-->GT30N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT50N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT90N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 5v 12.7mm |- | <!--Brand-->HP | <!--Model-->TS-L633 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->HP | <!--Model-->GU70N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 5v 1.8A 9.5mm |- | <!--Brand-->HP | <!--Model-->GUD0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.8A 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->GTA0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic | <!--Model-->Uj870a Uj880 UJ890 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->UJ8A0 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic MATSHITA 12.5mm SATA DVD burner inside Asus K53S | <!--Model-->UJ8B0 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 12.7mm 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8B1 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8C0 UJ8C1 UJ8C2 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.6a |- | <!--Brand-->Panasonic Precision Devices Co Ltd | <!--Model-->UJ8D0, UJ8D1 KCC-REM-PPD-UJ8D1 HP 657534-TC2, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 ok lifeline, |- | <!--Brand-->Panasonic | <!--Model-->UJ8E2Q | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 9.5mm |- | <!--Brand-->Panasonic | <!--Model-->UJ8FB | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5a 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->DS-8A5LH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm |- | <!--Brand-->HP | <!--Model-->DU-8A6SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5A 9.5mm |- | <!--Brand-->Philips and LiteOn | <!--Model-->DS-8A8SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5a 12.7mm |- | <!--Brand-->PLSD | <!--Model-->DS-8A9SH DS8A9SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7561S, AD-7560S Thickness: 12.7 MM Interface: SATA | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 |- | <!--Brand-->Sony | <!--Model-->AD-7580s, AD-7581s, AD-7583s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7585H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm cleaning the laser lens inside the drive with a liquid lens cleaner. Also check the lens carrier slides freely from one extreme to the other inside the drive without sticking |- | <!--Brand-->Sony | <!--Model-->AD7590s, AD-7591s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7700s, AD-7710h, AD-7701H, AD-7703S | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7760H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5A 12.7mm |- | <!--Brand--> | <!--Model-->AD-7711H AD-7740H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->Toshiba Samsung | <!--Model-->SN-S208B Ver BB Rev 00 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm |- | <!--Brand-->Toshiba TSSTCorp Samsung | <!--Model-->SN-S083C Ver C Rev 03 /BEBE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.5a 12.7 mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} === [https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data SATA Desktop 3.5inch Hard Disks] === Datasheets with the SMR (overlapped packing Shingled Magnetic Recording) and CMR (faster Conventional Magnetic Recording) parts <pre> WD: https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/internal-drives/wd-blue-hdd/product-brief-western-digital-wd-blue-pc-hdd.pdf Seagate: https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/datasheets/pdfs/3-5-barracudaDS1900-14-2007US-en_US.pdf Toshiba: https://storage.toshiba.com/docs/support-docs/P300-SalesSheet_English_Web_r2.pdf </pre> {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Seagate Barracuda 7200.9 | ST3160812AS, ST3160212AS | {{yes}} | Icaros Desktop 1.5.2 - Capacity: 160 GB - Speed: 7200RPM - Cache: 8 MB - Interface: SATA2 |- | <!--Brand-->Seagate Barracuda LP Green 5400rpm | <!--Model-->ST1000DL002 1TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SkyHawk Surveillance HDD ST4000VX000 Series | <!--Model-->ST4000VX013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Baracuda Compute | <!--Model-->ST500DM009 2F110A-500 / 02PKVY / 2PKVY (500m), | <!--Work--> | <!--Tested under--> - SATA III (6Gb/s) - Format 3.5" - 32MB Cache |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate CMR | <!--Model-->ST1000DM010 ST500DM009 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 2TB SMR | <!--Model-->ST2000DM008 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SMR | <!--Model-->ST8000DM004 ST6000DM003 ST4000DM004 ST3000DM007 ST2000DM005 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 5400rpm | <!--Model-->HDWD220 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 7200rpm | <!--Model-->HDWD320 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba P300 CMR | <!--Model-->HDWD130XZSTA HDWD130UZSVA, HDWD120XZSTA HDWD120UZSVA, HDWD110XZSTA HDWD110UZSVA | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital 2010 | <!--Model-->WD20EARS Green 2TB 5400rpm 64mb cache | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD20EFRX WD40EFRX 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital | <!--Model-->WD4002FFWD | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD80EAAZ WD80EAZZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD20EARZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD40EZAZ, WD60EZAZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD20EARZ, WD20EZAZ - 2TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD40EZAX - 4TB, WD60EZAX - 6TB, WD80EZAX - 8TB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- |} ==PATA== === IDE Desktop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | M1624TAU | {{yes}} | Icaros Desktop 1.5.2 |- | IBM | DHEA-38451 | {{yes}} | Icaros Desktop 1.5.2 |- | Samsung | SP40A2H | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST3160215ACE | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST32122A | {{maybe}} | Icaros Desktop 1.5.2 |- | Western Digital | WD102AA | {{yes}} | Icaros Desktop 1.5.2 |- | Western Digital | WD200 | {{maybe}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Laptop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHV2040AH | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->HGST Hitachi Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Toshiba | MK2011GAP | {{yes}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | Compaq | CR-594-BCQ | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8322B(CP1) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8484B(AM2A) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | LTN-485 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Creative | CD220E | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Hitachi-LG | GDA-4120B | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | LG | CRD-8400B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Lite-On | LTN486S | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Mitsumi | CRMC-FX4830T | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | CDR-1700B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | DV-5800A | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | ND-2100A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | NEC | NR-7900A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | Philips | DVD8631 | {{no}} | {{no}} | Icaros Desktop 2.2 |- | Samsung | SC-148 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SCR-2030 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SM-348B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU601 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU611-25 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Toshiba | SD-M1202 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |} === IDE Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->H-L Hitachi LG | <!--Model-->GCC-4244N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2006 |- | Hitachi-LG | GCCT10N | {{yes}} | {{Maybe|FryingPan WRITE seems to have no problem with data sections (track 1) - combos with audio sections (track 2) white screens aros eventually}} | AspireOS Xenon with 25th Jan 2014 self update kernel |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Philips | SDR089 | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | TSSTcorp | TS-L462C TS-L462D | {{yes}} | {{unk}} | 2005 Icaros Desktop 2.2 |- | TSSTcorp | TS-L632H | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Sony | DW-Q58A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | Sony Optiarc | AD-7540A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | <!--Brand-->Sony | <!--Model-->Optiarc DVD RW AD-7560A IDE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7590A | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} == SCSI == {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} NVMe accepts up to 64,000 queues with up to 64,000 commands each. o5ulwkmm69csgei1m1ix8p6ue3h0tcp 4634264 4634262 2026-05-05T11:54:34Z Jeff1138 301139 4634264 wikitext text/x-wiki {{ArosNav}} ==Introduction== AROS supports hard disks and optical drives attached to several interfaces: * [[#NVMe M.2 SSD (M key)]] on the pci-e bus * [[#SATA]] aka Serial ATA or AHCI (IDE compatibility mode used in most cases) * IDE (also known as ATA, [[#PATA]] or Parallel ATA) * USB * SCSI limited ==PCI-e== ===NVMe M.2 SSD (M key)=== *Controller and firmware *DRAM better having if heavy workloads but not necessary for gaming *Cache like SLC HMB techniques *NAND (Main storage area with MLC, TLC or QLC versions of varying life expectancy) SSDs, USB flash drive, SD and Micro SD Cards have a limited amount of write cycles, therefore guaranteed to fail randomly and suddenly at any time. All SSDs are prone to corrupt firmware due to poor quality NAND where both the data and the firmware resides. The drive tends to go read only when too many errors occur before complete failure. That is up to 10 years for things like memory cards and USB sticks. In general, unless there is a firmware design issue, cheap materials used, stress like bending or overheating causing cold solder joints, an SSD can last a long time if minimal writing activity takes place but eventually if flash isn't written to, it degrades. Catch 22. Dram and cache are not the same thing. Dram stores the ssds indexes and metadata for faster data retrieval and wear leveling. The cache keeps part of the nand memory as SLC storage which can be written to faster. Basically all ssds will have a dynamic SLC cache where it will decrease as the drive fills up. Cache controller designs that are DRAM less use the internal SRAM cache in the controller to cache the NAND mapping table. It just requires a different mapping table design since SRAM caches are much smaller than DRAM. Ultimately the mapping table is still stored in NAND. General rule of thumb: the cheaper an SSD, the higher the likelihood it uses lower quality flash chips so sudden failing NAND, problematic controller chips (e.g. SandForce), outsourced firmware. Generic brand like old SP, Corsair or Crucial may be recoverable whilst major brands Samsung, Intel and Western Digital are impossible due to firmware encryption and customizations. Recommend sticking with older Silicon Motion or Phison controllers if possible. A ssd isn't good because it has dram or bad because it doesn't. Other things should be taken into account like sustained writes so check the TPU write intensive usage See [https://www.techpowerup.com/ssd-specs/ here] for more information {| class="wikitable" width="100%" ! width="15%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="30%" |Tested Distribution |- | <!--Brand-->Unnamed | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 to - SM2259XT2 SM2263XT MAS0902 MAP1202 YS9082HP RM1135 RTS5765 PS3111 |- | <!--Brand-->Unnamed OEMs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 to date - Realtek RTS5765/66 controller + Micron 96L (B27A) |- | <!--Brand-->Acer Predator GM7 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Acer drives built by Biwin, that also supplies HP, Maxio MAP1602A no DRAM so HMB, YMTC 128L TLC, |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 NVME IM2P33F8, IM2S3168 SSD | <!--Model-->IM2P33F8-512GD | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - industrial 12L 3D TLC NAND flash Supports LDPC ECC, RAID Engine, and SLC Cache End-to-End (E2E) Data Path Protection with Host Memory Buffer (HMB) i.e. DRAMless |- | <!--Brand-->ADATA XPG SX8200 Pro M.2 nvme | <!--Model-->ASX8200PNP1TTC | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 NVM Express 1.3 SN2262G later SN2262EN chipset - |- | <!--Brand-->ADATA 256GB GEN4 x4 NVMe PCIe M2 2230 SSD | <!--Model-->SM2P41C3-256GC2 DP/N 0KM1Y6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 consumer |- | <!--Brand-->ADATA XPG GAMMIX S50 Lite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Silicon Motion SM2267XT dramless |- | <!--Brand-->ADATA XPG ATOM 50 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Innogrit RainierQX IG5220 |- | <!--Brand-->Adata Legend 710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->ADATA Legend 900 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->BiWin PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Innogrit IG5216 controller, no DRAM so HMB which appears to be the standard - |- | <!--Brand-->BiWin NV7200 PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SM2263XT |- | <!--Brand-->Biwin NV7400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force LE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Corsair Force Series MP500 MP510 M.2 NVMe PCIe Gen 3 x4 SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 PS5012-E12-27 from Phison, 64-layer TLC Toshiba BiCS flash, may have dram cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 on DRAM DDR4 with Micron 96L QLC - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Corsair Force MP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Corsair MP600 Elite | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E16 and Bics DDR4 DRAM buffer and TLC-based with SLC-mode cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Corsair MP600 Pro XT, PRO LPX, PRO NH PCIe4 | <!--Model-->CSSD-F1000GBMP600ECS Elite, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 DRAMless SSD controller Phison PS5026-E26, BiCS6 162L QLC NAND |- | <!--Brand-->Corsair MP600 Core XT | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison and Bics QLC-based with SLC-mode cache - |- | <!--Brand-->Corsair MP700 Pro PCIe 5.0 | <!--Model-->CSSD-F1000GBMP700PNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial P1 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 QLC NAND but a controller with a DRAM cache - |- | <!--Brand-->Crucial P2 M.2 2280 Gen3 x4 NVM-express | <!--Model-->CT1000P2SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 dram-less Phison PS5013-E13-31 on 96-layer QLC NAND - |- | <!--Brand-->Crucial P3 Plus M.2 2280 | <!--Model-->CT1000P3PSSD8 CT2000P3PSSD801 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with Host Memory Buffer HMB tech to use a small bit of system RAM as DRAM cache and Micron 176-layer QLC NAND - |- | <!--Brand-->Crucial P3 M.2 nvme SSD | <!--Model-->CT2000P3SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron QLC (N48R) - |- | <!--Brand-->Crucial P5 m.2 nvme PCIe 4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 runs hot - Crucial NVMe with DRAM LPDDR4 and Micron 96L TLC |- | <!--Brand-->Crucial P5 Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 some have DRAM cache |- | <!--Brand-->Crucial T500 Gen4.0 nvme 2.0 | <!--Model-->CT1000T500SSD8, CT2000T500SSD8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison PS5025-E25 with micron B58R 232-layer 3D TLC NAND and Micron LPDDR4 DRAM cache - beware win update kb5063878 kb5062660 preview - |- | <!--Brand-->Crucial T700 Gen5 SSD | <!--Model-->CT1000T700SSD3, CT2000T700SSD3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 SSD controller Phison PS5026-E26, Micron 232-layer NAND with no dram as standard - |- | <!--Brand-->Crucial P310 M.2 2280 NVMe PCIe Gen4 SSD | <!--Model-->CT2000P310SSD801 (2Tb), | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 DRAM-less Phison E27T Micron 232-layer NAND - |- | <!--Brand-->Crucial T705 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 dramless Phison SSD controller |- | <!--Brand-->Crucial T710 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 SMI SM2508 SSD controller dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN605 PCIe Gen3 x4 interface, NVMe 1.3 support | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Ediloca EN660 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca EN760 PCIe Gen4 x4 M.2 NVMe 1.4 interface | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 gets hot |- | <!--Brand-->Ediloca EN870 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 no dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca EN855 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Ediloca | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S500 pro PCIe Gen3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 MaxioTech MAP1202A-F1C with YMTC 128L and pseudo-SLC cache |- | <!--Brand-->Fanxiang S660 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S880/R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Fanxiang S770 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX550 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Fikwot FN501 Pro m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->FIKWOT FN950 FN955 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 MAP1602 (at 1600 MT/s) flash YMTC TLC no dram |- | <!--Brand-->Fikwot FX991 m.2 nvme | <!--Model-->FW-FX991-2TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FN960 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand-->Fikwot FN970 m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Maxio MAP1602 + YMTC 232L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Geil ZEN ITH m.2 nvme | <!--Model-->S3-240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Gigabyte Aorus Gen4 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash - DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Gigabyte Aorus 10000 PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->HP EX950 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HP FX900 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dram less |- | <!--Brand-->HP | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Integral M2 Series NVME M.2 2280 PCIe Gen 3x4 | <!--Model-->INSSD500GM280NM2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Inland Professional TLC E12S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E18 |- | <!--Brand-->Inland Gaming performance Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash |- | <!--Brand-->Inland TD510 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM DDR4 with 232-Layer Micron TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->intel SSD Pro 7600p Series M.2 80mm 2280 PCIe 3.0 x4, 3D TLC | <!--Model-->SSDPEKKF512GB, SSDPEKKF256G8L, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel 660p m.2 nvme | <!--Model-->ssdpeknw010tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 SMI SM2263 controller with 1GB DRAM cache and 1TB of Intel QLC NAND similar to crucial P1 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] 670p | <!--Model-->SSDPEKNU010TZ | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 256 MB DDR3L cache and 12-140 GB SLC-Cache QLC NAND |- | <!--Brand-->Intel P4511 m.2 nvme PCIe3.1 x4 22110 110mm | <!--Model-->SSDPELKX020T8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 very long |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A1000 NVME PCIE M2 2280 SSD | <!--Model-->SA1000M8/480G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Kingston A2000 NVME PCIE M2 2280 SSD | <!--Model-->SA2000M8/250G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->Kingston KC3000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] PS5018-E18 PCIe 4.0 x4 NVMe controller and Micron’s 176L TLC NAND flash - |- | <!--Brand-->Kingston NV1 m.2 nvme pcie | <!--Model-->SNV1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 entry-level consumer DRAMless Phison E13T or Silicon Motion 4-channel SM2263XT - one brand TLC up to 1Tb and QLC after - |- | <!--Brand-->Kingston NV2 | <!--Model-->SNV2 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 entry-level, first SMI SM2267XT or Phison E19T and later SMI SM2269XT or Phison E21T with various flash memory |- | <!--Brand-->Kingston FURY Renegade m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 [https://www.kingston.com/en/support/technical/ksm-firmware-update Firmware Rev. EIFK31.7 (07-08-2024) update for] Phison E18 controller, Micron 176L nand and ddr4 dram - |- | <!--Brand-->Kingston NV3 | <!--Model-->SNV3S/500G, SNV3S/1000G, SNV3S/2000G, SNV3S/4000G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 entry-level, SMI SM2268XT2 or Phison E27T controller with BiCS6 TLC or QLC flash - dramless so hmb - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia (Toshiba) XG4? M2 2280 NVMe PCIe SSD | <!--Model-->THNSF5512GPUK, THNSN51T02DUK, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 Phison has done custom controller work for Kioxia, and Kioxia has also worked with SMI and InnoGrit (the latter more recently). Kioxia label their controllers as their own but these are largely rebadged. |- | <!--Brand-->Kioxia (Toshiba) XG5 for Data Centres | <!--Model-->KXG5 KXG50ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 nanya ddr3 dram? with 64-layer BiCS 3D flash memory |- | <!--Brand-->Kioxia XG6 OEM m.2 nvme | <!--Model-->KXG60ZNV512G, KXG60ZNV1T02, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 TC58NCP090GSD with DRAM NANYA LPDDR3 and Toshiba BiCS FLASH 96-layer 3D TLC - |- | <!--Brand-->Kioxia (Toshiba) BG4 m.2 nvme | <!--Model--> *KBG40ZNS128G, KBG40ZNS256G, KBG40ZNS512G, KBG40ZNS1T02 *KBG40ZNT256G, *KBG40ZNV1T02 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - no dram but NVMe's Host Memory Buffer (HMB) i.e. portion of the system's RAM for caching - Toshiba's 96-Layer BiCS FLASH - seems Windows UASP driver and the JMS583 chipset interacts badly with the Kioxia BG4 - early firmware upgrade to prevent overheating hot - |- | <!--Brand-->Kioxia XG7 | <!--Model-->KXG70ZNV1T0G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 - might need firmware update on early 2tb 4tb versions - controller with sk hynix dram and tlc nand |- | <!--Brand-->KIOXIA EXCERIA PLUS G2 SSD series PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5012-E12S-32 aka TC58NC1201GST 4-channel controller along with KIOXIA proprietary 96-layer 3D TLC and "MG2h" version has BiCS4.5 which is faster than launch BiCS4 - - |- | <!--Brand-->Kioxia XG8 OEM m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 TC58NC0L1XGSD with DRAM LPDDR4 and 112-Layer Kioxia BiCS5 TLC - |- | <!--Brand-->Kioxia (Toshiba) BG5 | <!--Model-->KGB50ZNV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 HMB buffer |- | <!--Brand-->Kioxia (Toshiba) BG6 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless |- | <!--Brand-->KIOXIA EXCERIA PLUS G3 SSD series PCIe 4.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 has hmb, like most dram-less nvmes KIOXIA |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar 1TB SSD M.2 NVME 1.4 Gen3x4 M.2 2280 | <!--Model-->NM610Pro | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Lexar NM620 *IG5216 (worse?) not great original 96L *MAP1202 YMTC up to 232L, or 176L Micron, TLC for the 1TB | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 a few versions all DRAM-less, |- | <!--Brand-->Lexar NM790 SSD M.2 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Maxio MAP1602 no DRAM so HMB with 232-Layer YMTC TLC |- | <!--Brand-->Lexar m.2 nvme | <!--Model-->EQ790 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Maxio MAP1602, no DRAM so HMB, Flash Memory 232-Layer YMTC TLC, |- | <!--Brand-->Lexar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Liteon M.2 NVME 512GB SSD 2280 | <!--Model-->CAZ-51282512-Q11 DP/N 0K64PG | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI controller |- | <!--Brand-->Micron 2200S m.2 nvme 2200 series | <!--Model-->MTFDHBA256TCK, MTFDHBA512TCK | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 for a time, Micron controller with 64L TLC 3D Nand [https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=3jg3g BSOD occurred as CRITICAL_PROCESS_DIED] before self applied firmware [https://support.lenovo.com/us/en/downloads/ds119265-nvme-solid-state-drive-firmware-update-utility-for-windows-10-64-bit-thinkpad apparently it is related to the power management that disconnects the Micron SSD] |- | <!--Brand-->Micron 2300 m.2 nvme Gen 3 x4 | <!--Model-->MTFDHBA256TDV P/N M02626-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Micron 3400 M.2 NVME SSD Gen4 | <!--Model-->MTFDKBA512TFH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no cache |- | <!--Brand-->Micron 2450 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 E19T |- | <!--Brand-->Micron 2600 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison's PS5029-E29T SSD controller with Micron 276-layer G9 QLC NAND in a DRAMless - Adaptive Write Technology (AWT) using various NAND modes (SLC, TLC, and QLC) as a dynamic cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium S270 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->MSI Spatium M450 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV2000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac NV7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico J10 J-10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Orico D10 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Orico e3500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->Orico O7000 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Patriot P300 m.2 nvme pcie 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Patriot Viper VP4300 Lite M.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS2230 Gen3 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->PNY CS2140 CS2342 Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Raydisk 1T 2280 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 no dram, Memory QLC Intel 144 layer. Chip Realtek |- | <!--Brand-->Raydisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket Nano 2242 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sabrent Rocket 4.0 m.2 nvme | <!--Model-->SB-2130-512, SB-2280-1TB, SB-Rocket-NVME4-HTSK-2TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E16 controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 4.0 PLUS m.2 nvme | <!--Model-->SB-RKT4P-1TB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E1? controller and TLC flash - |- | <!--Brand-->Sabrent Rocket 5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Phison E25 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung PM951 m.2 nvme | <!--Model-->MZVLV1T | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 950 PRO PM961 M.2 2280 NVMe 1.3 PCI-Express 3.0 x4 | <!--Model--> *MZ-VKW5120 *MZ-VLW2560 MZVLW256HEHP-000L7, MZ-VLW5120, MZ-SLW1T00 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - possibly 512M LPDDR3 Samsung K4E4E324EE-ECCF cache - Polaris (S4LP077X01-8030) unit with Samsung 48-layer TLC V-NAND V3 flash Samsung K90MGY8S7M-CCK0 - |- | <!--Brand-->Samsung 960 Pro SM961 M.2 PCi-e NVMe SSD 2280 | <!--Model-->MZ-V6P1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 Polaris (S4LP077X01-8030) controller Samsung 48-layer multi-level cell (MLC) V-NAND, pseudo-SLC cache or LPDDR3-1866 Samsung K4E8E304EE-EGCF |- | <!--Brand-->Samsung PM981 2280 PCI-Express 3.0 x4 | <!--Model--> *Rev 0 MZ-VLB256A, MZ-VLB512A, MZ-VLB1T0A, *Rev 0 MZ-VLB2560, MZ-VLB5120 P/N MZVLB512HAJQ, MZ-VLB1T00, *Rev ? MZ-VLB256B, MZ-VLB512B, MZ-VLB1T0B, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache hybrid SLC Samsung’s TurboWrite - |- | <!--Brand-->Samsung PM981a 2280 PCI-Express 3.0 x4 | <!--Model-->MZ-VLB5120 P/N MZVLB512HBJQ-000L7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 - tlc flash with SSD controller Samsung Phoenix (S4LR020) - pseudo-SLC cache |- | <!--Brand-->SAMSUNG PM991 NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ2560 MZVLQ256HBJD-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SAMSUNG PM991a NVMe M.2 SSD 2242 2280 | <!--Model-->MZ-VLQ256B MZVLQ256HBJD-00BH1, MZ-9LQ256C, MZ-VLQ512B MZVLQ512HBLU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->Samsung 970 EVO Plus m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 Samsung Phoenix on Samsung LPDDR4 dram and 2 Samsung 9x-layer V-NAND TLC |- | <!--Brand-->Samsung 980 EVO Plus | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->Samsung 980 Pro m.2 nvme | <!--Model-->MZ-V8P1T0BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 originally made in Korea ([https://semiconductor.samsung.com/consumer-storage/support/tools/ 2tb firmware issues] with versions starting with 3) and year later Vietnam - DRAM |- | <!--Brand-->Samsung 990 EVO m.2 nvme | <!--Model-->MZ-V9E2T0BW, MZ-V9E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo no DRAM so HMB Samsung 133-Layer TLC (V6P) and Samsung 133-Layer TLC (V6P) - |- | <!--Brand-->SAMSUNG PM9A1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model-->MZ-VL25120 MZVL2512HCJQ, MZVL21T00 MZVL21T0HCLR-00BL2, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 might be OEM variant of the 980 Pro |- | <!--Brand-->Samsung PM9B1 SSD M.2 2280 PCIe NVME Gen4x4 | <!--Model--> *2023 MZ9L4256HCJQ-00BD1 MZ-9L4256A, , *2025 MZ-VL42560, MZ-VL45120, MZ-VL421T, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 SSD controller is Marvell 88SS1322 Whistler Plus, no DRAM cache and Samsung 128-layer TLC NAND flash |- | <!--Brand-->Samsung 990 EVO Plus m.2 nvme2.0 | <!--Model-->MZ-V9S2T0BW, MZ-V9S1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Samsung Piccolo with no DRAM so HMB and Samsung 236-Layer (V8) TLC - |- | <!--Brand-->Samsung 990 Pro m.2 nvme | <!--Model-->MZ-V9P2T0BW, MZ-V9P1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 2tb early firmware issue - Samsung Pascal with DRAM LPDDR4 and 176-Layer V-NAND TLC - has had firmware design issues, causing premature failure - |- | <!--Brand-->Samsung 9100 PRO PCIe Gen5 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Samsung | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Seagate Firecuda 510 G3 x4 nvme | <!--Model--> *ZP1000GM30001, *ZP500GM30021 P/N 2NT308-300, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad early batch - Phison E12 STXYP0160031 on SK Hynix DRAM DDR4 with Kioxia BiCS3 64L TLC |- | <!--Brand-->Seagate Firecuda Q5 | <!--Model-->ZP500CV30001,ZP250CV30001,ZP1000CV30001 P/N 2ZK307-881,ZP2000CV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 PS5013-E13-31 from Phison, no DRAM cache and QLC nand |- | <!--Brand-->Seagate Firecuda 515 | <!--Model-->ZP500GV30001,ZP250GV30001,ZP1000GV30001,ZP2000GV30001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 no dram and qlc nand |- | <!--Brand-->Seagate FireCuda 520 SSD M.2 PCIe Gen4 ×4 NVMe 1.4 | <!--Model-->ZP2000GM30002, ZP1000GM30002, ZP500GM30002 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E16 and Toshiba 96-layer TLC (triple-level cell) BiCS4 NAND flash DDR4 DRAM buffer and TLC-based with SLC-mode cache - |- | <!--Brand-->Seagate Firecuda 520N m.2 nvme | <!--Model-->ZP2000GV3A012, ZP1000GV3A012 and ZP500GV3A012 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 530 m.2 nvme | <!--Model-->ZP500GM3A013, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison PS5018-E18 on DRAM DDR4 with Micron 176L TLC |- | <!--Brand-->Seagate | <!--Model-->ZP1000CV3A002, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless |- | <!--Brand-->Seagate Firecuda 540 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 Phison E26 on DRAM LPDDR4 with 232-Layer Micron TLC |- | <!--Brand-->Seagate Firecuda 530R | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power UD85 m.2 nvme PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 [http://vlo.name:3000/ssdtool/ firmware tools] |- | <!--Brand-->Silicon Power UD90 PCIe 4.0 nvme | <!--Model-->SP250GBP44UD9005, SP500GBP44UD9005, SP01KGBP44UD9005, SP02KGBP44UD9005, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Phison E21T with no DRAM so HMB and 176-Layer Micron TLC (B47R) but later no name QLC nand instead - |- | <!--Brand-->Silicon Power A60 A80 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 various originally an E12 drive with 64L Toshiba NAND, then had variations with E12S and SM2262EN as well as random 64L/96L, now it comes with a MAP1001A controller by Maxio and some YMTC NAND - |- | <!--Brand-->Silicon Power US75 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 multiple variants with different NAND flash and/or controller like MAP1602A (F1C F2C uses NVMe 1.4, F3C U uses NVMe 2.0) and 232-layer TLC NAND flash, no dram |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix BC501 M.2 m.2 NVMe PCIe Gen3 SSD | <!--Model--> *Rev0 HFM256GDHTNG-8510B SSS0L24764, HFM256GDJTNG-8310A, *Rev1 HFM256GDHTNG-8310A SSS0Q68673, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 bad batch early - |- | <!--Brand-->SK Hynix BC511 512GB NVMe PCIe M2 2230 SSD | <!--Model-->HFM256GDJTNI-82A0A HFM512GDGTNI-82A0A D P/N 0TG8T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 no dram cache |- | <!--Brand-->SK hynix BC711 PCIe Gen3 x4 | <!--Model-->HFM001TD3JX013N, HFM512GD3JX013N, HFM256GD3JX013N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 okay but no dram cache |- | <!--Brand-->SK hynix PC711 m.2 2280 PCIe Gen3 x4 | <!--Model--> *HFS001TDE9X073N, HFS512GDE9X073N, HFS256GDE9X073N *HFS001TDE9X080N, HFS512GDE9X080N, HFS256GDE9X081N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->SK Hynix SC210 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SK Hynix PC601 PCIe 3.0 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 - Cepheus Plus YCN34PTA0FR Controller and 48L TLC Flash, pseudo-SLC cache and LPDDR4-3733 SK Hynix H9HCNNN8KUMLHR-NME dram - |- | <!--Brand-->SK Hynix PC401 3rd gen PCIe | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 bad batch early - |- | <!--Brand-->SK hynix Gold P31 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 SK hynix’s proprietary Cepheus controller |- | <!--Brand-->Sk Hynix SK500 Gen 4 (x4) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 |- | <!--Brand-->SK hynix Platinum P41 m.2 nvme | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 Aries SSD controller with 176-Layer TLC flash - SK hynix LPDDR4 dram - |- | <!--Brand-->Sk Hynix PC801 PCIe Gen4 x4 m.2 nvme | <!--Model-->HFS001TEJ9X101N, HFS512GEJ9X101N, HFS256GEJ9X101N, HFS002TEJ9X101N | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->SK Hynix BC901 m.2 nvme PCIe Gen4 2230 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 Silicon Motion SM2269XT with no DRAM so HMB buffer cache - SK Hynix 176-layer TLC NAND flash 1TB only - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team | <!--Model-->TM8PS7512G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TeamGroup MP34 | <!--Model-->MP34 256GB, MP34 512GB, MP34 1TB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 good Phison E12 with DRAM NANYA DDR3L and Toshiba BiCS 3 64L TLC - |- | <!--Brand-->Team Group T-Force Cardea A440 PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison PS5018-E18 NVMe 1.4 controller and Micron’s 96L TLC with SK hynix 8Gb DDR4 chips but not OPAL-compliant AES 256-bit |- | <!--Brand-->Team Group TForce Cardea A440 Lite PCIe Gen4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 dram-less E27T controller and 162L TLC but not OPAL-compliant AES 256-bit |- | <!--Brand-->teamgroup Team Z44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison’s E19T controller |- | <!--Brand-->teamgroup Team MP44L m.2 nvme pcie | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Phison E21T no DRAM so HMB with 176-Layer Micron TLC |- | <!--Brand-->Team MP33Q | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - dramless maxio MAP1202 with TLC (MP33) or QLC (MP33Q) - |- | <!--Brand-->Team Group QX GE Pro m.2 nvme PCIe5 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 innogit IG5666 with QLC 3D 232L nand with DRAM - |- | <!--Brand-->Team Group T-Force G70 Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 InnoGrit IG5236 (Rainier) with DRAM and NAND YMTC TLC - |- | <!--Brand-->Team Group T-Force Cardea Z540 m.2 nvme PCIe 5.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 Phison E26 controller and 232L TLC and DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE110S PCIe Gen3 x4 M.2 2280 TS128GMTE110S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND |- | <!--Brand-->Transcend MTE220S PCIe Gen3 x4 M.2 2280 TS2TMTE220S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND with DRAM Cache |- | <!--Brand-->Transcend MTE300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand-->Transcend MTE300S PCIe Gen3 x4 M.2 2230 TS256GMTE300S TS512GMTE300S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 3D TLC NAND, 1G and 2G get hot |- | <!--Brand-->Transcend | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend MTE400S | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 mlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TWSC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Union Memory (Shenzhen) AM6672 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM6A0 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Verbatim V15000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->WD Blue SN500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western digital SN720 M.2 2280 NVME PCIE for Data Centers | <!--Model-->SDAQNTW-512G-1001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2021 |- | <!--Brand-->WDC SN520 2230 Gen3 x2 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 to 2020 |- | <!--Brand-->Western digital ix sn530 M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 industrial sandisk controller and firmware, as well as 96-layer 3D TLC NAND memory that can work in TLC or SLC mode - |- | <!--Brand-->Western digital SN730 Gen3 x4 M.2 2280 M.2 NVME | <!--Model-->SDBPNTY-1T00, SDBPNTY-512G-1012, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 to 2021 DRAM Cache DDR4-2666 CL18 Micron MT40A512M16LY-075:E (D9WFH) with Controller WD 20-82-00705-A2 Triton MP28 and NAND Flash Toshiba BiCS4 60082 512G (Rebranded by SanDisk) TLC 96-layer |- | <!--Brand-->WD Black SN750 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 64-layer 3D stacked NAND with 3 bits per cell TLC (Triple Level Cell) with 256MB of skhynix DRAM cache for every 250GB |- | <!--Brand-->WD Black SN850 m.2 nvme Gen4 PHY | <!--Model-->WDS100T1X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 Sandisk G2 controller with Micron DDR4 cache - new nCache 4.0 slc cache total dynamic capacity spans one-third (300GB on 1TB) with a small static SLC cache (12GB on 1TB) from the Kioxia BiCS4 96L TLC 96-layer NAND flash - |- | <!--Brand-->Western digital SN550 Blue M.2 NVME PCIE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - various controllers and NANDs |- | <!--Brand-->Western Digital SN810 NVMe SSD 2280 Gen4 x4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 slc cache - laptop oem only no retail version - |- | <!--Brand-->WD SN850X | <!--Model-->WDS100T2X0E, WDS200T2X0E, WDS400T2X0E, WDS800T2X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 issues with early ssd firmware and AMD Zen 3 X570 and X670E chipsets - Sandisk A101000291-82 controller with 112-layer TLC and DDR4 DRAM cache |- | <!--Brand-->WD_Blue SN570 single-sided M.2 2280 (80mm) PCIe 3.0 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless - WD/SanDisk SSD controller with BiCS 5 3D NAND TLC 112-layer NAND flash memory - |- | <!--Brand-->WD_Black SN770 m.2 nvme | <!--Model-->WDS100T3X0E, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless cache with TLC |- | <!--Brand-->WD Green SN350 m.2 NVMe SSD | <!--Model-->WDS100T3G0C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 DRAM-less cache with SanDisk controller and QLC (quad-level cell) NAND |- | <!--Brand-->WD_BLACK SN750 SE | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 controller Phison E19T, dramless |- | <!--Brand-->WD SN740 M.2 (2230) PCIe 4.0 x4 2280 | <!--Model-->SDDQTQD-1T00, SDDPNQD-, SDDPNQD-256G-2006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 dramless with SSD controller WD Sandisk 20-82-10081-A1 Polaris MP16+ with Toshiba BiCS5 112-layer TLC NAND flash |- | <!--Brand-->WD_Blue SN580 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 dramless SanDisk controller with (HMB) and 112-Layer Kioxia TLC (BiCS5) |- | <!--Brand-->WD Blue SN5000 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Black SN8100 / Sandisk Optimus GX Pro 8100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk Optimus GX 5100 7100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk Optimus GX Pro 850X | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2026 |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Sandisk | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Zhitai (Yangtze Memory) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === Mini SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand-->Biwin PCIe 4×2 NVMe 1.3 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 GPDwin5 and Oneplayer Superx hybrid - 3D TLC - LGA packaging - V1 slide tray mechanism - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2025 |- |} ==SATA== Advanced Host Controller Interface (AHCI), a programming interface for SATA host controllers. Platforms supporting AHCI may take advantage of performance features such as no master/slave designation for SATA devices — each device is treated as a master — and hardware-assisted native command queuing. AHCI may but not often also provides usability enhancements such as Hot-Plug (Desktop and Mobile Only). AHCI requires appropriate software support (e.g., an AHCI driver) AHCI, the underlying protocol for SATA, only supports one queue with 32 commands. The issue with AHCI is that it's going to take a pile of test hardware just to figure out all the different bugs in all the motherboard chipsets and add-on PCI cards that 'kinda' implement AHCI. Not to mention Silicon Image, which took a very different approach from Intel's AHCI in their SATA controllers. === SATA 7mm 2.5inch SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand-->ADATA 240GB Ultimate SU630 2.5" | <!--Model-->ASU630SS-240GQ-R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->ADATA Ultimate Su650 2.5in | <!--Model-->ASU650SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->ADATA Ultimate Su800 2.5in | <!--Model-->ASU800 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SMI SM2258 controller with Micron 3D TLC NAND but low performance when data fills the SLC cache - slow write speed - |- | <!--Brand-->ADATA Ultimate Su680 2.5in | <!--Model-->ASU680SS240GTR | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS340 Panther | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Apacer AS350 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Crucial M225 SSD 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2009 sata2 3gbp/s |- | <!--Brand-->Crucial C300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 sata3 6gbps - |- | <!--Brand-->Crucial M4 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2011 Marvell 88SS9174-BKK2 processor, 25nm MLC NAND flash and 128MB dram cache |- | <!--Brand-->Crucial M500 120Gb to 960Gb | <!--Model-->CT250M500SSD1, CT500M500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 dram cache |- | <!--Brand-->Crucial M550 120G to 1T | <!--Model-->CT250M550SSD1, CT500M550SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dram cache |- | <!--Brand-->Crucial (Micron) BX100 | <!--Model-->CT500BX100SSD1, CT1000BX100SSD1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - no dram - Silicon Motion SM2246EN and ATA version ACS-2 - |- | <!--Brand-->Crucial (Micron) MX100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache Micron controller and nand - |- | <!--Brand-->Crucial MX200 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC NAND |- | <!--Brand-->Crucial (Micron) BX300 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dramless cache - Micron ex Tidal controller and TLC nand - |- | <!--Brand-->Crucial (Micron) MX300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand-->Crucial (Micron) bx500 2.5inch | <!--Model-->CT240BX500SSD1, CT480BX500SSD1, CT960BX500SSD1, CT1000BX500SSD1, CT2000BX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 SM2258XT 4channel later SM2259XT paired with Micron’s latest 64-Layer 3D TLC flash but dramless SLC cache (part of the tlc flash) - |- | <!--Brand-->Crucial (Micron) MX500 | <!--Model-->CT250MX500SSD1, CT500MX500SSD1, CT1000MX500SSD1, CT2000MX500SSD1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - dram cache from 256M to 2G - discontinued end of 2024 |- | <!--Brand-->Fanxiang S101 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 - no dram cache, Hynix memory 3dv7-176l 176 layer QLC (one chip), either raymx rm1135, SM2259XT controller or Realtek rts5735dlq |- | <!--Brand-->Fanxiang ranxiana S102 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 - no dram - |- | <!--Brand-->Fanxiang S101Q 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fanxiang | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->Fikwot founded in 2018 |- | <!--Brand-->Fikwot FX815 Standard 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Fikwot FS810 Ultra 2.5inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertec FirestormLite 2.5inch | <!--Model-->S240GHS3-M or SDSSD240GB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Hypertech | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral V2 Plus 2.5inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel SSD 520 Series 2.5 inch SATA 6Gb/s 2.5" SSD Solid State Drive | <!--Model-->SSDSC2CW240A3, SSDSC2CW480A3, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 LSI SandForce SF2281, Flash Memory Intel Synchronous 25nm MLC - |- | <!--Brand-->Intel Pro Series 1500 | <!--Model-->SSDSC2BF180A4L SSD0E38417, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Intel S3610 Series 2.5" 400GB 6GBPS SATA SSD | <!--Model-->SSDSC2BX400G4R | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 data center |- | <!--Brand-->Intel SSD Pro 5400s 512 GB | <!--Model-->SSDSC2KF512H6 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3510 Series MLC 2.5" | <!--Model-->SSDS2BB400G6, SSDSC2BB480G6R, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Intel SSD DC S3520 Series MLC 2.5" | <!--Model-->SSDSC2BB800G7, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Intel SSD DC S3710 Series 800GB 2.5" | <!--Model-->SSDSC2BA800G4P, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 server |- | <!--Brand-->Intel SSD 545S Series 256GB 512GB | <!--Model-->SSDSC2KW256G8X1, SSDSC2KW512G8 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->[https://www.solidigm.com/support-page/warranty-rma/ka-00032.html Solidigm formerly Intel] SSD DC S4500 240GB 2.5inch - HP Enterprise | <!--Model-->SSDSC2KB240G7P | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingspec P3-512 P3-1T0 P3-2TO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston SSDNow 300 | <!--Model-->SV300S37A/240G, SV300S37A/120G, SV300S37A/60G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 dramless - lsi sandforce SF2281 or JMicron JMF662 controller with Toshiba MLC or Intel MLC |- | <!--Brand-->Kingston A400 120G to 960Gb 2.5inch | <!--Model-->SA400S37/240G SBFK61K1, SA400S37/480G, SA400S37/960G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 half case sized ssd 4 x FH64B08UCT1-60 64G - t6 security torx into metal case - dram less - poor write speeds - |- | <!--Brand-->Kingston | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kioxia formerly Toshiba HG6 2.5in | <!--Model--> *9.5mm THNSNJ512GBSU, THNSNJ256GBSU, THNSNJ128GBSU *7mm THNSNJ512GCSU THNSNJ512GCSY, THNSNJ256GCSU THNSNJ256GCSY, THNSNJ128GCSU THNSNJ128GCSY | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - no dram |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lexar NS100 2.5 inch sata | <!--Model-->LNS100-1TRB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - Marvell 88NV1120 Artemis, a DRAM cache is not available and pseudo-SLC. Micron 64-layer TLC NAND flash 4 chips @ 512 Gbit TS7512G181 (Rebranded by Lexar) (256G) - 4 nand flash chips Lexar/TST22T181/ B1924 and one controller: Lexar DM918/NOD43 1907 (512G) - |- | <!--Brand-->Lexar NQ100 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - DM928 controller which operates without a DRAM buffer. Two 128GB Micron NAND flash chips |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LiteOn | <!--Model-->LCS-128L9S-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 no dram - sata2 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Matrix 256Gb 512GB SATA 2.5in SSD | <!--Model-->MIS512GSDS, MIS256GSDS | <!--Work MSDos-->UP TO 550MB/S | <!--Work GPT-->UP TO 500MB/S | <!--Tested Distribution--> |- | <!--Brand-->Micron 1100 | <!--Model-->MTFDDAK2T0TBN-1AR1ZA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron 1300 2TB 1300 2.5" | <!--Model-->MTFDDAK2T0TDL-1AW1ZABHA | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2010 - old sdd - TLC nand - |- | <!--Brand-->Micron RealSSD C400 2.5inch | <!--Model-->MTFDDAK256MAM-1K12 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Mushkin Reactor | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC flash |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Netac SA500 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico Y-20 Y20 2.5 inch sata SHENZHEN ORICO TECHNOLOGIES CO.,LTD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 flash nand - |- | <!--Brand-->Orico S500-Pro s500pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Origin Storage Inception TLC830 Pro Series 2.5in SATA III SSD | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D tlc flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand-->Patriot P210 2.5 inch sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> qlc flash nand - |- | <!--Brand-->Patriot P220 | <!--Model-->P220S2TB25 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> flash nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Plextor M6V | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->PNY CS900 2.5 in sata SSD | <!--Model-->SSD7CS900-480-PB | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->PNY CS2311, CS3030 and Pro Elite SSDs | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Samsung SM PM | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->PM871a or PM871b? SM/PM = 2-bit or 3-bit MLC. PM = 3-bit MLC = TLC. 8 = generation = 8xx, 7 = model = 850 EVO (in this case), 1 = usage (e.g. 3 = datacenter). a/b = revision or type of flash, the 850 EVO had multiple revisions including at least three types of flash (32L, 48L, 64L) so a = 32/48L, b = 64L. At lower capacities it might use different flash, for example the 256GB SM951 utilizies 2D/planar while the higher capacities use 3D. OEM drives tend to have different, optimized firmware, so performance will not be the same |- | <!--Brand-->Samsung 840 PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Samsung 840 EVO | <!--Model-->MZ-7TE120 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 |- | <!--Brand-->Samsung PM851 2.5in sata | <!--Model-->MZ-7TE5120 P/N MZ7TE512HMHP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Samsung 850 EVO | <!--Model-->MZ-75E120, MZ-75E500 (P/N MZ7LN500) to MZ-75E4T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 Samsung MGX controller (S4LN062X01) up to 500GB capacities whilst Samsung MEX controller (3-core) beyond - Samsung TLC 3D V‐NAND 48 and later 64 layers and possibility of 256MB, 512MB or 1GB LPDDR2-1066 DRAM chip - |- | <!--Brand-->Samsung 850 PRO | <!--Model-->MZ-7KE1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung PM871a 2.5 inch sata | <!--Model-->MZ-7LN512A P/N MZ7LN512HMJP, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung PM883 1.92TB | <!--Model-->MZ-7LH1T90 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - - Samsung MJX Maru (S4LR030) - 1gb LPDDR4-1866 dram - |- | <!--Brand-->Samsung 860 EVO | <!--Model-->MZ-76E1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND - Samsung MJX Maru (S4LR030) contoller with no dram as standard - |- | <!--Brand-->Samsung 860 EVO PRO | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 860 QVO | <!--Model-->MZ-76Q1T0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 used 64-layer QLC V-NAND |- | <!--Brand-->Samsung 870 QVO 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - MKX 8-channel controller |- | <!--Brand-->Samsung 870 EVO | <!--Model-->MZ-7LN56F, MZ-77E1T0 P/N MZ7L31TOHBLB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 beware of bad batch early death - uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand-->Samsung PM871b | <!--Model-->MZ7LN256HCHP-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2021 uses 9x layer 3D QLC V-NAND (or V-NAND 4-bit MLC Samsung), may have no DRAM cache - Samsung MKX 8-channel controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Sandisk Ultra 3D/Extreme Pro | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 SandForce SF-2281 dram |- | <!--Brand-->Sandisk Ultra Plus | <!--Model-->SDSSDHP-256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell SS889175 processor with SanDisk's 19nm NAND and 128MB Samsung DDR2 DRAM chip |- | <!--Brand-->Sandisk Z300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Marvell 88SS9188 Marvell 88SS9187 with SanDisk 64Gbit 19nm MLC - |- | <!--Brand-->Sandisk x300 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->Sandisk x300s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk Plus | <!--Model-->SDSSDA-240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 pseudo SLC cache dramless |- | <!--Brand-->Sandisk Z400s | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - Silicon Motion SM2246XT DRAM-less - budget end of market - |- | <!--Brand-->Sandisk x400 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 4 NAND packages and marvell controller 88ss1074 on blue pcb - 512MB DDR3L-1600 Micron DRAM - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Seagate BarraCuda Q1 SSD | <!--Model-->ZA240CV10001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 dramless A55 started with the Phison S10 but later the S11 i.e. Phison PS3111-S11-13 controller and 96-layer TLC NAND flash memory with a pseudo-SLC cache - |- | <!--Brand-->Silicon Power Ace A55 2.5in | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand-->sk hynix | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 sandforce controller - |- | <!--Brand-->sk Hynix SH910A | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 - Link_A_Media (LAMD) controller with eight 256Gbit H27QEGDVEBLR NAND 20nm hynix MLC - SK hynix H5PS1G83JFA DRAM - |- | <!--Brand-->sk Hynix SC300 | <!--Model-->HFS256G32MND-3210A, HFS256G32MND-3312A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 - red strip around edges - 8-channel controller SK hynix LM87810AA-A0 with DDR2 buffer chip and four pieces of 16nm hynix MLC NAND - |- | <!--Brand-->Sk Hynix Canvas SL300 series 2.5in SSD *3110A SL301STD *3210A *3300A *3310A | <!--Model-->HFS500G32TND, HFS256G32TNE, HFS128G32TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC - consumer line red in corners - SK hynix LM878100AA (HFS256G32MND-3312A) later SH87820BB and NAND 16nm hynix TLC - 256mb dram |- | <!--Brand-->Sk Hynix Canvas SC3 series 2.5in SSD *N1A0A , , *N1A1A *N1A2A SC308STD, *N2A0A , , SC311STD | <!--Model-->HFS512G32TNF-N2A0A, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - red in corners - no dram and no SLC cache - Hynix ex Link_A_Media Devices (LAMD) SH87820BB 2c but poor mixed workload ability MLC - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Team EX2 GX2 Elite QX | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2023 |- | <!--Brand-->TEAMGROUP AX2 2.5 Inch SATA III Solid State Drive SSD | <!--Model-->T253A3512G0C101, T253A3001T0C101, T253A3002T0C101, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 3D NAND TLC |- | <!--Brand-->TeamGroup TF Vulcan Z 2.5in sata | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dramless smi2259xt 128L tlc nand - |- | <!--Brand-->TeamGroup T-Force Vulcan ZQLC | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 dram-less smi2259xt qlc 144L nand - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Topesel | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend 220S 2.5in | <!--Model-->TS120GSSD220S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 3D TLC without dram |- | <!--Brand-->Transcend SSD230S 2.5in | <!--Model-->TS256GSSD230S TS512GSSD230S TS1TSSD230S TS2TSSD230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 3D TLC NAND with DRAM Cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Viathan | <!--Model-->S001T3V | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red SA500 NAS | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->WD Blue SA510 250Gb to 4Tb | <!--Model-->WDS400T3B0A WDS200T3B0A WDS100T3B0A WDS500G3B0A WDS250G3B0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - |- | <!--Brand-->Western Digital WD Green SSD 2.5" | <!--Model-->WDS240G1G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Green 200Gb to 2Tb | <!--Model-->WDS200T2G0A WDS100T3G0A WDS480G2G0A WDS240G2G0A WDS120G2G0A | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 - cheap and slow ssd - |- | <!--Brand-->WD SA530 | <!--Model-->SDASB8Y-256G SD9SB8W, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand-->[https://www.xray-disk.com xraydisk] 2.5 inch | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> from the manufacturer only - Phsion/SMI(2258XT)/Realtek/Yeestor |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Xum | <!--Model-->hx256gssdsata3 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Yottamaster | <!--Model-->Y3000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCie 3.0 |- | <!--Brand-->Yottamaster | <!--Model-->Y7000 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> PCIe 4.0 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |} === SATA M.2 (M and B key) === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->ADATA M.2 2280 Sata | <!--Model-->AXNS381E-128GM-B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fanxiang S201 m.2 sata 2280 | <!--Model-->S201 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fikwot FN203 m.2 sata (oldtan, twipps, teexin aka Shenzhen Pingfan "Ordinary" Road Technology Co., Ltd) | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 lifespan not long Maxio MAP + YMTC 128L |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Foresee (Shenzhen Longsys) | <!--Model-->YSM80CD-128G YSDE128G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 - 88nv1120-bt22 T3WU030 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral 2242 120G | <!--Model-->INSSD120GM242 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral M.2 2280 | <!--Model-->INSSD256GM.26M2280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc nand |- | <!--Brand-->Integral 256GB/512GB/1TB/2TB | <!--Model-->INSSD1TM280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 netac rebrand - no dram cache - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intel Pro ‎545S 2280 | <!--Model-->SSDSCKKF256G8H | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> no dram, TLC nand |- | <!--Brand-->Intel | <!--Model-->SSDSC2KF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Intenso M.2 internalSSD SATA III 1 TB | <!--Model-->Top | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston A400 m.2 | <!--Model-->SA400M8/240G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 entry level ssd 4 x FH64B08UCT1-60 64G - |- | <!--Brand-->Kingston | <!--Model-->RBU-SNS8350DES3128GP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingston V300 | <!--Model-->SV300S3505AG | <!--Work MSDos-->{{yes}} | <!--Work GPT--> | <!--Tested under-->Nightly Build 2014-09-18 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON SATA 128GB | <!--Model-->CV3-8D128-11 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LITEON | <!--Model-->CV1-8B256-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Lite-On | <!--Model-->L8H-256V2G-HP L8H-128V2G-HP | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 2016 nanya nt5c864m16fp-dh |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->LSI | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 SF37000 controller |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron | <!--Model-->M550 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 Marvell 88SS9189 SATA controller |- | <!--Brand-->Micron M600 enterprise m.2 sata up to 512GB | <!--Model-->MTFDDAV256MBF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 Marvell 88SS9189 SATA controller, DRAM chip 256MB 533MHz LPDDR2, NAND for the 256GB drive MT29F1T08CQCCBG2-10:C 16nm MLC NAND each 128GB package |- | <!--Brand-->MICRON 1100 M.2 SATA 6Gb/s 2280 | <!--Model-->MTFDDAV256TBN HP P/N 903109-001, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Orico Y20M-2242 | <!--Model-->Y20M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->Orico | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->202 |- | <!--Brand-->PNY | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung PM841 M.2 sata3 2280 | <!--Model-->MZ-NTD2560/0L9 MZNTD256HAGL-000L9 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 TLC |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Samsung CM871 Rev 0 | <!--Model-->MZNLF128HCHP-000H1 MZ-NLF1280 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM871a m.2 Sata | <!--Model-->MZNLN256HMHQ, NLN512A P/N MZNLN512HMJP-000H1, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 TLC |- | <!--Brand-->SAMSUNG PM871b | <!--Model-->MZNLN128HAHQ-000H1, MZNLN256HAJQ MZ-NLN256F MZ-NLN256C, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM881 | <!--Model-->MZ-NLH1280 MZNLH128HBHQ-000H1 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SanDisk X300 M.2 sata 2280 80mm SSD Solid State Drive | <!--Model-->SD7SN6S-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Sandisk X400 SSD M.2 sata 2280 | <!--Model-->SD8SN8U-128G-1006, SD8SN8U-256G-1006, SD8SN8U-512-1006, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 SSD controller Marvell 88SS1074 four channel supports variety of NAND and up to 512MB DDR3L-1600 Micron DRAM cache - |- | <!--Brand-->SanDisk X600 M.2 SSD Solid State Drive | <!--Model-->SD9SN8W-128G-1006 SD9TN8W-256G-1006 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->SANDISK X110 DELL 6T4HK M.2 2260 | <!--Model-->SD6SP1M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK Hynix SC300 | <!--Model-->SC308M280S HFS128G39TND | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 SH87820BB controller - No dram buffer - multi-level cell (MLC) NAND |- | <!--Brand-->SK HYNIX | <!--Model-->SC311 HFS256G39TNF | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->SK HYNIX | <!--Model-->SC401 HFS256G39TNH | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Silicon Power A55 M.2 sata 2280 | <!--Model-->A55 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 - no dram - |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TEAMGROUP Team MS30 SSD M.2 Sata 2280 | <!--Model-->TM8PS7001T0C101 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Toshiba RC100 (retail version of BG3) | <!--Model-->KBG30ZMV256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Toshiba HG6 m.2 | <!--Model-->THNSNJ512GDNU THNSNJ512G8NY, THNSNJ256GDNU THNSNJ256G8NY, THNSNJ128GDNU THNSNJ128G8NY, THNSNJ256GVNU THNSNJ128GVNU, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2018 |- | <!--Brand-->TOSHIBA SSD M.2 2280 256GB | <!--Model-->KSG50ZMV256G | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2019 |- | <!--Brand-->Kioxia (Toshiba) BG6 | <!--Model-->KSG60ZMG256G, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend | <!--Model-->400 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Transcend M.2 SSD 2242 TS32GMTS400S TS64GMTS400S TS128GMTS400S | <!--Model-->400S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> DDR3 dram cache and mlc nand |- | <!--Brand-->Transcend | <!--Model-->M.2 SSD 600 (2260), M.2 SSD 800S (2280) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> mlc nand |- | <!--Brand-->Transcend M.2 SSD 2242 TS120GMTS420S TS240GMTS420S TS480GMTS420S | <!--Model-->420S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> can run hot slc cache |- | <!--Brand-->Transcend M.2 SSD 2242 TS256GMTS430S TS512GMTS430S | <!--Model-->430S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache - 3d tlc nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS120GMTS820S TS240GMTS820S TS960GMTS820S | <!--Model-->820S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3D nand |- | <!--Brand-->Transcend M.2 SSD 2280 TS256GMTS830S TS512GMTS830S TS1TMTS830S TS4TMTS830S | <!--Model-->830S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> dram cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 120GB to 480Gb | <!--Model-->WDS480G2G0B WDS240G2G0B WDS120G2G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2020 made in malaysia |- | <!--Brand-->Western Digital WD Green SATA SSD m.2 2280 240Gb to | <!--Model-->WDS240G3G0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2022 made in |- | <!--Brand-->WD Blue SA510 M.2 SATA 250Gb to 2Tb | <!--Model-->WDS200T3B0B WDS100T3B0B WDS500G3B0B WDS250G3B0B | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->WD Red 500GB 1TB 2TB | <!--Model-->SA500 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->union memory AM610 m.2 sata | <!--Model-->SSS0R27339, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === mSATA SSD === {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fangxiang S301 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Kingchuxing | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Integral | <!--Model-->INSSD256GMSA MO-300 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> tlc 3d nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Micron enterprise | <!--Model-->M600 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Orico ZH-10 ZH10 | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2024 |- | <!--Brand-->Samsung 840 EVO 1.8inch msata | <!--Model-->MZ-M | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2015 |- | <!--Brand-->Samsung 850 EVO 1.8in | <!--Model-->MZ-M5E120BW, MZ-M5E250BW, MZ-M5E500BW, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung PM851 1.8" msata | <!--Model-->MZ-MTE256D P/N MZ-MTMTE256HMHP, MZ-MTE1T00, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2016 |- | <!--Brand-->Samsung 860 EVO 1.8inch msata | <!--Model-->MZ-MM6E250BW, MZ-M6E500BW, MZ-M6E1T0BW | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2017 |- | <!--Brand-->Transcend TS64GMSA370S | <!--Model-->MSA370S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> MLC nand |- | <!--Brand-->Transcend TS64GMSA230S | <!--Model-->230S | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 3d tlc nand |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} === SATA 2.5inch Laptop Hard Disks === ====7mm==== {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP628230-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP552605-01 250Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->CP693440-01 500Gb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->HGST Hitachi Z5K320 Z5K500-500 Z5K100 series * 2013 HTS545050A7E380 HTS * 2015 HTS545050A7E680 HTS | <!--Model-->HTS 320GB 500Gb 1Tb | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->HGST Hitachi Z7K320 Z7K500 series | <!--Model-->HTS725050A7E630 320Gb HTS725050A7E635 500Gb 7200rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> avoid if it does not have the DCM code |- | <!--Brand-->HGST 1T 5400rpm | <!--Model-->HTS541010B7E610 | <!--Work--> | <!--Tested under-->2017 128m cache |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->Seagate Momentus Thin | <!--Model-->ST500LT012 ST320LT012. ST250LT012 500Gb 320gb 250gb 2014 5.4K rpm | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012 |- | <!--Brand-->Seagate Thin SSHD 5400RPM Sata 2.5" | <!--Model-->ST500LM000 500GB, ST500LM001, ST500LM020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2013 up to 64M cache and with 8GB NAND Flash |- | <!--Brand-->Seagate MomentusThin-B Video 2.5 HDD * 2014 * 2015 * 2016 * 2017 | <!--Model-->ST500VT000 500GB, | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2014 |- | <!--Brand-->SEAGATE Baracuda 2.5 5400 | <!--Model-->ST2000LM015 (2Gb), ST1000LM049 (1Tb), ST500LM030 (500Gb) | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Seagate Barracuda Pro | <!--Model-->ST1000LM048 ST1000LM035 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> up to 128MB cache |- | <!--Brand-->SEAGATE FireCuda Compute 2.5 | <!--Model-->ST500LX025 ST1000LX015 ST2000LX001 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 8GB NAND Commercial Multilevel Cell (cMLC), 128MB buffer and 5400-RPM spindle speed up to 140 MB/s |- | <!--Brand-->Toshiba 2.5in | <!--Model-->MQ04ABF100 1TB 5400 RPM 2018 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand-->TOSHIBA MQ01ACF | <!--Model-->MQ01ACF050 500GB 7200rpm 2020 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |- style="background:lightgrey; text-align:center; font-weight:bold;" | Brand | Model | Work MSDos | Work GPT | Tested Under |- | <!--Brand-->western digital wd blue 500G 8meg cache 5400rpm * 2014 Rev T0 * 2015 Rev T1 | <!--Model-->wd5000lpvx | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under-->2012-2015 sequential 2MB block transfers 110 MB/s reading and writing - |- | <!--Brand-->Western Digital 2.5" WD Blue Slim | <!--Model-->WD10SPCX 1TB Nov 2016 | <!--Work MSDos-->{{Yes|hdd under partition table msdos/pc, boots on bios machines, will not on uefi machine}} | <!--Work GPT-->{{Unk|untested hdd under gpt partition protocol scheme, not booting on uefi}} | <!--Tested under-->AROS One 1.8 USB |- | <!--Brand-->Western Digital WD | <!--Model-->WD5000LUCX 500Gb 5400rpm 16mb cache Rev Y0 | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> 2017 Malaysia |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} ====9.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu | <!--Model-->MHW2040BH | <!--Work--> | <!--Tested under--> 40gig |- | <!--Brand-->Fujitsu | <!--Model-->MHY2080BH | <!--Work--> | <!--Tested under--> 80gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHW2120B | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST bought by WD mid-2012 5K1000-1000 | <!--Model-->HTS541010A9E662 type TS5SAF100 | <!--Work--> | <!--Tested under--> 5400rpm |- | <!--Brand-->Hitachi Travelstar 5K500.B-320 | <!--Model-->HTS545025B9SA02 HTS545032B9A300 HTS545040B9A300 HTS545050B9A300 250Gb 320Gb 400Gb 500Gb 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Hitachi Global Storage Technologies HGST 1TB 7200rpm | <!--Model-->HTS721010A9E630 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung bought by Seagate late 2011 | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung Spinpoint with Seagate HD REV A (Jan 2014) | <!--Model-->ST1000LM024 | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand-->Samsung Spinpoint with Seagate 9.5mm * 2013 Rev A HN-M500MBB/I * 2014 Rev B HN-M500MBB/SP4 * 2015 Rev B HN-M500MBB/P4C | <!--Model-->ST500LM012 (500M) | <!--Work--> | <!--Tested under--> , Advanced Format (AF) |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Momentus 5400.3 | <!--Model-->ST9160821AS | <!--Work--> | <!--Tested under--> 160gig |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SSHD 1t | <!--Model-->ST1000LM014, ST1000LM028, ST1000LM015 | <!--Work--> | <!--Tested under--> 8g nand flash |- | <!--Brand-->Seagate SSHD 1T | <!--Model-->ST1000LX001 | <!--Work--> | <!--Tested under--> 32G nand flash |- | <!--Brand-->Toshiba | <!--Model-->MK2555GSX HDD2H24 | <!--Work--> | <!--Tested under--> 250g 5400rpm |- | <!--Brand-->Toshiba | <!--Model-->MK5065GSX - 500GB 5400RPM SATA 3Gb/s 8MB Cache 2.5-Inch | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MKxx59GSXP, eg Toshiba MK6459GSXP 640GB 2011 | <!--Work-->{{yes}} | <!--Tested under-->Icaros 2.2 with uses Advanced Format (AF) in 4,096 bytes per sector. Compatibility with legacy, 512 bytes through AF emulation techniques, called 512e |- | <!--Brand-->Toshiba (2013 to 2016) | <!--Model-->MQ01ABD100 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba (2015 to 2020) *2013 *2014 *2015 AA50/AX0D5A *2016 AA60/AX0E1A * *2017 AGM AA01/AX002V *2018 AGS AA70/AX0G1A *2020 AA71/AX0G1A | <!--Model-->MQ01ABD050 500meg | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba | <!--Model-->MQ04ABF100 1TB 5400 RPM 2013 | <!--Work-->{{Yes}} | <!--Tested under--> |- | <!--Brand-->TOSHIBA | <!--Model-->MQ04ABD200 2TB 5400 RPM 128MB Cache SATA 6.0Gb/s | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD7500BPVX 2013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WESTERN DIGITAL 1TB 2.5" SATA DRIVE 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-80JC3T0 (OCT 2014) | <!--Work--> | <!--Tested under--> , uses Advanced Format (AF) |- | <!--Brand-->WDC Western Digital Blue 1TB SATA 2.5" Hard Drive 5400 rpm, 8MB cache | <!--Model-->WD10JPVX-08JC3T6 (Jun 2017) | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD10JPCX 1Tb | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital * 2019 | <!--Model-->WD10JUCT 1TB (1000GB) 2019 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->WD Western Digital Scorpio Black * 2010 * 2014 | <!--Model-->WD5000BEKT, WD5000BPKX-22HPJT0, WD5000BPKT, | <!--Work--> | <!--Tested under--> 16m cache, 7200rpm thailand then malaysia |- | <!--Brand-->WD Western Digital Black * 2016 | <!--Model-->WD2500LPLX, WD3200LPLX, WD5000LPLX SMR: WD5000LPSX, WD10SPSX | <!--Work--> | <!--Tested under--> 32m cache , 7200rpm SATA-III malaysia |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA 2.5in NON-Laptop Hard Disks === ====11mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Fujitsu 160GB 250GB 300GB | <!--Model-->MHX2160BT, MHX2250BT, MHX2300BT | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model-->TP00640GB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====12.5mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} ====15mm==== {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 1TB IBM System X 15mm 2.5" SATA | <!--Model-->ST91000640NS 81Y9731 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT10N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 5v 12.7mm |- | <!--Brand-->HL Data Storage BD-Rom DVD Rewriter | <!--Model-->CT10N AFCK101 LGE-DMCT10A(B) | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 5v 12.7mm fails early |- | <!--Brand-->Hitachi LG | <!--Model-->GT20L | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009/2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model-->GT30N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT50N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 12.7mm |- | <!--Brand-->HL Data Storage | <!--Model-->GT90N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 5v 12.7mm |- | <!--Brand-->HP | <!--Model-->TS-L633 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.3A 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->HP | <!--Model-->GU70N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 5v 1.8A 9.5mm |- | <!--Brand-->HP | <!--Model-->GUD0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.8A 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->GTA0N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic | <!--Model-->Uj870a Uj880 UJ890 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->UJ8A0 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Panasonic MATSHITA 12.7mm SATA DVD | <!--Model-->UJ8B0 (Asus K53S), | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 12.7mm 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8B1 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2011 5v 1.5a |- | <!--Brand-->Panasonic | <!--Model-->UJ8C0 UJ8C1 UJ8C2 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.6a |- | <!--Brand-->Panasonic Precision Devices Co Ltd | <!--Model-->UJ8D0, UJ8D1 KCC-REM-PPD-UJ8D1 HP 657534-TC2, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2013 ok lifeline, |- | <!--Brand-->Panasonic | <!--Model-->UJ8E2Q | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2014 9.5mm |- | <!--Brand-->Panasonic | <!--Model-->UJ8FB | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5a 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model-->DS-8A5LH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm |- | <!--Brand-->HP | <!--Model-->DU-8A6SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2015 5v 1.5A 9.5mm |- | <!--Brand-->Philips and LiteOn | <!--Model-->DS-8A8SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5a 12.7mm |- | <!--Brand-->PLSD | <!--Model-->DS-8A9SH DS8A9SH | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7561S, AD-7560S Thickness: 12.7 MM Interface: SATA | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 |- | <!--Brand-->Sony | <!--Model-->AD-7580s, AD-7581s, AD-7583s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7585H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm cleaning the laser lens inside the drive with a liquid lens cleaner. Also check the lens carrier slides freely from one extreme to the other inside the drive without sticking |- | <!--Brand-->Sony | <!--Model-->AD7590s, AD-7591s, | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7700s, AD-7710h, AD-7701H, AD-7703S | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony Optiarc | <!--Model-->AD-7760H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2012 5v 1.5A 12.7mm |- | <!--Brand--> | <!--Model-->AD-7711H AD-7740H | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 12.5mm 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand-->Toshiba Samsung | <!--Model-->SN-S208B Ver BB Rev 00 | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2009 12.7mm |- | <!--Brand-->Toshiba TSSTCorp Samsung | <!--Model-->SN-S083C Ver C Rev 03 /BEBE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2010 5v 1.5a 12.7 mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> 9.5mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} === [https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data SATA Desktop 3.5inch Hard Disks] === Datasheets with the SMR (overlapped packing Shingled Magnetic Recording) and CMR (faster Conventional Magnetic Recording) parts <pre> WD: https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/internal-drives/wd-blue-hdd/product-brief-western-digital-wd-blue-pc-hdd.pdf Seagate: https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/datasheets/pdfs/3-5-barracudaDS1900-14-2007US-en_US.pdf Toshiba: https://storage.toshiba.com/docs/support-docs/P300-SalesSheet_English_Web_r2.pdf </pre> {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->HGST Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Seagate Barracuda 7200.9 | ST3160812AS, ST3160212AS | {{yes}} | Icaros Desktop 1.5.2 - Capacity: 160 GB - Speed: 7200RPM - Cache: 8 MB - Interface: SATA2 |- | <!--Brand-->Seagate Barracuda LP Green 5400rpm | <!--Model-->ST1000DL002 1TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SkyHawk Surveillance HDD ST4000VX000 Series | <!--Model-->ST4000VX013 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate Baracuda Compute | <!--Model-->ST500DM009 2F110A-500 / 02PKVY / 2PKVY (500m), | <!--Work--> | <!--Tested under--> - SATA III (6Gb/s) - Format 3.5" - 32MB Cache |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate CMR | <!--Model-->ST1000DM010 ST500DM009 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate 2TB SMR | <!--Model-->ST2000DM008 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate SMR | <!--Model-->ST8000DM004 ST6000DM003 ST4000DM004 ST3000DM007 ST2000DM005 | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 5400rpm | <!--Model-->HDWD220 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba 7200rpm | <!--Model-->HDWD320 | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Toshiba P300 CMR | <!--Model-->HDWD130XZSTA HDWD130UZSVA, HDWD120XZSTA HDWD120UZSVA, HDWD110XZSTA HDWD110UZSVA | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital 2010 | <!--Model-->WD20EARS Green 2TB 5400rpm 64mb cache | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital WD | <!--Model-->WD20EFRX WD40EFRX 5400rpm | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital | <!--Model-->WD4002FFWD | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD80EAAZ WD80EAZZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD20EARZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital CMR | <!--Model-->WD40EZAZ, WD60EZAZ | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD20EARZ, WD20EZAZ - 2TB | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Western Digital SMR | <!--Model-->WD40EZAX - 4TB, WD60EZAX - 6TB, WD80EZAX - 8TB | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === SATA Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- |} ==PATA== === IDE Desktop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | M1624TAU | {{yes}} | Icaros Desktop 1.5.2 |- | IBM | DHEA-38451 | {{yes}} | Icaros Desktop 1.5.2 |- | Samsung | SP40A2H | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST3160215ACE | {{yes}} | Icaros Desktop 1.5.2 |- | Seagate | ST32122A | {{maybe}} | Icaros Desktop 1.5.2 |- | Western Digital | WD102AA | {{yes}} | Icaros Desktop 1.5.2 |- | Western Digital | WD200 | {{maybe}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Laptop Hard Disks === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Fujitsu | MHV2040AH | {{yes}} | Icaros Desktop 1.4 |- | <!--Brand-->HGST Hitachi Travelstar | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Samsung | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand-->Seagate | <!--Model--> | <!--Work--> | <!--Tested under--> |- | Toshiba | MK2011GAP | {{yes}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} === IDE Desktop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | Compaq | CR-594-BCQ | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8322B(CP1) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | CRD-8484B(AM2A) | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Compaq | LTN-485 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Creative | CD220E | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Hitachi-LG | GDA-4120B | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | LG | CRD-8400B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Lite-On | LTN486S | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Mitsumi | CRMC-FX4830T | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | CDR-1700B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | DV-5800A | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | NEC | ND-2100A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | NEC | NR-7900A | {{yes}} | {{no}} | Icaros Desktop 1.5.2 |- | Philips | DVD8631 | {{no}} | {{no}} | Icaros Desktop 2.2 |- | Samsung | SC-148 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SCR-2030 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Samsung | SM-348B | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU601 | {{yes}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Sony | CDU611-25 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | Toshiba | SD-M1202 | {{no}} | {{n/a}} | Icaros Desktop 1.5.2 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested under--> |} === IDE Laptop Optical Drives === {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Reads ! width="10%" |Writes ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->H-L Hitachi LG | <!--Model-->GCC-4244N | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2006 |- | Hitachi-LG | GCCT10N | {{yes}} | {{Maybe|FryingPan WRITE seems to have no problem with data sections (track 1) - combos with audio sections (track 2) white screens aros eventually}} | AspireOS Xenon with 25th Jan 2014 self update kernel |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Philips | SDR089 | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | TSSTcorp | TS-L462C TS-L462D | {{yes}} | {{unk}} | 2005 Icaros Desktop 2.2 |- | TSSTcorp | TS-L632H | {{yes}} | {{unk}} | Icaros Desktop 1.4 |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | Sony | DW-Q58A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | Sony Optiarc | AD-7540A | {{yes}} | {{unk}} | Icaros Desktop 2.2 |- | <!--Brand-->Sony | <!--Model-->Optiarc DVD RW AD-7560A IDE | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand-->Sony | <!--Model-->AD-7590A | <!--Reads--> | <!--Writes--> | <!--Tested Distribution-->2008 12.7mm |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |- | <!--Brand--> | <!--Model--> | <!--Reads--> | <!--Writes--> | <!--Tested Distribution--> |} == SCSI == {| class="wikitable" width="100%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- | <!--Brand--> | <!--Model--> | <!--Work--> | <!--Tested under--> |- |} {| class="wikitable" width="70%" ! width="20%" |Brand ! width="20%" |Model ! width="10%" |Works MSDos/PC Bios ! width="10%" |Works GPT/UEFI ! width="20%" |Tested Distribution |- | <!--Brand--> | <!--Model--> | <!--Work MSDos--> | <!--Work GPT--> | <!--Tested under--> |- |} NVMe accepts up to 64,000 queues with up to 64,000 commands each. ryboof6pzi4cj3ly1s069lnbjezt5ra 0 296615 4634103 3698906 2026-05-04T15:45:47Z ErrinDev 3581204 change to gender neutral wording 4634103 wikitext text/x-wiki <noinclude>{{Nav}}</noinclude> <br /> <div class="nonumtoc"> __TOC__ </div> The TRUNCATE TABLE command deletes '''all''' rows of a table without causing any triggered action. Unlike the DELETE command, it contains no WHERE clause to specify individual rows. With respect to the TRUNCATE TABLE command, most DBMS show significantly better performance than with DELETE command. This results from the fact that the DBMS can empty the table (and its indexes) as a whole. It's not necessary to access individual rows. *There is - per definition - no WHERE clause. *No trigger action will be launched - per definition. *The transaction locks the complete table. *If there is an [[Structured Query Language/Foreign_Key#DROP_TABLE_/_TRUNCATE_TABLE|Foreign-Key-constraint]] from table ''t1'' to ''t2'', the command <code>'TRUNCATE TABLE t2'</code> will fail. This holds true independent from the question whether any row of ''t1'' refers actually to one of the rows of ''t2'' or not. The DBMS checks only the existence of the Forgeign-Key-constraint definition. The syntax of the TRUNCATE TABLE command is very simple. <syntaxhighlight lang="sql" style="background:LightGreen"> TRUNCATE TABLE <tablename>; </syntaxhighlight> == Example == <syntaxhighlight lang="sql"> -- Delete ALL rows of the table 'myTable' TRUNCATE TABLE myTable; -- In most DBMS ROLLBACK is not possible - in opposite to situations with a DELETE command. </syntaxhighlight> == An Analogy == To illustrate the difference between the TRUNCATE TABLE command and the DELETE command (without a WHERE clause), one can imagine a trucker, who wants to empty a trailer full of sand at a construction site. To do so, they have two possibilities; either empty the trailer by tilting it - this corresponds to the TRUNCATE TABLE command -, or climb onto the trailer and throw down one grain of sand after the next - this corresponds to the DELETE command. == Exercises == <div style=background:gold> Delete all rows of table 'person_hobby' using the DELETE command.<br />Verify that there are no rows left in 'person_hobby'.<br />Delete all rows of table 'hobby' using the TRUNCATE TABLE command.<br />What will happen? (Consider that there is an FK constraint from the table empty 'person_hobby' to 'hobby'.) </div> {{ExerciseSolution|width=100%|text= <syntaxhighlight lang="sql"> -- Delete all rows of 'person_hobby' with a DELETE command DELETE FROM person_hobby; COMMIT; -- Are there any rows? SELECT count(*) FROM person_hobby; -- Try TRUNCATE TABLE command: TRUNCATE TABLE hobby; -- An exception will be thrown. Although there is no row in 'person_hobby' referring a row in 'hobby', -- the definition of the Foreign Key constraint exists. This is the reason for the exception. </syntaxhighlight> }} <div style=background:gold> What will happen in the above example, if the TRUNCATE TABLE command is replaced by a DELETE command? </div> {{ExerciseSolution|width=100%|text= <syntaxhighlight lang="sql"> -- As there is no row in 'person_hobby' referring to 'hobby', the DELETE command deletes all rows in 'hobby'. DELETE FROM hobby; COMMIT; </syntaxhighlight> }} <div style=background:gold> The original data of the example database can be reconstructed as shown on the [[../Example Database Data|example database data]] page. </div> <noinclude>{{Nav}}</noinclude> tr6mhurvcihaxaqkgwwr7qwljgv7bg5 0 299155 4634106 3698918 2026-05-04T15:49:35Z ErrinDev 3581204 change to gender neutral wording 4634106 wikitext text/x-wiki <noinclude>{{Nav}}</noinclude> <br /> <div class="nonumtoc"> __TOC__ </div> For multiuser systems like DBMSs, it is necessary to grant and revoke rights for manipulating its objects. The GRANT command defines which user can manipulate (create, read, change, drop, ...) which object (tables, views, indexes, sequences, triggers, ...). <syntaxhighlight lang="sql" style="background:LightGreen"> GRANT <privilege_name> ON <object_name> TO [ <user_name> | <role_name> | PUBLIC ] [WITH GRANT OPTION]; </syntaxhighlight> The REVOKE statement deprives the granted rights. <syntaxhighlight lang="sql" style="background:LightGreen"> REVOKE <privilege_name> ON <object_name> FROM [ <user_name> | <role_name> | PUBLIC ]; </syntaxhighlight> The example statement grants SELECT and INSERT on table ''person'' to the user ''hibernate''. The second statement removes the granted rights. <syntaxhighlight lang="sql"> GRANT SELECT, INSERT ON person TO hibernate; REVOKE SELECT, INSERT ON person FROM hibernate; </syntaxhighlight> == Privileges == Privileges are actions that users can perform. The SQL standard supports only a limited list of privileges, whereas real implementations offer a great bunch of different privileges. The list consists of: SELECT, INSERT, UPDATE, DELETE, CREATE <object_type>, DROP <object_type>, EXECUTE, ... . == Object Types == The list of object types, to which privileges may be granted, is short in the SQL standard and long for real implementations. It consists of tables, views, indexes, sequences, triggers, procedures, ... . == Roles / Public == If there is a great number of users connecting to the DBMS, it is helpful to group users with identical rights to a role and grant privileges not to the individual users but the role. To do so, the role must be created by a CREATE ROLE statement. Afterward, users are joined with this role. <syntaxhighlight lang="sql"> -- Create a role -- (MySQL supports only predefined roles with special semantics). CREATE ROLE department_human_resources; -- Enrich the role with rights GRANT SELECT, INSERT, UPDATE, DELETE ON person TO department_human_resources; GRANT SELECT, INSERT ON hobby TO department_human_resources; GRANT SELECT, INSERT, UPDATE, DELETE ON person_hobby TO department_human_resources; -- Join users with the role GRANT department_human_resources TO user_1; GRANT department_human_resources TO user_2; </syntaxhighlight> Instead of individual usernames, the keyword PUBLIC denotes '''all''' known users. <syntaxhighlight lang="sql"> -- Everybody shall be allowed to read the rows of the 'person' table. GRANT SELECT ON person TO PUBLIC; </syntaxhighlight> == Grant Option == If a DBA wants to delegate the managing of rights to special users, they can grant privileges to the users and extend the statement with the phrase 'WITH GRANT OPTION'. This enables the users to grant the received privileges to any other user. <syntaxhighlight lang="sql"> -- User 'hibernate' gets the right to pass the SELECT privilege on table 'person' to any other user. GRANT SELECT ON person TO hibernate WITH GRANT OPTION; </syntaxhighlight> <noinclude>{{Nav}}</noinclude> 2tfuatpanmtfbabhhvabbidjusx8wn9 0 301046 4634172 4003432 2026-05-04T19:10:08Z JCrue 2226064 request deletion 4634172 wikitext text/x-wiki {{delete|Out of scope (rare sideline, not theory); Burris is vanity name.}} {{Chess Opening Theory/Position|= |Caro–Kann Defence: Burris Gambit| |rd|nd| |qd|kd|bd| |rd|= |pd|pd| | |pd|pd|pd|pd|= | | |pd| | |nd| | |= | | | | | |bd| | |= | | | | |nl| | | |= | | | |bl| |nl| | |= |pl|pl|pl| |ql|pl|pl|pl|= |rl| |bl| |kl| | |rl|= }} = Caro-Kann Defence:Burris Gambit accepted = Black does not drop the piece. <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">8</th> <th align="left">9</th> <th align="left">10</th> </tr> <tr> <th align="right"></th> <td>Nxf6+<br>gxf6</td> <td>Bxf5<br>Qa5+</td> <td>Bd2<br>Qxf5</td> <td>=</td> </tr> </table> {{ChessMid}} ==References== {{reflist}} {{BCO2}} {{Chess Opening Theory/Footer}} {{ChessStub}} tq3vxmqlhl8ai2cktvyki2k8crq8uwa 0 307788 4634087 3698563 2026-05-04T14:53:00Z ~2026-27064-11 3581190 change to gender neutral wording 4634087 wikitext text/x-wiki <noinclude>{{Nav}}</noinclude> <br /> <div class="nonumtoc"> __TOC__ </div> When learning SQL (or any other programming language), it is not sufficient to read books or listen to lectures. It's absolutely necessary that one does exercises - prescribed exercises as well as own made-up tests. In the case of SQL, one needs access to a DBMS installation, where they can create tables, store, retrieve and delete data, and so on. This page offers hints and links to some popular DBMS. In most cases, one can download the system for test purposes or use a free community edition. Some of them offer an online version so that there is no need for any local installation. Instead, such systems can be used in the cloud. Often, but not always, a DBMS consists of more than the pure database engine. To be able to formulate SQL commands easily, we additionally need an interactive access to the database engine. Different client programs and IDEs provide this. They offer interactive access, and in many cases, they are part of the downloads. (In some cases, there are several different clients from the same producer.) At the same time, there are client programs and IDEs from other companies or organizations which offer only an interactive access but no DBMS. Such clients often support a lot of different DBMS. == Derby == http://db.apache.org/derby/ == Firebird == http://www.firebirdsql.org/ == IBM DB2 == http://www-01.ibm.com/software/data/db2/linux-unix-windows/ == IBM Informix == http://www-01.ibm.com/software/data/informix/ == MariaDB == https://mariadb.org/ == MS SQL Server == http://www.microsoft.com/en/server-cloud/products/sql-server/default.aspx == MySQL == DBMS: http://dev.mysql.com/downloads/<br /> IDE for administration and SQL-tests: http://dev.mysql.com/downloads/workbench/ == Oracle == The Oracle database engine is available in 4 editions: Enterprise Edition (EE), Standard Edition (SE), Standard Edition One (SE One), and Express Edition (XE). The last-mentioned is the community edition and is sufficient for this course. http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html. SQL-Developer is an IDE with an Eclipse-like look-and-feel and offers access to the database engine. http://www.oracle.com/technetwork/developer-tools/sql-developer/overview/ In the context of Oracles application builder APEX (APplication EXpress), there is a cloud solution consisting of a database engine plus APEX. https://apex.oracle.com/. Among a lot of other things, it offers an SQL workshop where everybody can execute his own SQL commands for testing purposes. On the other hand, APEX can be downloaded separately and installed into any of the above editions except for the Express Edition. == PostgreSQL == http://www.postgresql.org/ == SQLite == http://www.sqlite.org/ == Online Access == [http://sqlfiddle.com/ SQL Fiddle ] offers an online access to following implementations:<br /> [[MySQL]], [[PostgreSQL]], [[Microsoft SQL Server|MS SQL Server]], [[Oracle Database|Oracle]], and [[SQLite]]. <br /> <noinclude>{{Nav}}</noinclude> i9czvrazljswuc94zw3yr4ngz6d0am3 0 365141 4634206 4633545 2026-05-05T01:00:10Z JackBot 396820 Formatting, [[Special:UncategorizedPages]] 4634206 wikitext text/x-wiki Nervous System – Anatomy and Common Ailments 1. Overview of the Nervous System The nervous system is the body’s control and communication network. It detects changes, processes information, and coordinates responses. It works closely with the endocrine system to maintain internal balance. 2. Divisions of the Nervous System A. Central Nervous System (CNS) The CNS is the main control center. Components: Brain Spinal cord Functions: Processes sensory information Makes decisions Sends commands to the body B. Peripheral Nervous System (PNS) The PNS connects the CNS to the rest of the body. Components: Cranial nerves Spinal nerves Subdivisions: Somatic nervous system (voluntary control of muscles) Autonomic nervous system (involuntary functions) C. Autonomic Nervous System (ANS) Sympathetic system “Fight or flight” response Increases heart rate, dilates pupils Parasympathetic system “Rest and digest” Conserves energy, slows heart rate 3. Structure of the Brain The brain is the most complex organ and is divided into major regions: A. Cerebrum Largest part Responsible for thinking, memory, emotions, and voluntary movement B. Cerebellum Coordinates balance and movement C. Brainstem Controls vital functions such as breathing and heart rate 4. Spinal Cord The spinal cord is a long cylindrical structure extending from the brainstem. Functions: Transmits signals between brain and body Controls reflex actions 5. Neurons and Nerve Function Neuron Structure Dendrites: receive signals Cell body: processes information Axon: transmits signals Types of Neurons Sensory neurons Motor neurons Interneurons 6. Protective Structures The nervous system is protected by: Skull and vertebral column Meninges (three protective layers) Cerebrospinal fluid (CSF) (cushions and nourishes) 7. Common Ailments of the Nervous System 1. Stroke A stroke occurs when blood supply to part of the brain is interrupted. Causes: Blood clot (ischemic) Bleeding (hemorrhagic) Symptoms: Sudden weakness Difficulty speaking Loss of coordination 2. Epilepsy A disorder characterized by recurrent seizures due to abnormal electrical activity in the brain. Symptoms: Seizures Loss of consciousness Uncontrolled movements 3. Parkinson’s Disease A progressive disorder affecting movement. Symptoms: Tremors Muscle stiffness Slow movement 4. Alzheimer’s Disease A degenerative brain disorder affecting memory and thinking. Symptoms: Memory loss Confusion Difficulty performing daily tasks 5. Multiple Sclerosis (MS) An autoimmune disease affecting the protective covering of nerves. Symptoms: Muscle weakness Vision problems Coordination difficulties 6. Meningitis Inflammation of the protective membranes covering the brain and spinal cord. Causes: Bacterial or viral infection Symptoms: Severe headache Fever Neck stiffness 7. Peripheral Neuropathy Damage to peripheral nerves. Causes: Diabetes Injury Infections Symptoms: Tingling Numbness Pain 8. Migraine A neurological condition causing intense headaches. Symptoms: Throbbing pain Sensitivity to light and sound Nausea 8. Prevention and Care Maintain a healthy diet Exercise regularly Avoid smoking and excessive alcohol Manage stress Control chronic diseases like diabetes and hypertension Conclusion The nervous system plays a vital role in controlling and coordinating body functions. Disorders of this system can significantly affect quality of life, making early detection and proper care essential. {{BookCat}} 2y8d32rj3ucegh7yd5n0yrhxftyu2y3 0 380958 4634062 4414471 2026-05-04T12:18:25Z Jcb 90773 4634062 wikitext text/x-wiki {{:RadOnc_Resident_Wiki/Uterus:TOC}} ==Current staging== <big>'''Endometrial Carcinomas'''</big> '''AJCC 7th Edition (2009)''' <br> :Corresponds to updated FIGO staging (2009) :'''FIGO 2009''' {{PMID|19345353}} -- "Revised FIGO staging for carcinoma of the endometrium." :This staging now applies only to endometrial carcinomas and there is now a separate staging for [[RadOnc_Resident_Wiki/Uterine Sarcoma/Staging|uterine sarcomas]]. ::Carcinosarcomas (MMMT) should be staged as high grade carcinoma. <br> ''Primary Tumor:'' (FIGO Stage in parentheses) :Note: FIGO uses pathologic staging *Tis - in situ *:Note: FIGO no longer includes Stage 0 *T1 (I) - confined to corpus **T1a (IA) - limited to endometrium or invades less than 1/2 of myometrium **T1b (IB) - invades &ge; 1/2 of myometrium *T2 (II) - invades stromal tissue of the cervix but does not extend beyond uterus *:Note: endocervical glandular involvement only should be considered as Stage I not Stage II *T3 **T3a (IIIA) - involves serosa and/or adnexa (direct extension or metastasis) **T3b (IIIB) - vaginal involvement (direct extension or metastasis) or parametrial involvement *T4 (IVA) - invades bladder mucosa and/or bowel mucosa ''Regional Lymph Nodes:'' *N0 - none *N1 (IIIC1) - metastasis to pelvic lymph nodes *N2 (IIIC2) - metastasis to para-aortic lymph nodes *:Note: Regional nodes include obturator, internal iliac, external iliac, common iliac, para-aortic, presacral, and parametrial *:Note: For pathologic staging, FIGO classifies cases with <6 resected LNs as pNX ''Distant Metastases:'' *M0 - none *M1 (IVB) - distant metastasis - includes inguinal LN, intraperitoneal disease (including omentum), lung, liver, or bone. ''Stage Grouping:'' *Corresponds to FIGO stage given above (in parentheses) ''Changes from 6th Edition:'' *No longer includes uterine sarcoma (now staged with a new staging system) *Positive peritoneal cytology is no longer considered (previously was T3a/IIIA) *Involvement of the endocervical glands is no longer considered (previously was Stage IIA) *Stages IA+IB combined (now: IA). IC moved to IB. *Stage IIIC subdivided into IIIC1 and IIIC2. ===Older staging systems=== FIGO moved to surgical staging in 1988 (AJCC 6th edition same). There is also a clinical staging system developed by FIGO in 1971. Note: until the update of the FIGO / AJCC in 2009, '''uterine sarcomas''' and carcinomas were staged using the same system '''AJCC 6th Edition (2002)''' <br> *IA - Limited to endometrium *IB - < 1/2 of myometrium *IC - 1/2 or more of myometrium *II - invades cervix **IIA - glandular epithelium of endocervix **IIB - stroma of cervix *III - extra-uterine **IIIA - involves serosa and/or adnexa (direct extension or mets) and/or ascites or positive peritoneal washings **IIIB - vaginal involvement (direct extension or mets) **IIIC - LN+ (pelvic and/or paraaortic) *IV - other organs **IVA - bladder or bowel **IVB - distant mets ===Clinical staging=== Staging is now surgical (see above), but clinical staging may be utilized for non-operative pts. '''FIGO 1971''' *I - Confined to corpus **IA - Length of uterine cavity 8 cm or less **IB - Length of uterine cavity > 8 cm *II - Involves corpus and cervix, but no extension beyond the uterus *III - Extends outside uterus but not outside true pelvis *IV - Outside the true pelvis or involves bladder or rectum **IVA - Involves bladder, rectum, sigmoid, or small bowel **IVB - Distant mets ==Stage distribution== {| border="1" |+ '''Stage Distribution''' ! Stage !! US SEER ({{PMID|16977653}}) !! FIGO ({{PMID|17161155}}) |- ! Stage I | align="center" | 73% || align="center" | 67% |- ! Stage II | align="center" | 10% || align="center" | 11% |- ! Stage III | align="center" | 10% || align="center" | 13% |- ! Stage IV | align="center" | 7% || align="center" | 3% |} duo5p7um8d837q44qunrrccpwti5o5m 0 396435 4634263 4003285 2026-05-05T11:52:48Z JCrue 2226064 4634263 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Dragon variation |eco=[[Chess/ECOB|B27]] |parent=[[Chess Opening Theory/1. e4/1...c5|Sicilian defence]] → [[Chess Opening Theory/1. e4/1...c5/2. Nf3/2...d6/3. d4/3...cxd4/4. Nxd4/4...Nf6/5. Nc3/5...g6|Dragon variation]] → [[../|6...Ng4]] }} == 7. Ng4?? == {{Chess/sideline}} Black attacks White's bishop, but falls into a common amateur trap.<ref>It is the fourth move in the Lichess database, played over 24,000 times as of May 2026.</ref> White's queen attack's Black's knight, but it is currently guarded by their light square bishop. [[/7. Bb5|'''7. Bb5+''']] cuts off that protection. If Black blocks the check with 7...Nd7, their bishop no longer guards g4. If 7...Bd7, the bishop becomes pinned and so also does not guard g4. If 7...Nc6, White can trade knights, 8. Nxc6 (attacking the queen) bxc6, and 9. Bxc6+ forks the king and rook. {{ChessMid}} == References == {{reflist}} === See also === {{Wikipedia|Sicilian Defence, Dragon Variation}} {{ChessFooter}} futiax0o797w2xkeg1q38zva31xg6vt 0 403829 4634084 4634015 2026-05-04T14:30:25Z EthanZhang95 3578075 added and fixed information in this chapter. 4634084 wikitext text/x-wiki <b>The Deep Web</b> (also referred to as <b>The Hidden Web</b> and <b>The Invisible Web</b>) is a collection of non-indexed web content. The deep web is often confused with the term "[[w:Dark Web|dark web]]", the darknet networks that require special tools and authorizations to access. The dark web is a subset of the deep web, as the two fulfill separate purposes. Both are separate from the "surface web", web pages openly accessible to anyone. [[w:Hypertext Transfer Protocol| HTTP]] form hide content on the deep web <Ref>{{cite web|url=|title=How Do You Want Me to Do It? Does It Have to Look like an Accident? – an Assassin Selling a Hit on the Net; Revealed Inside the Deep Web|newspaper=[[Sunday Mail (Scotland)|Sunday Mail]] |date=June 8, 2014 |first=Sam |last=Shedden |accessdate=December 9, 2018}}</ref> that [[w:Web indexing| web crawlers]] cannot access nor index. This secures data from the public. A login page can hide information from unauthorized users. With most of the inaccessible deep web being dedicated to business transactions and database storage with limited widespread social impact, this page will focus on the dark web with respects to anonymity, privacy, and security. =The Dark Web= People can access the dark web through either onion routing or garlic routing. Onion routing and garlic routing are most commonly employed by the Tor and I2P projects, respectively. The Tor Project has a larger user base. There are several differences between the two projects.<ref>https://geti2p.net/en/comparison/tor</ref> While originally developed for government and military communications, dark web use has expanded to civilians, journalists, law enforcers, activists, business executives, and professionals.<ref name="TorUsers">{{cite web |url=https://www.torproject.org/about/torusers |title=Who uses Tor? |publisher=The Tor Project |accessdate=2018-12-09 }}</ref> ==The Onion Router Project== [[File:Tor-logo-2011-flat.svg|thumb|The Tor Project logo]] The Onion Router (Tor) Project<ref name=":0">https://www.torproject.org/index.html.en</ref> is an open-source volunteer-driven project with the agenda of improving the privacy and security of people on the Internet.<ref>{{cite web |url=https://www.torproject.org/about/overview |title=Tor Project: Overview |publisher=The Tor Project |accessdate=2018-12-08 }}</ref> Its Tor browser software protects users by bouncing their communications around a distributed network of relays run by volunteers around the world. The software is a modified Mozilla Firefox web browser that can access darknet [[w:.onion|.onion domains]] as well as surface web domains. ==The Invisible Internet Project== [[File:I2P logo.svg|thumb|The I2P logo]] The Invisible Internet (I2P) Project<ref>https://geti2p.net/en/is</ref> an open-source anonymous overlay network that relies on bouncing encrypted messages around numerous one-way tunnels.<ref name=":1">{{cite web |url=https://geti2p.net/en/about/intro |title=Intro |work=The Invisible Internet Project |accessdate=2018-12-10 }}</ref> Instead of the Tor's .onion sites, the I2P browser features its own .i2p eepsites. Its browser can only access darknet domains within the I2P network.<ref>{{cite web |url=https://www.comparitech.com/blog/vpn-privacy/how-to-access-the-deep-web-and-darknet/ |title=Step by step guide to safely accessing the dark net and deep web |last=Bischoff |first=Paul |work=VPN & Privacy |publisher=Comparitech |date=2018-09-12 |accessdate=2018-12-10 }}</ref> ==Peer-to-Peer Networks== The dark web uses a peer-to-peer network. It differs from the conventional client-server model since there are no designated servers. The network's infrastructure, processing power, and storage comes from the computers, also called nodes, on the network. They function as servers and routers. Tor<ref name=":2">https://www.torproject.org/docs/documentation.html.en</ref> uses standard internet communication protocol, which allows any computer to join the network. The list of Tor relays at any moment is public. A user's Tor client facilitates the routing process to provide security, privacy, and anonymity. The client retrieves the list of active relays, generates a random path, and then adds additional overhead layers to the data packet for each node on the path. The computers at each node can only access their layer, which tells them the location of the next relay. As a result, a relay node does not know the end destination of the data, nor can it see the data. The last node, called exit node, delivers the data packet to the end destination. The network contains many features and vulnerabilities such as eavesdropping, protocol sabotage, and IP reveals. =Participants= Internet service providers have sold their customers' browsing records.<ref>{{cite news |last=Blodget |first=Henry |url=https://seekingalpha.com/article/29449-compete-ceo-isps-sell-clickstreams-for-5-a-month |title=Compete CEO: ISPs Sell Clickstreams For $5 A Month |work=Seeking Alpha |date=2007-03-13 |accessdate=2018-12-11 }}</ref> Participants who care about their online privacy can communicate and research without unwanted surveillance. Darknet softwares hide peoples' identities and web traffic while browsing. ==Governments and Militaries== Governments and militaries need private untraceable communications. Originally designed by the US government for military communications, onion routing's original purpose was to distribute robust messages through centralized server sites.<ref name="TorUsers" /> By routing messages through multiple encrypted layers, they can protect intelligence operations from interception, traffic analysis, or infrastructure shutdown. Beyond defense, governments also use the dark web for law enforcement and intelligence gathering, such as infiltrating criminal networks and conducting undercover operations. However, similar tools can also be used for domestic surveillance and control, including monitoring dissidents or restricting information, showing how the same technology can serve both security and authoritarian purposes. ==Activists and Whistleblowers== Under government censorships in countries like China,<ref>{{cite journal |title=Race to the Bottom: Corporate Complicity in Chinese Internet Censorship |journal=Human Rights Watch |date=2006-08 |volume=18 |issue=8 |url=https://www.hrw.org/reports/2006/china0806/china0806web.pdf |format=PDF |accessdate=2018-12-10 }}</ref> activists and whistleblowers need protections and anonymity to protect themselves. Readers can evade national firewalls to research global censored and/or controversial topics without risk of persecution.<ref name="TorUsers" /> Whistleblower submission systems such as SecureDrop<ref>https://securedrop.org/</ref> allow media organizations to securely accept documents from anonymous sources.<ref>{{cite web |url=https://securedrop.org/ |title=SecureDrop |accessdate=2018-12-10 }}</ref> Journalists can access the dark web to write about local events and social reforms that would otherwise be censored.<ref name="TorUsers" /> However, the anonymity provided for whistleblowers can complicate credibility and accountability, as sources are harder to verify. This highlights an important tension as the dark web enables free expression and broad information access, but introduces challenges in trust and verification. ==Illicit Actors== Illicit actors include cybercriminals, black-market vendors, and extremist/terrorist groups, all drawn to the dark web for its core features of anonymity and decentralization, allowing them to operate outside traditional legal and regulatory systems, reducing the risk of identification and prosecution from authorities. Compared to the surface web, the dark web offers a far more secure environment for sensitive communication and coordination. Moreover, trading cryptocurrencies over the dark web allow these groups and individuals to negotiate and transfer large amounts of funds without detection, allowing them to operate outside traditional financial oversight, further supporting their operations. ==General Privacy Users== A majority of dark web users are not malicious, but rather privacy-conscious individuals who value anonymity and protection from digital tracing. These users include everyday citizens who wish to browse the internet, communicate, or access information without being monitored by corporations such as their internet service providers or big tech companies. Unlike activists or whistleblowers, privacy users use of the dark web is typically not politically motivated, but instead driven by concerns over personal data privacy, targeted advertising, and online profiling. The strong association of the dark web with illicit activity often stigmatizes these users, creating a tension between legitimate privacy-seeking behavior and public perceptions of digital anonymity as suspicious and criminal. ==Infrastructure Builders== Infrastructure builders include developers, researchers, and organizations that design, maintain, and extend the technical systems that hold up the dark web. This ranges vastly from core anonymity networks like Tor to platforms, marketplaces, communication tools, and privacy-enhancing applications built on top of them. These builders are often motivated by core dark web values such as privacy, decentralization, and open access to information, aiming to create systems that resist surveillance and centralized control. However, they typically do not control how their technologies are ultimately used and as a result, tools intended to support privacy and free expression also enable illicit activities, highlighting a tension between design intentions and real-world use. =Case Studies= ==Darknet Markets== Darknet markets and communications platforms do not simply pit technology against law enforcement - they are arenas where competing social actors content control, trust, and legitimacy. The cases below, spanning drug markets, financial whistleblowing, and AI, each illustrate how the dark web's conflicts are fundamentally about who sets the rules when there is no central authority. ===Silk Road=== [[File:Silk Road Seized.jpg|thumb|Screenshot of the Silk Road shutdown]] [[w:Silk Road (marketplace)| Silk Road]] was an online black market marketplace for drugs and other illegal goods founded by [[w:Ross Ulbricht| Ross Ulbricht]] who used the pseudonym "Dread Pirate Roberts".<ref>{{cite web |url=https://www.engadget.com/2015/02/08/silk-road-trial-lessons/ |title=Anonymity is dead and other lessons from the Silk Road trial |last=Lee |first=Nicole |publisher=Engadget |date=2015-02-08 |accessdate=2018-12-09 }}</ref> Ulbricht's explicit goal was to build a free market where drug use was treated as a victimless personal choice, bypassing violet middlemen. To make that work without institutional backing, Silk Road layered ratings, escrow systems, and buyer feedback on top of [[wikipedia:Tor_(network)|Tor's]] anonymity - technology substituting for the social trust that ordinarily requires knowing someone in person. Buyers could purchase drugs with untraceable [[w:Bitcoin| Bitcoin]] transactions, and have them delivered by the postal service, an unwitting participant. In June 2013, FBI agents identified Silk Road's true server location through a software flaw, and Ulbricht was arrested.<ref>{{cite web |url=https://www.wired.com/2014/09/fbi-silk-road-hacking-question/ |title=FBI's Story of Finding Silk Road's Server Sounds a Lot Like Hacking |last=Greenberg |first=Andy |work=Security |publisher=Wired |date=2014-09-08 |accessdate=2018-12-09 }}</ref> Despite having no prior criminal record, he was sentenced to double life plus 40 years without parole. The severity of the sentence was widely debated: proportionate justice, or a strategic deterrent to discourage future operators?<ref>{{cite web |url=https://freeross.org/1-page-overview/ |title=1-page Overview |work=One-page Overview |publisher=Ross Ulbricht Defense Fund |accessdate=2018-12-10 }}</ref> That question was reopened in January 2025, when President Trump pardoned Ulbricht, reigniting debate about how states should respond to darknet markets.<ref>{{cite web |url=https://www.npr.org/2025/01/21/nx-s1-5270051/trump-pardons-dark-web-marketplace-creator-ross-ulbricht |title=Trump pardons Ross Ulbricht, creator of the Silk Road dark web marketplace|last=McLaughlin |first=Jenna |publisher=NPR |date=2025-01-21 |accessdate=2025-04-22 }}</ref> ===AlphaBay=== [[File:Alphabay-forfeiture-notice-screenshot-2017-05-12.png|thumb|AlphaBay forfeiture notice screenshot|alt=Alphabay-forfeiture-notice-screenshot-2017-05-12.png]] Canadian citizen Alexandre Cazes launched [[w:AlphaBay| AlphaBay]] in September 2014,<ref>{{cite news |first=Django |url=https://darkwebnews.com/darkwebmarkets/alphabay/ |title=AlphaBay |work=Darkweb News |publisher=Dark Web News Publication |date=2018-11-12 |accessdate=2018-12-11 }}</ref> and by July 2017 it had grown to ten times the size of the Silk Road by expanding beyond drugs into stolen corporate data, credentials, and financial records - making businesses unwitting victims alongside individual users. Cazes relocated to Thailand to operate the market and displayed his wealth publicly on social media, lapses that contributed to his arrest. But the most consequential innovcation in AlphaBay's takedown was the enforcement strategy surrounding it. As part of [[wikipedia:Operation_Bayonet_(darknet)|Operation Bayonet,]] the Dutch National Police secretly seized and continued operating the competing darknet market [[wikipedia:Hansa_(market)|Hansa]] in the weeks before AlphaBay was shut down.<ref name="Bayonet">{{cite news |last=Greenberg |first=Andy |url=https://www.wired.com/story/hansa-dutch-police-sting-operation/ |title=Operation Bayonet |work=Wired |location=New York |publisher=Wired Magazine |date=2018-03-08 |accessdate=2018-12-11 }}</ref> When AlphaBay fell and users fled to what they believed was a safe alternative, they walked directly into a law enforcement honeypot. The FBI and DEA's goal was not merely to close one market but to destroy user confidence in the darknet markets as a category. The operation succeeded not because authorities broke the encryption, but because they understood the ecosystem's social dynamics - displacement behavior, trust migration, and platform loyalty - better than the users themselves did. Thai authorities found Cazes dead in his cell days after his arrest and suspect suicide. ==Whistleblowing== Whistleblowing on the dark web centers on control over sensitive information rather than economic exchange. Unlike darknet markets, which rely on pricing, reputation, and cryptocurrency transactions, whistleblowing platforms are structure around trust, credibility, and the safe transfer of information between anonymous sources and journalists. The case below demonstrates how anonymity reshapes the relationship between individuals, institutions, and the public by enabling the disclosure of information that would otherwise remain hidden. === "John Doe" and the Panama Papers === [[File:Countries implicated in the Panama Papers.svg|thumb|Countries implicated in the Panama Papers leak]] Not all dark web activity involves markets. In 2015, an anonymous source using the pseudonym "John Doe" contacted journalists at the German newspaper ''Süddeutsche Zeitung'' through encrypted, anonymous channels and offered access to internal documents from the Panamanian law firm Mossack Fonseca.<ref>{{cite web |url=https://www.icij.org/investigations/panama-papers/the-story-that-rocked-the-world-ten-years-of-the-panama-papers-part-1/ |title=The story that rocked the world: Ten years of the Panama Papers, part 1 |last=Mauriello |first=Tracie |publisher=ICIJ |date=2026-03-31 |accessdate=2025-04-22 }}</ref> The whistleblower insisted on communicating exclusively over encrypted channels and refused any face-to-face contact, stating that their lift was in danger. The resulting leak - over 11.5 million documents exposing the offshore financial networks of politicians, executives, and celebrities worldwide - become known as the [[wikipedia:Panama_Papers|Panama Papers]] and triggered investigations in more than 80 countries. Without the ability to contact journalists anonymously, the source would have faced near-certain legal retaliation. The case surfaces a tension that runs through the entire dark web; the same infrastructure that enables criminal markets also enables accountability journalism. The Panama Papers strengthened financial transparency laws, increased regulation of offshore accounts, and expanded international cooperation on tax enforcement - while simultaneously legitimizing anonymous communication tools as instruments of the public interest. ==Artificial Intelligence== The emergence of large language models (LLMs), which rose to prominence in the early 2020s, has introduced a new dimension to the dark web: the automation and amplification of technical capability. Unlike markets or whistleblowing platforms, which mainly focus on exchange and the flow of information, AI systems reshape what users are able to do by lowering the skill barrier for complex tasks. The case below highlights how the integration of AI into the dark web transforms it from a space of coordination into a space of on-demand malicious capability generation, raising questions about control, responsibility, and the scalability of harm. === DIG AI === The dark web's sociotechnical contests have expanded into [[wikipedia:Artificial_intelligence|artificial intelligence]]. In September 2025, DIG AI launched as a [[wikipedia:Tor_(network)|Tor]]-hosted [[wikipedia:Large_language_model|large language model]] built on open-weight models that were explicitly fine-tuned to operate without the content restrictions that mainstream AI systems enforce.<ref>{{cite web |url=https://www.resecurity.com/blog/article/dig-ai-uncensored-darknet-ai-assistant-at-the-service-of-criminals-and-terrorists |title=DIG AI: Uncensored Darknet AI Assistant at the Service of Criminals and Terrorists |publisher=Resecurity |date=2025-12-18 |accessdate=2025-04-22 }}</ref> While mainstream surface web LLMs like [[wikipedia:ChatGPT|ChatGPT]] and [[wikipedia:Claude_(language_model)|Claude]] deliberately decline requests for phishing emails, weapons instructions, or malicious code, DIG AI fulfills them. As a result, criminal capability becomes significantly more accessible. Tasks that previously required hiring skilled technical specialists, such as hacking a website, can now be performed directly by non-technical users through simple prompts to the un-restricted LLM. The governance vacuum is striking: AI companies whose models were appropriated can only file threat reports; cybersecurity firms can monitor DIG AI but cannot remove it; no internal authority has jurisdiction over a Tor-hosted service. DIG AI extends a central pattern: each time enforcement closes one avenue, the ecosystem reconstitutes around a new technology. The question is not only how to respond to one uncensored model, but what it means for the dark web when AI-powered capability becomes as accessible as a drug listing. This development also reveals a deeper tension between governments and AI capabilities. While states actively pursue advanced and potentially unrestricted AI systems through partnerships with private companies, they simultaneously seek to restrict public access to those same capabilities. However, the dark web functions as the critical infrastructure that undermines this control. By enabling anonymous hosting, distribution, and access, it allows tools like DIG AI to exist outside traditional regulatory and corporate boundaries. The implication is a shift in the balance of power: while governments attempt to centralize access to high-capability AI, the dark web enables capability diffusion, redistributing these tools to a broader set of actors. This raises a fundamental question: does restricting such technologies enhance security, or does it simply incentivize their migration to decentralized, less controllable environments? ==Darknet Communications== ===Facebook=== [[w:Facebook| Facebook]] <ref>{{cite news |last=Greenberg |first=Andy |url=https://www.wired.com/2014/10/facebook-tor-dark-site/ |title=Why Facebook Just Launched Its Own 'Dark Web' Site |work=Wired |location=New York |publisher=Wired Magazine |date=2014-10-31 |accessdate=2018-12-11 }}</ref> launched [[w:facebookcorewwwi.onion| its services on the dark web]] in 2014 allowing users to circumvent any firewalls or censorship. The launch aligns with Facebook’s mission to connect people. Once the user reaches Facebook they can use services normally. Facebook used to flag excessive routing, like Tor, as suspicious behavior and even denied services. Android support and dark web client plug-ins followed. Dark web traffic to Facebook spiked temporarily near the end of 2015. Political conflict and civil unrest caused the Bangladesh government to ban Facebook and other social media services in November of 2015. However, they could not shut down nor block the Tor network. This rendered the ban ineffective. Most bans use IP, but Tor conceals the IP. Over 1 million users connect to Facebook monthly through Tor<ref>{{cite news |last=Wong |first=Joon |url=https://qz.com/667880/a-million-people-now-access-facebook-on-the-dark-web-every-month/ |title=A million people now access Facebook on the “dark web” every month |work=Quartsz |location=New York |publisher=Quartz |date=2016-04-22 |accessdate=2018-12-11 }}</ref>. Alec Muffett, a Facebook engineer wrote, “It’s important to us to provide methods for people to use our services securely—particularly if they lack reliable methods to do so.” Security expert Runa Sandvik praised Facebook and expects other companies to do the same. ===Chat Rooms and JavaScript=== In early 2018, a chatroom called OnionChat was developed for users to communicate anonymously and privately over the dark web.<ref>{{cite web |url=https://darkwebnews.com/anonymity-tools/tor/introducing-onionchat-first-anonymous-web-chat-service-tor/ |title=Introducing OnionChat, The First Anonymous Web Chat Service For Tor |date=2018-05-27 |accessdate=2018-12-11 }}</ref> OnionChat is the first anonymous web chat service for Tor that does not use JavaScript. Malicious JavaScript inserted into darknet sites can leave users vulnerable to tracking and private information leaks. In April of 2012, Higinio O. Ochoa III, a hacker that goes by the w0rmer, was charged by the FBI with hacking into US law enforcement agencies and releasing phone numbers and home addresses of police officers.<ref>{{cite web |url=https://gizmodo.com/5901430/these-breasts-nailed-anonymous-hacker-in-fbi-case |title=These Breasts Nailed a Hacker For the FBI |last=Diaz |first=Jesus |date=2012-04-12 |accessdate=2018-12-11 }}</ref> Ochoa posted pictures of his girlfriend on sites that he had hacked as a digital signature, indicating that he had exposed private information. The FBI was able to extract metadata contained in the JavaScript used to post the pictures, matching the GPS coordinates where the pictures were taken to Melbourne, Victoria, Australia. Similar concerns have been raised for chat room and email services that use JavaScript, leaving users prone to information leaks and real time tracking. ===Dead Man Zero=== Dead Man Zero is a darknet site that allows whistleblowers to set up automatic releases of information in the case that they die, get jailed, or get injured. The site charges around 0.3 Bitcoin to provide users with a digital switch that is linked to encrypted files in a cloud storage service. The site relies on these external cloud storage services so that they do not have to upkeep their own file servers, which may be subject to targeting. The creators of Dead Man Zero built the site in response to [[w:Global surveillance disclosures (2013–present)| NSA scandals]], claiming that "there should be consequences if you are hurt, jailed, or even killed for trying to render a genuine and risky service to our free society." As of September 22, 2014, over 400 archives of encrypted files had been uploaded, with 17 pending release within the next 24 hours unless their owners logged in.<ref>{{cite web |url=https://motherboard.vice.com/en_us/article/wnjz7m/a-deep-web-service-will-leak-your-documents-if-the-government-murders-you |title=A Deep Web Service Will Leak Your Documents If the Government Murders You |last=Cox |first=Joseph |date=2014-09-22 |accessdate=2018-12-11 }}</ref> ===Further Work=== Future editors might consider renaming this page from "The Deep Web" to "The Dark Web" to better reflect its focus. The case studies section could also be retitled "Case Studies as Sociotechnical Contests" to make the analytical framing explicit. =References= <references/> {{BookCat}} iz3jib0nmgubzp2idm4ka4yzbkyn2tp 4634117 4634084 2026-05-04T16:39:07Z ~2026-27084-07 3581217 Added a social dynamic and trust in systems part 4634117 wikitext text/x-wiki <b>The Deep Web</b> (also referred to as <b>The Hidden Web</b> and <b>The Invisible Web</b>) is a collection of non-indexed web content. The deep web is often confused with the term "[[w:Dark Web|dark web]]", the darknet networks that require special tools and authorizations to access. The dark web is a subset of the deep web, as the two fulfill separate purposes. Both are separate from the "surface web", web pages openly accessible to anyone. [[w:Hypertext Transfer Protocol| HTTP]] form hide content on the deep web <Ref>{{cite web|url=|title=How Do You Want Me to Do It? Does It Have to Look like an Accident? – an Assassin Selling a Hit on the Net; Revealed Inside the Deep Web|newspaper=[[Sunday Mail (Scotland)|Sunday Mail]] |date=June 8, 2014 |first=Sam |last=Shedden |accessdate=December 9, 2018}}</ref> that [[w:Web indexing| web crawlers]] cannot access nor index. This secures data from the public. A login page can hide information from unauthorized users. With most of the inaccessible deep web being dedicated to business transactions and database storage with limited widespread social impact, this page will focus on the dark web with respects to anonymity, privacy, and security. =The Dark Web= People can access the dark web through either onion routing or garlic routing. Onion routing and garlic routing are most commonly employed by the Tor and I2P projects, respectively. The Tor Project has a larger user base. There are several differences between the two projects.<ref>https://geti2p.net/en/comparison/tor</ref> While originally developed for government and military communications, dark web use has expanded to civilians, journalists, law enforcers, activists, business executives, and professionals.<ref name="TorUsers">{{cite web |url=https://www.torproject.org/about/torusers |title=Who uses Tor? |publisher=The Tor Project |accessdate=2018-12-09 }}</ref> ==The Onion Router Project== [[File:Tor-logo-2011-flat.svg|thumb|The Tor Project logo]] The Onion Router (Tor) Project<ref name=":0">https://www.torproject.org/index.html.en</ref> is an open-source volunteer-driven project with the agenda of improving the privacy and security of people on the Internet.<ref>{{cite web |url=https://www.torproject.org/about/overview |title=Tor Project: Overview |publisher=The Tor Project |accessdate=2018-12-08 }}</ref> Its Tor browser software protects users by bouncing their communications around a distributed network of relays run by volunteers around the world. The software is a modified Mozilla Firefox web browser that can access darknet [[w:.onion|.onion domains]] as well as surface web domains. ==The Invisible Internet Project== [[File:I2P logo.svg|thumb|The I2P logo]] The Invisible Internet (I2P) Project<ref>https://geti2p.net/en/is</ref> an open-source anonymous overlay network that relies on bouncing encrypted messages around numerous one-way tunnels.<ref name=":1">{{cite web |url=https://geti2p.net/en/about/intro |title=Intro |work=The Invisible Internet Project |accessdate=2018-12-10 }}</ref> Instead of the Tor's .onion sites, the I2P browser features its own .i2p eepsites. Its browser can only access darknet domains within the I2P network.<ref>{{cite web |url=https://www.comparitech.com/blog/vpn-privacy/how-to-access-the-deep-web-and-darknet/ |title=Step by step guide to safely accessing the dark net and deep web |last=Bischoff |first=Paul |work=VPN & Privacy |publisher=Comparitech |date=2018-09-12 |accessdate=2018-12-10 }}</ref> ==Peer-to-Peer Networks== The dark web uses a peer-to-peer network. It differs from the conventional client-server model since there are no designated servers. The network's infrastructure, processing power, and storage comes from the computers, also called nodes, on the network. They function as servers and routers. Tor<ref name=":2">https://www.torproject.org/docs/documentation.html.en</ref> uses standard internet communication protocol, which allows any computer to join the network. The list of Tor relays at any moment is public. A user's Tor client facilitates the routing process to provide security, privacy, and anonymity. The client retrieves the list of active relays, generates a random path, and then adds additional overhead layers to the data packet for each node on the path. The computers at each node can only access their layer, which tells them the location of the next relay. As a result, a relay node does not know the end destination of the data, nor can it see the data. The last node, called exit node, delivers the data packet to the end destination. The network contains many features and vulnerabilities such as eavesdropping, protocol sabotage, and IP reveals. =Participants= Internet service providers have sold their customers' browsing records.<ref>{{cite news |last=Blodget |first=Henry |url=https://seekingalpha.com/article/29449-compete-ceo-isps-sell-clickstreams-for-5-a-month |title=Compete CEO: ISPs Sell Clickstreams For $5 A Month |work=Seeking Alpha |date=2007-03-13 |accessdate=2018-12-11 }}</ref> Participants who care about their online privacy can communicate and research without unwanted surveillance. Darknet softwares hide peoples' identities and web traffic while browsing. ==Governments and Militaries== Governments and militaries need private untraceable communications. Originally designed by the US government for military communications, onion routing's original purpose was to distribute robust messages through centralized server sites.<ref name="TorUsers" /> By routing messages through multiple encrypted layers, they can protect intelligence operations from interception, traffic analysis, or infrastructure shutdown. Beyond defense, governments also use the dark web for law enforcement and intelligence gathering, such as infiltrating criminal networks and conducting undercover operations. However, similar tools can also be used for domestic surveillance and control, including monitoring dissidents or restricting information, showing how the same technology can serve both security and authoritarian purposes. ==Activists and Whistleblowers== Under government censorships in countries like China,<ref>{{cite journal |title=Race to the Bottom: Corporate Complicity in Chinese Internet Censorship |journal=Human Rights Watch |date=2006-08 |volume=18 |issue=8 |url=https://www.hrw.org/reports/2006/china0806/china0806web.pdf |format=PDF |accessdate=2018-12-10 }}</ref> activists and whistleblowers need protections and anonymity to protect themselves. Readers can evade national firewalls to research global censored and/or controversial topics without risk of persecution.<ref name="TorUsers" /> Whistleblower submission systems such as SecureDrop<ref>https://securedrop.org/</ref> allow media organizations to securely accept documents from anonymous sources.<ref>{{cite web |url=https://securedrop.org/ |title=SecureDrop |accessdate=2018-12-10 }}</ref> Journalists can access the dark web to write about local events and social reforms that would otherwise be censored.<ref name="TorUsers" /> However, the anonymity provided for whistleblowers can complicate credibility and accountability, as sources are harder to verify. This highlights an important tension as the dark web enables free expression and broad information access, but introduces challenges in trust and verification. ==Illicit Actors== Illicit actors include cybercriminals, black-market vendors, and extremist/terrorist groups, all drawn to the dark web for its core features of anonymity and decentralization, allowing them to operate outside traditional legal and regulatory systems, reducing the risk of identification and prosecution from authorities. Compared to the surface web, the dark web offers a far more secure environment for sensitive communication and coordination. Moreover, trading cryptocurrencies over the dark web allow these groups and individuals to negotiate and transfer large amounts of funds without detection, allowing them to operate outside traditional financial oversight, further supporting their operations. ==General Privacy Users== A majority of dark web users are not malicious, but rather privacy-conscious individuals who value anonymity and protection from digital tracing. These users include everyday citizens who wish to browse the internet, communicate, or access information without being monitored by corporations such as their internet service providers or big tech companies. Unlike activists or whistleblowers, privacy users use of the dark web is typically not politically motivated, but instead driven by concerns over personal data privacy, targeted advertising, and online profiling. The strong association of the dark web with illicit activity often stigmatizes these users, creating a tension between legitimate privacy-seeking behavior and public perceptions of digital anonymity as suspicious and criminal. ==Infrastructure Builders== Infrastructure builders include developers, researchers, and organizations that design, maintain, and extend the technical systems that hold up the dark web. This ranges vastly from core anonymity networks like Tor to platforms, marketplaces, communication tools, and privacy-enhancing applications built on top of them. These builders are often motivated by core dark web values such as privacy, decentralization, and open access to information, aiming to create systems that resist surveillance and centralized control. However, they typically do not control how their technologies are ultimately used and as a result, tools intended to support privacy and free expression also enable illicit activities, highlighting a tension between design intentions and real-world use. =Case Studies= ==Darknet Markets== Darknet markets and communications platforms do not simply pit technology against law enforcement - they are arenas where competing social actors content control, trust, and legitimacy. The cases below, spanning drug markets, financial whistleblowing, and AI, each illustrate how the dark web's conflicts are fundamentally about who sets the rules when there is no central authority. ===Silk Road=== [[File:Silk Road Seized.jpg|thumb|Screenshot of the Silk Road shutdown]] [[w:Silk Road (marketplace)| Silk Road]] was an online black market marketplace for drugs and other illegal goods founded by [[w:Ross Ulbricht| Ross Ulbricht]] who used the pseudonym "Dread Pirate Roberts".<ref>{{cite web |url=https://www.engadget.com/2015/02/08/silk-road-trial-lessons/ |title=Anonymity is dead and other lessons from the Silk Road trial |last=Lee |first=Nicole |publisher=Engadget |date=2015-02-08 |accessdate=2018-12-09 }}</ref> Ulbricht's explicit goal was to build a free market where drug use was treated as a victimless personal choice, bypassing violet middlemen. To make that work without institutional backing, Silk Road layered ratings, escrow systems, and buyer feedback on top of [[wikipedia:Tor_(network)|Tor's]] anonymity - technology substituting for the social trust that ordinarily requires knowing someone in person. Buyers could purchase drugs with untraceable [[w:Bitcoin| Bitcoin]] transactions, and have them delivered by the postal service, an unwitting participant. In June 2013, FBI agents identified Silk Road's true server location through a software flaw, and Ulbricht was arrested.<ref>{{cite web |url=https://www.wired.com/2014/09/fbi-silk-road-hacking-question/ |title=FBI's Story of Finding Silk Road's Server Sounds a Lot Like Hacking |last=Greenberg |first=Andy |work=Security |publisher=Wired |date=2014-09-08 |accessdate=2018-12-09 }}</ref> Despite having no prior criminal record, he was sentenced to double life plus 40 years without parole. The severity of the sentence was widely debated: proportionate justice, or a strategic deterrent to discourage future operators?<ref>{{cite web |url=https://freeross.org/1-page-overview/ |title=1-page Overview |work=One-page Overview |publisher=Ross Ulbricht Defense Fund |accessdate=2018-12-10 }}</ref> That question was reopened in January 2025, when President Trump pardoned Ulbricht, reigniting debate about how states should respond to darknet markets.<ref>{{cite web |url=https://www.npr.org/2025/01/21/nx-s1-5270051/trump-pardons-dark-web-marketplace-creator-ross-ulbricht |title=Trump pardons Ross Ulbricht, creator of the Silk Road dark web marketplace|last=McLaughlin |first=Jenna |publisher=NPR |date=2025-01-21 |accessdate=2025-04-22 }}</ref> ===AlphaBay=== [[File:Alphabay-forfeiture-notice-screenshot-2017-05-12.png|thumb|AlphaBay forfeiture notice screenshot|alt=Alphabay-forfeiture-notice-screenshot-2017-05-12.png]] Canadian citizen Alexandre Cazes launched [[w:AlphaBay| AlphaBay]] in September 2014,<ref>{{cite news |first=Django |url=https://darkwebnews.com/darkwebmarkets/alphabay/ |title=AlphaBay |work=Darkweb News |publisher=Dark Web News Publication |date=2018-11-12 |accessdate=2018-12-11 }}</ref> and by July 2017 it had grown to ten times the size of the Silk Road by expanding beyond drugs into stolen corporate data, credentials, and financial records - making businesses unwitting victims alongside individual users. Cazes relocated to Thailand to operate the market and displayed his wealth publicly on social media, lapses that contributed to his arrest. But the most consequential innovcation in AlphaBay's takedown was the enforcement strategy surrounding it. As part of [[wikipedia:Operation_Bayonet_(darknet)|Operation Bayonet,]] the Dutch National Police secretly seized and continued operating the competing darknet market [[wikipedia:Hansa_(market)|Hansa]] in the weeks before AlphaBay was shut down.<ref name="Bayonet">{{cite news |last=Greenberg |first=Andy |url=https://www.wired.com/story/hansa-dutch-police-sting-operation/ |title=Operation Bayonet |work=Wired |location=New York |publisher=Wired Magazine |date=2018-03-08 |accessdate=2018-12-11 }}</ref> When AlphaBay fell and users fled to what they believed was a safe alternative, they walked directly into a law enforcement honeypot. The FBI and DEA's goal was not merely to close one market but to destroy user confidence in the darknet markets as a category. The operation succeeded not because authorities broke the encryption, but because they understood the ecosystem's social dynamics - displacement behavior, trust migration, and platform loyalty - better than the users themselves did. Thai authorities found Cazes dead in his cell days after his arrest and suspect suicide. ==Whistleblowing== Whistleblowing on the dark web centers on control over sensitive information rather than economic exchange. Unlike darknet markets, which rely on pricing, reputation, and cryptocurrency transactions, whistleblowing platforms are structure around trust, credibility, and the safe transfer of information between anonymous sources and journalists. The case below demonstrates how anonymity reshapes the relationship between individuals, institutions, and the public by enabling the disclosure of information that would otherwise remain hidden. === "John Doe" and the Panama Papers === [[File:Countries implicated in the Panama Papers.svg|thumb|Countries implicated in the Panama Papers leak]] Not all dark web activity involves markets. In 2015, an anonymous source using the pseudonym "John Doe" contacted journalists at the German newspaper ''Süddeutsche Zeitung'' through encrypted, anonymous channels and offered access to internal documents from the Panamanian law firm Mossack Fonseca.<ref>{{cite web |url=https://www.icij.org/investigations/panama-papers/the-story-that-rocked-the-world-ten-years-of-the-panama-papers-part-1/ |title=The story that rocked the world: Ten years of the Panama Papers, part 1 |last=Mauriello |first=Tracie |publisher=ICIJ |date=2026-03-31 |accessdate=2025-04-22 }}</ref> The whistleblower insisted on communicating exclusively over encrypted channels and refused any face-to-face contact, stating that their lift was in danger. The resulting leak - over 11.5 million documents exposing the offshore financial networks of politicians, executives, and celebrities worldwide - become known as the [[wikipedia:Panama_Papers|Panama Papers]] and triggered investigations in more than 80 countries. Without the ability to contact journalists anonymously, the source would have faced near-certain legal retaliation. The case surfaces a tension that runs through the entire dark web; the same infrastructure that enables criminal markets also enables accountability journalism. The Panama Papers strengthened financial transparency laws, increased regulation of offshore accounts, and expanded international cooperation on tax enforcement - while simultaneously legitimizing anonymous communication tools as instruments of the public interest. ==Artificial Intelligence== The emergence of large language models (LLMs), which rose to prominence in the early 2020s, has introduced a new dimension to the dark web: the automation and amplification of technical capability. Unlike markets or whistleblowing platforms, which mainly focus on exchange and the flow of information, AI systems reshape what users are able to do by lowering the skill barrier for complex tasks. The case below highlights how the integration of AI into the dark web transforms it from a space of coordination into a space of on-demand malicious capability generation, raising questions about control, responsibility, and the scalability of harm. === DIG AI === The dark web's sociotechnical contests have expanded into [[wikipedia:Artificial_intelligence|artificial intelligence]]. In September 2025, DIG AI launched as a [[wikipedia:Tor_(network)|Tor]]-hosted [[wikipedia:Large_language_model|large language model]] built on open-weight models that were explicitly fine-tuned to operate without the content restrictions that mainstream AI systems enforce.<ref>{{cite web |url=https://www.resecurity.com/blog/article/dig-ai-uncensored-darknet-ai-assistant-at-the-service-of-criminals-and-terrorists |title=DIG AI: Uncensored Darknet AI Assistant at the Service of Criminals and Terrorists |publisher=Resecurity |date=2025-12-18 |accessdate=2025-04-22 }}</ref> While mainstream surface web LLMs like [[wikipedia:ChatGPT|ChatGPT]] and [[wikipedia:Claude_(language_model)|Claude]] deliberately decline requests for phishing emails, weapons instructions, or malicious code, DIG AI fulfills them. As a result, criminal capability becomes significantly more accessible. Tasks that previously required hiring skilled technical specialists, such as hacking a website, can now be performed directly by non-technical users through simple prompts to the un-restricted LLM. The governance vacuum is striking: AI companies whose models were appropriated can only file threat reports; cybersecurity firms can monitor DIG AI but cannot remove it; no internal authority has jurisdiction over a Tor-hosted service. DIG AI extends a central pattern: each time enforcement closes one avenue, the ecosystem reconstitutes around a new technology. The question is not only how to respond to one uncensored model, but what it means for the dark web when AI-powered capability becomes as accessible as a drug listing. This development also reveals a deeper tension between governments and AI capabilities. While states actively pursue advanced and potentially unrestricted AI systems through partnerships with private companies, they simultaneously seek to restrict public access to those same capabilities. However, the dark web functions as the critical infrastructure that undermines this control. By enabling anonymous hosting, distribution, and access, it allows tools like DIG AI to exist outside traditional regulatory and corporate boundaries. The implication is a shift in the balance of power: while governments attempt to centralize access to high-capability AI, the dark web enables capability diffusion, redistributing these tools to a broader set of actors. This raises a fundamental question: does restricting such technologies enhance security, or does it simply incentivize their migration to decentralized, less controllable environments? ==Darknet Communications== ===Facebook=== [[w:Facebook| Facebook]] <ref>{{cite news |last=Greenberg |first=Andy |url=https://www.wired.com/2014/10/facebook-tor-dark-site/ |title=Why Facebook Just Launched Its Own 'Dark Web' Site |work=Wired |location=New York |publisher=Wired Magazine |date=2014-10-31 |accessdate=2018-12-11 }}</ref> launched [[w:facebookcorewwwi.onion| its services on the dark web]] in 2014 allowing users to circumvent any firewalls or censorship. The launch aligns with Facebook’s mission to connect people. Once the user reaches Facebook they can use services normally. Facebook used to flag excessive routing, like Tor, as suspicious behavior and even denied services. Android support and dark web client plug-ins followed. Dark web traffic to Facebook spiked temporarily near the end of 2015. Political conflict and civil unrest caused the Bangladesh government to ban Facebook and other social media services in November of 2015. However, they could not shut down nor block the Tor network. This rendered the ban ineffective. Most bans use IP, but Tor conceals the IP. Over 1 million users connect to Facebook monthly through Tor<ref>{{cite news |last=Wong |first=Joon |url=https://qz.com/667880/a-million-people-now-access-facebook-on-the-dark-web-every-month/ |title=A million people now access Facebook on the “dark web” every month |work=Quartsz |location=New York |publisher=Quartz |date=2016-04-22 |accessdate=2018-12-11 }}</ref>. Alec Muffett, a Facebook engineer wrote, “It’s important to us to provide methods for people to use our services securely—particularly if they lack reliable methods to do so.” Security expert Runa Sandvik praised Facebook and expects other companies to do the same. ===Chat Rooms and JavaScript=== In early 2018, a chatroom called OnionChat was developed for users to communicate anonymously and privately over the dark web.<ref>{{cite web |url=https://darkwebnews.com/anonymity-tools/tor/introducing-onionchat-first-anonymous-web-chat-service-tor/ |title=Introducing OnionChat, The First Anonymous Web Chat Service For Tor |date=2018-05-27 |accessdate=2018-12-11 }}</ref> OnionChat is the first anonymous web chat service for Tor that does not use JavaScript. Malicious JavaScript inserted into darknet sites can leave users vulnerable to tracking and private information leaks. In April of 2012, Higinio O. Ochoa III, a hacker that goes by the w0rmer, was charged by the FBI with hacking into US law enforcement agencies and releasing phone numbers and home addresses of police officers.<ref>{{cite web |url=https://gizmodo.com/5901430/these-breasts-nailed-anonymous-hacker-in-fbi-case |title=These Breasts Nailed a Hacker For the FBI |last=Diaz |first=Jesus |date=2012-04-12 |accessdate=2018-12-11 }}</ref> Ochoa posted pictures of his girlfriend on sites that he had hacked as a digital signature, indicating that he had exposed private information. The FBI was able to extract metadata contained in the JavaScript used to post the pictures, matching the GPS coordinates where the pictures were taken to Melbourne, Victoria, Australia. Similar concerns have been raised for chat room and email services that use JavaScript, leaving users prone to information leaks and real time tracking. ===Dead Man Zero=== Dead Man Zero is a darknet site that allows whistleblowers to set up automatic releases of information in the case that they die, get jailed, or get injured. The site charges around 0.3 Bitcoin to provide users with a digital switch that is linked to encrypted files in a cloud storage service. The site relies on these external cloud storage services so that they do not have to upkeep their own file servers, which may be subject to targeting. The creators of Dead Man Zero built the site in response to [[w:Global surveillance disclosures (2013–present)| NSA scandals]], claiming that "there should be consequences if you are hurt, jailed, or even killed for trying to render a genuine and risky service to our free society." As of September 22, 2014, over 400 archives of encrypted files had been uploaded, with 17 pending release within the next 24 hours unless their owners logged in.<ref>{{cite web |url=https://motherboard.vice.com/en_us/article/wnjz7m/a-deep-web-service-will-leak-your-documents-if-the-government-murders-you |title=A Deep Web Service Will Leak Your Documents If the Government Murders You |last=Cox |first=Joseph |date=2014-09-22 |accessdate=2018-12-11 }}</ref> == Trust in Systems == The dark web has never been as anarchic as it seems from the outside; even early marketplaces like Silk Road developed surprisingly structured systems of governance. On Silk Road, users relied on escrow payments, detailed vendor reviews, and a ranking system that mirrored legitimate e-commerce platforms. Its founder, Ross Ulbricht, even enforced rules about what could be sold, banning certain types of harmful goods to maintain internal order. After Silk Road was shut down, successors like AlphaBay and Hansa Market expanded these systems with more sophisticated reputation metrics and security features. These examples show that governance on the dark web emerges through community-enforced norms and technical safeguards rather than formal law. At the same time, these systems are constantly strained by distrust and competing incentives. AlphaBay’s collapse in 2017, followed by the revelation that Hansa had been secretly controlled by law enforcement during the Operation Bayonet, highlighted how fragile trust can be. Users who believed they were operating in a secure, anonymous marketplace suddenly found their data exposed. Exit scams are another recurring tension. Platforms like Evolution Marketplace vanished overnight with millions in escrowed funds, reinforcing the constant fear that even “trusted” administrators might betray users. Meanwhile, vendors compete for reputation but sometimes engage in selective scamming, and buyers may attempt fraud themselves, creating a system where no participant fully trusts another. === Current Social Dynamic === More recently, the ecosystem has shifted away from large centralized markets toward smaller, more fragmented networks. After repeated takedowns, activity has migrated to encrypted platforms like Telegram and decentralized forums, where invite-only access replaces open registration. Some communities experiment with multi-signature escrow and cross-platform reputation systems to reduce reliance on any single authority. The shutdown of Hydra Market in 2022 further accelerated this trend, pushing users into more distributed and harder-to-monitor spaces. Today, the dark web looks less like a marketplace ecosystem and more like a patchwork of semi-private networks, where governance is constantly renegotiated and trust is both the most valuable currency and the most fragile weakness. == Further Work == Future editors might consider renaming this page from "The Deep Web" to "The Dark Web" to better reflect its focus. The case studies section could also be retitled "Case Studies as Sociotechnical Contests" to make the analytical framing explicit. =References= <references/> {{BookCat}} 1c6t7lzv5k40z9p8r4sul2igzr179ue 0 410413 4634068 3930917 2026-05-04T12:27:05Z Jcb 90773 4634068 wikitext text/x-wiki ==Cancer Epidemiology== • '''[http://tcr.cph.ntu.edu.tw/main.php?Page=N2 Taiwan Cancer Registry Website]''' • '''Chiang et al. (2016) Incidence and survival of adult cancer patients in Taiwan, 2002–2012. J Formos Med Assoc. 2016 Dec;115(12):1076-1088. ({{PMID|26786251}})''' • A total of 105,832 people diagnosed with various types of cancer in 2016 in Taiwan • Estimated a new cancer case every four minutes and 58 seconds • Median age for cancer diagnosis about 63 years of age '''• [[Radiation Oncology/Epidemiology/Cancer Incidence in Taiwan|Cancer Incidence]] (2016) in Taiwan:''' (1) Colon cancer (2) Lung cancer (3) Female breast cancer (4) Liver cancer (5) Oral cavity cancer (including oropharyngeal cancer, hypopharyngeal cancer, etc.) (6) Prostate cancer (7) Thyroid cancer (8) Stomach cancer (9) Skin cancer (10) Esophageal cancer • '''[[/Taiwan Cancer Registry (Male)/|Male Cancer Incidence]] (2016) in Taiwan:''' (1) Colon cancer (2) Liver cancer (3) Lung cancer (4) Oral cavity cancer (including oropharyngeal cancer, hypopharyngeal cancer, etc.) (5) Prostate cancer (6) Esophageal cancer (7) Gastric cancer (8) Skin cancer (9) Bladder cancer (10) Leukemia • '''[[/Taiwan Cancer Registry (Female)/|Female Cancer Incidence]] (2016) in Taiwan:''' (1) Breast cancer (2) Colon cancer (3) Lung cancer (4) Thyroid cancer (5) Liver cancer (6) Endometrial cancer (7) Ovarian cancer (8) Cervical cancer (9) Skin cancer (10) Gastric cancer • '''[[/Childhood Cancer (Taiwan)/|Childhood Cancer Incidence]] ({{PMID|25599927}}) in Taiwan:''' (1) Leukemia (2) Brain tumor (3) Lymphoma (4) Neuroblastoma (5) Germ cell tumor (6) Osteosarcoma (7) Soft tissue sarcoma (8) Wilms' tumor (9) Hepatic tumor (10) Retinoblatoma • '''[[Radiation Oncology/Epidemiolgy/Cancer Death in Taiwan|The 10 leading causes of cancer death in 2016 in Taiwan]]''' {{BookCat}} ==Radiation Oncology== *[[/Therapeutic Radiology and Oncology (TRO)|/Therapeutic Radiology and Oncology]] **Therapeutic Radiology and Oncology (Ther Radiol Oncol; TRO; 2616-2768), launched in September 2017 and originated in 1994 and known in the field as the Blue Journal, publishes papers describing original research, case reports and clinical investigations related to radiation oncology **This includes clinical radiotherapy, radiobiology, chemotherapy, immunotherapy, hyperthermia, tumor biology, experimental therapeutics and clinical oncology. It also covers fields of medical physics, radiology, nursing care, education, technology, health information and health policy as it relates to radiology and oncology *[[/Taiwan Society for Therapeutic Radiology and Oncology (TASTRO)|/Taiwan Society for Therapeutic Radiology and Oncology]] *[[/Taiwan Society of Neutron Capture Therapy (TSNCT)|/Taiwan Society of Neutron Capture Therapy]] *[[/Chinese Society of Medical Physics, Taipei|/Chinese Society of Medical Physics]] rsxb5cwyb8o0k72b50zbyk5s3vb6umw 0 417636 4634104 4623556 2026-05-04T15:46:49Z Tyoyafud 6233 /* Proper Nouns */ 4634104 wikitext text/x-wiki <noinclude>{{status|100%}}</noinclude> == Noun Types == : Nouns in Mirad can be distinguished in the following 7 ways: ::# '''''common''''' vs. '''''proper''''' ::# '''''concrete''''' vs. '''''abstract''''' ::# '''''countable''''' vs. '''''mass''''' ::# '''''gender-neutral''''' vs. '''''masculine/feminine''''' ::# '''''singular''''' vs. '''''plural''''' ::# '''''animate''''' vs. '''''inanimate''''' ::# '''''full form''''' vs. '''''acronym/abbreviation''''' :::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Common vs. Proper Nouns |- ! Common !! Proper |- | '''tam'''....''house'' || '''Emer'''....''Venus'' |- | '''yagsim'''....''bench'' || '''Ferom'''....''France'' |- | '''dyes'''....''book'' || '''Notre Dame'''...''Notre Dame'' |- | '''tej'''....''life'' || '''Tot'''....''God'' |} :::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Concrete vs. Abstract Nouns |- ! Concrete !! Abstract |- | '''tab'''....''body'' || '''ifon'''....''love'' |- | '''mil'''....''water'' || '''oyman'''....''coolness'' |- | '''deuz'''....''song'' || '''deuzen'''....''singing'' |} : Abstract nouns include '''''gerunds''''', i.e. nouns which are nominalized derivations of verbs like '''deuzen'''....''singing'' < '''deuzer'''....''to sing'' or '''osexen'''....''destruction'' < '''osexer'''....''to destroy''. Infinitives like ''deuzer''....'''to sing''' are also considered abstract nouns. :::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Countable vs. Mass Nouns |- ! Countable !! Mass |- | '''pat'''....''bird'' || '''pattel'''....''bird food'' |- | '''patayebi'''....''feathers'' || '''patayebyan'''....''plumage'' |- | '''megi'''....''rocks'' || '''mil'''....''water'' |} : In native Mirad, all '''''common''''' nouns in their '''''singular''''' dictionary lookup form end in a consonant. Proper nouns sometimes end in a vowel, such as '''Roma'''....''Rome''. Plural common countable nouns end in the vowel ''i'' ('''pat'''....''bird'' ⇒ '''pat<u>i</u>'''....''birds''). :::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Gender-neutral vs. Gendered |- ! Gender-neutral !! Feminine !! Masculine |- | '''tob'''....''human being'' || '''toyb'''....''woman'' || '''twob'''....''man'' |- | '''edeb'''....''monarch'' || '''edeyb'''....''queen'' || '''edweb'''....''king'' |- | '''ted'''....''parent'' || '''teyd'''....''mother'' || '''twed'''....''father'' |} :::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Singular vs. Plural Nouns |- ! Singular !! Plural |- | '''dom'''....''city'' || '''domi'''....''cities'' |- | '''gon'''....''part'' || '''goni'''....''parts'' |- | '''jub'''....''day'' || '''jubi'''....''days'' |} :::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Inanimate vs. Animate Nouns |- ! Inanimate !! Animate |- | '''mam'''....''sky'' || '''pot'''....''animal'' |- | '''tom'''....''building'' || '''aot'''....''person'' |- | '''job'''....''time'' || '''tobet'''....''child'' |} :::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Full form vs. Acronym ! Full Form !! Acronym/Abbreviation |- | '''Anxwa Doobi'''....''United Nations'' || '''AD'''....''UN'' |- | '''Mir Nunuien Xob'''....''World Trade Organization'' || '''MNX'''....''WTO'' |- | '''iza makilp'''....''direct current'' || '''i.m'''....''d.c.'' |} : The above noun type distinctions are relevant in various parts of Mirad's grammar. == Pluralization of Common Nouns == : A '''''singular countable common noun''''' always ends in a consonant and is made plural by suffixing the pluralizing marker '''-i'''. So, the plural of '''pur'''....''car'' is '''pur<u>i</u>'''....''cars''. In noun phrases, for example, where a noun is modified by an article and adjective, only the noun is pluralized, that is, there is no agreement across word boundaries as in many European languages ('''la belle fleur''' <big>→</big>'''les belles fleurs'''). The plural suffix '''-i''' is the only way nouns in Mirad are inflected. All other changes to nouns are derivational in nature, eg. genderization, augmentation, diminution, capitalization, etc. : {| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Pluralization of Nouns |- ! Singular !! Plural |- | '''tam'''....''house''|| '''tam<u>i</u>'''....''houses'' |- | '''toyb'''....''woman'' || '''toyb<u>i</u>'''....''women'' |- | '''tej'''....''life'' || '''tej<u>i</u>'''....''lives'' |- | '''ha via dom'''....''the beautiful city'' || '''ha via dom<u>i</u>'''....''the beautiful cities'' |} == Modifying Nouns with the Definite Article == : In Mirad, there is only a single noun-modifying article, the invariable definite article '''ha''' (''the''). There is no '''''indefinite article''''' like English ''a / an''. A noun is considered indefinite or general unless modified by the definite article '''ha''' (which in reality is a '''''definite deictic determiner''''', discussed with other deictic determiners in the later section on [[Mirad Grammar/Determiners#Deictic Determiners]]). The definite article '''ha''' is positioned, as in English, before the noun and before any other adjectives or modifiers of that noun. It is invariable, in that it does not vary for gender, number, or case as in German or Spanish. The definite article acts like its counterpart in English, as shown in the following chart: : {| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Use of the Definite Article |- ! Mirad !! English !! Specificity |- | '''tam''' || ''a house'' || indefinite, no article |- | '''<u>ha</u> tam''' || ''<u>the</u> house'' || definite |- | '''<u>ha</u> tami''' || ''<u>the</u> houses'' || definite, plural |- | '''tej''' || ''life'' || general, no article |- | '''fitejawa <u>tej</u>''' || ''<u>a life</u> well-lived'' || indefinite, no article |- | '''<u>ha</u> tej (...ho at bayse)''' || ''<u>the</u> life (... that I have)'' || specific |- | '''Ferad''' || ''French'' || language name, already specific, no article |- | '''Ivan''' || ''Ivan'' || person's name, no article |- | '''Ifliu <u>yivan</u>!''' || ''Cherish <u>freedom</u>'' || abstraction, no article |- | '''<u>Ha</u> yivani ho yat ifie.''' || ''<u>The</u> freedoms that we enjoy.'' || abstraction specified |- | '''Yata <u>yivani</u>...''' || ''Our <u>freedoms</u>...'' || abstraction specified with possessive pronoun, no article |} : Speakers of French and other European languages should take note that general concepts like ''love'', ''life'', ''freedom'' do not employ the definite article unless they refer to a specific instance, such as in the phrases ''the love that dare not speak its name'' or ''the life well-lived'' or ''the freedoms we possess''. The names of languages and countries are also considered already specific, and so as in English, they do not take a definite article as they might in some European languages. Names of persons do not take the definite article as they do in modern Greek, unless in a phrase like "the Ivan I once knew." == Proper Nouns == : Proper nouns, such as names of people, places, languages, etc., are capitalized as in English. The formation of country names and languages is discussed in [[Mirad_Grammar#Countries_of_the_World|Countries of the World]] and [[Mirad_Grammar#Languages of the World|Languages of the World]]. It can be said here, though, that country names end in '''-m'''; the inhabitants of those places end in '''-t''' or pl. '''-ti'''; and the languages they speak end in '''-d'''. Language names are capitalized, eg. '''At tixe Ferad.''' (''I study French.''). In fact, this is the case for all parts of speech derived from a proper name, eg. '''Usama tel Feramxweye.''' ''American food is being Frenchified.''. French speakers beware; this is not like in French. And German speakers beware, too! Not all nouns are capitalized; only ones that are proper, such as names of people, companies, languages, countries, etc. : Names of people, cities, etc. are spelled in Mirad to best reflect the foreign pronunciation, but also to remain recognizable. For example: ::* '''Xikago'''....''Chicago'' ::* '''Paris'''....''Paris'' ::* '''Munxen'''....''Munich/M&uuml;nchen'' ::* '''Beijing'''....''Beijing'' ::* '''Nu York'''....''New York'' ::* '''Nu Orlinz'''....''New Orleans'' ::* '''Xampanya'''....''Champagne'' ::* '''Mehiko Dom'''....''Mexico City'' ::* '''Waxington'''....''Washington'' ::* '''Seol'''....''Seoul'' ::* '''Xeykspir'''....''Shakespeare'' : An inhabitant of a city is formed by adding '''-t''' or '''-at''' to the name, depending on whether it ends in a vowel or consonant, respectively, eg. '''Parisat'''....''a Parisian'' or '''Waxingtonati'''....''Washingtonians''. ''Chicago's main newspaper'' is expressed in Mirad as '''ha agala jubdindref bi Xikago'''. The English preposition ''in'' used before cities, states, and countries is translated by '''be''' in Mirad, eg. '''At tambese <u>be</u> Paris.'''....''I live <u>in</u> Paris.'' or '''Iyt yexe be Deum.'''....''She works in Germany.'' == Noun Modifiers: Placement and Agreement == : Nouns can be modified by various qualitative, quantitative, and deictic adjectives, which all precede the noun. These modifiers come in the same order as in English. There is no gender or number agreement between the modifiers and the noun, except that numeric adjectives, such as '''ewa'''....''two'' naturally are followed by a noun in the plural number. :{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Noun Modifiers |- ! Mirad !! English |- | '''ha <u>ewa</u> aga tami''' || ''the <u>two</u> big houses'' |- | '''<u>gla</u> ifxea taxi''' || ''<u>many</u> pleasant memories'' |- | '''hya <u>fia</u> tob''' || ''every <u>good</u> man'' |- | '''ha yaga <u>via</u> mepi''' || ''the long, <u>beautiful</u> roads'' |- | '''gra <u>vua</u> sexen''' || ''too much <u>ugly</u> construction'' |- | '''ata <u>aja</u> teji''' || ''my <u>past</u> lives'' |} == Noun Linkage == : Nouns can be ::# '''''linked''''' with a preposition or conjunction, where the prepositional/conjunctional phrase follows the head noun, or ::# '''''juxtaposed''''', where the modifier noun is separated by a space and comes before the head noun, or ::# '''''compounded''''', where the modifier noun is prefixed to a headword, or ::# '''''hyphenated''''', where two equal elements are joined by a hyphen. : Examples: ::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Noun Linkage |- ! Linkage Example !! Construction |- | '''Ivan <u>ay Maria</u>'''....''Ivan <u>and Maria</u>'' || nouns linked associatively by the conjunction '''ay''' (''and'') |- | '''ha tam <u>ey ha par</u>'''....''the house <u>or the car</u>'' || nouns linked associatively by the conjunction '''ey''' (''or'') |- | '''hyati <u>oy ha toybi</u>'''....''all <u>but the women</u>'' || nouns linked associatively by the conjunction '''or''' (''but'') |- | '''nyandras <u>boy eta dyun</u>'''....''a list <u>without your name</u>'' || nouns linked associatively by the preposition '''boy''' (''without'') |- |'''tej <u>bi nasuk</u>'''....''a life <u>of poverty</u>'' || nouns linked associatively by the preposition '''bi''' (''of'') |- | '''ha tam <u>bi Maria</u>''' ....''Mary&apos;s house (the house <u>of Mary</u>''|| nouns linked possessively by the preposition '''bi''' (''of'') |- | '''job <u>bi aga ivan</u>'''....''a time <u>of great joy</u>'' || nouns linked associatively by the preposition '''bi''' (''of'') |- | '''dyes <u>ayv ha Ea Mira Dropek</u>'''....''a book <u>about the Second World War</u>'' || nouns linked associatively by the preposition '''ayv''' (''about'') |- | '''dropek <u>jwabeni</u>'''....''war <u>preparations</u>'' || modifier noun '''dropek''' (''war'') juxtaposed with the head noun <u>'''jwabeni'''</u> (''preparations'') |- | '''dom <u>yuzpur</u>'''....''a city <u>bus</u>'' || modifier noun '''dom''' (''city'') juxtaposed with the head noun <u>'''yuzpur'''</u> (''bus'') |- | '''toj<u>ojfon</u>'''....''a death <u>wish</u>'' || modifier noun '''toj''' (''death'') compounded with the head noun '''<u>ojfon</u>''' (''wish'') |- | '''jogat<u>anyaf</u>'''....''youth <u>league</u>'' || modifier noun '''jogat''' (''youth'') compounded with the head noun '''<u>anyaf</u>''' (''league'') |- | '''maj-moj'''....''a day-and-night'' || two or more equal, opposed nouns hyphenated |} : The '''X bi Y''' prepositional construction must always be used for possession by a '''''named''''' person, eg. '''ha tam <u>bi</u> Sam''' (Sam's house = the house <u>of</u> Sam). The methods of noun linkage otherwise follow the English pattern in most all cases. Pronominal possession such as ''his car'' is discussed in the section on personal pronouns. The preposition '''bi'''....''of'' is used in partitive expressions like '''tilzyeb <u>bi</u> vifil'''....''a glass <u>of</u> wine'' (but: '''vifil tilzeb'''....''wine glass'', where ''wine'' modifies ''the glass'' associatively). More about this and other prepositions or conjunctions can be found in the section on [[Mirad Grammar/Prepositions]] or [[Mirad Grammar/Conjunctions]]. : Details on how noun vocabulary is derived appears in the section on [[Mirad Grammar/Vocabulary Formation]]. == Noun Derivational Affixes == : Nouns can be divided into: ::* '''''simple nouns''''' such as '''pur'''....''vehicle'' ::* '''''compound nouns''''' such as '''bixpur'''....''train'' < '''bix'''....''pull'' + '''pur'''....''vehicle'' ::* '''''hybrid nouns''''' such as '''vaod'''....''decision'' < '''va'''....''yes'' + '''vo'''....''no'' (hybridized to '''vao''') + '''d'''....''utterance'' ::* '''''derived nouns''''' such as '''fabyan'''....''forest'' < '''fab'''....''tree'' + '''-yan'''<br> a suffix meaning ''collection'' : Derived nouns can be formed by attaching nominal suffixes or prefixes to words or roots. A list of nominal suffixes to form derived nouns is shown in the following table. More can be read about noun derivation in the section on vocabulary-building. === Noun Suffixes === {{small/top}} :{| class="wikitable sortable" style="background:lightyellow" |+ Noun Derivational Suffixes |- valign=top ! Suffix !! Meaning !! Base Onto Which<br>Suffix Is Added !! Examples |- | '''-ag''' || big || noun || '''tam'''....''house'' → '''tam<u>ag</u>'''....''mansion''<br>'''tyal'''....''meal'' → '''tyal<u>ag</u>'''....''banquet''<br>'''tilar'''....''spoon'' → '''tilar<u>ag</u>'''....''ladle'' |- | -'''an''' || abstact quality<br> -ness<br> -hood, -ity || adjective stem ||'''vi<s>a</s>'''....''beautiful'' → '''vi<u>an</u>'''....''beauty''<br>'''yev<s>a</s>'''....''fair'' → '''yev<u>an</u>'''....''fairness, equity''<br>'''tob<s>a</s>'''....''human'' → '''tob<u>an</u>'''....''humanity, humanness, manhood'' |- | -'''ayg''' || big and cute || noun || '''tam'''....''house'' → '''tam<u>ayg</u>'''....''cozy mansion''<br>'''kapet'''....''dog'' → '''kapet<u>ayg</u>'''....''wolfie'' |- | -'''ambok''' || -itis, inflammation || noun || '''buixtaib'''....''tendon'' → '''buixtaib<u>ambok</u>'''....''tendonitis'' |- | -'''d''' || language<br>speech<br>utterance || adjective and other stems|| '''Enigem'''....''English'' → '''Enige<u>d</u>'''....''English (language)''<br>'''Mira'''....''of the world'' → '''Mirad'''....''Mirad (world speech)''<br>'''ekpe<s>t</s>'''....''horse'' →'''ekpe<u>d</u>'''....''neigh, whinny'' |- | -'''drun''' || -gram || noun stems || '''tiib'''....''heart'' → '''tiib<u>drun</u>'''....''cardiogram'' |- | -'''dra/i/ur''' || -graph || noun stems || '''am'''....''heat'' → '''am<u>drar</u>'''....''thermograph'' |- | -'''dren''' || -graphy || mostly noun stems || '''yib'''....''far'' → '''yib<u>dren</u>'''....''telegraphy'' |- | -'''ef''' || need of || various stems || '''tel'''....''food''→'''tel<u>ef</u>'''....''hunger''<br>'''ig<s>a</s>'''....''fast''→'''ig<u>ef</u>'''....''emergency''<br>'''til'''....''drink''→ '''til<u>ef</u>'''....''thirst'' |- | -'''en''' || present gerund<br> -ing<br> -tion<br> -ment || verb stem ||'''ifi-'''....''enjoy'' →'''ifi<u>en</u>'''....''enjoyment''<br>'''deuz-'''....''sing''→'''deuz<u>en</u>'''....''singing''<br>'''axl-'''....'''act''' → '''axl<u>en</u>'''....''acting'' |- | -'''eyn''' || present gerund<br> -tion<br> -ment || verb stem ||'''x-'''....''do'' →'''x<u>eyn</u>'''....''deed''<br>'''s-'''....''to be''→'''s<u>eyn</u>'''....''essence''<br>'''jaup-'''....'''preceed''' → '''jaup<u>eyn</u>'''....''precedent'' |- | -'''es''' || smaller counterpart thing || noun || '''tef'''....''hat''→ '''tef<u>es</u>''' cap<br>'''saun'''....''kind''→ '''saun<u>es</u>'''....''sample''<br>'''dreuz'''....''poem'' → '''deuz<u>es</u>'''....''stanza''<br>'''mek'''....''dust, powder''→'''mek<u>es</u>'''....''speck, grain'' |- | -'''et''' || smaller counterpart person || noun || '''twob'''....''man'' → '''twob<u>et</u>'''....''boy''<br>'''toyb'''....''woman''→ '''toyb<u>et</u>'''....''girl'' |- | -'''if''' || love of<br> -philia || noun || '''tel'''....''food'' → '''tel<u>if</u>'''....''gourmandise''<br>'''doab'''....''homeland'' → '''doab<u>if</u>'''....''patriotism''<br>'''dyes'''....''book'' → '''dyes<u>if</u>'''....''bibliophilia, love of books'' |- | -'''ig''' || quick || noun and verb stem || '''man'''....''light'' → '''man<u>ig</u>'''....''flash''<br>'''pyex'''....''stroke''→'''pyexig'''....''swat''<br>'''yopap-'''....''dive, fly down'' → '''yopap<u>ig</u>'''....''swoop'' |- | -'''im''' || room, chamber || various stems || '''fyadil-'''....''to pray'' →'''faydil<u>im</u>'''....''chapel''<br>'''magel-'''....''to cook'' → '''magel<u>im</u>'''....''kitchen''<br>'''tof-'''....''to dress'' → '''tof<u>im</u>'''....''dressing room'' |- | -'''in''' || doctrine, dogma, -ism || various stems || '''tot'''....''god'' → '''totin'''....''religion, theism''<br>'''otof<s>a</s>'''....''nude''→'''otof<u>in</u>'''....''nudism''<br>'''yufr-'''....'''terror''' → '''yufr<u>in</u>'''....''terrorism'' |- | -'''kyaoxar''' || -stat || noun stems || '''am'''....''heat'' → '''am<u>kyaoxar</u>'''....''thermostat'' |- | -'''n''' || abstract noun || various stems || '''ze'''....''in the middle of'' → '''zen'''....''center''<br>'''za'''....''in front of'' →'''za<u>n</u>'''....''face''<br>'''byi'''....''since, starting with'' → '''byi<u>n</u>'''....''source''<br>'''go'''....''less''→ '''go<u>n</u>'''....''part'' |- |-'''kunid''' || -hedron, sided volume || number prefixes || '''alen'''....''dodeca (twelve)'' → '''alenkunid'''....''dodecahedron'' |- | -'''am''' || house<br> building || various stems || '''nun-'''....''merchandise'' → '''nun<u>am</u>'''....''store''<br>'''til''' drink → '''til<u>am</u>'''....''bar, tavern''<br>'''fyadil-'''....''to pray'' → '''fyadil<u>am</u>'''....''church'' |- | -'''(e)m''' || place || various stems || '''duho-?''' what-?→ '''duho<u>m</u>?'''....''where''?<br>'''yex'''....''work'' → '''yex<u>em</u>'''....''worksite''<br>'''ab'''....''on, above'' → '''ab<u>em</u>'''....''top, surface''<br>'''ku<s>a</s>'''....''lateral''→'''ku<u>m</u>'''....''side'' |- | -'''um''' || compartment<br> booth || various stems || '''teuzibar'''....''telephone'' → '''teuzibar<u>um</u>'''....''telephone booth'' |- | -'''yem''' || enclosure, box || various stems || '''ekpet'''....''horse'' →'''ekpet<u>yem</u>'''....''corral''<br>'''b-'''....''put'' → '''b<u>yem</u>'''....''position'' |- | -'''ud''' || offspring, baby of || noun || '''ekpet'''....''horse''→'''ekpet<u>ud</u>'''....''foal'' |- | -'''wud''' || son of || noun || '''ekpet'''....''horse''→'''ekpet<u>wud</u>'''....''colt'' |- | -'''uyd''' || daughter of || noun || '''ekpet'''....''horse''→'''ekpet<u>uyd</u>'''....''filly'' |- | -'''og''' || little || noun || '''tab''' body→ '''tab<u>og</u>'''....''corpuscle''<br>'''ekpet'''....''horse'' → '''ekpet<u>og</u>'''....''pony''<br>'''tyal'''....''meal'' → '''tyal<u>og</u>'''....''snack''<br>'''golbun'''....''cut'' → '''golbun<u>og</u>'''....''cutlet'' |- | -'''oyg''' || little and cute || noun || '''tam'''....''house'' → '''tam<u>oyg</u>'''....''cottage''<br>'''gafapayt'''....''chicken'' →'''gafapayt<u>oyg</u>'''....''chickadee''<br>'''mimpar'''....''boat'' → '''mirpar<u>oyg</u>'''....''dingy'' |- | -'''nagar''' || ''-ometer'' || noun || '''am'''....''heat'' → '''am<u>nagar</u>'''....''thermometer'' |- | -'''ar''', '''-ir''', '''-ur''' || tool, machine, engine || usu. verb stem || '''p-'''....''to go''→ '''p<u>ur</u>'''....''car''<br>'''dr-'''....''to write'' → '''drar'''....''pencil''<br>'''gobl-'''....''to cut'' → '''gobl<u>ar</u>'''....''knife''<br>'''yaobl-'''....''to lift up and down'' → '''yaobl<u>ur</u>'''....''elevator, lift''<br>'''yaobl<u>ir</u>'''....''lift, crane''<br>'''dop'''....''military'' → '''dop<u>ar</u>'''....''gun''<br>'''dop<u>ur</u>'''....''machine gun''<br>'''dop<u>ir</u>'''....''artillery, cannon''<br> |- | -'''s''' || thing, object, the X one || adjective || '''aa''' first → '''aa<u>s</u>'''....''first one, first thing''<br>'''otwa'''....''unknown'' → '''otwa<u>s</u>'''....''mystery, an unknown''<br>'''tejea'''....''living'' → '''tejea<u>s</u>'''....''living thing'' |- | -'''(s)on''' || abstract thing<br> issue || various stems || '''if-'''....''to love''→'''if<u>on</u>'''....''love''<br>'''ov against'''→ '''ov<u>on</u>'''....''obstacle''<br> '''az<s>a</s>''' strong → '''az<u>on</u>'''....''force''<br>'''yik<s>a</s>'''....''difficult'' → '''yik<u>son</u>'''....''problem'' |- | -'''(s)un''' || object<br> thing<br> result of an action || various stems || '''vyu<s>a</s>'''....''dirty'' → '''vyu<u>n</u>'''....''spot''<br>'''tamb-'''....''settle'' →'''tambi<u>un</u>'''....''settlement''<br>'''gofr-''' ''shred'' → '''gofr<u>un</u>'''....''scrap, shred''<br>'''hyo'''....''not a single''→ '''hyo<u>sun</u>'''....''not a single thing'' |- | -'''t''' || person || adjective || '''ea''' second → '''eat'''....''second one, second person''<br>'''fya-'''....''holy'' → '''fya<u>t</u>'''....''holy one, saint''<br>'''ujna'''....''last''→'''uja<u>t</u>'''....''last one, last person''<br>'''Usoma'''....''American'' →'''Usoma<u>t</u>'''....''an American'' |- | -'''tajbus''' || -ogen, producer || noun || '''om'''....''cold, cry-'' → '''omtajbus'''....''cryogen'' |- | -'''tun''' || science of, -ology || noun || '''tot'''....''god'' → '''tot<u>tun</u>'''....''theology''<br>'''tob'''....''man'' → '''tob<u>tun</u>'''....''anthropology''<br>'''vob'''....''plant'' →'''vob<u>tun</u>'''....''botany'' |- | -'''tuyn''' || pseudo-science || noun || '''mar'''....''star'' → '''mar<u>tuyn</u>'''....''astrology'' |- | -'''tuin''' || theory || noun || '''vyelan'''....''relativity''→ '''vyelan<u>tuin</u>'''....''theory of relativity'' |- | -'''tyen''' || skill, craft || noun || '''sur'''....''engine'' → '''sur<u>tyen</u>'''....''engineering'' |- | -'''(t)in''' || doctrine, -ism || noun || '''zaypas-'''....''progress'' → '''zaypas<u>in</u>'''....''progressivism'' |- | -'''tut''', '''tuyt''' (f.) || scientist<br> -ologist<br> -ist || noun || '''tot'''....''god'' → '''tot<u>tut</u>'''....''theologist''<br>'''tob'''....''man'' → '''tob<u>tuyt</u>'''....''woman anthropologist''<br>'''vob'''....''plant''→ '''vob<u>tut</u>'''....''botanist'' |- | -'''uf''' || hate of, -phobia || noun || '''mil'''....''water'' → '''mil<u>uf</u>'''....''hydrophobia''<br>'''totin'''....''religion'' → '''totin<u>uf</u>'''....''hatred of religion''<br> '''toyb'''....''woman'' → '''toyb<u>uf</u>'''....''misogyny'' |- | -'''ut''', '''uyt''' (f.)|| agent, one who Xes, -er, -ant, -ist || verb stem || '''bek-'''....''treat'' → '''bek<u>uyt</u>'''....''female nurse''<br>'''pop-'''....''travel''→'''pop<u>ut</u>'''....''traveler''<br>'''ak-'''....''win'' → '''ak<u>ut</u>'''....''winner'' |- |-'''teliut''' || eater, -phage, -vore || verb stem || '''hyas'''....''everything, omni-'' → '''hyas<u>teliut</u>'''....''omnivore''<br>'''bokogrun'''....''bacteria'' → '''bokogrunteliut'''....''bacteriophage'' |- | -'''yaf'''|| ability to, power<br> -ability || verb stem || '''teat-'''....''to see'' → '''teat<u>yaf</u>'''....''ability to see''<br>'''tex-'''....''to think'' → '''tex<u>yaf</u>'''....''cognition''<br>'''test-'''....''to understand'' → '''test<u>yaf</u>'''....''comprehension''<br>'''nos-'''....''to spend'' → '''nos<u>yaf</u>'''....''spending power''<br>'''t-'''....''to know'' → '''t<u>yaf</u>'''....''cognizance'' |- | -'''yafwan''' || possibility, -ability || verb stem || '''teat-'''....''to see'' → '''teat<u>yafwan</u>'''....''visibility'' |- | -'''yof''' || inability to, disability || verb stem || '''teat-'''....''to see'' → '''teat<u>yof</u>'''....''blindness''<br>'''teet-'''....''to hear'' → '''teet<u>yof</u>'''....''deafness''<br>'''pas-'''....''to move''→'''pas<u>yof</u>'''....''paralysis''<br>'''tuj-'''....''to sleep'' → '''tuj<u>yof</u>'''....''insomnia'' |- | -'''yofwan''' || impossibility || verb stem || '''teat-'''....''to see'' → '''teat<u>yofwan</u>'''....''invisibility'' |- | -'''yag''' || big and ugly, long || noun || '''tetwid'''....''uncle''→ '''tetwid<u>yag</u>'''....''dirty old uncle''<br>'''toyb'''....''woman'' → '''toyb<u>yag</u>'''....''hag'' |- | -'''yan''' || collection, grouping<br> -ary || noun || '''tob'''....''man'' → '''tob<u>yan</u>'''....''mankind''<br>'''mar'''....''star'' → '''mar<u>yan</u>'''....''constellation''<br>'''fab'''....''tree'' → '''fab<u>yan</u>'''....''forest''<br>'''dyes'''....''book''→ '''dyes<u>yan</u>'''....''library'' |- | -'''yen''' || manner, kind || noun || '''dal'''....''talk'' →'''dal<u>yen</u>'''....''parlance''<br>'''sex-'''....''build'' →'''sex<u>yen</u>'''....''structure'' |- | -'''yef''' || duty, obligation || verb stem || '''dud-'''....''to answer'' → '''dud<u>yef</u>'''....''responsibility''<br>'''byok-'''....''to ache'' → '''byok<u>yef</u>'''....''punishment'' |- | -'''yik''' || difficulty to || verb stem || '''teet<u>er</u>'''....''to hear'' → '''teet<u>yik</u>'''....''difficulty hearing''<br>'''tiex-'''....''to breathe'' → '''tiex<u>yik</u>'''....''difficulty breathing, asthma'' |- | -'''yog''' || little and ugly || noun || '''tam'''....''house'' →'''tam<u>yog</u>'''....''shack''<br>'''anpiat'''....''duck'' → '''anpiat<u>yog</u>'''....''ugly duckling''<br>'''kod'''....''secret'' → '''kod<u>yog</u>'''....''little dirty secret'' |- | -'''yuf''' || fear of, -phobia || noun || '''serpyet'''....''snake''→ '''serpyet<u>yuf</u>'''....''fear of snakes''<br>'''mil'''....''water'' → '''mil<u>yuf</u>'''....''hyrophobia'' |- | -'''yuk'''<br>'''yukwan''' || ease of || verb stem || '''pes-''' ''to wait'' → '''pes<u>yuk</u>'''....''patience''<br>'''kovyox-''' ''to fool'' → '''kovyox<u>yukwan</u>'''....''gullibility, foolhardiness'' |} {{small/end}} === Differences between '''-en''', '''-eyn''', and '''-un''' === : The noun suffixes '''-en''', '''-eyn''', and '''-un''' create nominalized forms from a verb stem, but are a bit confusing. The suffix '''-en''' is equivalent to the English '''-ing''' and forms a gerundive. It also used to translate many English verbal nominalizations ending in ''-tion''. The suffix '''-eyn''' is a slight variation and refers to a single action or state. The ending '''-un''' forms a word meaning the result of an action and is often a thing. Sometimes '''-eyn''' is used instead of '''-un''' where the latter has a special meaning. Here are some examples: ::* '''xer'''....''to do'' :::* '''xen'''....''doing'' :::* '''xeyn'''....''deed'' :::* '''xun'''....''fact'' ::* '''yugxer'''....''to slow up'' :::* '''yugxen'''....''decelera<u>tion</u>'' :::* '''yugxun'''....''bottleneck'' ::* '''der'''....''to say'' :::* '''den'''....''saying'' :::* '''deyn'''....''utterance, a saying'' :::* '''dun'''....''word'' ::* '''ujer'''....''to end'' :::* '''ujen'''....''ending'' eg. ''I like <u>ending</u> on a happy note.'' :::* '''ujeyn'''....''an ending, finale'' eg. ''This play's <u>finale</u> was emotional.'' :::* '''ujun'''....''end, tail end'' eg. ''The road came to a sudden <u>end</u>.'' === Examples of the Suffix '''-yen''' === : This suffix is a stub of '''byen'''....''way, manner''. {{small/top}} ::{| class="wikitable sortable" style="background:lightyellow" |+ Wording Ending in -yen |- valign=top ! Base Word !! Derivation |- | '''ajtyod'''....''past people'' || '''ajtyodyen'''....''tradition'' |- | '''d-'''....''to say'' || '''dyen'''....''expression'' |- | '''akpas'''....''winning move'' || '''akpasyen'''....''tactic'' |- | '''dre(r)'''....''to write'' || '''dreyen'''....''writing system'' |- | '''amal'''....''atmosphere'' || '''amalyen'''....''weather'' |- | '''an-'''....''single'' || '''anyen'''....''quirk, idio-'' |- | '''axl-'''....''to act'' || '''axlyen'''....''behavior'' |- | '''aot'''....''person'' || '''aotyen'''....''character, personality'' |- | '''ty-'''....''to know how'' || '''tyen'''....''skill, craft'' |- | '''x-'''....''to do'' || '''xyen'''....''profession'' |- | '''ze-'''....''middle'' || '''zeyen'''....''means'' |- | '''bas-'''....''gesture'' || '''basyen'''....''body language'' |- | '''tex'''....''thought'' || '''texyen'''....''opinion'' |- | '''es-'''....''to exist'' || '''esyen'''....''state'' |- | '''kya-'''....''change'' || '''kyayen'''....''version'' |- | '''p-'''....''to go'' || '''pyen'''....''pace, gait'' |- | '''yex-'''....''to work'' || '''yexyen'''....''line of work'' |- | '''tayot-'''....''to feel'' || '''tayotyen'''....''texture'' |} {{small/end}} === Noun Prefixes === : Prefixes can also be attached to nouns to create derivatives. Here are some common productive ones: {{small/top}} :{| class="wikitable sortable" style="background:lightyellow" |+ Noun Prefixes |- valign=top ! Prefix !! Meaning !! Base Noun !! Derivations |- | '''aa-''' || ''first, arch-'' || '''deb'''....''leader''<br>'''dezun'''....''performance''<br>'''tat'''....''angel'' || '''aadeb'''....''premier''<br>'''aadezun'''....''premiere''<br>'''aatat'''....''archangel'' |- | '''aag-''' || ''macro-'' || '''donex'''....''economics'' || '''aagdonex'''....''macroeconomics'' |- | '''aaj-''' || ''paleo-, proto-'' || '''tejsan'''...''life form''<br>'''tobtun'''....''anthropology'' || '''aajtejsan'''....''protozoon''<br>'''aajtobtun'''....''paleoanthropology'' |- | '''ab-''' || ''superior, sur-, on'' || '''donab'''....''rank''<br>'''dout'''....''gentleman''<br>'''dyun'''....''name'' || '''abdonab'''....''superior rank''<br>'''abdout'''....''aristocrat''<br>'''abdyun'''....''title, surname'' |- | '''ag-''' || ''mega-, megalo-, grandi-'' || '''amlot'''....''millionaire''<br>'''dal'''....''talk''|| '''agamlot'''....''megamillionaire''<br>'''agdal'''....''grandiloquence'' |- | '''agal-''' || ''arch-, main-'' || '''mem'''....''land''<br>'''nad'''....''line'' || '''agalmem'''....''mainland''<br>'''agalnad'''....''mainline'' |- | '''agr(a)-''' || ''mega-, megalo-'' || '''meg'''....''stone''<br>'''akuj'''...''success'' || '''agrameg'''....''megalith''<br>'''agrakuj'''....''megahit'' |- | '''an-''' || ''one, uni-, mono-'' || '''zyukpar'''....''wheeled vehicle''<br>'''dungon'''....''syllable'' || '''anzyukpar'''....''unicycle''<br>'''andungon'''....''monosyllable'' |- | '''ao-''' || ''vertical'' || '''nab'''....''rank''<br>'''muf'''....''pole'' || '''aonab'''....''column''<br>'''aomuf'''....''column'' |- | '''aoyeb-''' || ''in-and-out'' || '''belen'''....''carrying'' || '''aoyebelen'''....''import-exports'' |- | '''aov-''' || ''for-and-against'' || '''dalson'''....''subject'' || '''aovdalson'''...''controversy'' |- | '''ayb-''' || ''over-, super-'' || '''dras'''....''script''<br>'''ilp'''....''flow''<br>'''mas'''....''name'' || '''aybdrun'''....''superscript''<br>'''aybilp'''....''overflow''<br>'''aybmas'''....''ceiling'' |- | '''ayn-''' || ''holo-'' || '''dras'''....''script''<br>'''meg'''....''stone''<br>'''sag'''....''number'' || '''ayndras'''....''hologram''<br>'''aynmeg'''....''hololith''<br>'''aynsag'''....''integer'' |- | '''aj-''' || ''past, pre-, fore-, ex-'' || '''din'''....''story''<br>'''gex'''....''equity''<br>'''tayd'''....''wife'' || '''ajdin'''....''history''<br>'''ajgex'''....''revenge''<br>'''ajtayd'''....''ex-wife'' |- | '''anyen-''' || ''idio-, odd'' || '''dyen'''....''expression''<br>'''fin'''....''quality'' || '''anyendyen'''....''idiom''<br>'''anyenfin'''....''quirk'' |- | '''av-''' || ''pro-, for'' || '''bol'''....''support''<br>'''dun'''....''word'' || '''avbol'''....''endorsement''<br>'''avdun'''....''pronoun'' |- | '''az-''' || ''strong'' || '''hihid'''....''laugh''<br>'''ojvad'''....''promise''<br>'''tos'''....''feeling'' || '''azhihid'''....''guffaw''<br>'''azojvad'''....''covenant''<br>'''aztos'''....''passion'' |- | '''do-''' || ''public'' || '''del'''....''statement''<br>'''did'''....''question''<br>'''vyab'''....''rule'' || '''dodel'''....''announcement''<br>'''dodid'''....''inquiry''<br>'''dovyab'''....''law'' |- | '''eb-''' || ''inter-, dia-'' || '''dal'''....''statement''<br>'''ifek'''....''gram''<br>'''kyax'''....''change'' || '''ebdal'''....''dialog''<br>'''ebifek'''....''interlude''<br>'''ebkyax'''....''interchange'' |- | '''en-''' || ''bi-, di-, two-'' || '''zyukpar'''....''wheeled vehicle'' || '''enzyukpar'''....''bicycle'' |- | '''eg-''' || ''normal'' || '''byen'''....''manner'' || '''egbyen'''....''norm'' |- | '''ej-''' || ''step-, current'' || '''twid'''....''brother''<br>'''din'''....''story'' || '''ejtwid'''....''step-brother''<br>'''ejdin'''....''current news item'' |- | '''ejna-''' || ''neo-'' || '''dun'''....''word'' || '''ejnadun'''....''neologism'' |- | '''ev-''' || ''a-, neutral'' || '''totin'''....''deism''<br>'''dofina'''....''moral'' || '''evtotin'''....''atheism''<br>'''evdofina'''....''amoral'' |- | '''eyn-''' || ''semi-, hemi-, pen-, half-, quasi-''|| '''moyn'''....''shade''<br>'''zyum'''....''sphere''<br>'''ayma'''....''warm''<br>'''dobyena'''<br>'''daba'''....''governmental'' || '''eynmoyn'''....''penumbra''<br>'''eynzyum'''....''hemisphere''<br>'''aynayma'''....''lukewarm''<br>'''anydobyena'''....''semi-official''<br>'''aydaba'''....''quasi-governmental'' |- | '''fi-''' || ''eu-, bene-, well-'' || '''dyen'''....''expression''<br>'''tos'''....''feeling'' <br>'''fon'''....''will''|| '''fidyen'''....''euphemism''<br>'''fitos'''....''euphoria''<br>'''fifon'''....''benevolence'' |- | '''fyi-''' || ''useful'' || '''dal'''....''talk'' || '''fyidal'''....''advice'' |- | '''fu-''' || ''caco-, mal-, ill-, dys-'' || '''seux'''....''sound''<br>'''fon'''....''will''<br>'''tos'''....''feeling'' || '''fuseux'''....''cacophony''<br>'''fufon'''....''ill-will, malevolence''<br>'''futos'''....''dysphoria'' |- | '''fyu-''' || ''harmful'' || '''mil'''....''water''<br>'''pelt'''...''insect'' <br>'''mul'''....''stuff''|| '''fyumil'''....''waste water''<br>'''fyupelt'''....''pest''<br>'''fyumul'''....''garbage'' |- | '''fya-''' || ''holy'' || '''din'''....''story''<br>'''buun'''....''gift''<br>'''byekut'''....''healer'' || '''fyadin'''....''gospel''<br>'''fyabuun'''....''oblation, offering''<br>'''fyabyekut'''....''shaman, witchdoctor'' |- | '''fye-''' || ''fantasy, mytho-'' || '''din'''....''story''<br>'''diyn'''....''tale''<br>'''mir'''....''world'' || '''fyedin'''....''myth, fantasy''<br>'''fyediyn'''....''fairy-tale, fable''<br>'''fyemir'''....''fantasia, fantasy-world'' |- | '''fyo-''' || ''evil'' || '''tat'''....''angel''<br>'''xeyn'''....''deed'' || '''fyotat'''....''demon''<br>'''fyoxeyn'''....''sin'' |- | '''gab-''' || ''plus'' || '''nix'''....''earning'' || '''gabnix'''....''interest'' |- | '''gaw-''' || ''re-'' || '''aklen'''....''conquest''<br>'''del'''....''statement'' || '''gawaklen'''....''reconquest''<br>'''gawdel'''....''restatement'' |- | '''ge-''' || ''equi-, iso-, even-'' || '''eksag'''....''score''<br>'''kyin'''....''weight'' || '''geeksag'''....''tie''<br> '''gekyin'''....''equilibrium'' |- | '''gel-''' || ''homo-, like-, simul-'' || '''dredun'''....''speling''<br>'''san'''....''form'' || '''geldredun'''....''homograph''<br>'''gelsan'''....''isomorph, clone'' |- | '''gla-''' || ''multi-, plur-, poly-'' || '''gon'''....''part'' || '''glagon'''....''plurality'' |- | '''glo-''' || ''few, poorly, little, hypo-, ligo-''|| '''tiibilnid'''....''blood volume'' || '''glotiibilnid'''....''hypovolemia, oligemia'' |- | '''gro-''' || ''hypo-, under-'' || '''agxen'''....''growth''<br>'''del''' || '''grogxen'''....''hypotrophy''<br>'''grodel'''....''understatement'' |- | '''gra-''' || ''too, hyper-'' || '''bik'''....''caution'' || '''grabik'''....''hypercaution'' |- | '''gwa-''' || ''macro-, super-'' || '''mor'''....''universe'' || '''gwamor'''....''macrocosm'' |- | '''hyi-''' || ''homo-, same'' || '''toobif'''....''gender preference'' || '''hyitoobif'''....''homosexualtiy'' |- | '''hyu-''' || ''hetero-, different, other-, allo-, xeno-'' || '''toobif'''....''gender preference''<br>'''mer'''....''planet''<br>'''san'''....''shape'' || '''hyutoobif'''....''heterosexuality''<br>'''hyumer'''....''alien planet''<br>'''hyusan'''....''allomorph'' |- | '''hya-''' || ''omni-, pan-, all-'' || '''doobin'''....''nationalism'' || '''hyadoobin'''....''pan-nationalism'' |- | '''hye-''' || ''any, whatever'' || '''saun'''....''kind'' || '''hyesaun'''....''any kind'' |- | '''hyo(s)-''' || ''nothing'' || '''ten'''....''knowledge'' || '''hyosten'''....''ignorance'' |- | '''hyuit-''' || ''mutual'' || '''fizuen'''....''respect'' || '''hyuitfizuen'''....''mutual respect'' |- | '''ig-''' || ''fast'' || '''didyan'''....''questionnaire'' || '''igdidyan'''....''pop quiz'' |- | '''ij-''' || ''initial, head'' || '''dun'''....''word''<br>'''miap'''....''stream'' || '''ijdun'''....''prologue''<br>'''ijmiap'''....''headstream'' |- | '''ik-''' || ''full'' || '''nuxen'''....''payment'' || '''iknuxen'''....''liquidation'' |- | '''il-''' || ''liquid'' || '''ok'''....''loss'' || '''ilok'''....''leak'' |- | '''im''' || ''wet'' || '''mel'''....''soil'' || '''immel'''....''loam, wetland'' |- | '''in-''' || ''tri-, three'' || '''goblun'''....''cut'' || '''ingoblun'''....''trisection'' |- | '''iv-''' || ''happy'' || '''din'''....''story'' || '''ivdin'''....''comedy'' |- | '''iz-''' || ''straight, orth-, rect-, direct'' || '''fin'''....''quality''<br>'''mep'''....''path'' || '''izfin'''....''rectitude''<br>'''izmep'''....''beeline, vector'' |- | '''ja-''' || ''before, pre-'' || '''bik'''....''caution'' || '''jabik'''....''precaution'' |- | '''je-''' || ''continuous'' || '''teaxer'''....''to look'' || '''jeteaxer'''....''to watch'' |- | '''jo-''' || ''after, post-'' || '''dren'''....''writing'' || '''jodren'''....''postscript'' |- | '''jwa-''' || ''proto-, eo-, early'' || '''ajdin'''....''history''<br>'''ejob'''....''modern era'' || '''jwaajdin'''....''protohistory''<br>'''jwaejob'''....''eocene'' |- | '''jwe-''' || ''prompt'' || '''puen'''....''arrival'' || '''jwepuen'''....''on-time arrival'' |- | '''jwo-''' || ''latter, late'' || '''moj'''....''night'' || '''jwomoj'''....''late night'' |- | '''ku-''' || ''side, aside, lateral'' || '''bux'''....''push''<br>'''deyn'''....''saying'' || '''kubux'''....''rebuff''<br>'''kudeyn'''....''remark'' |- | '''ki-''' || ''diagonal, slant'' || '''nad'''....''line''<br>'''texyen'''....''opinion'' || '''kinad'''....''diagonal, slant''<br>'''kitexyen'''....''bias'' |- | '''ko-''' || ''hide, covert, pseudo-'' || '''d'''....''utterance''<br>'''exut'''....''operative''<br>'''flen'''....''desire''<br>'''jadrun'''....''plan'' || '''kod'''....''secret''<br>'''koexut'''....''spy''<br>'''koflen'''....''envy''<br>'''kojadrun'''....''plot'' |- | '''kya-'''|| ''change, para-, re-''||'''bax'''....''movement''<br>'''dyan'''....''phrase''<br>'''din'''....''story''<br>'''naz'''....''value''<br>'''napxen'''....''ordering''||'''kyabax'''....''shift''<br>'''kyadyan'''....''paraphrase''<br>'''kyadin'''....''version''<br>'''kyanaz'''....''variable''<br>'''kyanapxen'''....''reordering, shuffling'' |- | '''kye-''' || ''haphazard'' || '''den'''....''saying''<br>'''fyun'''....''harm''<br>'''kaxun'''....''find'' || '''kyeden'''....''guesswork''<br>'''kyefyun'''....''danger''<br>'''kyekaxun'''....''discovery'' |- | '''kyo-''' || ''fixed'' || '''byen'''....''manner''<br>'''deyn'''....''saying''<br>'''doneg'''....''social class'' || '''kyobyen'''....''habit''<br>'''kyodeyn'''....''clich&eacute;''<br>'''kyodoneg'''....''caste'' |- | '''kyi-''' || ''heavy'' || '''azon'''....''force''<br>'''tes'''....''meaning''<br>'''bal'''....''pressure''|| '''kyiazon'''....''gravity''<br>'''kyites'''....''importance''<br>'''kyibal'''....''strain'' |- | '''kyu-''' || ''light'' || '''azon'''....''force''<br>'''mamil''' || '''kyuazon'''....''ballast''<br>'''kyumamil'''....''drizzle'' |- | '''lo-''' || ''dis-, de-, un-'' || '''bexun'''....''possession'' <br>'''bokulxen'''....''toxification''<br>'''box'''...''quiet''|| '''lobexun'''....''dispossession, divestment''<br>'''lobokulxen'''....''detoxification''<br>'''lobox'''....''disquiet'' |- | '''lyo-''' || ''totally not'' || '''fibyen'''....''good manner''<br>'''dot'''....''society'' || '''lyofibyen'''....''insolence''<br>'''lyodot'''....''wilderness'' |- | '''mak-''' || ''electro-, e-'' || '''ebdras'''....''letter''<br>'''nagar'''....''meter'' || '''makebdras'''....''email''<br>'''maknagar'''....''electrometer'' |- | '''o-''' || ''not, un-'' || '''bik'''....''care''|| '''obik'''....''neglect'' |- | '''ob-''' || ''off-, vice-'' || '''goflun'''....''rip''<br>'''fub'''....''branch'' || '''obgoflun'''....''stub''<br>'''obfub'''....''offshoot'' |- | '''oge-''' || ''unequal, aniso-'' || '''izonan'''...''orientation'' || '''ogeizonan'''....''anisotropy'' |- | '''ogel-''' || ''hetero-, different'' || '''toobifan'''....''sexual preference''<br>'''tin'''....''doctrine'' || '''ogeltoobifan'''....''heterosexuality''<br>'''ogeltin'''....''heterodoxy'' |- | '''oyb-''' || ''under-, sub-, infra-'' || '''mos'''....''floor''<br>'''neg'''....''level''<br>'''alza'''....''red''|| '''oybmos'''....''basement''<br>'''oybneg'''....''sublevel''<br>'''oybalza'''....''infrared'' |- | '''of-''' || ''prohibited'' || '''birun'''....''grab''<br>'''dresini'''....''drawings''<br>'''gelxun'''....''copy'' || '''ofbirun'''....''loot''<br>'''ofdresini'''....''grafitti''<br>'''ofgelxun'''....''plagiarism'' |- | '''og-''' || ''small'' || '''soni'''....''matters'' || '''ogsoni'''....''trivia'' |- | '''oog-''' || ''micro-, mini-'' || '''drenod'''....''dot''<br>'''naab'''....''file''<br>'''tyoyf'''....''skirt''|| '''oogdrenod'''....''microdot''<br>'''oognaab'''....''microfiche''<br>'''oogtyoyf'''....''miniskirt'' |- | '''oj-''' || ''future, fore-'' || '''buen'''....''giving''<br>'''deyn'''....''utterance'' || '''ojbuen'''....''lending''<br>'''ojdeyn'''....''forecast'' |- | '''ok-''' || ''loss'' || '''buun'''....''gift''<br>'''tos'''....''feeling'' || '''okbuun'''....''sacrifice''<br>'''oktos'''....''heartache'' |- | '''ov-''' || ''against, counter-, contra-, anti-'' || '''adabinut'''....''imperialist''<br>'''apyex'''....''attack'' || '''ovadabinut'''....''anti-imperialist''<br>'''ovapyex'''....''counterattack'' |- | '''oy-''' || ''without'' || '''tof'''....''clothes'' || '''oytofa'''....''naked'' |- | '''oz-''' || ''weak'' || '''duun'''....''suggestion'' || '''ozduun'''....''hint'' |- | '''ug-''' || ''slow'' || '''dal'''....''speech''<br>'''ilok'''....''leak'' <br>'''teax'''....''look''|| '''ugdal'''....''drawl''<br>'''ugilok'''....''seepage''<br>'''ugteax'''....''gaze'' |- | '''ui-''' || '''horizontal'' || '''nab'''....''rank'' || '''uinab'''....''row'' |- | '''un-''' || ''quadri-, tetra-, four-'' || '''drezun'''....''poem'' <br>'''yan'''....''collection''|| '''undrezun'''....''quatrain''<br>'''unyan'''....''tetrad'' |- |'''uj-''' || ''end'' || '''ak'''....''win''<br>'''dun'''....''word''<br>'''jud'''....''date'' || '''ujak'''....''success''<br>'''ujdun'''....''epilogue''<br>'''ujjud'''....''deadline'' |- | '''uk''' || ''empty'' || '''dal'''....''talk''<br>'''mel'''....''soil''<br>'''nod'''....''point'' || '''ukdal'''....''blather''<br>'''ukmel'''....''desert''<br>'''uknod'''....''puncture'' |- | '''ut-''' || ''self-, sui-, aut(o)-'' || '''tojben'''....''killing''<br>'''dab'''....''government'' || '''uttojben'''....''suicide''<br>'''utdab'''....''autarchy'' |- | '''uv-''' || ''sad'' || '''deuzun''''....''song''<br>'''dolen'''....''silence''<br>'''kyeuj'''....''fate'' || '''uvdeuzun'''....''dirge''<br>'''uvdolen'''....''sulking''<br>'''uvkyeuj'''....''tragedy'' |- | '''uf-''' || ''hate'' || '''dal'''....''speech''<br>'''tos'''....''feeling'' || '''ufdal'''....''rant''<br>'''uftos'''....''anger'' |- | '''uz-''' || ''crooked, curved, arc'' || '''aybmas'''....''roof''<br>'''dopar'''....''weapon''<br>'''kunad'''....''edge'' || '''uzaybmas'''....''vault, arch''<br>'''uzdopar'''....''bow, arch''<br>'''uzkunad'''....''rim'' |- | '''va-''' || ''yes'' || '''bien'''....''taking''<br>'''diun'''....''request''<br>'''dud'''....''answer'' || '''vabien'''....''acceptance''<br>'''vadiun'''....''claim''<br>'''vadud'''....''assent'' |- | '''vao-''' || ''yes-or-no'' || '''d'''....''utterance'' || '''vaod'''....''decision'' |- | '''ve-''' || ''maybe'' || '''texen'''....''thinking''<br>'''yovdeyn'''....''inculpation'' || '''vetexen'''....''supposition''<br>'''veyovdeyn'''....''indictment'' |- | '''vo-''' || ''no'' || ''texen'''....''thinking''<br>'''fon'''....''will'' || '''votexen'''....''doubting''<br>'''vofon'''....''disinclination'' |- | '''vya-''' || ''true'' || '''deyn'''....''utterance''<br>'''dud'''....''answer''<br>'''nad'''....''line'' || '''vyadeyn'''....''avowal''<br>'''vyadud'''....''solution''<br>'''vyanad'''....''guideline'' |- | '''vye-''' || ''relative'' || '''dren'''....''writing'' || '''vyedren'''....''correspondence'' |- | '''vyo-''' || ''wrong, mis-'' || '''bek'''....''treatment''<br>'''dat'''....''friend'' || '''vyobek'''....''mistreatment''<br>'''vyodat'''....''false friend'' |- | '''yag-''' || ''long'' || '''igpek'''....''race'' || '''yagigpek'''....''marathon'' |- | '''yan-''' || ''together, con-'' || '''dal'''....''talk'' || '''yandal'''....''conversation'' |- | '''yog-''' || ''short, steno-'' || '''drir'''....''typewriter''<br>'''job'''....''time'' || '''yogdrir'''....''stenograph''<br>'''jogjob'''....''short while'' |- | '''yok-''' || ''sudden'' || ''apyex'''....''attack'' || '''yokapyex'''....''raid'' |- | '''yon-''' || ''apart'' || '''byex'''....''strike'' || '''yonbyex'''....''breach'' |- | '''yov-''' || ''shame'' || '''bixen'''....''pulling''<br>'''byok'''....''pain''<br>'''if'''....''pleasure'' || '''yovbixen'''....''seduction''<br>'''yovbyok'''....''punishment''<br>'''yovif'''....''schadenfreude'' |- | '''yab-''' || ''up, super-, high-, hyper-'' || '''dom'''....''city''<br>'''dot'''....''society'' || '''yabdom'''....''uptown''<br>'''yabdot'''....''high society'' |- | '''yabnan-''' || ''hypso-, acro-, height'' || '''dren'''....''recording'' || '''yabnandren'''....''hypsography'' |- | '''yaob-''' || ''up-and-down'' || '''yuijar'''....''valve''<br>'''pusen'''....''jumping'' || '''yaobyuijar'''....''piston''<br>'''yaopusen'''....''bouncing'' |- | '''yaz-''' || ''swollen, protruding, convex'' || '''dal'''....''talk''<br>'''buk'''....''wound''<br>'''tiub'''....''belly''<br>'''mem'''....''land'' || '''yazdal'''....''bombast''<br>'''yazbuk'''....''boil, blister''<br>'''yaztiub'''....''potbelly''<br>'''memyaz'''....''mountain'' |- | '''yez-''' || ''flush, along, para-'' || '''baktut'''....''medic''<br>'''mel'''....''terrain'' || '''yezbaktut'''....''paramedic''<br>'''yezmel'''....''meadow'' |- | '''yiz-''' || ''beyond, meta-, ultra-, hyper-'' || '''doobin'''....''nationalism''<br>'''dreniv'''....''text'' || '''yizdoobin'''....''ultra-nationalism''<br>'''yizdreniv'''....''hypertext'' |- | '''yoz-''' || ''sunken, concave'' || '''nad'''....''line'' || '''yoznad'''....''groove, gutter'' |- | '''yaoz-''' || ''saw-toothed, convex-concave'' || '''nad'''....''line''<br>'''goblar'''....''knife'' || '''yaoznad'''....''tilde''<br>'''yaozgoblar'''....''saw'' |- | '''yuz-''' || ''around, circ-, circum-, peri-'' || '''pipen'''....''navigation''<br>'''teaxar'''....''scope''<br>'''tyop'''....''walk'' || '''yuzpipen'''....''circumnavigation''<br>'''yuzteaxar'''....''periscope''<br>'''yuztyop'''....''stroll'' |- | '''yeb-''' || ''in-, intro-, inner-'' || '''dungab'''....''affix''<br>'''deym'''....''yard, court'' || '''yebdungab'''....''infix''<br>'''yebdeym'''...''courtyard'' |- | '''oyeb-''' || ''out-, extro-, outer-'' || '''dom'''....''city''<br>'''dovyaban'''....''legality'' || '''oyebdom'''....''outskirts''<br>'''oyebdovyaban'''....''extralegality'' |- | '''yib-''' || ''tele-, far'' || '''drir'''....''typewriter''<br>'''teaxar'''....''viewer, scope'' || '''yibdrir'''....''teletype''<br>'''yibteaxar'''....''telescope'' |- | '''yibaj''' || ''ancient, archaeo-, paleo-'' || '''deyn'''....''utterance''<br>'''tun'''....''science'' || '''yibajdeyn'''....''archaism''<br>'''yibajtun'''....''archaeology'' |- | '''yub-''' || ''near, para-, juxta-'' || '''gexen'''....''equaling''<br>'''kex'''....''search''<br>'''dop'''....''military''<br>'''tayov'''....''membrane''|| '''yubgexen'''....''approximation''<br>'''yubkex'''....''examination''<br>'''yubdop'''....''paramilitary''<br>'''juxtamembrane''' |- | '''yubaj-''' || ''recent, ceno-'' || || |- | '''yob-''' || ''down, sub-, de-'' || '''doneg'''....''class''<br>'''byex'''....''beat'' || '''yobdoneg'''....''low class''<br>'''yobbyex'''....''downbeat'' |- | '''za-''' || ''front, fore-, pre-, north'' || '''dungab'''....''affix''<br>'''dyun'''....''name''<br>'''mer'''....''planet'' || '''zadungab'''....''prefix''<br>'''zadyun'''....''forename''<br>'''zamer'''....''north'' |- | '''ze-''' || ''middle, mid-'' || '''dom'''....''city''<br>'''jub'''....''day'' || '''zedom'''....''downtown''<br>'''zejub'''....''midday'' |- | '''zo-''' || ''behind, back'' || '''bex'''....''hold''<br>'''bix'''....''pull'' || '''zobex'''....''delay''<br>'''zobix'''....''drag'' |- | '''zay-''' || ''forward, pro-'' || '''bix'''....''pull''<br>'''bux'''....''push'' || '''zaybix'''....''protraction''<br>'''zaybux'''....''propulsion'' |- | '''zey-''' || ''across, trans-, meta-'' || '''dras'''....''script''<br>'''ilp'''....''flow'' || '''zeydras'''....''transcript''<br>'''zeyilp'''....''crosscurrent'' |- | '''zoy-''' || ''re-, retro-, back'' || '''axlen'''....''action''<br>'''kix'''....''bend''<br>'''mag'''....''fire''<br>'''mav'''....''flash'' || '''zoyaxlen'''....''reaction''<br>'''zoykix'''....''reflection''<br>'''zoymag'''....''retrofire''<br>'''zoymav'''....''flashback'' |- | '''zya-''' || ''wide'' || '''dodal'''....''speech''<br>'''drurun'''....''printout'' || '''zyadodal'''....''propaganda''<br>'''zyadrurun'''....''poster'' |- | '''zye-''' || ''through, per-, trans-, dia-'' || '''belun'''....''cargo''<br>'''muf'''....''rod''<br>'''bwas'''....''something put'' || '''zyebelun'''....''shipment''<br>'''zyebuxmuf'''....''ramrod (through-push-rod)''<br>'''zyebwas'''....''metaphor'' |- | '''zyi-''' || ''flat, plat-'' || '''dyen'''....''expression''<br>'''mos'''....''floor'' || '''zyidyen'''....''platitude''<br>'''zyimemyaz'''....''plateau''<br>'''zyimos'''....''platform'' |- | '''zyo-''' || ''narrow'' || '''bex'''....''hold''<br>'''bix'''....''pull''<br>'''gun'''....''angle'' || '''zyobex'''....''clasp, grip''<br>'''zyobix'''....''tension''<br>'''zyogun'''....''acute angle'' |- | '''zyu-''' || ''round, roto-, cyclo-'' || '''abaun'''....''cover''<br>'''drurun'''....''printout''<br>'''tom'''....''building'' || '''zyuabaun'''....''dome''<br>'''zyudrurun'''....''rotograph''<br>'''zyutom'''....''tower'' |} {{small/end}} == Gender == [[File:Gender Neutral (13777) - The Noun Project.svg|thumb|]] : Nouns in Mirad are gender-neutral, unless those relating to people, animals, and sometimes clothing are altered to be specifically male/male-oriented or female/female-oriented. To create the male or male-oriented form of an otherwise gender-neutral noun, prefix the vowel of the semantically significant syllable with the letter '''w'''. To create the female or female-oriented form, suffix the vowel of the semantically significant syllable with '''y'''. If the noun is an agent noun with the suffix '''-ut''', that is, a noun that means "one who does something as an occupation or behavior", the ending '''-ut''' is changed to '''-uyt''' for the female form, but the male form ending stays the same or becomes '''-twob'''. The reason for this is that the addition of a '''w''' to the agentive ending could be confused with the verbal passive marker '''w''' (see the chapter on [[Mirad Grammar/Verbs]]. The chart below shows how this works: ::{| class="wikitable" style="background:lightyellow; font-size:smaller;" |+ Making Nouns Gender-specific |- ! Neutral !! Masculine !! Feminine |- | '''tob'''....''human being, person'' || '''twob'''....''man'' || '''toyb'''....''woman'' |- | '''tobet'''....''child'' || '''twobet'''....''boy'' || '''toybet'''....''girl'' |- | '''tad'''....''spouse'' || '''twad'''....''husband'' || '''tayd'''....''wife'' |- | '''ejtad'''....''step spouse'' || '''ejtwad'''....''step-husband'' || '''ejtayd'''....''step-wife'' |- | '''ajtad'''....''ex-spouse'' || '''ajtwad'''....''ex-husband'' || '''ajtayd'''....''ex-wife'' |- | '''ted'''....''parent'' || '''twed'''....''father'' || '''teyd'''....''mother'' |- | '''datif'''....''sweetheart'' || '''dwatif'''....''boyfriend'' || '''daytif'''....''girlfriend'' |- | '''supet'''....''pig''|| '''supwet'''....''boar'' || '''supeyt'''....''sow'' |- | '''edeb'''....''monarch'' || '''edweb'''....''king'' || '''edeyb'''....''queen'' |- | '''gafapat'''....''fowl'' || '''gafapwat'''....''rooster'' || '''gafapayt'''....''hen'' |- | '''tiuv'''....''underwear'' || '''twiuv'''....''briefs'' || '''tiuyv'''....''panties'' |- | '''anbopet'''....''antelope'' || '''anbopwet'''....''deer'' || '''anbopeyt'''....''doe'' |- | '''deuzut'''....''singer'' || '''deuzut / deuztwob'''....''male singer'' || '''deuzuyt''' ....''songstress'' |- | '''tud'''....''child'' || '''twud'''....''son'' || '''tuyd'''....''daughter'' |} : For gender specification in pronouns, see [[Mirad Grammar/Pronouns]], below). <noinclude>{{Chapter navigation with TOC|Parts of Speech|Adjectives}}</noinclude> jwp3tlrlxu6v0is1wp0oq8p72610nk7 0 438545 4634225 4634005 2026-05-05T08:06:21Z Flimonkes 3581169 Added Military AI section 4634225 wikitext text/x-wiki Algorithmic bias refers to undesirable results from a computer system that incorrectly or unfairly prioritizes one group over another. This chapter currently focuses on algorithmic bias in the United States. == Background == Of particular importance is algorithmic bias in Machine Learning (ML) and Artificial Intelligence (AI). Companies and individuals are increasing their reliance on AI systems. Search engine results, social media recommendations, hiring decisions, stock market predictions, and policing practices use information from AI predictive modeling. <ref>[https://www.ibm.com/analytics/hadoop/big-data-analytics IBM. (n.d.). ''Big Data Analytics''. https://www.ibm.com/analytics/hadoop/big-data-analytics.]</ref> Algorithmic bias in these models is particularly dangerous due to human Automation Bias, the tendency for humans to disregard contradictory information when presented with a computer-generated solution <ref> Cummings, Mary (2004). "Automation Bias in Intelligent Time Critical Decision Support Systems" (PDF). AIAA 1st Intelligent Systems Technical Conference (PDF). doi:10.2514/6.2004-6313. {{#isbn:978-1-62410-080-2}}. Archived from the original on 2014-11-01. </ref>. This increases the likelihood that bias in the AI system will result in unfair or inequitable outcomes where the system is in use. How does Algorithmic Bias occur in AI systems? Often, AI systems operate on massive data sets amalgamated from existing sources [[Lentis/"Data is the new oil"|without refinement]]. This leads to any existing bias, often institutional or implicit, being passed along to the AI system. <ref>[https://www.technologyreview.com/2019/02/04/137602/this-is-how-ai-bias-really-happensand-why-its-so-hard-to-fix/ Hao, K. (2019, February 4). ''This is how AI bias really happens-and why it's so hard to fix''. MIT Technology Review. https://www.technologyreview.com/2019/02/04/137602/this-is-how-ai-bias-really-happensand-why-its-so-hard-to-fix/.]</ref> Consider an AI hiring algorithm created to give a competitive advantage in finding the best possible candidates for a computer science position. Because computer science is currently male dominated field, the hiring algorithm might erroneously prioritize male applicants. An example of a similar case is the Amazon Hiring Algorithm. In this way, AI systems will replicate existing bias and perpetuate existing prejudice in the status quo. Assembled bias, a proposed type of Algorithmic Bias unique to AI and ML systems, describes novel biases introduced by AI systems that do not currently exist in society.<ref>Waller, R.R., Waller, R.L. Assembled Bias: Beyond Transparent Algorithmic Bias. ''Minds & Machines'' 32, 533–562 (2022). <nowiki>https://doi-org.proxy1.library.virginia.edu/10.1007/s11023-022-09605-x</nowiki></ref> Assembled bias arises from the idea that AI models are generative rather than purely statistical. A toy example to better understand this phenomenon is AI generation of realistic images.<ref>Gray, Richard. (2018, November 27). ''Why machines dream of spiders with 15 legs.'' https://www.bbc.com/future/article/20181127-the-weird-way-machines-with-ai-see-the-world </ref> When asked to create an image of a spider, an AI model might produce a highly detailed, realistically textured image of an eleven-legged spider. Even though the AI has only ever trained with images of eight-legged spiders, the AI has no concept of how to count legs – instead, it creates its own metrics for what defines a spider. Diversity is notably lacking from AI development and research positions. Only about 20% of AI researchers are women, and other minority groups are similarly underrepresented.<ref>Kumar, S., Choudhury, S. Gender and feminist considerations in artificial intelligence from a developing-world perspective, with India as a case study. ''Humanit Soc Sci Commun'' 9, 31 (2022). <nowiki>https://doi.org/10.1057/s41599-022-01043-5</nowiki></ref> Because the end goal when developing an AI system is often quantifying a nebulous concept, the perspectives of those present and working on the system strongly influence the outcome. The lack of diversity in AI positions represents another possible source of bias because the majority perspective will be overvalued in the outcome. Currently, the unfair outcomes resulting from Algorithmic Bias in AI systems appear to be disadvantaging primarily women and sexual or racial minorities. Combating this unintended result of AI and ML is an ongoing field of research.<ref name=":2">[https://www.technologyreview.com/2019/02/04/137602/this-is-how-ai-bias-really-happensand-why-its-so-hard-to-fix/ Hao, K. (2019, February 4). ''This is how AI bias really happens-and why it's so hard to fix''. MIT Technology Review. https://www.technologyreview.com/2019/02/04/137602/this-is-how-ai-bias-really-happensand-why-its-so-hard-to-fix/.]</ref> == Case Studies and Social Impacts == === Amazon's Hiring Algorithm === In 2014, Amazon initiated a program that used AI to review job resumes. The purpose of the program was to reduce the time spent on finding good candidates to fill job openings. The AI was trained on resumes submitted to the company during the previous 10 years. The demographics of the submitted resumes were similar to that of most tech companies: composed mostly of men, especially in technical roles. Consequently, the AI produced an algorithm that favored male resumes more than female resumes, as most of the previously successful candidates were male. This manifested itself in the algorithm as it penalized resumes that included the word “women’s”, or rewarding those with words more commonly found on male resumes such as “captured” or “executed”. The algorithm was also found to downgrade candidates who graduated from all-women’s colleges.<ref name=":0">Dastin, J. (2018, Oct. 10). ''Amazon Scraps secret AI recruiting tool that showed bias against women.'' Reuters. <nowiki>https://www.reuters.com/article/us-amazon-com-jobs-automation-insight/amazon-scraps-secret-ai-recruiting-tool-that-showed-bias-against-women-idUSKCN1MK08G</nowiki></ref> To combat the gender-bias outcome of the tool, Amazon made the program neutral to gender-correlated terms. By doing so, Amazon engaged in internal auditing, a technique designed to reduce algorithmic bias by ensuring any emerging bias in a machine learning model is caught and stopped. However, it did not address the crux of the problem, which was the underlying data. A different approach would have been to analyze the existing data set to predict where the algorithm could be biased, evaluating and modifying assumptions about the data as necessary. This approach has been successful in other AI applications. In this case, however, Amazon left the underlying data unaddressed. This abetted the algorithm to find additional discriminatory ways of sorting the candidates. The tool was retired in 2017 after “executives lost hope for the project.”<ref name=":0" /> Critics of Amazon argue this algorithm has perpetuated the gender disparity in their workforce. Amazon does not dispute that their recruiters looked at the recommendations generated by the tool, but maintain the tool “was never used by [them] to evaluate candidates.”<ref name=":0" /> Opponents of Amazon argue the two are mutually exclusive; recruiters were surely influenced by a tool that rates candidates from 1-5 stars, even if they claim they were not. Some critics, like ACLU Attorney Rachel Goodman, further contend that AI hiring tools “are not eliminating human bias – they are merely laundering it through software.”<ref>Goodman, R. (2018, Oct. 12). Why Amazon’s Automated Hiring Tool Discriminated Against Women. ''American Civil Liberties Union.'' <nowiki>https://www.aclu.org/blog/womens-rights/womens-rights-workplace/why-amazons-automated-hiring-tool-discriminated-against</nowiki></ref> Proponents of AI hiring technology are more optimistic: In a 2017 survey from CareerBuilder, 55% of U.S. human resources managers said AI would be a regular part of their work within the next five years.<ref>CareerBuilder. (2017, May 18). ''More than half of HR managers say artificial intelligence will become a regular part of HR in next 5 years'' [press release]. <nowiki>https://www.scribbr.com/apa-examples/press-release/</nowiki></ref> However, as Vice President of LinkedIn Talent Solutions John Jersin explains, the technology has much room for improvement before it can “make a hiring decision on its own.”<ref name=":0" /> Amazon has since revived the project, hoping that emphasizing diversity will lead to more equitable algorithmic outcomes. However, in the absence of critically evaluating the data the models are trained on, it is unclear why a certain algorithmic emphasis will lead to a non-discriminatory outcome of the algorithm. === Vendors, Regulators, and the Hiring Pipeline === While Amazon's algorithm represents one company's failed attempt at automated recruiting, automated hiring tools are now widespread. As of 2025, an estimated 99% of Fortune 500 companies use some form of applicant tracking system, and a growing share rely on AI for screening, ranking, and video assessment.<ref name=":hire1">Jobscan. (2025). ''Fortune 500 ATS usage report''. <nowiki>https://www.jobscan.co/blog/fortune-500-use-applicant-tracking-systems/</nowiki></ref> Vendors such as HireVue, Pymetrics, and Eightfold supply these tools to employers across industries. HireVue, one of the largest, reports having facilitated over 70 million video interviews.<ref>HireVue. (2025). ''AI-powered skill validation, video interviewing, assessments and more''. <nowiki>https://www.hirevue.com/</nowiki></ref> Vendors frame their tools as standardizing fairness. HireVue states that its AI provides "a standard, structured, and fair way to screen many candidates… in a shorter time and at lower cost."<ref>HireVue. (2022, April). ''AI explainability statement (short form)''. <nowiki>https://www.hirevue.com/wp-content/uploads/2022/04/HV_AI_Short-Form_Explainability_1pager.pdf</nowiki></ref> Critics argue this framing conflates algorithmic consistency with equity. The Electronic Privacy Information Center filed an FTC complaint against HireVue in 2019, alleging that the company's facial analysis features lacked scientific basis and produced biased outcomes.<ref name=":10">Electronic Privacy Information Center. (2019, November 6). ''EPIC files FTC complaint against HireVue''. <nowiki>https://epic.org/epic-files-complaint-with-ftc-about-employment-screening-firm-hirevue/</nowiki></ref> HireVue announced in January 2021 that it had removed facial analysis from its assessments, citing public concern, but retained voice and language analysis.<ref>Maurer, R. (2021, February 3). HireVue discontinues facial analysis screening. ''SHRM''. <nowiki>https://www.shrm.org/topics-tools/news/talent-acquisition/hirevue-discontinues-facial-analysis-screening</nowiki></ref> Employers and HR departments occupy a distinct position in this pipeline. The Society for Human Resource Management reports that among organizations using AI in hiring, nearly nine in ten do so to save time or increase efficiency.<ref>SHRM. (2024). ''2024 Talent Trends Survey: Artificial intelligence findings''. <nowiki>https://shrm-res.cloudinary.com/image/upload/AI/2024-Talent-Trends-Survey_Artificial-Intelligence-Findings.pdf</nowiki></ref> However, most HR departments lack the technical capacity to independently audit the tools they purchase, creating a diffusion of responsibility: vendors maintain that employers control how the tools are used, while employers defer to algorithmic outputs they cannot meaningfully evaluate. === The Regulatory Landscape === Governance of automated hiring is fragmented. In the United States, no federal law specifically addresses AI in employment. The Equal Employment Opportunity Commission has issued guidance noting that automated screening can violate the Americans with Disabilities Act and Title VII, but this guidance is non-binding.<ref>U.S. Equal Employment Opportunity Commission. (2022, May 12). ''U.S. EEOC and U.S. Department of Justice warn against disability discrimination''. <nowiki>https://www.eeoc.gov/newsroom/us-eeoc-and-us-department-justice-warn-against-disability-discrimination</nowiki></ref> In the absence of federal action, individual states and cities have legislated. Illinois passed the Artificial Intelligence Video Interview Act in 2019, requiring employers to notify applicants when AI evaluates video interviews and obtain their consent.<ref>Illinois Artificial Intelligence Video Interview Act, 820 ILCS 42 (2019). <nowiki>https://www.ilga.gov/Legislation/ILCS/Articles?ActID=4015&ChapterID=68</nowiki></ref> New York City's Local Law 144, effective in 2023, requires employers using automated employment decision tools to commission annual independent bias audits and publish the results.<ref>New York City Local Law 144 of 2021, Administrative Code § 20-871 (2023).</ref> The European Union has taken a different approach: the EU AI Act, which entered into force in 2024, classifies hiring AI as "high-risk" and imposes mandatory pre-deployment impact assessments.<ref>European Parliament. (2024). ''Regulation (EU) 2024/1689 of the European Parliament and of the Council laying down harmonised rules on artificial intelligence''. <nowiki>https://eur-lex.europa.eu/eli/reg/2024/1689/oj</nowiki></ref> This product-safety framework contrasts with the U.S. civil-rights model, which generally requires harm to occur before legal action can proceed. The trade group BSA | The Software Alliance, whose members include Microsoft, Oracle, and Workday, has actively lobbied to narrow these regulations. In comments on Local Law 144, BSA argued that "requiring third-party audits is not a feasible or optimal approach," citing the absence of common AI auditing standards and professional oversight bodies.<ref>BSA | The Software Alliance. (2023, January 23). ''Comments on the New York City Department of Consumer and Worker Protection's revised proposed rules implementing Local Law 144''. <nowiki>https://www.bsa.org/files/policy-filings/01232023nyctools.pdf</nowiki></ref> The result is a contested regulatory environment in which the standards meant to govern these tools are themselves shaped by the industries they are intended to constrain. === Facial Recognition Algorithms === Several companies, including IBM and Microsoft, have developed facial recognition algorithms to recognize people only using their face<ref>Najibi, A. (2020). ''Racial Discrimination in Face Recognition Technology''. Science in the News; Harvard University. https://sitn.hms.harvard.edu/flash/2020/racial-discrimination-in-face-recognition-technology/</ref>. These algorithms are available to the public and have been used by police departments in conjunction with [[Lentis/Video Surveillance|video surveillance]] programs <ref>Hao, K. (2020, June 12). ''The two-year fight to stop Amazon from selling face recognition to the police''. MIT Technology Review. https://www.technologyreview.com/2020/06/12/1003482/amazon-stopped-selling-police-face-recognition-fight/</ref>. In 2018, Joy Buolamwini studied biases in gender classification for facial recognition algorithms from IBM, Microsoft, and Face++, and discovered that all of them perform better on "lighter faces than darker faces", and performed worst for "darker female faces "<ref name=":8">Buolamwini, J., Gebru, T., Friedler, S., & Wilson, C. (2018). Gender Shades: Intersectional Accuracy Disparities in Commercial Gender Classification *. ''Proceedings of Machine Learning Research'', ''81'', 1–15. http://proceedings.mlr.press/v81/buolamwini18a/buolamwini18a.pdf</ref>. All of the algorithms had an accuracy gap between "lighter males and darker females" of over 20% with IBM's algorithm performing the worst with a gap of 34.4%<ref name=":8" />. In 2019, the National Institute of Standards and Technology (NIST) confirmed the issue of [[Lentis/Algorithmic bias by gender|algorithmic gender bias]] and racial bias is an industry wide problem with 189 of the studied facial recognition algorithms being least accurate for people of color, and in particular, women of color<ref>Grother, P., Ngan, M., & Hanaoka, K. (2019). Face recognition vendor test part 3: ''Face Recognition Vendor Test (FRVT) Part 3: Demographic Effects''. https://doi.org/10.6028/nist.ir.8280 ‌</ref>. In response to the research IBM stopped working on their facial recognition algorithm<ref>Jee, C. (2020, June 9). ''IBM says it is no longer working on face recognition because it’s used for racial profiling''. Technology Review; MIT Technology Review. https://www.technologyreview.com/2020/06/09/1002947/ibm-says-it-is-no-longer-working-on-face-recognition-because-its-used-for-racial-profiling/</ref>, Microsoft and Face++ released improved versions of their facial recognition algorithms and reduced their accuracy gap by over 19%<ref>Buolamwini, J. (2019). ''Actionable Auditing: Investigating the Impact of Publicly Naming Biased Performance Results of Commercial AI Products – MIT Media Lab''. MIT Media Lab. https://www.media.mit.edu/publications/actionable-auditing-investigating-the-impact-of-publicly-naming-biased-performance-results-of-commercial-ai-products/</ref>, and Amazon stopped police departments from using its facial recognition algorithm<ref>Hao, K. (2020, June 12). ''The two-year fight to stop Amazon from selling face recognition to the police''. MIT Technology Review. https://www.technologyreview.com/2020/06/12/1003482/amazon-stopped-selling-police-face-recognition-fight/</ref>. === Wrongful Arrests and the Limits of Corporate Response === While companies like IBM and Amazon paused or withdrew their facial recognition products in response to research findings, deployment by law enforcement continued through other vendors. In January 2020, Detroit police arrested Robert Williams in front of his wife and two daughters after a facial recognition system incorrectly matched him to surveillance footage of a shoplifting suspect.<ref>Hill, K. (2020, June 24). Wrongfully accused by an algorithm. ''The New York Times''. <nowiki>https://www.nytimes.com/2020/06/24/technology/facial-recognition-arrest.html</nowiki></ref> Williams spent thirty hours in jail before officers acknowledged the match was wrong. His was the first publicly reported case of a wrongful arrest caused by facial recognition technology.<ref name=":fr1">American Civil Liberties Union of Michigan. (2024). ''Williams v. City of Detroit''. <nowiki>https://www.aclumich.org/en/cases/facial-recognition</nowiki></ref> Williams's case was not isolated. By 2025, the American Civil Liberties Union had documented more than a dozen publicly known wrongful arrests in the United States caused by police reliance on facial recognition matches, with nearly all of the affected individuals being Black.<ref>American Civil Liberties Union. (2025). ''More than a dozen wrongful arrests due to police reliance on facial recognition technology''. <nowiki>https://www.aclu.org/news/privacy-technology/more-than-a-dozen-wrongful-arrests-due-to-police-reliance-on-facial-recognition-technology</nowiki></ref> Cases include Nijeer Parks in New Jersey, Porcha Woodruff in Detroit (arrested while eight months pregnant), and Randal Reid in Georgia.<ref>Innocence Project. (2024, January 17). ''Artificial intelligence is putting innocent people at risk of being incarcerated''. <nowiki>https://innocenceproject.org/news/artificial-intelligence-is-putting-innocent-people-at-risk-of-being-incarcerated/</nowiki></ref> The American Civil Liberties Union, working with the University of Michigan Civil Rights Litigation Initiative, filed suit on Williams's behalf in 2021, arguing that Detroit's use of the technology violated his civil rights.<ref>American Civil Liberties Union. (2024, June 28). ''Williams v. City of Detroit''. <nowiki>https://www.aclu.org/cases/williams-v-city-of-detroit-face-recognition-false-arrest</nowiki></ref> The case settled in June 2024, with Detroit agreeing to what advocates described as the strongest police facial recognition policy in the United States, including a prohibition on arrests based solely on algorithmic matches.<ref>Michigan Public Radio. (2024, June 28). ''Wrongful facial recognition arrest in Detroit leads to landmark settlement''. <nowiki>https://www.michiganpublic.org/criminal-justice-legal-system/2024-06-28/it-didnt-make-sense-at-all-wrongful-facial-recognition-arrest-leads-to-landmark-settlement</nowiki></ref> The Williams case illustrates a recurring pattern in algorithmic bias advocacy. Researchers such as Joy Buolamwini generate quantitative evidence of bias; advocacy organizations identify specific victims whose stories make the harm legible to non-technical audiences; journalists amplify these cases; and litigators or legislators use the resulting political pressure to force change. Buolamwini's Gender Shades findings were published in 2018, but the most consequential policy responses came only after individual harms became public. This dynamic raises questions about the time lag between technical research and accountability: tools shown to be biased often remain in deployment for years before specific cases generate enough visibility to compel response. === Predictive Policing === {{See also|Lentis/Predictive_Policing}} === Loan Lending Algorithms === Financial technology (Fintech) is a field in which loan lending algorithms have begun to replace face-to-face meetings. In the U.S., 45% of the largest mortgage lenders offer software-based loan solutions but they have been scrutinized for discriminative pricing. A study by Bartlett et al. found that through online platforms and face-to-face meetings Black and Latinx borrowers paid, on average, 7.9 basis points higher interest on purchase loans than comparable borrowers and paid 3.6 basis points more on refinance loans. This difference costs Black and Latinx borrowers $756M annually. Researchers found the discrimination in algorithms to be about 40 percent less than face-to-face lenders. Specifically, when Fintech algorithms are used, underrepresented borrowers pay 5.3 basis points higher than their counterparts (2.6 points lower than traditional methods)<ref>Gunn, D. (2019, Oct.). Minority Borrowers Pay More, Even under Algorithmic Lending. ''The Digest No. 10''. www.nber.org/digest/oct19/minority-borrowers-pay-more-even-under-algorithmic-lending</ref>. The study analyzed 30-year, fixed-rate, single-family residential loans issued by Fannie Mae and Freddie Mac between 2008 and 2015, and lenders were found to make 11 percent to 17 percent higher profits from purchase loans to underrepresented groups<ref name=":9">Counts, L. (2018, Nov. 13). Minority homebuyers face widespread statistical lending discrimination, study finds. BerkeleyHaas. newsroom.haas.berkeley.edu/minority-homebuyers-face-widespread-statistical-lending-discrimination-study-finds</ref>. Although loaning algorithms demonstrate less bias than traditional face-to-face lenders, the persistence of bias of any degree emphasizes the need to examine loaning algorithms and determine the source of the algorithmic bias. Loaning algorithms are based on machine learning and big data, which use a wide array of customer attributes to set prices. For example, geography can play a major role since the algorithm can target locations where comparison shopping is less likely. The algorithm may determine areas that are financial deserts where financial reserves are low and applicants are faced with monopoly pricing instead of having access to many options. The algorithm may not specifically target underrepresented applicants, but its logic may set a higher price knowing the applicant is more likely to accept it<ref name=":9" />. Underlying historical discrimination in training data may also lead algorithms to disfavor underrepresented groups and further wealth disparity. Fintech loaning algorithms use the prospective borrower’s credit histories, employment status, assets, debts, and the size of the loan requested to set interest rates. “If the data that you’re putting in is based on historical discrimination, then you’re basically cementing the discrimination at the other end,” says Aracely Panameño, director of Latino affairs for the Center for Responsible Lending. Research also shows that payday loan sellers often prey on neighborhoods predominantly populated with people of color since they typically have fewer bank branches. Banks report both positive and negative credit behavior while payday loan services only report missed payments. As a result, underrepresented groups from these neighborhoods find themselves with incomplete or skewed credit histories that are later fed into loan financing algorithms<ref>Martinez, E., & Kirchner, L. (2021, Aug. 25). The Secret Bias Hidden in Mortgage-Approval Algorithms. ''The Markup''. themarkup.org/denied/2021/08/25/the-secret-bias-hidden-in-mortgage-approval-algorithms</ref>. === COMPAS Recidivism Algorithm === ==== The Algorithm ==== The Correctional Offender Management Profiling for Alternative Sanctions algorithm (COMPAS), is a machine learning algorithm for judicial decision-making during criminal sentencing. Used in Wisconsin, New York, California, and Florida, COMPAS predicts the potential risk of recidivism. Created by Northpointe, Inc. (now Equivant), this commercial algorithm uses a questionnaire to categorize defendants as "low-risk", "medium-risk", or "high-risk", with respective scores of 1-4, 5-7, or 8-10.<ref name=":4">Park, A. L. (2019, February 19). ''Injustice Ex Machina: Predictive Algorithms in Criminal Sentencing''. Law Meets World. <nowiki>https://www.uclalawreview.org/injustice-ex-machina-predictive-algorithms-in-criminal-sentencing/#_ftn2</nowiki>.</ref> Factors such as age, gender, and criminal history are used while race is not.<ref>Rahman, F. (2020, September 7). ''Compas case study: Fairness of a Machine Learning Model''. Towards Data Science. <nowiki>https://towardsdatascience.com/compas-case-study-fairness-of-a-machine-learning-model-f0f804108751</nowiki>.</ref> Used still today to advise on bail, sentencing, and early release, many are questioning the validity and fairness of COMPAS in providing objective advice, particularly by race.<ref name=":5">Angwin, J., & Larson, J. (2016, December 30). ''BIAS in Criminal Risk Scores is Mathematically Inevitable, Researchers Say''. ProPublica. <nowiki>https://www.propublica.org/article/bias-in-criminal-risk-scores-is-mathematically-inevitable-researchers-say</nowiki>.</ref> In 2016 the Pulitzer Prize-winning nonprofit news organization ProPublica<ref name=":6">Spielkamp, M. (2017, June 12). ''Inspecting Algorithms for Bias''. MIT Technology Review. <nowiki>https://www.technologyreview.com/2017/06/12/105804/inspecting-algorithms-for-bias/</nowiki>.</ref> conducted a study to assess COMPAS for racial bias. A COMPAS score of medium or high risk and a defendant recidivating in 2 years, and a COMPAS score of low and a defendant not recidivating in 2 years are considered correct predictions<ref name=":7">Larson, J., Mattu, S., Kirchner, L., & Angwin, J. (2016, May 23). ''How we Analyzed the COMPAS Recidivism Algorithm''. ProPublica. <nowiki>https://www.propublica.org/article/how-we-analyzed-the-compas-recidivism-algorithm</nowiki>.</ref>. ProPublica found that a correct prediction of recidivism was made for white and black defendants 59 percent and 63 percent of the time, respectively. This is roughly the same rate. Upon questioning, the company said "it had devised the algorithm to achieve this goal. A test that is correct in equal proportions for all groups cannot be biased.”<ref name=":5" /> Northpointe Inc. even cites other studies within their Practitioner's Guide confirming the success and neutrality of their algorithm.<ref>Northpointe Inc. (2015, March 19). Practitioner's Guide to COMPAS Core. <nowiki>http://www.northpointeinc.com/downloads/compas/Practitioners-Guide-COMPAS-Core-_031915.pdf</nowiki></ref> ProPublica found that Black defendants had uniform scores from 1-10, while White defendants had predominantly lower scores. After adjusting for Black defendants having higher recidivism rates overall, ProPublica found that COMPAS, while maintaining a similar accuracy, is "more likely to misclassify a black defendant as higher risk than a white defendant...the test tended to make the opposite mistake with whites."<ref name=":7" /> ==== Perpetuated Systemic Racism ==== COMPAS perpetuates the historic and structural bias that is found in the criminal system. For example, COMPAS considers one's area of residence. Minority-dominated areas are often more policed, which inflates arrest statistics. If geography correlates to recidivism, then race indirectly does too. Thus, these correlations can be dangerous when not taking validity measures. As a private company, Northpointe has no legal obligation to share details on how COMPAS calculates its score or weighs its variables.<ref name=":4" /> Defendants labeled high/medium risk may be subject to harsher sentencing. The United States Sentencing Commission found that offenders who were sentenced to an incarceration length between 60 to 120 months and over 120 months were significantly less likely to recidivate.<ref>ORD (2020, April). Office of Research and Data, United States Sentencing Commission. ''Length of Incarceration and Recidivism.'' <nowiki>https://www.ussc.gov/sites/default/files/pdf/research-and-publications/research-publications/2020/20200429_Recidivism-SentLength.pdf</nowiki></ref> If a defendant is suspected of being high-risk, they may be given a longer sentence, and be less likely to receive bail or early release. COMPAS’s mislabeling of Black defendants may result in negative consequences despite reported racial neutrality, and could further perpetuate racial inequity in the criminal justice system.<ref name=":6" /> === United States Health Care Management Algorithm === ==== The Algorithm ==== Several U.S. health care systems use commercial algorithms to guide health decisions and target patients for "high-risk care management" programs to help ensure that appropriate care is provided. Most of these programs are beneficial to patients with critical conditions because they have teams of specialized nurses, extra primary care appointment slots, and other scarce resources.<ref name=":1">[https://www.science.org/doi/10.1126/science.aax2342?adobe_mc=MCMID=75787059768315457960559156472529521667%7CMCORGID=242B6472541199F70A4C98A6%40AdobeOrg%7CTS=1638729658 Obermeyer, Z., Powers, B., Vogeli, C., & Mullainathan, S. (2019). Dissecting racial bias in an algorithm used to manage the health of populations. ''Science'', ''366''(6464), 447–453. https://doi.org/10.1126/science.aax2342]</ref> As a result, hospitals and insurance companies have relied on one specific algorithm to minimize the cost for patients while targeting sicker patients that would benefit most from these programs.<ref>[https://www.scientificamerican.com/article/racial-bias-found-in-a-major-health-care-risk-algorithm/ Vartan, S. (2019, October 24). ''Racial bias found in a major health care risk algorithm''. Scientific American. https://www.scientificamerican.com/article/racial-bias-found-in-a-major-health-care-risk-algorithm/.]</ref> In 2019, Obermeyer et al. conducted a study funded by the National Institute for Health Care Management Foundation on this commercial care management algorithm in response to “the growing concern that algorithms may reproduce racial and gender disparities via the people building them or through the data used to train them." This predictive-risk algorithm generated a risk score for each patient to infer their medical needs, which was primarily based on the patient's previous health care spending. Based on the score, patients would be automatically enrolled to the program, referred to their primary care physician for consultation, or no recommendations were made.<ref name=":1" /> The study found that Black patients with the same level of algorithm-predicted risk as White patients had 26.3% more chronic illnesses. Furthermore, researchers found that when looking at specific biomarkers that index the severity of various chronic illnesses (hypertension, diabetes, bad cholesterol, etc.), Black patients had more severe illnesses than White patients with the same risk score. This was due to Black patients generating lower expected medical costs than White patients with the same chronic illnesses. These spending differences resulted in disparities between the perceived level of sicknesses between Black and White patients since the algorithm focused on patient health care spending as it's primary mechanism for producing risk scores.<ref name=":1" /> ==== Perpetuated Systemic Racism ==== The study identifies two systemic causes for reduced health care spending by Blacks that contributed to this algorithm's bias. First, poor patients face several barriers that can impede their access to healthcare despite having health insurance (geography, transportation access, competing demands from jobs or child care, knowledge of reasons to seek care, etc.). Second, race can impact patient spending through either direct discrimination by physicians or changes to the doctor-patient relationship, causing patients to not be recommended for or choosing not to seek further care. These observations demonstrate that accurate methods for decision-making models can indirectly disadvantage specific groups in society and have the ability to perpetuate existing systemic racism.<ref name=":1" /> === The Dutch Childcare Benefit Scandal (Toeslagenaffaire) === The Dutch Childcare Benefit Scandal, known in the Netherlands as the ''Toeslagenaffaire'', serves as a landmark case of how algorithmic bias can lead to systemic human rights violations outside of the United States. Starting in 2013, the Dutch Tax and Customs Administration (''Belastingdienst'') employed a self-learning algorithm to create risk profiles of individuals suspected of childcare benefit fraud. The algorithm utilized "foreign-sounding names" and "dual nationality" as high-risk indicators for fraud.<ref>Amnesty International. (2021, October 25). ''Xenophobic machines: Discriminatory algorithmic detector in the Dutch childcare benefit scandal''. https://www.amnesty.org/en/documents/eur35/4686/2021/en/</ref> Because of the "High Risk" designation generated by the algorithm, tens of thousands of families—predominantly from low-income and ethnic minority backgrounds—were subjected to aggressive debt collection. The tax authorities demanded the immediate repayment of entire years of benefits based on minor clerical errors or mere suspicion. This led to severe financial ruin, divorces, and the illegal removal of children from their homes by social services. The scandal eventually led to the mass resignation of the Dutch cabinet in January 2021.<ref>Heikkilä, M. (2022, March 29). ''Dutch environment of 'institutional racism' led to childcare benefits scandal, report says''. Politico. https://www.politico.eu/article/dutch-institutional-racism-childcare-benefits-scandal-report/</ref> This case highlights the dangers of automation bias, where civil servants deferred to the "objective" output of the risk-scoring system, ignoring the obvious discriminatory variables embedded in the training data. === Generative AI and "Assembled Bias" (Google Gemini) === In early 2024, the launch of Google’s Gemini image generation tool introduced a new dimension of algorithmic bias: over-correction leading to historical inaccuracy. When users prompted the model to generate images of historically specific groups—such as the Founding Fathers of the United States or 1940s German soldiers—the model produced images featuring diverse racial and gender identities that did not align with the historical record.<ref>Milmo, D. (2024, February 22). ''Google pauses Gemini AI chatbot’s ability to generate images of people''. The Guardian. https://www.theguardian.com/technology/2024/feb/22/google-pauses-gemini-ai-chatbot-image-generation-people</ref> This phenomenon is a practical example of "Assembled Bias" discussed earlier in this chapter. The bias was not necessarily present in the original historical training data; rather, it was "assembled" by the developers' safety filters and diversity-tuning layers intended to prevent the exclusion of minority groups in contemporary contexts. While these guardrails were designed to combat the historical underrepresentation of minorities in AI, their application to historical prompts resulted in what critics described as an erasure of historical facts.<ref>Knight, W. (2024, February 27). ''Google’s Gemini AI image bias is a sign of a much larger problem''. Wired. https://www.wired.com/story/google-gemini-ai-image-bias-historical-accuracy/</ref> Google temporarily suspended the tool's ability to generate images of people, illustrating the sociotechnical challenge of balancing the need for diverse representation with the requirement for factual and contextual accuracy. === '''Regulatory Models and the Sociotechnical Divide''' === The failures of Amazon's hiring algorithm<ref name=":0" />, HireVue's facial analysis tools<ref name=":10" />, and the healthcare management algorithm<ref name=":1" /> described above have a common feature: internal auditing and voluntary corporate response did not prevent discriminatory outcomes. What regulatory structures are necessary to address this at a systemic level is contested, and the European Union and United States have taken markedly different approaches. ==== '''The EU AI Act''' ==== The EU AI Act, which entered into force in 2024, does not wait for individual algorithmic failures before intervening<ref>European Parliament. (2024, March 13). Artificial Intelligence Act: MEPs adopt landmark law. ''European Parliament News''. <nowiki>https://www.europarl.europa.eu/news/en/press-room/20240308IPR19015/artificial-intelligence-act-meps-adopt-landmark-law</nowiki></ref>. It assigns risk categories to AI systems prior to deployment. By August 2026, systems classified as "high-risk," including those used in employment, loan lending, and law enforcement, must meet requirements for fundamental rights impact assessments, data governance standards, and human oversight<ref>European Commission. (2024). AI Act. ''Shaping Europe's Digital Future''. <nowiki>https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai</nowiki></ref>. Systems classified as posing "unacceptable risk," including biometric categorization based on sensitive traits and predictive policing algorithms, are banned from deployment<ref>Future of Privacy Forum. (2024). FPF Resources on the EU AI Act. ''FPF Resources''. <nowiki>https://fpf.org/fpf-resources-on-the-eu-ai-act/</nowiki></ref>. ==== '''The U.S. Regulatory Environment''' ==== The United States has no comparable federal law. The EEOC has issued guidance noting that automated screening tools can violate the ADA and Title VII, but this guidance is non-binding. In the absence of federal legislation, state lawmakers have introduced over 1,500 AI-related bills as of 2026<ref>MultiState. (2026). State AI Legislation Tracker 2026: All 50 States. <nowiki>https://www.multistate.ai/artificial-intelligence-ai-legislation</nowiki></ref>. Legislation like the Colorado AI Act targets developers of high-risk systems that make consequential decisions about healthcare, housing, and employment <ref>Colorado General Assembly. (2024). Senate Bill 24-205: Consumer Protections for Artificial Intelligence. <nowiki>https://leg.colorado.gov/bills/sb24-205</nowiki></ref>. These state-level efforts face resistance from tech industry lobbying groups. Arguing that a fragmented compliance environment is unworkable for developers, industry organizations have actively advocated for a unified federal standard that would preempt state AI laws<ref>BSA | The Software Alliance. (2024). 2025 State AI Wave Building After 700 Bills in 2024. ''BSA News & Events''. <nowiki>https://www.bsa.org/news-events/news/2025-state-ai-wave-building-after-700-bills-in-2024</nowiki></ref>. This creates a volatile sociotechnical dynamic, pitting state legislatures, the primary source of binding regulation in this area, in direct conflict with an industry approach that prioritizes removing local barriers to AI development. ==== '''Regulatory Models and Accountability''' ==== The two regulatory models differ in when they require accountability. The EU treats high-risk AI as a product requiring pre-deployment safety assessment, similar to how medical devices are regulated. The U.S. model has generally required harm to occur before legal action follows. The facial recognition cases are illustrative: Buolamwini's findings were published in 2018, but the most consequential policy responses did not come until after Robert Williams's wrongful arrest became public in 2020. Whether pre-deployment regulation or a reactive civil-rights framework more effectively reduces algorithmic harm is an open question, and one that the case studies in this article do not definitively resolve. ==== '''Military AI''' ==== A January executive order by the Trump administration made void a Biden executive order that wanted to establish guardrails for AI by developing processes that protected citizens against harm, specifically protecting citizens' privacy and civil rights <ref>{{Cite web |date=February 28, 2025 |title=Trump administration rolls back Biden AI executive order and launches Stargate project |url=https://www.apaservices.org/practice/business/technology/on-the-horizon/ai-executive-orders |website=American Psychological Association}}</ref>. The executive order stated the official policy of the United States was to sustain and enhance the global AI dominance through a minimally burdensome national policy framework for AI<ref>{{Cite web |last=Trump |first=Donald |date=December 11, 2025 |title=ENSURING A NATIONAL POLICY FRAMEWORK FOR ARTIFICIAL INTELLIGENCE |url=https://www.whitehouse.gov/presidential-actions/2025/12/eliminating-state-law-obstruction-of-national-artificial-intelligence-policy/ |website=THE WHITE HOUSE}}</ref>. Based on this policy, Secretary of Defense Pete Hegseth addressed senior members of the U.S. military talking of how the Department of Defense would become an "AI-first" warfighting force and that the department would unleash experimentation with America's leading AI models<ref>{{Cite web |last=Hegseth |first=Pete |date=January 9, 2025 |title=MEMORANDUM FOR SENIOR PENTAGON LEADERSHIP COMMANDERS OF THE COMBATANT COMMANDS DEFENSE AGENCY AND DOW FIELD ACTIVITY DIRECTORS |url=https://media.defense.gov/2026/Jan/12/2003855671/-1/-1/0/ARTIFICIAL-INTELLIGENCE-STRATEGY-FOR-THE-DEPARTMENT-OF-WAR.PDF}}</ref>. Organizations such as the International Committee of the Red Cross (ICRC) are concerned of AI integration with military operations which they argue could misclassify individuals as "targets" if they perceive linkage to the adversary combatants, however remote or irrelevant. For instance, if both the adversary and non-combatant studied at the same school or, shared a mutual connection, or even invents inexistent patterns, that prompts the targeting of innocent civilians <ref>{{Cite web |last=Alvarez |first=Jimena Sofia Viveros |date=September 4, 2024 |title=The risks and inefficacies of AI systems in military targeting support |url=https://blogs.icrc.org/law-and-policy/2024/09/04/the-risks-and-inefficacies-of-ai-systems-in-military-targeting-support/#:~:text=The%20problem%20is%20that%20AI,the%20targeting%20of%20innocent%20civilians. |archive-date=t |website=blogs.icrc.org}}</ref> AI company Anthropic has also come out concerned, with a statement by CEO Dario Amodei which brings up the concern of fully autonomous weapons being used in war. Specifically, that without proper oversight, fully autonomous weapons cannot be relied upon to exercise the critical judgement that our highly troops exhibit, and that fully autonomous weapons need to be deployed with guardrails, which don't currently exist.<ref>{{Cite web |last=Amodei |first=Dario |date=February 26, 2026 |title=Statement from Dario Amodei on our discussions with the Department of War |url=https://www.anthropic.com/news/statement-department-of-war |website=Anthropic}}</ref> The "AI-first" U.S. military directive is still relatively new, where the effects of such policy won't be clearly seen or understood until the integrated system is used in real world battle conditions. The push to quickly integrate AI that has no safety measures in U.S. military operations, combined with high stakes missions where situations change rapidly, could lead to unintentional consequences such as the mistaken killing of non-combatants. == Conclusion == In the future, algorithmic biases will have an increased impact on human activity.<ref name=":3">Garcia, M. (2016, Dec. 1). Racist in the Machine: The Disturbing Implications of Algorithmic Bias. ''World Policy Journal'', 33(4), 111 - 117.</ref> It is clear that unmonitored, unrestrained production and application of algorithms can be detrimental to various groups of people. The ease with which companies and industries can utilize these algorithms creates an environment where inequitable outcomes are perpetuated. Possible avenues for reducing algorithmic biases include legislation, internal auditing, and community adjudication, as well as increased awareness and a culture of responsibility.<ref name=":3" /> Many of these avenues are primarily social and non-technical, which accords with the socio-technical nature of algorithmic bias. The increased prevalence of algorithmic biases is simply one way in which technology is impacting human life in the U.S, and more broadly, the world. Many other novel technologies with seemingly unlimited potential must be examined carefully before their widespread adoption, as failure to do so can result in harmful consequences, which is the case for many applied algorithms today. Further research is recommended on the impact of legislation on algorithmic bias, the impact of algorithmic bias in countries outside the U.S., and new bias-mitigation techniques. == References == {{reflist}} {{BookCat}} en787fqk5tgoomi4p3no8jf8v5ngiy4 0 438897 4634229 4002816 2026-05-05T08:38:02Z ~2026-26995-93 3581107 Expanded page. 4634229 wikitext text/x-wiki {{Chess Opening Theory/Position|= |Caro-Kann Defence: Finnish Variation |eco=[[Chess/ECOB|B15]] |parent=[[Chess/Caro-Kann Defense|Caro-Kann Defense]] }} = Caro-Kann Defence: Finnish Variation = == 4...h6 == The Finnish Variation. With this move, Black prepares an escape square for their c-bishop's later use. This is usually perceived as passive and is thus rarely seen at higher levels. '''[[/5. Nf3/]]''' is the main move. White develops their knight to its more natural square, ignoring Black's strange pawn move h6. '''[[/5. Bc4/]]''' is another good move, developing the bishop to an active square with good scope, and maybe even preparing Bxf7+ sacrifices to exploit the weakened kingside h6 caused. '''[[/5. Ng3/]]''' is playable. White stops the bishop from coming to f5 so it doesn't gain tempo on the knight nor does it get a chance to go to the newly opened h7. ==Theory table== {{Chess Opening Theory/Table}}. 1.e4 c6 2.d4 d5 3.Nc3 dxe4 4. Nxe4 h6 <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">5</th> </tr> <tr> <th align="right"></th> <td>[[/5. Nf3|Nf3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Bc4|Bc4]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng3|Ng3]] </td> </tr> </table> == References == {{reflist}} {{ChessMid}} {{Wikipedia|Caro-Kann}} {{Chess Opening Theory/Footer}} {{BookCat}} 3ck4k3ufhbi7pvvikr60hywiiiwqarm 4634238 4634229 2026-05-05T09:00:54Z ~2026-26995-93 3581107 Added sideline status. 4634238 wikitext text/x-wiki {{Chess Opening Theory/Position|= |Caro-Kann Defence: Finnish Variation |eco=[[Chess/ECOB|B15]] |parent=[[Chess/Caro-Kann Defense|Caro-Kann Defense]] }} {{Chess/sideline}} = Caro-Kann Defence: Finnish Variation = == 4...h6 == The Finnish Variation. With this move, Black prepares an escape square for their c-bishop's later use. This is usually perceived as passive and is thus rarely seen at higher levels. '''[[/5. Nf3/]]''' is the main move. White develops their knight to its more natural square, ignoring Black's strange pawn move h6. '''[[/5. Bc4/]]''' is another good move, developing the bishop to an active square with good scope, and maybe even preparing Bxf7+ sacrifices to exploit the weakened kingside h6 caused. '''[[/5. Ng3/]]''' is playable. White stops the bishop from coming to f5 so it doesn't gain tempo on the knight nor does it get a chance to go to the newly opened h7. ==Theory table== {{Chess Opening Theory/Table}}. 1.e4 c6 2.d4 d5 3.Nc3 dxe4 4. Nxe4 h6 <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">5</th> </tr> <tr> <th align="right"></th> <td>[[/5. Nf3|Nf3]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Bc4|Bc4]] </td> </tr> <tr> <th align="right"></th> <td>[[/5. Ng3|Ng3]] </td> </tr> </table> == References == {{reflist}} {{ChessMid}} {{Wikipedia|Caro-Kann}} {{Chess Opening Theory/Footer}} {{BookCat}} e2s3x5gbzauqzw8j0m162e4xomeaz1r 3 442343 4634182 4633563 2026-05-04T19:36:12Z Yqj3km 3579825 /* Undeletion request */ new section 4634182 wikitext text/x-wiki {| class="wikitable" |+ ! colspan="3" |Talk Page Archives |- |[[User talk:Kittycataclysm/Archive 2022|2022]] |[[User talk:Kittycataclysm/Archive 2023|2023]] |[[User talk:Kittycataclysm/Archive 2024|2024]] |} == That IP range calculator == Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 23:10, 9 January 2025 (UTC) :Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC) == A merge and unmerge from two years ago == I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 15:55, 10 January 2025 (UTC) :Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC) ::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 16:49, 10 January 2025 (UTC) == Undeletion request == I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary "Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution", so that I can do that. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 19:54, 14 January 2025 (UTC) :Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC) ::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them "bad transwikis"), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 21:19, 14 January 2025 (UTC) == Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow == Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe. If not, I'll use the revision before you contributed since I was the only author. Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions. Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC) ::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC) == Wikibooks community == Hi, @[[User:Kittycataclysm|Kittycataclysm]]! I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together? I am looking forward to join. Thank you! [[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC) :@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC) ::Yes. Do you know place for this? ::Thank you ::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC) :::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC) == Congratulations! == [[File:Admin T-shirt.svg|thumb|You get this now.]] You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 10:33, 29 January 2025 (UTC) :Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC) == Is there a way to contact a Steward on WikiBooks? == Hi {{PAGENAME}}, Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here at [[Special:ActiveUsers?username=&groups%5B%5D=steward&wpFormIdentifier=specialactiveusers]] but nothing shows up. The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not find this backward link. I tried to ask about this on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. Is there a way wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC) :@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC) <s>:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.</s> Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC) ::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else: ::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to. ::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC) :::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC) ::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF). It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more. The wmf has been hosting a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it. ::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier: ::::* "Some wikibookians prefer for various reasons to post only at wb" ::::* "The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it" ::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC) == [[Crystal ball]] == That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 03:04, 9 February 2025 (UTC) :Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC) == Question about an edit suggestion == Hi Kittycataclysm, Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient? Any specific recommendations you have would be greatly appreciated! Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]] Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC) :Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC) ::Following up on this—I noticed that you use the term "paper". However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC) == Talkback == {{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC) :@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC) == Hello == Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC) :I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC) :::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC) ::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC) == Cookbook == Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC) :Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC) ::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC) ::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC) :::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC) ::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC) :::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from "____ recipes" in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC) ::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC) :::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC) ::::::::I see you already had the same thought as me. I think all categories should include "for" or "using". Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC) :::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC) :Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC) == More Table of Content Edits == Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days. * Fix Bread wikilink * Remove "Creaming" from techniques, redirected to Mixing * [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized * [[Cookbook:Low-Carb]] points to redirect, needs capitalized * [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity * Remove the S from the cuisine wikilinks on ToC, currently redirecting * Create [[:Category:Lunch recipes]], wikilink to ToC * Wikilink [[Cookbook:Dessert]] under Meals * Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category * Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC * Change "Introductory Matter" header to just "Introduction" * Appendix and Equipment sections switch places Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC) :I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC) :Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below: :* {{xt|Fix Bread wikilink}} {{done}} :* {{xt|Remove "Creaming" from techniques, redirected to Mixing}} see below comments on TOC. :* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can! :* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above. :* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form "Cuisine of ____". It could be good to standardize, and I had been planning to do that once I got around to the cuisines. :* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects :* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page :* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}} :* {{xt|Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below. :* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines. :* {{xt|Change "Introductory Matter" header to just "Introduction"}} The reason I made it "Introductory Matter" instead of "Introduction" is because there's already a chapter itself titled "Introduction"—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. "Front Matter", which is a generally accepted book term) :* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC. :* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel. :Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC) ::Thanks for the notes! Here's my thoughts: ::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. "[[Cookbook:African Cuisine]]", and I think that shorter titles are preferable where it makes sense. ::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one "Asian Cuisine", but put the different locales under separate headers? ::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as "brunch" to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch. ::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say "Introductory Matter", or "Front Matter" as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC. ::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything. ::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it. ::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC) :::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC) ::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC) :::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC) == Cookbook ToC == Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC) :@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC) ::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go. ::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help. ::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like "I'm sorry that you feel that way" was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC) :::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC) ::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC) == [[Cookbook:Polish Doughnuts (Paczki)]] == Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC) :I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC) == [[Cookbook:Cream Cheese American Buttercream]] == Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC) == [[A Companion to Our Literary Journey]] == Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC) :Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC) == Exercising care with copyright == When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 18:32, 21 March 2025 (UTC) :Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC) == Splitting Pages == Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC) :@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:44, 29 March 2025 (UTC) :Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC) ::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC) == Minecraft book == Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC) :@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC) ::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC) :::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC) ::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC) == Request to Review Adjusted User Page (XoriantTeam) == Hello [[User:Kittycataclysm|Kittycataclysm]], I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check. I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation. If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method. Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments. Best regards, XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC) :Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC) == Planning to use AWB to update categories on the cookbook == Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC) :: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC) :::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC) == Tool for even faster category changes == See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:36, 19 June 2025 (UTC) :@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC) ::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just <kbd>Ctrl+Shift+R</kbd> once or twice. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:55, 19 June 2025 (UTC) :::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC) == Advice on when I should run for adminship == Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below: Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.<br> Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters). A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted. I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC) :: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC) ::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC) ::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC) ::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC) == how is it you feel able to interfere in my sandbox? == you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site. now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere. -- [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC) :Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC) ::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC) ::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC) :::No worries—it looks like you didn't add the prefix "User:" before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with "'''User:'''VulcanWikiEdit/sandbox", and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC) ::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC) :::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC) == Regarding the user Codename Tameirao == Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 23:51, 12 August 2025 (UTC) :I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC) :: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 16:30, 9 September 2025 (UTC) :::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC) :::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC) ::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC) ::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC) == IP block exempt == Hi Kitty, I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 10:51, 22 August 2025 (UTC) :Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC) ::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:25, 23 August 2025 (UTC) ::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:35, 23 August 2025 (UTC) == You've got mail! == {{You've got mail|sig=<span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 00:20, 6 September 2025 (UTC)}} :Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC) == Are you able to import? == I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC) : [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC) ::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC) ::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC) ::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC) :::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:11, 6 October 2025 (UTC) :::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC) :::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC) ::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC) == About the category parameter in the recipe summary template == When it uses a "recipe by type" category, should it use a "[type/food] recipes" name or "Recipes for [type/food]"? I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC) :: Probably, but I will say the following below (for my first sentence) to clarify: :: On the <code>|category =</code> parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC) == Please no more Unicode LTA == Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&#126;2025-30839-28|&#126;2025-30839-28]] ([[User talk:&#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC) :<small>I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here</small> I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:13, 5 November 2025 (UTC) ::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:23, 5 November 2025 (UTC) :::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC) == Administrator and reviewer user right combinations are not needed anymore == Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC) :Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC) :: The thing is, administrators have the <code>review</code> user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC) ::: @[[User:Kittycataclysm|Kittycataclysm]] <s>I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.</s> ({{doing}}) [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:24, 12 November 2025 (UTC) : I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC) == Nesting in Open Book of Ecovillages and Eco Communities == Hi Kittycataclysm, I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].) Yes, It will be not an average book but above the regular. This is the exact case: ''"this may be appropriate, such as with large textbooks that contain subsections with a lot of content."'' ''for to establish good structural and stylistic practices'' I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name''' The goal of this system to open bridge + experience highway for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion. I am kindly asking to revert your edits in this book. After that I will put a notification template about "This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page." Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC) :Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]: :* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace. :* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer. :* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions. :Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC) ::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed? :::The <u> local manual of style</u> development is ongoing together with the sample pages. ::'''MAIN PAGE''' ::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc. ::'''NESTING ''' :::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]] :::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] ::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]] ::: ::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC) :::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC) ::::It makes no sense to have some crazy abbreviation as a "main page" or "namespace" (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, "Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History." Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC) :::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC) ::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC) == Deletions of Wikibook subpages == Hello @[[User:Kittycataclysm|Kittycataclysm]], regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly. Best, Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC) :Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC) ::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time. ::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC) :::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC) == help with "Media Literacy and You" == {{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove <nowiki>{{Qr-em|not clear how this is to be structured as a book}}</nowiki>? I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the "Discussion" page associated with that book and by upgrading the content. The upgrades included adding the "Introduction" chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. ??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC) :Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC) ::{{re|Kittycataclysm}} ::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of "The wisdom of polarized crowds" discussed in [[Wikipedia:Reliability of Wikipedia]]. ::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. === Who is DavidMCEddy === ::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged] * 6,000+ edits in each of Wikipedia and Wikiversity, * 1,000+ in Wikimedia Commons, * 30,000+ in Wikidata, and * almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly "Media & Democracy" series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create "a world in which every single person on the planet is given free access to the sum of all human knowledge." Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC) ::{{re|Kittycataclysm}} ::"Media Literacy and You" is textbook to support both self study and classes on media literacy. ::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc. ::I think this "Media Literacy and You" project would lose the vast majority of its potential if it were not on Wikibooks. ::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC) {{outdent}} {{re|Kittycataclysm}} Will you please help me with the protocols of creating a book on Wikiversity? 1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the "Book creator" tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 2. What do you suggest I do next? :I can create an article on Wikiversity titled, "Media Literacy and You", and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. :If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports <nowiki>{{cite Q|...}}</nowiki>, which I have used extensively for years.) :Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC) ::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC) == Thank you! == Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC) :It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC) ::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC) == A test request == Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 01:49, 30 March 2026 (UTC) :Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC) == Linking == Hi,<br> For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information & seems relevant.<br> Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC) :@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC) ::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC) :::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Undeletion request == Hello, I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC) plkm8kgswe243afmkld6iwauz4faeec 4634187 4634182 2026-05-04T20:03:28Z Norton 379181 /* Undeletion request */ new section 4634187 wikitext text/x-wiki {| class="wikitable" |+ ! colspan="3" |Talk Page Archives |- |[[User talk:Kittycataclysm/Archive 2022|2022]] |[[User talk:Kittycataclysm/Archive 2023|2023]] |[[User talk:Kittycataclysm/Archive 2024|2024]] |} == That IP range calculator == Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 23:10, 9 January 2025 (UTC) :Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC) == A merge and unmerge from two years ago == I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 15:55, 10 January 2025 (UTC) :Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC) ::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 16:49, 10 January 2025 (UTC) == Undeletion request == I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary "Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution", so that I can do that. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 19:54, 14 January 2025 (UTC) :Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC) ::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them "bad transwikis"), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 21:19, 14 January 2025 (UTC) == Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow == Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe. If not, I'll use the revision before you contributed since I was the only author. Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions. Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC) ::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC) == Wikibooks community == Hi, @[[User:Kittycataclysm|Kittycataclysm]]! I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together? I am looking forward to join. Thank you! [[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC) :@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC) ::Yes. Do you know place for this? ::Thank you ::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC) :::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC) == Congratulations! == [[File:Admin T-shirt.svg|thumb|You get this now.]] You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 10:33, 29 January 2025 (UTC) :Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC) == Is there a way to contact a Steward on WikiBooks? == Hi {{PAGENAME}}, Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here at [[Special:ActiveUsers?username=&groups%5B%5D=steward&wpFormIdentifier=specialactiveusers]] but nothing shows up. The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not find this backward link. I tried to ask about this on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. Is there a way wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC) :@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC) <s>:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.</s> Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC) ::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else: ::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to. ::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC) :::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC) ::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF). It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more. The wmf has been hosting a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it. ::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier: ::::* "Some wikibookians prefer for various reasons to post only at wb" ::::* "The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it" ::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC) == [[Crystal ball]] == That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 03:04, 9 February 2025 (UTC) :Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC) == Question about an edit suggestion == Hi Kittycataclysm, Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient? Any specific recommendations you have would be greatly appreciated! Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]] Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC) :Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC) ::Following up on this—I noticed that you use the term "paper". However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC) == Talkback == {{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC) :@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC) == Hello == Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC) :I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC) :::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC) ::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC) == Cookbook == Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC) :Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC) ::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC) ::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC) :::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC) ::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC) :::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from "____ recipes" in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC) ::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC) :::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC) ::::::::I see you already had the same thought as me. I think all categories should include "for" or "using". Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC) :::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC) :Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC) == More Table of Content Edits == Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days. * Fix Bread wikilink * Remove "Creaming" from techniques, redirected to Mixing * [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized * [[Cookbook:Low-Carb]] points to redirect, needs capitalized * [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity * Remove the S from the cuisine wikilinks on ToC, currently redirecting * Create [[:Category:Lunch recipes]], wikilink to ToC * Wikilink [[Cookbook:Dessert]] under Meals * Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category * Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC * Change "Introductory Matter" header to just "Introduction" * Appendix and Equipment sections switch places Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC) :I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC) :Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below: :* {{xt|Fix Bread wikilink}} {{done}} :* {{xt|Remove "Creaming" from techniques, redirected to Mixing}} see below comments on TOC. :* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can! :* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above. :* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form "Cuisine of ____". It could be good to standardize, and I had been planning to do that once I got around to the cuisines. :* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects :* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page :* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}} :* {{xt|Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below. :* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines. :* {{xt|Change "Introductory Matter" header to just "Introduction"}} The reason I made it "Introductory Matter" instead of "Introduction" is because there's already a chapter itself titled "Introduction"—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. "Front Matter", which is a generally accepted book term) :* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC. :* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel. :Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC) ::Thanks for the notes! Here's my thoughts: ::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. "[[Cookbook:African Cuisine]]", and I think that shorter titles are preferable where it makes sense. ::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one "Asian Cuisine", but put the different locales under separate headers? ::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as "brunch" to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch. ::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say "Introductory Matter", or "Front Matter" as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC. ::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything. ::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it. ::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC) :::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC) ::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC) :::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC) == Cookbook ToC == Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC) :@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC) ::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go. ::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help. ::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like "I'm sorry that you feel that way" was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC) :::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC) ::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC) == [[Cookbook:Polish Doughnuts (Paczki)]] == Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC) :I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC) == [[Cookbook:Cream Cheese American Buttercream]] == Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC) == [[A Companion to Our Literary Journey]] == Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC) :Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC) == Exercising care with copyright == When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 18:32, 21 March 2025 (UTC) :Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC) == Splitting Pages == Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC) :@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:44, 29 March 2025 (UTC) :Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC) ::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC) == Minecraft book == Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC) :@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC) ::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC) :::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC) ::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC) == Request to Review Adjusted User Page (XoriantTeam) == Hello [[User:Kittycataclysm|Kittycataclysm]], I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check. I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation. If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method. Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments. Best regards, XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC) :Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC) == Planning to use AWB to update categories on the cookbook == Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC) :: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC) :::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC) == Tool for even faster category changes == See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:36, 19 June 2025 (UTC) :@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC) ::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just <kbd>Ctrl+Shift+R</kbd> once or twice. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:55, 19 June 2025 (UTC) :::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC) == Advice on when I should run for adminship == Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below: Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.<br> Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters). A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted. I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC) :: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC) ::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC) ::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC) ::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC) == how is it you feel able to interfere in my sandbox? == you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site. now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere. -- [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC) :Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC) ::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC) ::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC) :::No worries—it looks like you didn't add the prefix "User:" before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with "'''User:'''VulcanWikiEdit/sandbox", and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC) ::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC) :::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC) == Regarding the user Codename Tameirao == Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 23:51, 12 August 2025 (UTC) :I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC) :: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 16:30, 9 September 2025 (UTC) :::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC) :::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC) ::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC) ::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC) == IP block exempt == Hi Kitty, I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 10:51, 22 August 2025 (UTC) :Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC) ::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:25, 23 August 2025 (UTC) ::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:35, 23 August 2025 (UTC) == You've got mail! == {{You've got mail|sig=<span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 00:20, 6 September 2025 (UTC)}} :Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC) == Are you able to import? == I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC) : [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC) ::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC) ::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC) ::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC) :::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:11, 6 October 2025 (UTC) :::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC) :::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC) ::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC) == About the category parameter in the recipe summary template == When it uses a "recipe by type" category, should it use a "[type/food] recipes" name or "Recipes for [type/food]"? I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC) :: Probably, but I will say the following below (for my first sentence) to clarify: :: On the <code>|category =</code> parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC) == Please no more Unicode LTA == Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&#126;2025-30839-28|&#126;2025-30839-28]] ([[User talk:&#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC) :<small>I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here</small> I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:13, 5 November 2025 (UTC) ::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:23, 5 November 2025 (UTC) :::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC) == Administrator and reviewer user right combinations are not needed anymore == Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC) :Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC) :: The thing is, administrators have the <code>review</code> user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC) ::: @[[User:Kittycataclysm|Kittycataclysm]] <s>I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.</s> ({{doing}}) [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:24, 12 November 2025 (UTC) : I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC) == Nesting in Open Book of Ecovillages and Eco Communities == Hi Kittycataclysm, I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].) Yes, It will be not an average book but above the regular. This is the exact case: ''"this may be appropriate, such as with large textbooks that contain subsections with a lot of content."'' ''for to establish good structural and stylistic practices'' I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name''' The goal of this system to open bridge + experience highway for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion. I am kindly asking to revert your edits in this book. After that I will put a notification template about "This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page." Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC) :Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]: :* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace. :* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer. :* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions. :Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC) ::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed? :::The <u> local manual of style</u> development is ongoing together with the sample pages. ::'''MAIN PAGE''' ::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc. ::'''NESTING ''' :::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]] :::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] ::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]] ::: ::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC) :::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC) ::::It makes no sense to have some crazy abbreviation as a "main page" or "namespace" (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, "Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History." Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC) :::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC) ::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC) == Deletions of Wikibook subpages == Hello @[[User:Kittycataclysm|Kittycataclysm]], regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly. Best, Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC) :Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC) ::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time. ::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC) :::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC) == help with "Media Literacy and You" == {{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove <nowiki>{{Qr-em|not clear how this is to be structured as a book}}</nowiki>? I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the "Discussion" page associated with that book and by upgrading the content. The upgrades included adding the "Introduction" chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. ??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC) :Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC) ::{{re|Kittycataclysm}} ::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of "The wisdom of polarized crowds" discussed in [[Wikipedia:Reliability of Wikipedia]]. ::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. === Who is DavidMCEddy === ::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged] * 6,000+ edits in each of Wikipedia and Wikiversity, * 1,000+ in Wikimedia Commons, * 30,000+ in Wikidata, and * almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly "Media & Democracy" series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create "a world in which every single person on the planet is given free access to the sum of all human knowledge." Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC) ::{{re|Kittycataclysm}} ::"Media Literacy and You" is textbook to support both self study and classes on media literacy. ::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc. ::I think this "Media Literacy and You" project would lose the vast majority of its potential if it were not on Wikibooks. ::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC) {{outdent}} {{re|Kittycataclysm}} Will you please help me with the protocols of creating a book on Wikiversity? 1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the "Book creator" tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 2. What do you suggest I do next? :I can create an article on Wikiversity titled, "Media Literacy and You", and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. :If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports <nowiki>{{cite Q|...}}</nowiki>, which I have used extensively for years.) :Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC) ::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC) == Thank you! == Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC) :It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC) ::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC) == A test request == Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 01:49, 30 March 2026 (UTC) :Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC) == Linking == Hi,<br> For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information & seems relevant.<br> Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC) :@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC) ::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC) :::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Undeletion request == Hello, I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC) == Undeletion request == About the page on Lentis called Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad: I, too, request undeletion, please. If the authors made any msitakes, the fault is 100 percent mine, for failing to guide them correctly. Like all chapters in this book, this team's chapter is a class assignment. I will be interested also in the reason for deletion so that I can guide authors better. I want to help my students be constructive contributors. Many thanks! [[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 20:03, 4 May 2026 (UTC) 5c70sylelyygsx2gd5y0gkrojrzu2u1 4634192 4634187 2026-05-04T22:14:32Z Kittycataclysm 3371989 /* Undeletion request 3 */ Reply 4634192 wikitext text/x-wiki {| class="wikitable" |+ ! colspan="3" |Talk Page Archives |- |[[User talk:Kittycataclysm/Archive 2022|2022]] |[[User talk:Kittycataclysm/Archive 2023|2023]] |[[User talk:Kittycataclysm/Archive 2024|2024]] |} == That IP range calculator == Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 23:10, 9 January 2025 (UTC) :Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC) == A merge and unmerge from two years ago == I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 15:55, 10 January 2025 (UTC) :Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC) ::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 16:49, 10 January 2025 (UTC) == Undeletion request == I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary "Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution", so that I can do that. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 19:54, 14 January 2025 (UTC) :Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC) ::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them "bad transwikis"), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 21:19, 14 January 2025 (UTC) == Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow == Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe. If not, I'll use the revision before you contributed since I was the only author. Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions. Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC) ::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC) == Wikibooks community == Hi, @[[User:Kittycataclysm|Kittycataclysm]]! I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together? I am looking forward to join. Thank you! [[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC) :@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC) ::Yes. Do you know place for this? ::Thank you ::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC) :::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC) == Congratulations! == [[File:Admin T-shirt.svg|thumb|You get this now.]] You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 10:33, 29 January 2025 (UTC) :Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC) == Is there a way to contact a Steward on WikiBooks? == Hi {{PAGENAME}}, Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here at [[Special:ActiveUsers?username=&groups%5B%5D=steward&wpFormIdentifier=specialactiveusers]] but nothing shows up. The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not find this backward link. I tried to ask about this on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. Is there a way wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC) :@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC) <s>:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.</s> Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC) ::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else: ::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to. ::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC) :::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC) ::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF). It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more. The wmf has been hosting a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it. ::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier: ::::* "Some wikibookians prefer for various reasons to post only at wb" ::::* "The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it" ::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC) == [[Crystal ball]] == That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 03:04, 9 February 2025 (UTC) :Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC) == Question about an edit suggestion == Hi Kittycataclysm, Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient? Any specific recommendations you have would be greatly appreciated! Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]] Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC) :Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC) ::Following up on this—I noticed that you use the term "paper". However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC) == Talkback == {{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC) :@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC) == Hello == Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC) :I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC) :::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC) ::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC) == Cookbook == Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC) :Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC) ::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC) ::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC) :::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC) ::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC) :::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from "____ recipes" in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC) ::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC) :::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC) ::::::::I see you already had the same thought as me. I think all categories should include "for" or "using". Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC) :::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC) :Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC) == More Table of Content Edits == Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days. * Fix Bread wikilink * Remove "Creaming" from techniques, redirected to Mixing * [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized * [[Cookbook:Low-Carb]] points to redirect, needs capitalized * [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity * Remove the S from the cuisine wikilinks on ToC, currently redirecting * Create [[:Category:Lunch recipes]], wikilink to ToC * Wikilink [[Cookbook:Dessert]] under Meals * Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category * Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC * Change "Introductory Matter" header to just "Introduction" * Appendix and Equipment sections switch places Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC) :I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC) :Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below: :* {{xt|Fix Bread wikilink}} {{done}} :* {{xt|Remove "Creaming" from techniques, redirected to Mixing}} see below comments on TOC. :* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can! :* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above. :* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form "Cuisine of ____". It could be good to standardize, and I had been planning to do that once I got around to the cuisines. :* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects :* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page :* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}} :* {{xt|Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below. :* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines. :* {{xt|Change "Introductory Matter" header to just "Introduction"}} The reason I made it "Introductory Matter" instead of "Introduction" is because there's already a chapter itself titled "Introduction"—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. "Front Matter", which is a generally accepted book term) :* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC. :* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel. :Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC) ::Thanks for the notes! Here's my thoughts: ::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. "[[Cookbook:African Cuisine]]", and I think that shorter titles are preferable where it makes sense. ::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one "Asian Cuisine", but put the different locales under separate headers? ::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as "brunch" to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch. ::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say "Introductory Matter", or "Front Matter" as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC. ::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything. ::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it. ::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC) :::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC) ::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC) :::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC) == Cookbook ToC == Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC) :@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC) ::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go. ::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help. ::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like "I'm sorry that you feel that way" was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC) :::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC) ::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC) == [[Cookbook:Polish Doughnuts (Paczki)]] == Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC) :I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC) == [[Cookbook:Cream Cheese American Buttercream]] == Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC) == [[A Companion to Our Literary Journey]] == Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC) :Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC) == Exercising care with copyright == When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 18:32, 21 March 2025 (UTC) :Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC) == Splitting Pages == Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC) :@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:44, 29 March 2025 (UTC) :Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC) ::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC) == Minecraft book == Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC) :@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC) ::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC) :::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC) ::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC) == Request to Review Adjusted User Page (XoriantTeam) == Hello [[User:Kittycataclysm|Kittycataclysm]], I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check. I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation. If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method. Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments. Best regards, XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC) :Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC) == Planning to use AWB to update categories on the cookbook == Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC) :: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC) :::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC) == Tool for even faster category changes == See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:36, 19 June 2025 (UTC) :@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC) ::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just <kbd>Ctrl+Shift+R</kbd> once or twice. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:55, 19 June 2025 (UTC) :::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC) == Advice on when I should run for adminship == Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below: Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.<br> Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters). A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted. I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC) :: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC) ::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC) ::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC) ::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC) == how is it you feel able to interfere in my sandbox? == you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site. now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere. -- [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC) :Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC) ::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC) ::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC) :::No worries—it looks like you didn't add the prefix "User:" before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with "'''User:'''VulcanWikiEdit/sandbox", and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC) ::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC) :::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC) == Regarding the user Codename Tameirao == Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 23:51, 12 August 2025 (UTC) :I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC) :: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 16:30, 9 September 2025 (UTC) :::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC) :::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC) ::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC) ::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC) == IP block exempt == Hi Kitty, I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 10:51, 22 August 2025 (UTC) :Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC) ::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:25, 23 August 2025 (UTC) ::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:35, 23 August 2025 (UTC) == You've got mail! == {{You've got mail|sig=<span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 00:20, 6 September 2025 (UTC)}} :Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC) == Are you able to import? == I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC) : [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC) ::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC) ::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC) ::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC) :::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:11, 6 October 2025 (UTC) :::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC) :::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC) ::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC) == About the category parameter in the recipe summary template == When it uses a "recipe by type" category, should it use a "[type/food] recipes" name or "Recipes for [type/food]"? I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC) :: Probably, but I will say the following below (for my first sentence) to clarify: :: On the <code>|category =</code> parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC) == Please no more Unicode LTA == Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&#126;2025-30839-28|&#126;2025-30839-28]] ([[User talk:&#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC) :<small>I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here</small> I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:13, 5 November 2025 (UTC) ::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:23, 5 November 2025 (UTC) :::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC) == Administrator and reviewer user right combinations are not needed anymore == Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC) :Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC) :: The thing is, administrators have the <code>review</code> user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC) ::: @[[User:Kittycataclysm|Kittycataclysm]] <s>I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.</s> ({{doing}}) [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:24, 12 November 2025 (UTC) : I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC) == Nesting in Open Book of Ecovillages and Eco Communities == Hi Kittycataclysm, I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].) Yes, It will be not an average book but above the regular. This is the exact case: ''"this may be appropriate, such as with large textbooks that contain subsections with a lot of content."'' ''for to establish good structural and stylistic practices'' I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name''' The goal of this system to open bridge + experience highway for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion. I am kindly asking to revert your edits in this book. After that I will put a notification template about "This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page." Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC) :Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]: :* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace. :* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer. :* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions. :Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC) ::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed? :::The <u> local manual of style</u> development is ongoing together with the sample pages. ::'''MAIN PAGE''' ::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc. ::'''NESTING ''' :::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]] :::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] ::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]] ::: ::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC) :::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC) ::::It makes no sense to have some crazy abbreviation as a "main page" or "namespace" (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, "Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History." Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC) :::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC) ::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC) == Deletions of Wikibook subpages == Hello @[[User:Kittycataclysm|Kittycataclysm]], regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly. Best, Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC) :Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC) ::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time. ::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC) :::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC) == help with "Media Literacy and You" == {{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove <nowiki>{{Qr-em|not clear how this is to be structured as a book}}</nowiki>? I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the "Discussion" page associated with that book and by upgrading the content. The upgrades included adding the "Introduction" chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. ??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC) :Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC) ::{{re|Kittycataclysm}} ::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of "The wisdom of polarized crowds" discussed in [[Wikipedia:Reliability of Wikipedia]]. ::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. === Who is DavidMCEddy === ::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged] * 6,000+ edits in each of Wikipedia and Wikiversity, * 1,000+ in Wikimedia Commons, * 30,000+ in Wikidata, and * almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly "Media & Democracy" series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create "a world in which every single person on the planet is given free access to the sum of all human knowledge." Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC) ::{{re|Kittycataclysm}} ::"Media Literacy and You" is textbook to support both self study and classes on media literacy. ::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc. ::I think this "Media Literacy and You" project would lose the vast majority of its potential if it were not on Wikibooks. ::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC) {{outdent}} {{re|Kittycataclysm}} Will you please help me with the protocols of creating a book on Wikiversity? 1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the "Book creator" tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 2. What do you suggest I do next? :I can create an article on Wikiversity titled, "Media Literacy and You", and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. :If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports <nowiki>{{cite Q|...}}</nowiki>, which I have used extensively for years.) :Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC) ::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC) == Thank you! == Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC) :It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC) ::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC) == A test request == Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 01:49, 30 March 2026 (UTC) :Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC) == Linking == Hi,<br> For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information & seems relevant.<br> Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC) :@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC) ::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC) :::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Undeletion request == Hello, I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC) == Undeletion request == About the page on Lentis called Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad: I, too, request undeletion, please. If the authors made any msitakes, the fault is 100 percent mine, for failing to guide them correctly. Like all chapters in this book, this team's chapter is a class assignment. I will be interested also in the reason for deletion so that I can guide authors better. I want to help my students be constructive contributors. Many thanks! [[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 20:03, 4 May 2026 (UTC) :Hi @[[User:Norton|Norton]] and thanks for the ping! I deleted it because it was not titled/filed correctly, so I didn't realize it was part of [[Lentis]]. I have undeleted it and moved it to [[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:14, 4 May 2026 (UTC) damxxt3qivvlmb5xntz6yo7a0l7zhbh 4634193 4634192 2026-05-04T22:15:08Z Kittycataclysm 3371989 /* Undeletion request 2 */ Reply 4634193 wikitext text/x-wiki {| class="wikitable" |+ ! colspan="3" |Talk Page Archives |- |[[User talk:Kittycataclysm/Archive 2022|2022]] |[[User talk:Kittycataclysm/Archive 2023|2023]] |[[User talk:Kittycataclysm/Archive 2024|2024]] |} == That IP range calculator == Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 23:10, 9 January 2025 (UTC) :Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC) == A merge and unmerge from two years ago == I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 15:55, 10 January 2025 (UTC) :Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC) ::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 16:49, 10 January 2025 (UTC) == Undeletion request == I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary "Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution", so that I can do that. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 19:54, 14 January 2025 (UTC) :Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC) ::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them "bad transwikis"), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 21:19, 14 January 2025 (UTC) == Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow == Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe. If not, I'll use the revision before you contributed since I was the only author. Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions. Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC) ::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC) == Wikibooks community == Hi, @[[User:Kittycataclysm|Kittycataclysm]]! I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together? I am looking forward to join. Thank you! [[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC) :@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC) ::Yes. Do you know place for this? ::Thank you ::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC) :::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC) == Congratulations! == [[File:Admin T-shirt.svg|thumb|You get this now.]] You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 10:33, 29 January 2025 (UTC) :Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC) == Is there a way to contact a Steward on WikiBooks? == Hi {{PAGENAME}}, Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here at [[Special:ActiveUsers?username=&groups%5B%5D=steward&wpFormIdentifier=specialactiveusers]] but nothing shows up. The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not find this backward link. I tried to ask about this on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. Is there a way wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC) :@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC) <s>:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.</s> Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC) ::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else: ::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to. ::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC) :::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC) ::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF). It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more. The wmf has been hosting a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it. ::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier: ::::* "Some wikibookians prefer for various reasons to post only at wb" ::::* "The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it" ::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC) == [[Crystal ball]] == That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 03:04, 9 February 2025 (UTC) :Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC) == Question about an edit suggestion == Hi Kittycataclysm, Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient? Any specific recommendations you have would be greatly appreciated! Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]] Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC) :Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC) ::Following up on this—I noticed that you use the term "paper". However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC) == Talkback == {{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC) :@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC) == Hello == Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC) :I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC) :::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC) ::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC) == Cookbook == Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC) :Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC) ::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC) ::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC) :::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC) ::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC) :::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from "____ recipes" in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC) ::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC) :::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC) ::::::::I see you already had the same thought as me. I think all categories should include "for" or "using". Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC) :::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC) :Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC) == More Table of Content Edits == Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days. * Fix Bread wikilink * Remove "Creaming" from techniques, redirected to Mixing * [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized * [[Cookbook:Low-Carb]] points to redirect, needs capitalized * [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity * Remove the S from the cuisine wikilinks on ToC, currently redirecting * Create [[:Category:Lunch recipes]], wikilink to ToC * Wikilink [[Cookbook:Dessert]] under Meals * Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category * Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC * Change "Introductory Matter" header to just "Introduction" * Appendix and Equipment sections switch places Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC) :I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC) :Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below: :* {{xt|Fix Bread wikilink}} {{done}} :* {{xt|Remove "Creaming" from techniques, redirected to Mixing}} see below comments on TOC. :* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can! :* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above. :* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form "Cuisine of ____". It could be good to standardize, and I had been planning to do that once I got around to the cuisines. :* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects :* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page :* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}} :* {{xt|Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below. :* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines. :* {{xt|Change "Introductory Matter" header to just "Introduction"}} The reason I made it "Introductory Matter" instead of "Introduction" is because there's already a chapter itself titled "Introduction"—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. "Front Matter", which is a generally accepted book term) :* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC. :* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel. :Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC) ::Thanks for the notes! Here's my thoughts: ::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. "[[Cookbook:African Cuisine]]", and I think that shorter titles are preferable where it makes sense. ::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one "Asian Cuisine", but put the different locales under separate headers? ::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as "brunch" to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch. ::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say "Introductory Matter", or "Front Matter" as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC. ::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything. ::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it. ::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC) :::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC) ::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC) :::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC) == Cookbook ToC == Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC) :@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC) ::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go. ::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help. ::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like "I'm sorry that you feel that way" was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC) :::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC) ::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC) == [[Cookbook:Polish Doughnuts (Paczki)]] == Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC) :I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC) == [[Cookbook:Cream Cheese American Buttercream]] == Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC) == [[A Companion to Our Literary Journey]] == Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC) :Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC) == Exercising care with copyright == When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 18:32, 21 March 2025 (UTC) :Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC) == Splitting Pages == Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC) :@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:44, 29 March 2025 (UTC) :Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC) ::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC) == Minecraft book == Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC) :@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC) ::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC) :::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC) ::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC) == Request to Review Adjusted User Page (XoriantTeam) == Hello [[User:Kittycataclysm|Kittycataclysm]], I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check. I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation. If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method. Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments. Best regards, XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC) :Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC) == Planning to use AWB to update categories on the cookbook == Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC) :: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC) :::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC) == Tool for even faster category changes == See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:36, 19 June 2025 (UTC) :@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC) ::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just <kbd>Ctrl+Shift+R</kbd> once or twice. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:55, 19 June 2025 (UTC) :::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC) == Advice on when I should run for adminship == Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below: Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.<br> Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters). A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted. I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC) :: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC) ::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC) ::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC) ::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC) == how is it you feel able to interfere in my sandbox? == you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site. now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere. -- [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC) :Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC) ::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC) ::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC) :::No worries—it looks like you didn't add the prefix "User:" before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with "'''User:'''VulcanWikiEdit/sandbox", and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC) ::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC) :::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC) == Regarding the user Codename Tameirao == Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 23:51, 12 August 2025 (UTC) :I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC) :: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 16:30, 9 September 2025 (UTC) :::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC) :::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC) ::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC) ::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC) == IP block exempt == Hi Kitty, I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 10:51, 22 August 2025 (UTC) :Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC) ::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:25, 23 August 2025 (UTC) ::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:35, 23 August 2025 (UTC) == You've got mail! == {{You've got mail|sig=<span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 00:20, 6 September 2025 (UTC)}} :Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC) == Are you able to import? == I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC) : [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC) ::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC) ::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC) ::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC) :::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:11, 6 October 2025 (UTC) :::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC) :::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC) ::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC) == About the category parameter in the recipe summary template == When it uses a "recipe by type" category, should it use a "[type/food] recipes" name or "Recipes for [type/food]"? I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC) :: Probably, but I will say the following below (for my first sentence) to clarify: :: On the <code>|category =</code> parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC) == Please no more Unicode LTA == Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&#126;2025-30839-28|&#126;2025-30839-28]] ([[User talk:&#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC) :<small>I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here</small> I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:13, 5 November 2025 (UTC) ::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:23, 5 November 2025 (UTC) :::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC) == Administrator and reviewer user right combinations are not needed anymore == Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC) :Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC) :: The thing is, administrators have the <code>review</code> user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC) ::: @[[User:Kittycataclysm|Kittycataclysm]] <s>I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.</s> ({{doing}}) [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:24, 12 November 2025 (UTC) : I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC) == Nesting in Open Book of Ecovillages and Eco Communities == Hi Kittycataclysm, I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].) Yes, It will be not an average book but above the regular. This is the exact case: ''"this may be appropriate, such as with large textbooks that contain subsections with a lot of content."'' ''for to establish good structural and stylistic practices'' I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name''' The goal of this system to open bridge + experience highway for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion. I am kindly asking to revert your edits in this book. After that I will put a notification template about "This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page." Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC) :Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]: :* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace. :* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer. :* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions. :Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC) ::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed? :::The <u> local manual of style</u> development is ongoing together with the sample pages. ::'''MAIN PAGE''' ::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc. ::'''NESTING ''' :::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]] :::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] ::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]] ::: ::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC) :::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC) ::::It makes no sense to have some crazy abbreviation as a "main page" or "namespace" (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, "Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History." Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC) :::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC) ::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC) == Deletions of Wikibook subpages == Hello @[[User:Kittycataclysm|Kittycataclysm]], regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly. Best, Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC) :Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC) ::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time. ::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC) :::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC) == help with "Media Literacy and You" == {{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove <nowiki>{{Qr-em|not clear how this is to be structured as a book}}</nowiki>? I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the "Discussion" page associated with that book and by upgrading the content. The upgrades included adding the "Introduction" chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. ??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC) :Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC) ::{{re|Kittycataclysm}} ::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of "The wisdom of polarized crowds" discussed in [[Wikipedia:Reliability of Wikipedia]]. ::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. === Who is DavidMCEddy === ::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged] * 6,000+ edits in each of Wikipedia and Wikiversity, * 1,000+ in Wikimedia Commons, * 30,000+ in Wikidata, and * almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly "Media & Democracy" series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create "a world in which every single person on the planet is given free access to the sum of all human knowledge." Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC) ::{{re|Kittycataclysm}} ::"Media Literacy and You" is textbook to support both self study and classes on media literacy. ::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc. ::I think this "Media Literacy and You" project would lose the vast majority of its potential if it were not on Wikibooks. ::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC) {{outdent}} {{re|Kittycataclysm}} Will you please help me with the protocols of creating a book on Wikiversity? 1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the "Book creator" tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 2. What do you suggest I do next? :I can create an article on Wikiversity titled, "Media Literacy and You", and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. :If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports <nowiki>{{cite Q|...}}</nowiki>, which I have used extensively for years.) :Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC) ::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC) == Thank you! == Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC) :It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC) ::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC) == A test request == Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 01:49, 30 March 2026 (UTC) :Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC) == Linking == Hi,<br> For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information & seems relevant.<br> Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC) :@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC) ::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC) :::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Undeletion request == Hello, I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC) :@[[User:Yqj3km|Yqj3km]] see my response below regarding undeletion. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 May 2026 (UTC) == Undeletion request == About the page on Lentis called Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad: I, too, request undeletion, please. If the authors made any msitakes, the fault is 100 percent mine, for failing to guide them correctly. Like all chapters in this book, this team's chapter is a class assignment. I will be interested also in the reason for deletion so that I can guide authors better. I want to help my students be constructive contributors. Many thanks! [[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 20:03, 4 May 2026 (UTC) :Hi @[[User:Norton|Norton]] and thanks for the ping! I deleted it because it was not titled/filed correctly, so I didn't realize it was part of [[Lentis]]. I have undeleted it and moved it to [[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:14, 4 May 2026 (UTC) c6ly1pv0tmvp27edupzq3vgo7cyyg2i 4634194 4634193 2026-05-04T22:27:29Z Norton 379181 /* Undeletion request 3 */ Reply 4634194 wikitext text/x-wiki {| class="wikitable" |+ ! colspan="3" |Talk Page Archives |- |[[User talk:Kittycataclysm/Archive 2022|2022]] |[[User talk:Kittycataclysm/Archive 2023|2023]] |[[User talk:Kittycataclysm/Archive 2024|2024]] |} == That IP range calculator == Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 23:10, 9 January 2025 (UTC) :Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC) == A merge and unmerge from two years ago == I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 15:55, 10 January 2025 (UTC) :Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC) ::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 16:49, 10 January 2025 (UTC) == Undeletion request == I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary "Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution", so that I can do that. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 19:54, 14 January 2025 (UTC) :Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC) ::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them "bad transwikis"), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 21:19, 14 January 2025 (UTC) == Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow == Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe. If not, I'll use the revision before you contributed since I was the only author. Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions. Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC) ::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC) == Wikibooks community == Hi, @[[User:Kittycataclysm|Kittycataclysm]]! I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together? I am looking forward to join. Thank you! [[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC) :@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC) ::Yes. Do you know place for this? ::Thank you ::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC) :::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC) == Congratulations! == [[File:Admin T-shirt.svg|thumb|You get this now.]] You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 10:33, 29 January 2025 (UTC) :Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC) == Is there a way to contact a Steward on WikiBooks? == Hi {{PAGENAME}}, Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here at [[Special:ActiveUsers?username=&groups%5B%5D=steward&wpFormIdentifier=specialactiveusers]] but nothing shows up. The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not find this backward link. I tried to ask about this on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. Is there a way wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC) :@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC) <s>:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.</s> Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC) ::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else: ::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to. ::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC) :::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC) ::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF). It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more. The wmf has been hosting a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it. ::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier: ::::* "Some wikibookians prefer for various reasons to post only at wb" ::::* "The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it" ::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC) == [[Crystal ball]] == That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 03:04, 9 February 2025 (UTC) :Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC) == Question about an edit suggestion == Hi Kittycataclysm, Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient? Any specific recommendations you have would be greatly appreciated! Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]] Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC) :Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC) ::Following up on this—I noticed that you use the term "paper". However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC) == Talkback == {{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC) :@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC) == Hello == Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC) :I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC) :::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC) ::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC) == Cookbook == Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC) :Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC) ::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC) ::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC) :::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC) ::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC) :::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from "____ recipes" in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC) ::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC) :::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC) ::::::::I see you already had the same thought as me. I think all categories should include "for" or "using". Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC) :::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC) :Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC) == More Table of Content Edits == Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days. * Fix Bread wikilink * Remove "Creaming" from techniques, redirected to Mixing * [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized * [[Cookbook:Low-Carb]] points to redirect, needs capitalized * [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity * Remove the S from the cuisine wikilinks on ToC, currently redirecting * Create [[:Category:Lunch recipes]], wikilink to ToC * Wikilink [[Cookbook:Dessert]] under Meals * Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category * Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC * Change "Introductory Matter" header to just "Introduction" * Appendix and Equipment sections switch places Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC) :I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC) :Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below: :* {{xt|Fix Bread wikilink}} {{done}} :* {{xt|Remove "Creaming" from techniques, redirected to Mixing}} see below comments on TOC. :* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can! :* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above. :* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form "Cuisine of ____". It could be good to standardize, and I had been planning to do that once I got around to the cuisines. :* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects :* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page :* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}} :* {{xt|Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below. :* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines. :* {{xt|Change "Introductory Matter" header to just "Introduction"}} The reason I made it "Introductory Matter" instead of "Introduction" is because there's already a chapter itself titled "Introduction"—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. "Front Matter", which is a generally accepted book term) :* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC. :* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel. :Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC) ::Thanks for the notes! Here's my thoughts: ::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. "[[Cookbook:African Cuisine]]", and I think that shorter titles are preferable where it makes sense. ::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one "Asian Cuisine", but put the different locales under separate headers? ::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as "brunch" to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch. ::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say "Introductory Matter", or "Front Matter" as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC. ::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything. ::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it. ::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC) :::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC) ::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC) :::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC) == Cookbook ToC == Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC) :@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC) ::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go. ::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help. ::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like "I'm sorry that you feel that way" was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC) :::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC) ::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC) == [[Cookbook:Polish Doughnuts (Paczki)]] == Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC) :I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC) == [[Cookbook:Cream Cheese American Buttercream]] == Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC) == [[A Companion to Our Literary Journey]] == Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC) :Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC) == Exercising care with copyright == When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 18:32, 21 March 2025 (UTC) :Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC) == Splitting Pages == Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC) :@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:44, 29 March 2025 (UTC) :Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC) ::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC) == Minecraft book == Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC) :@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC) ::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC) :::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC) ::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC) == Request to Review Adjusted User Page (XoriantTeam) == Hello [[User:Kittycataclysm|Kittycataclysm]], I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check. I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation. If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method. Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments. Best regards, XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC) :Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC) == Planning to use AWB to update categories on the cookbook == Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC) :: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC) :::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC) == Tool for even faster category changes == See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:36, 19 June 2025 (UTC) :@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC) ::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just <kbd>Ctrl+Shift+R</kbd> once or twice. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:55, 19 June 2025 (UTC) :::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC) == Advice on when I should run for adminship == Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below: Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.<br> Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters). A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted. I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC) :: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC) ::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC) ::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC) ::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC) == how is it you feel able to interfere in my sandbox? == you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site. now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere. -- [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC) :Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC) ::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC) ::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC) :::No worries—it looks like you didn't add the prefix "User:" before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with "'''User:'''VulcanWikiEdit/sandbox", and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC) ::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC) :::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC) == Regarding the user Codename Tameirao == Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 23:51, 12 August 2025 (UTC) :I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC) :: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 16:30, 9 September 2025 (UTC) :::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC) :::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC) ::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC) ::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC) == IP block exempt == Hi Kitty, I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 10:51, 22 August 2025 (UTC) :Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC) ::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:25, 23 August 2025 (UTC) ::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:35, 23 August 2025 (UTC) == You've got mail! == {{You've got mail|sig=<span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 00:20, 6 September 2025 (UTC)}} :Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC) == Are you able to import? == I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC) : [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC) ::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC) ::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC) ::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC) :::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:11, 6 October 2025 (UTC) :::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC) :::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC) ::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC) == About the category parameter in the recipe summary template == When it uses a "recipe by type" category, should it use a "[type/food] recipes" name or "Recipes for [type/food]"? I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC) :: Probably, but I will say the following below (for my first sentence) to clarify: :: On the <code>|category =</code> parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC) == Please no more Unicode LTA == Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&#126;2025-30839-28|&#126;2025-30839-28]] ([[User talk:&#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC) :<small>I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here</small> I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:13, 5 November 2025 (UTC) ::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:23, 5 November 2025 (UTC) :::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC) == Administrator and reviewer user right combinations are not needed anymore == Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC) :Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC) :: The thing is, administrators have the <code>review</code> user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC) ::: @[[User:Kittycataclysm|Kittycataclysm]] <s>I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.</s> ({{doing}}) [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:24, 12 November 2025 (UTC) : I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC) == Nesting in Open Book of Ecovillages and Eco Communities == Hi Kittycataclysm, I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].) Yes, It will be not an average book but above the regular. This is the exact case: ''"this may be appropriate, such as with large textbooks that contain subsections with a lot of content."'' ''for to establish good structural and stylistic practices'' I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name''' The goal of this system to open bridge + experience highway for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion. I am kindly asking to revert your edits in this book. After that I will put a notification template about "This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page." Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC) :Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]: :* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace. :* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer. :* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions. :Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC) ::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed? :::The <u> local manual of style</u> development is ongoing together with the sample pages. ::'''MAIN PAGE''' ::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc. ::'''NESTING ''' :::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]] :::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] ::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]] ::: ::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC) :::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC) ::::It makes no sense to have some crazy abbreviation as a "main page" or "namespace" (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, "Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History." Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC) :::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC) ::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC) == Deletions of Wikibook subpages == Hello @[[User:Kittycataclysm|Kittycataclysm]], regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly. Best, Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC) :Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC) ::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time. ::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC) :::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC) == help with "Media Literacy and You" == {{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove <nowiki>{{Qr-em|not clear how this is to be structured as a book}}</nowiki>? I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the "Discussion" page associated with that book and by upgrading the content. The upgrades included adding the "Introduction" chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. ??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC) :Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC) ::{{re|Kittycataclysm}} ::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of "The wisdom of polarized crowds" discussed in [[Wikipedia:Reliability of Wikipedia]]. ::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. === Who is DavidMCEddy === ::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged] * 6,000+ edits in each of Wikipedia and Wikiversity, * 1,000+ in Wikimedia Commons, * 30,000+ in Wikidata, and * almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly "Media & Democracy" series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create "a world in which every single person on the planet is given free access to the sum of all human knowledge." Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC) ::{{re|Kittycataclysm}} ::"Media Literacy and You" is textbook to support both self study and classes on media literacy. ::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc. ::I think this "Media Literacy and You" project would lose the vast majority of its potential if it were not on Wikibooks. ::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC) {{outdent}} {{re|Kittycataclysm}} Will you please help me with the protocols of creating a book on Wikiversity? 1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the "Book creator" tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 2. What do you suggest I do next? :I can create an article on Wikiversity titled, "Media Literacy and You", and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. :If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports <nowiki>{{cite Q|...}}</nowiki>, which I have used extensively for years.) :Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC) ::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC) == Thank you! == Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC) :It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC) ::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC) == A test request == Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 01:49, 30 March 2026 (UTC) :Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC) == Linking == Hi,<br> For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information & seems relevant.<br> Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC) :@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC) ::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC) :::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Undeletion request == Hello, I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC) :@[[User:Yqj3km|Yqj3km]] see my response below regarding undeletion. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 May 2026 (UTC) == Undeletion request == About the page on Lentis called Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad: I, too, request undeletion, please. If the authors made any msitakes, the fault is 100 percent mine, for failing to guide them correctly. Like all chapters in this book, this team's chapter is a class assignment. I will be interested also in the reason for deletion so that I can guide authors better. I want to help my students be constructive contributors. Many thanks! [[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 20:03, 4 May 2026 (UTC) :Hi @[[User:Norton|Norton]] and thanks for the ping! I deleted it because it was not titled/filed correctly, so I didn't realize it was part of [[Lentis]]. I have undeleted it and moved it to [[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:14, 4 May 2026 (UTC) ::Many, many thanks, @[[User:Kittycataclysm|Kittycataclysm]]! I am very grateful as always for everything you do for Wikibooks! ::[[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 22:27, 4 May 2026 (UTC) anuo10oec97wbr7y00kx8dmd06700qc 0 443296 4634220 4628460 2026-05-05T05:35:15Z ~2026-27286-23 3581337 4634220 wikitext text/x-wiki {{Chess Position|Coca-Cola Gambit |eco=[[Chess/ECOA|A00]] |parent=[[../|Grob's Attack, Symmetrical Variation]] |responses=<br> * [[/2...f5|2...f5 - Pepsi Countergambit]]}} == 2...f4? · Coca-Cola Gambit == The Coca-Cola gambit is a highly unorthodox and aggressive "meme" chess opening<ref>{{Cite web |title=Grob Opening: Double Grob, Coca-Cola Gambit |url=https://lichess.org/analysis |access-date=2026-03-29 |website=lichess.org |language=en}}</ref><ref>{{Cite web |title=Grob Opening: Double Grob, Coca-Cola Gambit - Chess Openings |url=https://www.chess.com/openings/Grob-Opening-Double-Grob-Coca-Cola-Gambit |access-date=2026-03-29 |website=Chess.com |language=en-US}}</ref><ref>{{Cite web |title=Coca-Cola Gambit |url=https://chess.fandom.com/wiki/Coca-Cola_Gambit |access-date=2026-03-29 |website=Chess Wiki |language=en}}</ref><ref>{{Cite web |title=Grob Opening, Double Grob, Coca-Cola Gambit - Chess Opening |url=https://chesstempo.com/game-database/opening/grob-opening-double-grob-coca-cola-gambit/2758 |access-date=2026-03-29 |website=chesstempo.com}}</ref> After 2...gxf4 some theory has been developed⸺3.d4 e5 4.h4 d6 5. dxe5 dxe5 6. Qxd8+ Kxd8 7. g5 h6 8. Bg2 Nc6 9. e3 Bg4 10. c3 hxg5 11. hxg5 Rxh1 12. Bxh1 Nge7 13. exf4 Ng6 14. fxe5 Bc5 15. Kf1 is the so-called "main line". [[/2...f5|2...f5?!]] continues the chaos with the Pepsi Countergambit. === History === The origins of the name "Coca-Cola Gambit" are uncertain, with the first known online references to its name being a German forum post from 2008 by user ''<nowiki/>'Latvian Gambit'''<ref>{{Cite web |date=2 Feb 2008 |title=Schachfeld.de Threads: lustige eröffnungsnamen |url=https://www.schachfeld.de/threads/5865-lustige-eroeffnungsnamen |url-status=live |archive-url=https://web.archive.org/web/20221113230129/https://www.schachfeld.de/threads/5865-lustige-eroeffnungsnamen |archive-date=13 Nov 2022 |access-date=29 Mar 2026 |website=Schachfeld.de}}</ref> and a chess.com forum post from September 2008.<ref>{{Cite web |title=Funniest or Weirdest Opening Name? - Chess Forums |url=https://www.chess.com/forum/view/chess-openings/funniest-or-weirdest-opening-name |access-date=2026-03-29 |website=Chess.com |language=en-US}}</ref> It has featured in numerous Youtube videos, such as as Anish Giri's 2020 video ''"They made me play the worst gambit ever"'' <ref>{{Citation |last=Anish Giri |title=They made me play the worst gambit ever |date=2020-11-29 |url=https://www.youtube.com/watch?v=BubU67eV7ko |access-date=2026-03-29}}</ref> and Fischy Stream's "Weirdest Chess Openings Explained", which gained over 600,000 views<ref>{{Citation |last=Fischy Stream |title=Weirdest Chess Openings Explained |date=2024-04-19 |url=https://www.youtube.com/watch?v=b9t-cF_vSfM |access-date=2026-03-29}}</ref> == Theory table == {{Chess Opening Theory/Table}} {| cellpadding="4" cellspacing="0" border="0" !'''1. g4''' '''g5 2. f4''' |- ! ! align="left" |2 |'''Eval''' |- ! align="right" |[[Chess Opening Theory/1. g4/1...g5/2. f4/2...f5|Pepsi Countergambit]] |... [[Chess Opening Theory/1. g4/1...g5/2. f4/2...f5|f5?]] | +/- |} == References == <references /> * [https://www.chess.com/openings/Grob-Opening-Double-Grob-Coca-Cola-Gambit Grob Opening: Double Grob, Coca-Cola Gambit]. ''chess.com'' * [https://lichess.org/analysis/pgn/g4_g5_f4 Grob Opening: Double Grob, Coca-Cola Gambit]. ''lichess.org'' * [https://chess.fandom.com/wiki/Coca-Cola_Gambit Coca-Cola Gambit] ''chess.fandom.com'' 93llemkgunmowo21a8194gbr8syv0zc 0 448077 4634089 4490679 2026-05-04T15:18:09Z Tyoyafud 6233 /* Punctuation */ 4634089 wikitext text/x-wiki <noinclude>{{status|100%}}</noinclude> == The Alphabet == : Mirad uses the Roman alphabet as in Modern English. There is an '''''upper case''''' (majuscules or capital letters) and a '''''lower case''''' (miniscules or small letters). The upper case letters are used for capitalization exactly as in English. Mirad, at least for non-foreign words, uses no diacritic marks such as the br&egrave;ve, the grave accent, or the dieresis. The order of the alphabet is the same as in English. The letters, though, are pronounced as shown in the chart. Note that there is a pattern: The vowel of each Mirad letter name changes to the single vowel letter before it. For example, the vowel in the name for letter '''f''' changes to '''e''' following the letter '''e''' in the alphabetic sequence. The Mirad letter name for '''j''' is '''ji''' because it is just beyond the vowel letter '''i''' in the alphabetic sequence. Uppercase letters have a Mirad letter name beginning in '''ag''', a prefix meaning ''big''. ::{| class="wikitable" style="background:lightyellow; vertical-align:top; align:center; font-size:smaller;" |+ Alphabet A-N |- ! Lowercase !! a !! b !! c !! d !! !! e !! f !! g !! h !! !! i !! j !! k !! l !! m !! n |- align=center | !row=1| Mirad Letter Name | '''a''' || '''ba''' || '''ca''' || '''da''' ||bgcolor=lightgray| || '''e''' || '''fe''' || '''ge''' || '''he''' ||bgcolor=lightgray| || '''i''' || '''ji''' || '''ki''' || '''li''' || '''mi''' || '''ni''' |- ! Uppercase !! A !! B !! C !! D !! !! E !! F !! G !! H !! !! I !! J !! K !! L !! M !! N |- align=center | !row=1| Mirad Letter Name | '''aga''' || '''agba''' || '''agca''' || '''agda''' || bgcolor=lightgray| || '''age''' || '''agfe''' || '''agge''' || '''aghe''' ||bgcolor=lightgray| || '''agi''' || '''agji''' || '''agki''' || '''agli''' || '''agmi''' || '''agni''' |} ::{| class="wikitable" style="background:lightyellow; vertical-align:top; align:center; font-size:smaller;" |+ Alphabet O-Z |- ! Lowercase !! o !! p !! q !! r !! s !! t !! !! u !! v !! w !! x !! y !! z |- align=center | !row=1| Mirad Letter Name | '''o''' || '''po''' || '''ko''' || '''ro''' || '''so''' || '''to''' ||bgcolor=lightgray| || '''u''' || '''vu''' || '''wu''' || '''xu''' || '''yu''' || '''zu''' |- ! Uppercase !! O !! P !! Q !! R !! S !! T !! !! U !! V !! W !! X !! Y !! Z |- align=center | !row=1| Mirad Letter Name | '''ago''' || '''agpo''' || '''agko''' || '''agro''' || '''agso''' || '''agto''' ||bgcolor=lightgray| || '''agu''' || '''agvu''' || '''agwu''' || '''agxu''' || '''agyu''' || '''agzu''' |} : The letters '''c''' and '''q''' are used only to represent words and names imported into Mirad from other languages, or for words in which letters of the alphabet are used to spell out chemical terms, metric units, country names, languages, and other terms based on existing world standards like ISO. == Letter Names == : Spelling a word aloud means uttering the word's Mirad letter names in succession left to right. If the letter is a upper case, then the letter name is preceded by '''ag-'''....''big'', eg.: :* '''anxwa''' is spelled aloud as '''a-ni-xu-wu-a''' :* '''Mirad''' is spelled aloud as '''agmi-i-ro-a-da''' : Note that '''age''' for ''E'' and '''agge''' for ''G'' need to be carefully distinguished. The former, '''age''' is pronounced '''a-ge''', while the latter, '''agge''', is pronounced '''ag-ge'''. == Capitalization == : Capitalization in Mirad is handled almost exactly as in English: :* The first word of a new sentence is capitalized. ::* '''At ife et.'''....''I love you.'' ::* '''Iyt da: "At ife et."'''....''She said, "I love you."'' :* All proper nouns are capitalized, including names of people, organizations, books, languages, countries, etc. ::* '''Mirad'''....''Mirad'' ::* '''Ferom'''....''France'' ::* '''ha Feromati'''....''the French'' ::* '''Alica be Teazmem'''....''Alice in Wonderland'' ::* '''ha Yoongun'''....''The Pentagon'' :* Acronyms are capitalized. ::* '''ZUYX'''....''NATO''. ::* '''DXV'''....''FBI''. :* If a verb or adjective is based on a proper noun, the proper noun part of the word gets capitalized. ::* '''Deumxer'''....''to Germanify'' ::* '''loNazixer'''....''to de-Nazify'' ::* '''Irolim-ulza'''....''Kelly (= Ireland) green''. :* The planets and inhabitants of planets are capitalized. ::* '''Ha tyod bi <u>Imer</u>.'''....''The people of <u>Earth</u>.'' ::* '''Ha <u>Umerati</u> upeye.'''....''The <u>Martians</u> are coming.'' :* The word ''god'' is capitalized if referring to a religion's one, true god, otherwise not. ::* '''Ha <u>toti</u> se futipa.'''....''The <u>gods</u> are angry.'' ::* '''Fyadilu bu <u>Tot</u>.'''....''Pray to <u>God</u>.'' ::* '''Van yat fyadilu bu Allah.'''....''Let's pray to Allah.'' : Unlike in English, though: :* The days of the week, the months of the year, and the seasons are <u>not</u> capitalized. ::* '''juab'''....''Monday'' ::* '''jieb'''....''February'' ::* '''jeub'''....''Winter'' == Punctuation == : Punctuation is handled as in English, with the following exception: :* A colon (:) is used in direct quotations, as opposed to the comma (,) used in English, eg.: :: ''He said, "Let there be light."''....'''It da: "Van esu man."''' : Here is a chart showing punctuation marks and symbols along with their names in Mirad: ::{| class="wikitable sortable" style="background: lightyellow; font-size:smaller" |+ Punctuation Marks and Symbols |- ! English !! Symbol !! Mirad |- ! colspan=3| Marks ('''siyni''') |- | ''period'' || <big>.</big> || '''nodsiyn''' |- | ''comma'' || <big>,</big> || '''grunsiyn''' |- | ''colon'' || <big>:</big> || '''ennodsiyn''' |- | ''semi-colon'' || <big>;</big> || '''nodgrunsiyn''' |- | ''question mark'' || <big>?</big> || '''didsiyn''' |- | ''exclamation point'' || <big>!</big> || '''yoksiyn''' |- | ''single quote'' || <big>'</big> || '''aona gedsiyn''' |- | ''double quote'' || <big>"</big> || '''eona gedsiyn''' |- | ''hyphen'' || <big>-</big> || '''naydsiyn''' |- | ''dash, em dash'' || <big>--</big> || '''eona nadsiyn''' |- | ''underscore, low line'' || <big>_</big> || '''oybnadsiyn''' |- | ''vertical line'' || <big>&#124;</big> || '''aonadsiyn''' |- | ''wave dash'' || <big>~</big> || '''pyaon nadsiyn''' |- | ''forward slash, solidus''<br>''backward slash, reverse solidus'' || <big>/</big> || '''zaya kinad'''<br>'''zoya kinad''' |- | ''double slash'' || <big>//</big> || '''eona kinad''' |- | ''apostrophe'' || <big>'</big> || '''oysunsiyn''' |- | ''left parenthesis''<br>''right parenthesis'' || <big>(</big><br>)</br>|| '''zua uzkun yebyujarsiyn'''<br>'''zia uzkun yebyujarsiyn''' |- | ''left angle bracket''<br>''right angle bracket'' ||<big><</big><br><big>></big>|| '''zua gun yebyujarsiyn'''<br>'''zia gun yebyujarsiyn''' |- | ''left square bracket''<br>''right square bracket'' ||<big>[</big><br><big>]</big> || '''zua izkun yebyujarsiyn'''<br>'''zia izkun yebyujarsiyn''' |- | ''left curly bracket''<br>''right curly bracket'' || <big>{</big><br><big>}</big> || '''zua uzyua yebyujarsiyn'''<br>'''zia uzyua yebyujarsiyn''' |- | ''ellipsis'' || <big>...</big> || '''innodsiyn''' |- | ''caret'' || <big>^</big> || '''garsiyn''' |- ! colspan=3| Symbols ('''siun''') |- | ''ampersand'' || <big>&</big> || '''aysiun''' |- | ''at sign'' || <big>@</big> || '''asiun''' |- | ''percent sign'' || <big>%</big> || '''asoynsiun''' |- | ''hash tag, pound sign, number sign'' || <big>#</big> || '''sagsiun''' |- | ''asterisk'' || <big>*</big> || '''marsiun''' |- | ''dollar sign'' || <big>$</big> || '''Usodansiun''' |} : Note: Most of these marks and symbols are on a standard English-language keyboard. Mathematical symbols are not listed here, nor are most accent marks like "grave accent". See [[Mirad_Grammar/Numbers#Mathematical Expressions|the Mathematical Expressions section of Numbers]]. == Text Direction == : Text in Mirad is written from left to right with spaces between words. <noinclude>{{Chapter navigation with TOC|Why Mirad?|Pronunciation}}</noinclude> 5qstwbe65nys3ibc18xs2fpz564m620 0 448081 4634091 4521510 2026-05-04T15:24:47Z Tyoyafud 6233 /* Pronunciation of Consonants */ 4634091 wikitext text/x-wiki <noinclude>{{status|100%}}</noinclude> = Consonants = {{IPA notice}} : Consonants are sounds that restrict air flow in the mouth. The sounds of the consonants in an abstract sense are '''''phonemes''''', while the symbols used to represent these sounds in writing are '''''graphemes'''''. == Consonant graphemes and phonemes == : The following chart shows the correspondence of the consonant graphemes and their phonemic values represented in the International Phonetic Alphabet (IPA): {| class="IPA wikitable" style="text-align:center" style="background:lightyellow; margin-left:1.6em; font-size:smaller" |+ Correspondence of Consonant Graphemes and Phonemes |- !row=1| Grapheme | '''b''' || '''c''' || '''d''' || '''f''' || '''g''' || '''h''' || '''j''' || '''k''' || '''l''' || '''m''' || '''n''' || '''p''' || '''q''' || '''r''' || '''s''' || '''t''' || '''v''' || '''x''' || '''z''' |- !row=1| Phoneme | /b/ || /t͡ʃ/ || /d/ || /f/ || /g/ || /h/ || /ʒ/ || /k/ || /l/ || /m/ || /n/ || /p/ || /k/ || /ɽ/ || /s/ || /t/ || /v/ || /ʃ/ || /z/ |} == Pronunciation of Consonants == : The following chart shows the Mirad consonants with their phonemic values in the IPA: {| class="IPA wikitable" style="text-align:center" style="background:lightyellow; margin-left:1.6em; font-size:smaller" |+ Consonants |- ! !! !! '''Labial''' !! '''Alveolar''' !! '''Palatal''' !! '''Velar''' !! '''Glottal''' |- ! rowspan="1" | '''Nasal''' ! <small>'''voiced'''</small> | '''/m/''' || '''/n/''' || || || |- ! rowspan="2" | '''Plosive''' ! <small>'''voiced'''</small> | '''/b/''' || '''/d/''' || || '''/g/''' || |- ! <small>'''unvoiced'''</small> | '''/p/''' || '''/t/''' || || '''/k/''' || |- ! rowspan="2" | '''Affricate''' ! <small>'''voiced'''</small> | || || || || |- ! <small>'''unvoiced'''</small> | || || '''/t͡ʃ/''' || || |- ! rowspan="2" | '''Fricative''' ! <small>'''voiced'''</small> | '''/v/''' || '''/z/''' || '''/ʒ/''' || || |- ! <small>'''unvoiced'''</small> | '''/f/''' || '''/s/''' || '''/ʃ/''' || || '''/h/''' |- ! rowspan="1" | '''Approximant''' ! <small>'''voiced'''</small> | || '''/l/''' || || || |- ! rowspan="1" | '''Flap''' ! <small>'''voiced'''</small> | || '''/ɽ/''' || || || |} : The phonemes /'''r'''/ and /'''l'''/ are '''''consonant liquids''''' and behave in a special way in forming words in Mirad. : In Mirad, every consonant has a one-to-one correspondence with a single phoneme (ideal sound). Mirad does not use digraphs like ''sh'' or ''ph'' to represent consonant sounds. There are no double consonants, although sometimes a consonant will come together with the same consonant in the same word, but not the same syllable. There are no silent consonants, although the letter '''h''' is silent at the end of a word but causes the stress to move to the final syllable. It is used in that way only in borrowed, non-native Mirad words. Also, there are no letters in "native" Mirad with diacritical marks like '''&eacute;''' or '''&ntilde;'''. : Here are the letters that are pronounced somewhat differently from English: :* The letter '''x''' is pronounced like an ''sh'' in English, or a ''ch'' in French. :* In native Mirad words, '''h''' is pronounced like the ''h'' in English ''hand''. It is sometimes used to simulate foreign sounds like the ''ch'' in Yiddish '''la<u>ch</u>ayim''' (''to life!''), or German '''Ba<u>ch</u>'''. If '''h''' comes at the end of a word, it is silent, but, being a consonant, it can serve to move the stress to the word-final syllable, as in '''Allah''', pronounced '''al-LA'''. :* The letter '''j''' is pronounced like the ''zh'' in Russian ''<u>Zh</u>ivago'' or the ''ge'' in English ''mira<u>ge</u>''. :* The letter '''s''' is always unvoiced as English ''ss'' and never sounds like a '''z'''. :* The letter '''g''' is always a hard sound as in English ''<u>g</u>ap'', not as in English ''wa<u>g</u>e''. :* The letter '''c''' represents the unvoiced affricative sound '''t͡ʃ''' like the ''ch'' in English ''<u>ch</u>ur<u>ch</u>''. Some chemical names and metric units use the letter '''c''', such as '''calilk''' (''chlorine''). The the '''c''' is found in a foreign borrowing unchanged in its spelling, then it is pronounced as it would be in that foreign word. :* The unvoiced plosives '''p''', '''t''', and '''k''' are pronounced without the puff of breath that sometimes follows them in their English counterparts. The corresponding consonants in French are exact equivalents. :* The consonant '''r''' should be a flap or trill like the ''r'' in Brit. Eng. ''ve<u>r</u>y'' or the single, intervocalic ''r'' in Spanish ''pe<u>r</u>o''. :* The consonant '''q''' is usually pronounced as a '''k''', but in foreign borrowings or proper names, it may be pronounced according to context. :* The consonants in the Mirad alphabet correspond one-to-one with phonemes. There are no cases of consonant sounds being represented in native words by digraphs as in English ''ph'', ''sh'', ''ch'', or ''th''. For example, the ''sh'' sound in English is represented by '''x''' in Mirad. The English ''ch'' sound is represented in Mirad with the letter '''c'''. There are no equivalents in Mirad for the English sounds ''th'' in ''this'' or the ''th'' in ''think'', but the combination '''th''' in foreign borrowings is pronounced as it is in the source language. : Here is a chart showing the phonetic values of Mirad consonants: {| class="wikitable" style="background:lightyellow; font-size: smaller; margin-left:3.2em " |+ Consonants |- ! Mirad Consonant/<br>Semi-Consonant<br>Grapheme !! IPA !! Articulation !! Nearest Equivalents |- | '''b''' || [b] || unaspirated voiced bilabial plosive || French ''<u>b</u>on'', English ''<u>b</u>oy'' |- | '''c''' || [tʃ] || unvoiced palato-alveolar affricate || English ''<u>ch</u>ild'', Spanish ''<u>ch</u>ico'' |- | '''d''' || [d] || unaspirated voiced alveolar plosive || French ''<u>d</u>e'', English ''<u>d</u>og'' |- | '''f''' || [f] || unvoiced labio-dental fricative || English ''<u>f</u>og'' |- | '''g''' || [g] || unaspirated voiced velar plosive || French ''<u>g</u>are'', English ''<u>g</u>ood'' (always hard, even before ''e'' and ''i''). |- | '''h''' || [h]<br>[x] || glottal fricative || English ''<u>h</u>ouse''<br>(used in some foreign words and names as a ''kh''-like sound like German ''Ba<u>ch</u>''. Not pronounced at the end of foreign borrowings like ''Allah'' or ''Arkansah''. |- | '''j''' || [ʒ] || voiced palatal fricative || French ''<u>j</u>e'' or English ''mira<u>g</u>e''. |- | '''k''' || [k] || unaspirated unvoiced velar fricative || French ''<u>c</u>arte'', English ''s<u>k</u>ip'' (without aspiration). |- | '''l''' || [l] || voiced post-alveolar lateral approximant || English ''<u>l</u>ove'' or French ''be<u>l</u>'' (never a dark '''l''' as in English ''be<u>ll</u>''. |- | '''m''' || [m] || voiced bilabial nasal || English ''<u>m</u>other''. |- | '''n''' || [n]<br>[ŋ] || voiced alveolar nasal ||English ''<u>n</u>obody''<br>Before ''g'' or ''k'', like English ''fa<u>n</u>g''. |- | '''p''' || [p] || unvoiced bilabial plosive || French ''<u>p</u>ain'', English ''s<u>p</u>an'' (without aspiration). |- | '''q''' || - || - || (Only used in foreign words, or some chemical names, where it pronounced ''k'' in Mirad). |- | '''r''' || [r] || alveolar flap || Spanish ''mi<u>r</u>a'' or Italian ''<u>R</u>oma'' or British Eng. '''ve<u>r</u>y''. |- | '''s''' || [s] || unvoiced alveolar fricative || Always hard as in English ''<u>s</u>afe'' (never a ''z'' sound as in ''rose''). |- | '''t''' || [t] || unaspirated unvoiced alveolar plosive || French ''<u>t</u>ous'', English ''s<u>t</u>op'' (without aspiration). |- | '''v''' || [v] || voiced labial-dental fricative || English ''<u>v</u>ery''. Spanish and German speakers need to beware: this is not a bilabial consonant, nor is it an ''f'' sound. |- | '''x''' || [ʃ] || unvoiced post-alveolar fricative || English ''<u>sh</u>ape'' or French ''<u>ch</u>er'' |- | '''z''' || /z/ || voiced alveolar fricative || English ''<u>z</u>one''. German speakers, beware. Mirad '''z''' is pronounced like a German '''s''', as in '''<u>s</u>ehr''', not like '''z''' as in '''zehn''', which sounds more like ''ts''. |} : Note that the sounds '''y''' and '''w''' are not included in the section on consonants, because they are glides, that is, they act as boundaries of the vowel nucleus of a syllable, but not the vowel nucleus itself. They are sometimes called semivowels or approximants, but in the present description of Mirad, they are treated in the following section on vowels. = Vowels = : Mirad vowels are divided into simple and glided vowels. The simple vowels are single letters, while the glided vowels have one or more semi-vowel glides ('''y''' or '''w''') prefixed or suffixed. A '''y''' colors a vowel palatally, while a '''w''' colors a vowel labio-velarly. === Simple Vowels === The Mirad graphemes (alphabetic letters) used to represent the simple vowel phonemes (minimal meaningful sounds) are as follows: {| class="wikitable" style="text-align:center" style="background:lightyellow; font-size:smaller; margin-left:3.2em" |+ Vowel Graphemes and Phonemes |- ! Grapheme !! '''a''' !! '''e''' !! '''i''' !! '''o''' !! '''u''' |- !row=1| Phoneme | '''/a/''' || '''/e/''' || '''/i/''' || '''/o/''' || '''/u/''' |} === Pronunciation of Simple Vowels === : The vowel sounds depend on where they are produced in the mouth and whether the lips are rounded or not. {| class="wikitable" style="text-align:center" style="background:lightyellow; font-size:smaller; margin-left:3.2em" |+ Articulation of Simple Vowels |- ! || colspan="2" | Front || colspan="2"| Back |- class=small ! || colspan="3" | Unrounded || Rounded |- align=center ! High | colspan="2"| '''i''' || || '''u''' |- align=center ! Mid | colspan="2"| '''e''' || || '''o''' |- align=center ! Low | colspan="2"| || '''&#x0251;''' || |} :The simple vowels are pronounced as they are in many European Latin-based languages. The table below gives their phonetic values and some close examples in Spanish and French, and not-so-close examples in English. {| class="wikitable" style="background:lightyellow; margin-left:3.2em; font-size:smaller;" |+ Simple Vowels |- ! Vowel !! IPA<sup>1</sup> !! Spanish !! French !! English<br>Approximation |- | '''a''' || [''a''] || m<u>a</u>no || <u>à</u><br>[[File:fr-à.ogg]] || ''f<u>a</u>ther'' |- | '''e''' || [''e''] || h<u>e</u>cho || <u>et</u><br>[[File:fr-et.ogg]] || ''d<u>ay</u>'' <sup>2</sup> |- | '''i''' || [''i''] || s<u>i</u> || s<u>i</u><br>[[File:fr-si.ogg]] || ''s<u>ee</u>''<sup>2</sup> |- | '''o''' || [''o''] || n<u>o</u> || de l'<u>eau</u><br>[[File:fr-eau.ogg]] || ''s<u>o</u>''<sup>3</sup> |- | '''u''' || [''u''] || t<u>u</u> || <u>ou</u><br>[[File:fr-ou.ogg]] || ''t<u>oo</u>''<sup>3</sup> |} : Note that '''i''' and '''e''' have a shorter, more relaxed sound if they are followed by a consonant in the same syllable. The Mirad word '''it''' (''he/she/him/her'') sounds much like ''it'' in English. Similarly, '''e''' in '''mes''' sounds like the short ''e'' in English ''mess''. :<small>Note 1) The International Phonetic Alphabet</small> :<small>Note 2) This sound in English actually ends in palatal glide (''y'' sound) and is not pure as in French or Spanish.</small> :<small>Note 3) This sound in English ends in a velar glide (''w'' sound) and is not pure as in French or Spanish.</small> === Glided Vowels === : Glided vowels are those preceded and/or followed by the semi-vowel glides '''y''' or '''w'''. This chart shows the possible glided vowels, their IPA equivalents, and their approximate pronunciations using English and other languages. {| class="wikitable" style="background:lightyellow; font-size:smaller; margin-left:3.2em" |+ Glided Vowels |- ! Glided Vowels !! IPA<sup>1</sup> !! Pronunciation |- ! colspan=3 | Pre-y-glided Vowels |- | '''ya''' || [ja] || Eng. ''y<u>ach</u>t'', Fr. ''<u>hia</u>cinthe''<br>[[File:en-us-yacht.ogg]] |- | '''ye''' || [je] || Eng. ''<u>ye</u>t'', Fr. ''grill<u>é</u>'' (''grilled'')<br>[[File:fr-grillé.ogg]] |- | '''yi''' || [ji] || Eng. ''<u>yea</u>st''*, Fr. ''bou<u>illi</u>'' |- | '''yo''' || [jo] || Eng. ''<u>yo</u>ke''*, Fr. ma<u>illot</u><br>[[File:fr-maillot.ogg]] |- | '''yu''' || [ju] || Eng. ''<u>you</u>''*, Fr. ''p<u>iou-piou</u>'' |- ! colspan=3 | Pre-w-Glided Vowels |- | '''wa''' || [wa] || Eng. ''w<u>a</u>ter'', Fr. ''g<u>oua</u>che'' (''poster paint'') <br>[[File:en-us-water.ogg]] |- | '''we''' || [we] || Eng. ''w<u>e</u>t'', Fr. ''<u>ouais</u>'' (''yes'') |- | '''wi''' || [wi] || Eng. ''w<u>ee</u>''<sup>2</sup>, Fr. ''<u>oui</u>'' (''yes'')<br>[[File:Fr-oui.ogg]] |- | '''wo''' || [wo] || Eng. ''w<u>o</u>ke''<sup>2</sup> |- | '''wu''' || [wu] || Eng. ''w<u>oo</u>''<sup>2</sup> |- ! colspan=3 | Post-y-Glided Vowels |- | '''ay''' || [aɪ] || Eng. ''s<u>igh</u>t'', Sp. ''h<u>ay</u>'' (''there is'')<br>[[File:en-us-I.ogg]] |- | '''ey''' || [eɪ] || Eng. ''d<u>ay</u>'', Sp. ''r<u>ey</u>'' (''king'')<br>[[File:en-us-day.ogg]] |- | '''iy''' || [iɪ] || Eng. ''s<u>ee</u>'', Fr. ''b<u>ille</u>'' (''marble'')<br>[[File:en-us-see.ogg]] |- | '''oy''' || [oɪ] || Eng. ''b<u>oy</u>'', Sp. ''h<u>oy</u>'' (''today'')<br>[[File:en-us-boy.ogg]] |- | '''uy''' || [uɪ] || Eng. ''g<u>ooey</u>'', Sp. ''m<u>uy</u>'' (''very'')<br>[[File:en-us-gooey.ogg]] |- ! colspan=3 | Post-w-Glided Vowels |- | '''aw''' || [ɔ] || Eng. ''<u>awe</u>''<br>[[File:en-us-awe.ogg]] |- | '''ew''' || [eʊ] || colloq. Eng. ''T<u>ell</u> me!''<br>[[File:en-us-tell.ogg]] |- | '''iw''' || [iʊ] || Eng. ''<u>eew!</u> (sound of disgust)'', Du. ''ni<u>ew</u>''<br>[[File:Nl-nieuw.ogg]] (''new'') |- | '''ow''' || [oʊ] || Eng. ''kn<u>ow</u>'', f<u>oe</u><br>[[File:en-us-know.ogg]] |- | '''uw''' || [uʊ] || Eng. ''g<u>oo</u>''<br>[[File:en-us-goo.ogg]] |- ! colspan=3 | Pre-y-Post-w-Glided Vowels |- | '''yaw''' || [jaʊ] || Eng. ''y<u>a</u>w''<br>[[File:en-us-yaw.ogg]] |- | '''yew''' || [jeʊ] || Eng. ''y<u>e</u>ll'' (very rare) |- | '''yiw''' || [jiʊ] || Eng. ''y<u>ie</u>ld'' (very rare) |- | '''yow''' || [joʊ] || Eng. ''y<u>o</u> bro!'' |- | '''yuw''' || [juʊ] || Eng. ''y<u>ou</u>''<br>[[File:en-us-you.ogg]] |- ! colspan=3 | Circum-y-Glided Vowels |- | '''yay''' || [jaɪ] || Eng. ''y<u>i</u>kes''<br>[[File:en-us-yikes.ogg]] |- | '''yey''' || [jeɪ] || Eng. ''y<u>ea</u>!''<br>[[File:en-us-yay.ogg]] |- | '''yiy''' || [jiɪ] || Eng. ''y<u>ee</u>sh! (sound of disgust)''<br>[[File:en-us-ye.ogg]] |- | '''yoy''' || [joɪ] || Eng. ''y<u>oi</u>nk'' ( ''= New Jyoizy'' )<br> |- | '''yuy''' || [juɪ] || Eng. ''H<u>ughie</u>''<br>[[File:EN-AU_ck1_Hughie.ogg]] |- ! colspan=3 | Pre-w-Post-y-Glided |- | '''way''' || [waɪ] || Eng. ''<u>wi</u>se'', Fr. '''<u>ouailles</u>''' (''flock'')<br>[[File:en-us-wise.ogg]] |- | '''wey''' || [weɪ] || Eng. ''<u>way</u>''<br>[[File:en-us-way.ogg]] |- | '''wiy''' || [wiɪ] || Eng. ''<u>wee</u>!'' (sound of fun)<br>[[File:en-us-we.ogg]] |- | '''woy''' || [woɪ] || Eng. ''<u>woy</u>'' (rhymes with ''boy'') |- | '''wuy''' || [wuɪ] || Eng. ''<u>wooi</u>sh'' (rhymes with ''gooey'') |} : In Mirad, the above glided vowels are considered single vowels for the purposes of grammar, syllabification, and stress. <div style="font-size:smaller"> : Note 1: International Phonetic Alphabet. See chart and click on sounds at [[https://www.internationalphoneticalphabet.org/ipa-sounds/ipa-chart-with-sounds/]]. : Note 2: Without the typical ''y-glide'' at the end of the English vowel. The vowel should be pure, as in the Romance languages of Europe. : Note 3: Without the typical ''w-glide'' at the end of the English vowel. The vowel should be pure, as in the Romance languages of Europe. </div> <noinclude>{{Chapter navigation with TOC|Alphabet|Syllabification}}</noinclude> bske0a39d3lg4ur4wufrbaxv76ruubi 0 448082 4634095 4490483 2026-05-04T15:35:19Z Tyoyafud 6233 4634095 wikitext text/x-wiki <noinclude>{{status|100%}}</noinclude> : Every syllable in Mirad contains one and only one vowel. A '''y''' when final or followed by a consonant is used to post-y-glide or diphthongize the previous vowel and is therefore considered part of the syllable in which that vowel is the nucleus (see case 2, below). Similarly, the '''''liquids''''' '''r''' and '''l''', when final or followed by a consonant are considered to be a part of the syllable where the preceding vowel is the nucleus (see case 4, below). Two vowels in a row form two syllabic nuclei (see cases 3, 6, and 7, below). How syllables are divided is important for determining where the stress accent goes in a word (see [[Mirad_Grammar/Stress]], below). {| class="wikitable" style="background:lightyellow;font-size:smaller;margin-left:4.8em" |+ Syllabification |- ! Example !! Syllabified |- | '''ama'''.....''hot'' || '''a-ma''' |- | '''ayma'''.....''warm'' || '''ay-ma''' |- | '''aymsea'''.....''warming up'' || '''aym-se-a''' |- | '''pixwa'''....''caught'' || '''pix-wa''' |- | '''upayo'''....''will have come'' || '''u-pa-yo''' |- | '''vyaa'''....''true'' || '''vya-a''' |- | '''vyaay'''....''truly'' || '''vya-ay''' |- | '''vay'''....''indeed'' || '''vay''' |- | '''tambwa'''....''settled'' || '''tam-bwa''' |- | '''faof'''....''plank'' || '''fa-of''' |- | '''twoyba'''....''he-she'' || '''twoy-ba''' |- | '''yansauna'''....''common'' || '''yan-sa-u-na''' |} : If a '''y''' or '''w''' comes between vowels, a hyphen is used to indicate whether the '''y''' or '''w''' belongs to the previous or following syllable: '''zoy-aper'''....''to get back on'' '''zo-yeper'''....''to enter through the rear'' '''gaw-aber'''....''to re-mount'' <noinclude>{{Chapter navigation with TOC|Pronunciation|Stress}}</noinclude> gi6rt38lcigcx6mjj8dld12e3q3vila 4634096 4634095 2026-05-04T15:36:50Z Tyoyafud 6233 4634096 wikitext text/x-wiki <noinclude>{{status|100%}}</noinclude> : Every syllable in Mirad contains one and only one vowel. A '''y''' when final or followed by a consonant is used to post-y-glide or diphthongize the previous vowel and is therefore considered part of the syllable in which that vowel is the nucleus (see case 2, below). Similarly, the '''''liquids''''' '''r''' and '''l''', when final or followed by a consonant are considered to be a part of the syllable where the preceding vowel is the nucleus (see case 4, below). Two vowels in a row form two syllabic nuclei (see cases 3, 6, and 7, below). How syllables are divided is important for determining where the stress accent goes in a word (see [[Mirad_Grammar/Stress]], below). {| class="wikitable" style="background:lightyellow;font-size:smaller;margin-left:4.8em" |+ Syllabification |- ! Example !! Syllabified |- | '''ama'''.....''hot'' || '''a-ma''' |- | '''ayma'''.....''warm'' || '''ay-ma''' |- | '''aymsea'''.....''warming up'' || '''aym-se-a''' |- | '''pixwa'''....''caught'' || '''pix-wa''' |- | '''upayo'''....''will have come'' || '''u-pa-yo''' |- | '''vyaa'''....''true'' || '''vya-a''' |- | '''vyaay'''....''truly'' || '''vya-ay''' |- | '''vay'''....''indeed'' || '''vay''' |- | '''tambwa'''....''settled'' || '''tam-bwa''' |- | '''faof'''....''plank'' || '''fa-of''' |- | '''twoyba'''....''he-she'' || '''twoy-ba''' |- | '''yansauna'''....''common'' || '''yan-sa-u-na''' |} : If a '''y''' or '''w''' comes between vowels, a hyphen is used to indicate whether the '''y''' or '''w''' belongs to the previous or following syllable: :* '''zoy-aper'''....''to get back on'' :* '''zo-yeper'''....''to enter through the rear'' :* '''gaw-aber'''....''to re-mount'' <noinclude>{{Chapter navigation with TOC|Pronunciation|Stress}}</noinclude> 473f756inlbncq71ltcjeusj0l6pe5s 4634115 4634096 2026-05-04T16:31:07Z Tyoyafud 6233 4634115 wikitext text/x-wiki <noinclude>{{status|100%}}</noinclude> : Every syllable in Mirad contains one and only one vowel. A '''y''' when final or followed by a consonant is used to post-y-glide or diphthongize the previous vowel and is therefore considered part of the syllable in which that vowel is the nucleus (see case 2, below). Similarly, the '''''liquids''''' '''r''' and '''l''', when final or followed by a consonant are considered to be a part of the syllable where the preceding vowel is the nucleus (see case 4, below). Two vowels in a row form two syllabic nuclei (see cases 3, 6, and 7, below). How syllables are divided is important for determining where the stress accent goes in a word (see [[Mirad_Grammar/Stress]], below). {| class="wikitable" style="background:lightyellow;font-size:smaller;margin-left:4.8em" |+ Syllabification |- ! Example !! Syllabified |- | '''ama'''.....''hot'' || '''a-ma''' |- | '''ayma'''.....''warm'' || '''ay-ma''' |- | '''aymsea'''.....''warming up'' || '''aym-se-a''' |- | '''pixwa'''....''caught'' || '''pix-wa''' |- | '''upayo'''....''will have come'' || '''u-pa-yo''' |- | '''vyaa'''....''true'' || '''vya-a''' |- | '''vyaay'''....''truly'' || '''vya-ay''' |- | '''vay'''....''indeed'' || '''vay''' |- | '''tambwa'''....''settled'' || '''tam-bwa''' |- | '''faof'''....''plank'' || '''fa-of''' |- | '''twoyba'''....''he-she'' || '''twoy-ba''' |- | '''yansauna'''....''common'' || '''yan-sa-u-na''' |} : If a '''y''' or '''w''' comes between vowels, a hyphen is used to indicate whether the '''y''' or '''w''' belongs to the previous or following syllable: :* '''zoy-aper'''....''to get back on'' (< '''zoy'''....''back'' + '''aper'''....''get on'') :* '''zo-yeper'''....''to enter through the rear'' (< '''zo'''....''rear'' + '''yeper'''....''enter'') :* '''gaw-aber'''....''to re-mount'' (< '''gaw'''....''re-'' + '''aber'''....''to put on'') <noinclude>{{Chapter navigation with TOC|Pronunciation|Stress}}</noinclude> 92cmvaklninlyhnwgfntjzpc4uzh7lw 0 448109 4634209 4533025 2026-05-05T01:22:31Z BlockBot Empires 3541400 Added the steps so people can know what they need to do. If stuff needs to be added, go ahead 4634209 wikitext text/x-wiki {{Split}} With video games becoming a major part of the entertainment industry, the advent of video capture devices and screen recording software, and the existence of user-driven streaming services such as YouTube and Twitch, a new art form which combines all three has come about in recent years. Previously, the experience of playing a video game was a more or less solo experience; at most it could be shared with a few friends in the same room. Now you can record you experience and share it with people from all over the world, or live stream your game so people can watch with you as you play. But if you actually want to be a creator in this new realm, there are several technical hurdles you must overcome, and a few new skills you must master which have little to do with your game playing skills. It's a lot more complicated than just pressing a "Record" button while you play. This guide is intended to help beginners over the hurdles and teach the skills needed to create and make public your own game experiences. == Different sub-genres == There are several different sub-genres, and knowing what to call them will help your viewers to find you. Here is the list of sub-genres: * Live stream: This is where you play the game live for your audience. On most platforms which support live streaming, you can see viewers comments via text while you're playing, and respond if you want to. A possible disadvantage is that you can't edit the content. [[File:Let's Play 0 AD.webm|thumb|An example of a Let's Play, for the game 0 AD]] * Let's Play: This is where you record yourself playing the game. In this case you can edit the content to remove pauses and uneventful sections. Otherwise it's very similar to just sharing your experience playing the game. ** Blind: A blind Let's Play is where you're recording yourself playing the game for the first time and with little or no previous knowledge of the story. In this way you're sharing your reactions to events and plot developments as they happen. Some types of games are better for blind Let's Plays than others. * Walkthrough/guide: If you're already an expert at a game, and think others might benefit from what you've learned, you can create a walkthrough which guides new players through any problem areas. Or if you've discovered a new strategy you can share it with others. * Review/First look: This is where you can discuss the merits or problems with a game. In this case, you're taking a few representative scenes from the game rather than the entire thing. A "First look" is generally shorter and only covers the early part of a game, and is used for recently published games. Either way, the idea is to help viewers decide if they want to purchase the game for themselves. * Speedruns, glitch exploits, and other stunts: Here, you're just recording the fact that you can complete the game in a certain time, or completing the game under some unusual condition. * Highlights: A short video showing one specific event in a game, typically a feat of player skill. * Documentary or preservation: In instances where a game may be lost to time (Typically when a multiplayer service is shut down), a video recording can faithfully show how players interacted with a game while it was on the market. * Other: The format is flexible so you can try your own innovations. You might create a video exploring the back-story and lore associated with the game's characters and world. Or a video which pokes fun at everything that happens in the game. The sub-genres are just labels, not boxes you have to fit your ideas into. === Commentary === One decision you need to make is whether to include commentary. Commentary allows you to share your thoughts and feelings about what's happening in the game. But not all viewers appreciate commentary and prefer to just watch the gameplay. Commentary is necessary for walkthroughs and reviews, but it would probably be a distraction in a speedrun. If you do decide to do commentary, then you will need a microphone to record it. It's usually worthwhile to invest in a good microphone instead of relying on what may have come with your computer. Commentary can either be live, in other word recorded as you play, or recorded after the fact. A Let's Play would usually either have live commentary or no commentary at all. On the other hand review or video about lore would general have audio recorded after editing. == What you will need == ;A game, preferably one you like playing ;Recording software or a recording device For games you can play on a computer, you can run recording software while the game is playing to record what's happening. Be aware however, the resources available on a computer are limited, and if your game stretches the capacity of your computer then the additional load of recording the video may cause problems. Since the mid-2010's many video game consoles have come with limited video capture capabilities built in. These built in features are often limited in video quality, as well as in recording duration. For consoles without this feature, or for greater control of video quality, an external recording device is needed. These come in a few varieties, and are typically either oriented to older style consoles (RF, Composite jacks), or newer consoles (HDMI ports). In any case, knowing how to set up the software or device to get the best results is skill in itself. ;Microphone (for commentary) If you're going to do commentary then you will need a microphone to record it. One with digital output such as USB is recommended since it will not pick up interference from your computer. Headphones for listening are a good idea as well since you don't want to game sound to echo in your microphone. A headset with headphone plus mike will usually perform both functions well. It's best to keep your audio environment in mind as well. Find an area free of street and household noises if possible. Put your phone on vibrate and take common sense precautions to keep extraneous sounds from being recorded. ;Video editing software (except for live streams) Unless you're doing a live stream you'll need to edit your video to make it more appealing to your viewers. Editing is another skill in itself, but fortunately you don't need to be an expert to put together a gaming video. ;Video player (optional) You should be able to watch your video in the editor, but it won't hurt to have an alternate way of reviewing your final cut. It should be sophisticated enough do fast to step through a video frame by frame and to provide information about video quality. ;Camera setup (optional) If you plan on including reaction style content in your videos, a webcam or other camera will let you capture a video feed of yourself as you play your game. This video feed can then be superimposed in the video using software. Your camera feed can be enhanced or modified a number of ways. A green screen or other chroma key will allow you to more easily remove the background from this video feed using software, giving more space for gameplay footage, or to permit the use of a virtual background. Alternatively, if you would prefer to use a cartoon or 3D model for reactions, special avatar software can translate your movements captured on camera into a reaction on a virtual avatar. ;Image editor (except for live streams) You might think that if you upload a video to YouTube that it will create a thumbnail image for it automatically. While YouTube does offer to create a thumbnail, it's just a single frame chosen more or less at random. It's almost always better to create your own thumbnail, one which will catch a viewer's eye and provide some information about the video itself. But images don't create themselves; you generally have to combine elements from the game and other sources, text, and perhaps special effects to create a good thumbnail image. You'll need a image editor to put all these things together and create an image. An image editor and the skill needed to use it may have other benefits as well. ;A streaming service creator account A YouTube gaming channel channel is, at it's core, a YouTube channel. You'll need to master the mechanics of uploading videos or streaming live, and of publishing and organizing your videos. If you're really serious about catching views then there are all sorts of analytics you can study. There are also complex issues of monetization and age restrictions you should at least be familiar with at a basic level, even if you don't expect to receive any income from your channel. == Video quality == Knowing the basics of video quality will help in deciding how to set up your recording software or device for best results. You might think making every video as high quality as possible would be the way to go, but there are trade-offs. Higher quality video takes longer to upload and process, and streaming services often tailor the quality of video sent to viewers to match their internet capabilities. Given the additional overhead, it doesn't make sense to increase the quality of the recording beyond a certain amount. Televisions and computer monitors are only capable of displaying a certain level of quality. While technology is rapidly improving, there is also a limit to how much information the human eye can perceive and how much information the human brain can process. Some games, especially older games and those which use pixel graphics, don't produce high quality video to start with, and recording at high quality won't add quality that's not in the source. === Frame rate/Frames per second === [[File:Animhorse.gif|thumb|This animation of horse is displayed at about 12 drawings per second. It represents the lowest frame rate that viewers will find acceptable in most cases.]] A "moving" picture is really just a sequence of still pictures shown at such a high speed that the human eye perceives motion. But what speed is necessary to "fool" the human eye? The rate at which the pictures are shown is called the frame rate, and measured in frames per second (FPS). At 5 frames per second, individual pictures are clearly visible and the illusion of motion is lost. But for decades feature films were made at 24 frames per second and most people were satisfied with the result. Hand drawn cartoons often run at lower frame rate in order to save on production cost; if someone has to draw each frame then reducing the frame rate reduces the workload. For games with photorealistic graphics, a higher frame rate is usually expected, 30 frames per second is standard for computer video. For games with a lot of action and movement, some viewers may see an improvement at 60 frames per second, and some game consoles can create a frame rate of 120 FPS. Some games with hand drawn animation use, in effect, two frame rates. A lower frame rate (as low as 12 FPS) is used to save on drawing, but for background motion, where nothing changes but the position of the object, a higher frame rate is used. For text-based and point-and-click games where there is little of no motion, a lower frame rate can be used. A point-and-click game goes at one frame per click, not multiple frames per second. There is little point in recording more frames per second than the game actually displays, and it may take some research and experimentation to determine the best frame rate for an individual game. === Resolution/Pixels === Just as a moving picture is really just sequence of still pictures, an image shown on a computer screen is really just array of small dots. So, again, the question arises of how small do the dots have to be before they are no longer recognizable as individual dots and are perceived as a continuously shaded picture. The individual dots are known as pixels and a typical computer screen may show them in a 1920 by 1080 array, and these dimensions define the resolution of the image. In other words the image is composed of a rectangle, 1920 pixels wide and 1080 high. The ratio of these numbers, in this case 1920:1080 = 16:9 or 1.777..., is called the aspect ratio. The 16:9 aspect ratio is the current standard for digital television and video, but the older 5:4 aspect ratio is still seen. At a resolution of 480 by 270, the image will appear noticeably blocky, but some games use this resolution as a deliberate design choice; older video games used low resolution because of limitations on technology, and some games imitate that look, called pixel graphics, to give the game a retro feel. Some gaming consoles can produce higher resolutions, for example 4k or approximately 4000 pixels high. Another aspect of image quality is color depth, but it's not really necessary to consider that here. === Video compression === Video compression is the method used to amount of information used by a video. At the standard 30 frames per second and 1920 by 1080 resolution (and assuming 3 bytes per pixel color depth), it would take 625 gigabytes to store an hour of video. With compression, it's possible to store the same hour of video in less than 1% of the space with little noticeable loss in quality. It is video compression that makes streaming even possible; no one would stream an hour television show if it took a week to download, and communications infrastructure would quickly become overloaded if many people tried. Video compression uses complex algorithms and sophisticated mathematics to perform its magic, but there is one aspect you should be familiar with if you plan on creating and editing videos: ;Key Frames The difference between two consecutive frames of video is usually very small. This can be used to compress video much more than would otherwise be possible. A typical compression scheme breaks up a video into chunks of a few seconds long, fully records the first frame of each chunk, and only records the differences for the remaining frames. The first frame of each chunk is called a key frame. When editing a video, it's much easier to cut only on the key frame boundaries of the chunks. It's relatively easy to move the chunks around since they are independent, but making changes on a random frame will require that the video be recompressed to allow for the fact that the start of a chunk is no longer there. So it's very preferable to work with whole chunks when editing a video if possible. The alternative is to recompress the video after editing, a lengthy and processor intensive process. More sophisticated editing, such as overlaying text or special effects, will also require a recompression step. If you only plan on doing basic editing, such as trimming the beginning or the end, or that section where you put the game on pause for a few minutes, you need to plan ahead and make the chunks fairly small, around 1 second, to give you some flexibility on where make your cuts. You can do with by setting the key frame interval in your recording software. Key frames are important for streaming as well. If a viewer is joining your stream, they won't be able to see your video until the next key frame. For this reason, streaming platforms usually insist that your key frame interval be set to at most 2 seconds. == Steps to create a Let's Play == Now let's talk about what goes into to creating a Let's Play, or any recorded game play video. Streaming is somewhat different and will be covered elsewhere. === Preparation === # Decide on a game and what type of video it will be. If you're doing a Let's Play then it should be a game you think you would like. The idea is that you're sharing the fun of playing with viewers, so if you're playing a game you don't like then no one will enjoy it. If you're doing a first look or a review, then at least pick a game that you might like. For a tutorial, find an issue in a game that other players seem to having trouble with, or which you had trouble with and managed to figure out. # Decide on an editing style. This is needed because simple editing requires much less effort and processing power than more complex editing, see the discussion on Key Frames above. A simple editing style requires only a few seconds to process the final edit, but more complex editing make take an hour of intense computation to process an edit. Related to this, try to decide on the overall format of the video. Will it be a single video or a series of videos? Will each video cover a single session of gameplay, or will you be gathering clips from multiple sessions, or will you be splitting a single session into multiple videos? How long will your video(s) be? # Optimize you hardware for recording, since some of you computer and GPU settings may affect the quality of your recording. For example we recommend that you set a frame rate limit on your GPU so your game doesn't too much graphics processing power; your recording will require some processing power as well. Limit the framerate to the framerate of your recording since there is no reason to generate frames that won't be seen. In addition, make sure there are no programs running other than the game and the recorder, this to ensure that your game and recorder have all available CPU and memory resources available. # Set up your recording software or device to record the game. Video quality settings should be appropriate for the game, but may be limited by the hardware you're using. If possible, save settings customized for each game. It's a good idea to record your settings somewhere such as a spreadsheet. For information on individual recording software and devices, see the following: #* [[/Recording game video using OBS/]] #* (Other recording software and devices to be added.) # Run one or more technical tests before starting. This should cover the entire process from recording to editing, to make sure everything runs smoothly and that you get a satisfactory result. It may mean playing the first five minutes of a game multiple times, but the alternative is that you may discover after the fact that your game recording is unusable. Remember to check audio quality and balance as well; can you hear both yourself and the game clearly in the video? This is the time to adjust game volume and your mike's volume. # Start the game. === For each video === # Turn on your recording software or device, check that you have the correct settings for the game you're playing, and make sure it's recording. The most common, basic, and fatal mistake you can make is to forgot to press the Record button. This not only results in lost effort, but if you're doing a blind Let's Play or a first look video it means you've lost the chance to record your first reaction to what happens in the game. It's much better to prevent this by turning the recording on early and record a minute or two of blank screen which you can edit out. # Switch your audio to headphones if necessary. Check audio levels to make sure audio (from both the game and yourself) is being picked up. # Depending on how good your memory is, how long since your last episode, and how much of a summary of where you are you like to give, you may want to refresh your memory about where you were and what was going on in your last episode. If it's a difficult game and you've gotten rusty after a long hiatus, then by all means practice your skills before starting again. # Double check your recording is on and video and audio are both working, then start playing. If you're doing live commentary then it's customary to introduce yourself at the start of each video, though not everyone does this. Perhaps the must unnatural, not to mention distracting aspect of live commentary is that you're keeping up a running conversation with an imaginary person as you play. You may want to do no commentary or record commentary afterward depending of the type of video and your personal preference. If you're recording commentary afterwards then you may want to use a script, in which case writing a script will have to be part of your process. # When you're done with a session, wrap up the commentary (if any) and shut everything down. # Your video file will probably have a meaningless name, so rename it to include the name of the game and other relevant information, for example HappyFarmingSimEp5.mkv. # Now it's time to edit your video. At the least you should trim the beginning and end of the video, and cut out pauses and other "dead" sections. For example if you just walking or going through a merchant's inventory for a long period of time then you might want to cut most of those sections. Of course how aggressive you are with this kind of thing is up to you. You may be gathering clips from different recordings for certain projects, in which case editing will be more difficult and time consuming. Remember that the video will have to be reprocessed for some edits, including specials effect such as dissolved and wipes, and adding on-screen text. When you're done editing, avoid writing over you're original recording; video files are large and you'll probably want to delete raw footage eventually, but save them for a while in case something goes wrong in the editing process. As long as you have the video open in an editor, you may want to save a few frames to use in thumbnail images. For information on individual video editing tools, see the following: #* [[/Editing game video using Avidemux/]] #* (Other video editing software to be added.) # Create a thumbnail image for the video. This can contain various elements such as text, an image from the game, a channel logo, or a picture or drawing of yourself. Thumbnails are key for drawing attention of viewers. A good thumbnail usually brings in more views. For information on individual editing tools, see the following: #* [[/Creating a thumbnail using GIMP/]] #* [[/Creating a thumbnail using Photoshop/]] #* (Other image software to be added.) # Upload the finished video. Depending on the video platform you will probably need a video title and a detailed video description. For information on individual video platforms, see the following: #* [[/Uploading a game video to YouTube/]] #* (Other video platforms to be added.) # Review the video to make sure everything went as expected. Depending on how much effort you want to put into it, you can probably expect to spend twice as much time on other activities as you spend actually playing the game. For more complex projects that ratio will go up. == Steps to stream a game video == # Get a streaming platform (Such as Twitch) # Open your streaming software. If you’re just starting out, use a simple streaming software you can understand. # Open the game you want to stream and begin the livestream. ==Related Wikibooks== * [[Open Broadcaster Software]] - A general guide to a popular screen capture software. (Now known as OBS Studio) {{shelves|Electronic games}} {{Status|25%}} i4bt8ii2tlkfp9mpalsh947gftwnrds 3 452115 4634061 4632793 2026-05-04T12:16:20Z MediaWiki message delivery 1188004 /* Wikipedia translation of the week: 2026-19 */ new section 4634061 wikitext text/x-wiki <noinclude> {{User:Xeverything11/tabs}} {{User:Xeverything11/header|Welcome to|Xeverything11's|updates talk page!|archives= * [[User talk:Xeverything11/archives/2022|2022]] * [[User talk:Xeverything11/archives/2023|2023]] }} </noinclude> __NOTOC__ {{User:MiszaBot/config |archive = User talk:Xeverything11/archives/%(year)d |algo = old(60d) |counter = 1 |minthreadsleft = 1 |minthreadstoarchive = 1 }} == Tech News: 2023-03 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/03|Translations]] are available. '''Problems''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] The URLs in "{{int:last}}" links on page history now contain <bdi lang="zxx" dir="ltr"><code><nowiki>diff=prev&oldid=[revision ID]</nowiki></code></bdi> in place of <bdi lang="zxx" dir="ltr"><code><nowiki>diff=[revision ID]&oldid=[revision ID]</nowiki></code></bdi>. This is to fix a problem with links pointing to incorrect diffs when history was filtered by a tag. Some user scripts may break as a result of this change. [https://phabricator.wikimedia.org/T243569] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-17|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-01-18|en}}. It will be on all wikis from {{#time:j xg|2023-01-19|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Some [[mw:Special:MyLanguage/Talk pages project/Usability|changes to the appearance of talk pages]] have only been available on <code>{{ns:1}}:</code> and <code>{{ns:3}}:</code> namespaces. These will be extended to other talk namespaces, such as <code>{{ns:5}}:</code>. They will continue to be unavailable in non-talk namespaces, including <code>{{ns:4}}:</code> pages (e.g., at the Village Pump). You can [[Special:Preferences#mw-prefsection-editing-discussion|change your preferences]] ([[Special:Preferences#mw-prefsection-betafeatures|beta feature]]). [https://phabricator.wikimedia.org/T325417] *On Wikisources, when an image is zoomed or panned in the Page: namespace, the same zoom and pan settings will be remembered for all Page: namespace pages that are linked to a particular Index: namespace page. [https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ProofreadPage/+/868841] * The Vector 2022 skin will become the default for the English Wikipedia desktop users. The change will take place on January 18 at 15:00 UTC. [[:en:w:Wikipedia:Vector 2022|Learn more]]. '''Future changes''' * The 2023 edition of the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey]], which invites contributors to make technical proposals and vote for tools and improvements, starts next week on 23 January 2023 at 18:00 UTC. You can start drafting your proposals in [[m:Community Wishlist Survey/Sandbox|the CWS sandbox]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:11, 17 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24381020 --> == Tech News: 2023-04 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/04|Translations]] are available. '''Problems''' * Last week, for ~15 minutes, all wikis were unreachable for logged-in users and non-cached pages. This was caused by a timing issue. [https://wikitech.wikimedia.org/wiki/Incidents/2023-01-17_MediaWiki] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-24|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-01-25|en}}. It will be on all wikis from {{#time:j xg|2023-01-26|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * If you have the Beta Feature for [[mw:Special:MyLanguage/Talk pages project|DiscussionTools]] enabled, the appearance of talk pages will add more information about discussion activity. [https://www.mediawiki.org/wiki/Special:MyLanguage/Talk_pages_project/Usability#Status][https://phabricator.wikimedia.org/T317907] * The 2023 edition of the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey]] (CWS), which invites contributors to make technical proposals and vote for tools and improvements, starts on Monday 23 January 2023 at [https://zonestamp.toolforge.org/1674496814 18:00 UTC]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:46, 23 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24418874 --> == Tech News: 2023-05 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/05|Translations]] are available. '''Problems''' * Last week, for ~15 minutes, some users were unable to log in or edit pages. This was caused by a problem with session storage. [https://wikitech.wikimedia.org/wiki/Incidents/2023-01-24_sessionstore_quorum_issues] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.21|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-31|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-01|en}}. It will be on all wikis from {{#time:j xg|2023-02-02|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] Wikis that use localized numbering schemes for references need to add new CSS. This will help to show citation numbers the same way in all reading and editing modes. If your wiki would prefer to do it yourselves, please see the [[mw:Special:MyLanguage/Parsoid/Parser Unification/Cite CSS|details and example CSS to copy from]], and also add your wiki to the list. Otherwise, the developers will directly help out starting the week of February 5. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 31 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24455949 --> == Wikipedia translation of the week: 2023-06 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sweden Finns' Day]] '''<br /> <small>''([[:fi:Ruotsinsuomalaisten päivä]]) ([[:sv:Sverigefinnarnas dag]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sverigefinskaflaggan.svg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Sweden Finns' Day''' (Finnish: Ruotsinsuomalaisten päivä, Swedish: Sverigefinnarnas dag) is an anniversary celebrated in Sweden on 24 February. The anniversary of the calendar was approved by the Swedish Academy in 2010 and was celebrated for the first time in 2011. February 24 was chosen as the birthday of Carl Axel Gottlund, a collector of folk poetry and a defender of the status of the Finnish language. The purpose of the day is to celebrate the Sweden Finns and to recognize their history, language and culture as a prominent part of Sweden's cultural heritage. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:04, 6 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24491747 --> == Tech News: 2023-06 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/06|Translations]] are available. '''Recent changes''' * In the [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements|Vector 2022 skin]], logged-out users using the full-width toggle will be able to see the setting of their choice even after refreshing pages or opening new ones. This only applies to wikis where Vector 2022 is the default. [https://phabricator.wikimedia.org/T321498] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-08|en}}. It will be on all wikis from {{#time:j xg|2023-02-09|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Previously, we announced when some wikis would be in read-only for a few minutes because of a switch of their main database. These switches will not be announced any more, as the read-only time has become non-significant. Switches will continue to happen at 7AM UTC on Tuesdays and Thursdays. [https://phabricator.wikimedia.org/T292543#8568433] * Across all the wikis, in the Vector 2022 skin, logged-in users will see the page-related links such as "What links here" in a [[mw:Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Page_tools|new side menu]]. It will be displayed on the other side of the screen. This change had previously been made on Czech, English, and Vietnamese Wikipedias. [https://phabricator.wikimedia.org/T328692] *[[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey 2023]] will stop receiving new proposals on [https://zonestamp.toolforge.org/1675706431 Monday, 6 February 2023, at 18:00 UTC]. Proposers should complete any edits by then, to give time for [[m:Special:MyLanguage/Community_Wishlist_Survey/Help_us|translations]] and review. Voting will begin on Friday, 10 February. '''Future changes''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] Gadgets and user scripts will be changing to load on desktop and mobile sites. Previously they would only load on the desktop site. It is recommended that wiki administrators audit the [[MediaWiki:Gadgets-definition|gadget definitions]] prior to this change, and add <bdi lang="zxx" dir="ltr"><code>skins=…</code></bdi> for any gadgets which should not load on mobile. [https://phabricator.wikimedia.org/T328610 More details are available]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 10:21, 6 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24491749 --> == Wikipedia translation of the week: 2023-07 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Delivery robot]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Woman Takes Groceries from Dax Delivery Robot.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> A '''delivery robot''' is an autonomous robot that provides "last mile" delivery services. An operator may monitor and take control of the robot remotely in certain situations that the robot cannot resolve by itself such as when it is stuck in an obstacle. Delivery robots can be used in different settings such as food delivery, package delivery, hospital delivery, and room service. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:26, 13 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24515453 --> == Tech News: 2023-07 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/07|Translations]] are available. '''Problems''' * On wikis where patrolled edits are enabled, changes made to the [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|mentor list]] by autopatrolled mentors are not correctly marked as patrolled. It will be fixed later this week. [https://phabricator.wikimedia.org/T328444] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-15|en}}. It will be on all wikis from {{#time:j xg|2023-02-16|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * The Reply tool and other parts of [[mw:Special:MyLanguage/Help:DiscussionTools#Mobile|DiscussionTools]] will be deployed for all editors using the mobile site. You can [[mw:Special:MyLanguage/Talk_pages_project/Mobile#Status_Updates|read more about this decision]]. [https://phabricator.wikimedia.org/T298060] '''Future changes''' * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T328287][https://phabricator.wikimedia.org/T327920][https://wikitech.wikimedia.org/wiki/Deployments] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:49, 14 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24540832 --> == Wikipedia translation of the week: 2023-08 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Buddha Dhatu Jadi]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Swarno Mandir.JPG|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Buddha Dhatu Jadi''' (Bengali: বুদ্ধ ধাতু জাদি; Burmese: ဗုဒ္ဓဓာတုစေတီ also known as the Bandarban Golden Temple) is located close to Balaghata town, in Bandarban City, in Bangladesh. Dhatu are the material remains of a holy person, and in this temple the relics belong to Buddha. It is the largest Theravada Buddhist temple in Bangladesh and has the second-largest Buddha statue in the country. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:18, 20 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24581813 --> == Tech News: 2023-08 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/08|Translations]] are available. '''Problems''' * Last week, during planned maintenance of Cloud Services, unforeseen complications forced the team to turn off all tools for 2–3 hours to prevent data corruption. Work is ongoing to prevent similar problems in the future. [https://phabricator.wikimedia.org/T329535] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-22|en}}. It will be on all wikis from {{#time:j xg|2023-02-23|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). *The voting phase for the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey 2023]] ends on [https://zonestamp.toolforge.org/1677261621 24 February at 18:00 UTC]. The results of the survey will be announced on 28 February. '''Future changes''' * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T328287][https://phabricator.wikimedia.org/T327920][https://wikitech.wikimedia.org/wiki/Deployments] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:58, 21 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24570514 --> == Wikipedia translation of the week: 2023-09 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Alina Scholtz]] '''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Alina Scholtz''' (24 September 1908 – 25 February 1996) was a Polish landscape architect, known as one of country's pioneers in developing the field. Throughout her career she worked on various public and private projects for cemeteries, parks and green spaces. Some of her most noted works include the grounds of a villa on Kielecka Street in Warsaw for which she won a Silver Medal at the 1937 World Exhibition in Paris, the memorial cemetery to the victims of the Palmiry massacre, and landscaping projects along the East-West traffic route of Warsaw. In addition to her design work, she served as one of the founding members of the International Federation of Landscape Architects. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:04, 27 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24617511 --> == Tech News: 2023-09 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/09|Translations]] are available. '''Problems''' * Last week, in some areas of the world, there were problems with loading pages for 20 minutes and saving edits for 55 minutes. These issues were caused by a problem with our caching servers due to unforseen events during a routine maintenance task. [https://wikitech.wikimedia.org/wiki/Incidents/2023-02-22_wiki_outage][https://wikitech.wikimedia.org/wiki/Incidents/2023-02-22_read_only] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-01|en}}. It will be on all wikis from {{#time:j xg|2023-03-02|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:47, 27 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24634242 --> == Wikipedia translation of the week: 2023-10 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Mary Nzimiro]] '''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Mary Nzimiro''', birthname Mary Nwametu Onumonu, MBE (1898–1993) was a pioneering Nigerian businesswoman, politician and women's activist. In 1948, she was appointed principal representative of the United Africa Company (UAC) for Eastern Nigeria, while maintaining textile and cosmetics retail outlets of her own in Port Harcourt, Aba and Owerri. By the early 1950s, she was among the richest individuals in West Africa, becoming a resident of the exclusive Bernard Carr Street in Port Harcourt. On the political front, she was a member of the influential National Council of Nigeria and the Cameroons, becoming a member of its executive committee in 1957 and vice-president of the NCNC Estern Women's Association in 1962. During the Nigerian Civil War (1967–1970), she organized Igbo women in support of the Biafrans. As a result she lost most of her property in Port Harcourt and returned to her native Oguta where she died in 1993. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:47, 6 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24636259 --> == Tech News: 2023-10 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/10|Translations]] are available. '''Recent changes''' * The Community Wishlist Survey 2023 edition has been concluded. Community Tech has [[m:Special:MyLanguage/Community Wishlist Survey 2023/Results|published the results]] of the survey and will provide an update on what is next in April 2023. * On wikis which use [[mw:Special:MyLanguage/Writing_systems|LanguageConverter]] to handle multiple writing systems, articles which used custom conversion rules in the wikitext (primarily on Chinese Wikipedia) would have these rules applied inconsistently in the table of contents, especially in the Vector 2022 skin. This has now been fixed. [https://phabricator.wikimedia.org/T306862] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-08|en}}. It will be on all wikis from {{#time:j xg|2023-03-09|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * A search system has been added to the [[Special:Preferences|Preferences screen]]. This will let you find different options more easily. Making it work on mobile devices will happen soon. [https://phabricator.wikimedia.org/T313804] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:50, 6 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24676916 --> == Wikipedia translation of the week: 2023-11 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Elizabeth Langdon Williams]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Elizabeth Langdon Williams.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Elizabeth Langdon Williams''' (February 8, 1879 in Putnam, Connecticut – 1981 in Enfield, New Hampshire) was an American human computer and astronomer whose work helped lead to the discovery of Pluto, or Planet X. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:21, 13 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24700408 --> == Tech News: 2023-11 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/11|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.27|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-15|en}}. It will be on all wikis from {{#time:j xg|2023-03-16|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-cbk_zamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cdowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cebwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ckbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-csbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T304542][https://phabricator.wikimedia.org/T304550] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:20, 13 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24700189 --> == Wikipedia translation of the week: 2023-12 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:I Didn't Raise My Boy to Be a Soldier]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Peerless Quartet - I Didn't Raise my Boy to be a Soldier.ogg|300px|center]] <div style="text-align:left; padding: .4em;"> an American anti-war song that was influential within the pacifist movement that existed in the United States before it entered World War I. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:31, 20 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24720571 --> == Tech News: 2023-12 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/12|Translations]] are available. '''Problems''' * Last week, some users experienced issues loading image thumbnails. This was due to incorrectly cached images. [https://phabricator.wikimedia.org/T331820] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-22|en}}. It will be on all wikis from {{#time:j xg|2023-03-23|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] A link to the user's [[{{#special:CentralAuth}}]] page will appear on [[{{#special:Contributions}}]] — some user scripts which previously added this link may cause conflicts. This feature request was [[:m:Community Wishlist Survey 2023/Admins and patrollers/Add link to CentralAuth on Special:Contributions|voted #17 in the 2023 Community Wishlist Survey]]. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The [[{{#special:AbuseFilter}}]] edit window will be resizable and larger by default. This feature request was [[:m:Community Wishlist Survey 2023/Anti-harassment/Make the AbuseFilter edit window resizable and larger by default|voted #80 in the 2023 Community Wishlist Survey]]. * There will be a new option for Administrators when they are unblocking a user, to add the unblocked user’s user page to their watchlist. This will work both via [[{{#special:Unblock}}]] and via the API. [https://phabricator.wikimedia.org/T257662] '''Meetings''' * You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on [https://zonestamp.toolforge.org/1679677204 24 March at 17:00 (UTC)]. See [[mw:Special:MyLanguage/Wikimedia Apps/Office Hours|details and how to join]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:26, 21 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24732558 --> == Wikipedia translation of the week: 2023-13 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:es:Diana Aguavil]]'''<br /> <small>''([[:en:Diana Aguavil]]) ([[:pt:Diana Aguavil]]) ''</small> </div> Please be bold and help translate this article! ---- [[File:Diana Aguavil.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Diana Alexandra Aguavil Calazacón''' (born 7 August 1983) is an Ecuadorian indigenous leader, since 25 August 2018, the first female governor of the Tsáchila nationality after 104 years of male administrations and winning the 2018 Tsáchila election. She was also the second woman to become a candidate. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:39, 27 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24758626 --> == Tech News: 2023-13 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/13|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]] condition limit was increased from 1000 to 2000. [https://phabricator.wikimedia.org/T309609] * [[:m:Special:MyLanguage/Global AbuseFilter#Locally disabled actions|Some Global AbuseFilter]] actions will no longer apply to local projects. [https://phabricator.wikimedia.org/T332521] * Desktop users are now able to subscribe to talk pages by clicking on the {{int:discussiontools-newtopicssubscription-button-subscribe-label}} link in the {{int:toolbox}} menu. If you subscribe to a talk page, you receive [[mw:Special:MyLanguage/Notifications|notifications]] when new topics are started on that talk page. This is separate from putting the page on your watchlist or subscribing to a single discussion. [https://phabricator.wikimedia.org/T263821] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-29|en}}. It will be on all wikis from {{#time:j xg|2023-03-30|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). '''Future changes''' * You will be able to choose [[mw:Special:MyLanguage/VisualEditor/Diffs|visual diffs]] on all [[m:Special:MyLanguage/Help:Page history|history pages]] at the Wiktionaries and Wikipedias. [https://phabricator.wikimedia.org/T314588] * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] The legacy [[mw:Mobile Content Service|Mobile Content Service]] is going away in July 2023. Developers are encouraged to switch to Parsoid or another API before then to ensure service continuity. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/4MVQQTONJT7FJAXNVOFV3WWVVMCHRINE/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:14, 28 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24780854 --> == Tech News: 2023-14 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/14|Translations]] are available. '''Recent changes''' * The system for automatically creating categories for the [[mw:Special:MyLanguage/Extension:Babel|Babel]] extension has had several important changes and fixes. One of them allows you to insert templates for automatic category descriptions on creation, allowing you to categorize the new categories. [https://phabricator.wikimedia.org/T211665][https://phabricator.wikimedia.org/T64714][https://phabricator.wikimedia.org/T170654][https://phabricator.wikimedia.org/T184941][https://phabricator.wikimedia.org/T33074] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-05|en}}. It will be on all wikis from {{#time:j xg|2023-04-06|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Some older [[w:en:Web browser|Web browsers]] will stop being able to use [[w:en:JavaScript|JavaScript]] on Wikimedia wikis from this week. This mainly affects users of Internet Explorer 11. If you have an old web browser on your computer you can try to upgrade to a newer version. [https://phabricator.wikimedia.org/T178356] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The deprecated <bdi lang="zxx" dir="ltr"><code>jquery.hoverIntent</code></bdi> module has been removed. This module could be used by gadgets and user scripts, to create an artificial delay in how JavaScript responds to a hover event. Gadgets and user scripts should now use jQuery <bdi lang="zxx" dir="ltr"><code>hover()</code></bdi> or <bdi lang="zxx" dir="ltr"><code>on()</code></bdi> instead. Examples can be found in the [[mw:Special:MyLanguage/ResourceLoader/Migration_guide_(users)#jquery.hoverIntent|migration guide]]. [https://phabricator.wikimedia.org/T311194] * Some of the links in [[{{#special:SpecialPages}}]] will be re-arranged. There will be a clearer separation between links that relate to all users, and links related to your own user account. [https://phabricator.wikimedia.org/T333242] * You will be able to hide the [[mw:Special:MyLanguage/Talk pages project/Replying|Reply button]] in archived discussion pages with a new <bdi lang="zxx" dir="ltr"><code><nowiki>__ARCHIVEDTALK__</nowiki></code></bdi> magic word. There will also be a new <bdi lang="zxx" dir="ltr"><code>.mw-archivedtalk</code></bdi> CSS class for hiding the Reply button in individual sections on a page. [https://phabricator.wikimedia.org/T249293][https://phabricator.wikimedia.org/T295553][https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DiscussionTools/+/738221] '''Future changes''' * The Vega software that creates data visualizations in pages, such as graphs, will be upgraded to the newest version in the future. Graphs that still use the very old version 1.5 syntax may stop working properly. Most existing uses have been found and updated, but you can help to check, and to update any local documentation. [[phab:T260542|Examples of how to find and fix these graphs are available]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:40, 3 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24820268 --> == Tech News: 2023-15 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/15|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] In the visual editor, it is now possible to edit captions of images in galleries without opening the gallery dialog. This feature request was [[:m:Community Wishlist Survey 2023/Editing/Editable gallery captions in Visual Editor|voted #61 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T190224] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] You can now receive notifications when another user edits your user page. See the "{{int:Echo-category-title-edit-user-page}}" option in [[Special:Preferences#mw-prefsection-echo|your Preferences]]. This feature request was [[:m:Community Wishlist Survey 2023/Anti-harassment/Notifications for user page edits|voted #3 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T3876] '''Problems''' * There was a problem with all types of CentralNotice banners still being shown to logged-in users even if they had [[Special:Preferences#mw-prefsection-centralnotice-banners|turned off]] specific banner types. This has now been fixed. [https://phabricator.wikimedia.org/T331671] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-12|en}}. It will be on all wikis from {{#time:j xg|2023-04-13|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-arywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dinwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dsbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-elwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-emlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-etwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-euwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-extwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tumwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ffwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiu_vrowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fjwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frpwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-furwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gcrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-glwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-glkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gomwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gotwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-guwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gvwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T304551][https://phabricator.wikimedia.org/T308133] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:05, 10 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24851886 --> == Wikipedia translation of the week: 2023-16 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Lucy Salani]]'''<br /> <small>''([[:en:Lucy Salani]]) ([[:fr:Lucy Salani]]) ''</small> </div> Please be bold and help translate this article! ---- [[File:Lucy Salani.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lucy Salani''' was an Italian activist and is considered the only Italian transgender person to have survived the Nazi concentration camps. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:06, 17 April 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-16 == <section begin="technews-2023-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/16|Translations]] are available. '''Recent changes''' * You can now see [[mw:Special:MyLanguage/Help:Extension:Kartographer#Show_nearby_articles|nearby articles on a Kartographer map]] with the button for the new feature "{{int:Kartographer-sidebar-nearbybutton}}". Six wikis have been testing this feature since October. [https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Geoinformation/Nearby_articles#Implementation][https://phabricator.wikimedia.org/T334079] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The [[m:Special:GlobalWatchlist|Special:GlobalWatchlist]] page now has links for "{{int:globalwatchlist-markpageseen}}" for each entry. This feature request was [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Button to mark a single change as read in the global watch list|voted #161 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334246] '''Problems''' * At Wikimedia Commons, some thumbnails have not been getting replaced correctly after a new version of the image is uploaded. This should be fixed later this week. [https://phabricator.wikimedia.org/T331138][https://phabricator.wikimedia.org/T333042] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] For the last few weeks, some external tools had inconsistent problems with logging-in with OAuth. This has now been fixed. [https://phabricator.wikimedia.org/T332650] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-19|en}}. It will be on all wikis from {{#time:j xg|2023-04-20|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:55, 18 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24881071 --> == Wikipedia translation of the week: 2023-17 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ca:María Fernanda Castro Maya]]'''<br /> <small>''([[:pt:María Fernanda Castro Maya]]) ([[:eu:María Fernanda Castro Maya]]) ''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''María Fernanda Castro Maya''' is a Mexican self-advocate disability rights activist. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:55, 24 April 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-17 == <section begin="technews-2023-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/17|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The date-selection menu on pages such as [[{{#special:Contributions}}]] will now show year-ranges that are in the current and past decade, instead of the current and future decade. This feature request was [[m:Community Wishlist Survey 2023/Miscellaneous/Change year range shown in date selection popup|voted #145 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334316] '''Problems''' * Due to security issues with the [[mw:Special:MyLanguage/Extension:Graph|Graph extension]], graphs have been disabled in all Wikimedia projects. Wikimedia Foundation teams are working to respond to these vulnerabilities. [https://phabricator.wikimedia.org/T334940] * For a few days, it was not possible to save some kinds of edits on the mobile version of a wiki. This has been fixed. [https://phabricator.wikimedia.org/T334797][https://phabricator.wikimedia.org/T334799][https://phabricator.wikimedia.org/T334794] '''Changes later this week''' * All wikis will be read-only for a few minutes on April 26. This is planned for [https://zonestamp.toolforge.org/1682517653 14:00 UTC]. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.6|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-26|en}}. It will be on all wikis from {{#time:j xg|2023-04-27|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * The Editing team plans an A/B test for [[mw:Special:MyLanguage/Talk pages project/Usability|a usability analysis of the Talk page project]]. The [[mw:Special:MyLanguage/Talk pages project/Usability/Analysis|planned measurements are available]]. Your wiki [[phab:T332946|may be invited to participate]]. Please suggest improvements to the measurement plan at [[mw:Talk:Talk pages project/Usability|the discussion page]]. * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2023-2024|The Wikimedia Foundation annual plan 2023-2024 draft is open for comment and input]] until May 19. The final plan will be published in July 2023 on Meta-wiki. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:04, 24 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24933592 --> == Wikipedia translation of the week: 2023-18 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sonia Orbuch]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Sonia Shainwald Orbuch''' (born Sarah Shainwald, May 24, 1925 – September 30, 2018) was an American Holocaust educator. During the Second World War she was a Jewish resistance fighter in eastern Poland. Orbuch hid in the forests of Poland with her family during the Second World War. She joined a group of Soviet partisans, being renamed Sonia in case she was captured, and helped fight against the Germans. After the war, she returned home, where she met her future husband. After having a daughter in a refugee camp in Germany, the family eventually emigrated to the United States. She spent the rest of life in public engagement, speaking about her experiences and in 2009, published her autobiography, Here, There Are No Sarahs: A Woman's Courageous Fight Against the Nazis and Her Bittersweet Fulfillment of the American Dream. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 06:24, 1 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-18 == <section begin="technews-2023-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/18|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The content attribution tools [[mw:Special:MyLanguage/Who Wrote That?|Who Wrote That?]], [[xtools:authorship|XTools Authorship]], and [[xtools:blame|XTools Blame]] now support the French and Italian Wikipedias. More languages will be added in the near future. This is part of the [[m:Community Wishlist Survey 2023/Reading/Extend "Who Wrote That?" tool to more wikis|#7 wish in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T243711][https://phabricator.wikimedia.org/T270490][https://phabricator.wikimedia.org/T334891] * The [[:commons:Special:MyLanguage/Commons:Video2commons|Video2commons]] tool has been updated. This fixed several bugs related to YouTube uploads. [https://github.com/toolforge/video2commons/pull/162/commits] * The [[{{#special:Preferences}}]] page has been redesigned on mobile web. The new design makes it easier to browse the different categories and settings at low screen widths. You can also now access the page via a link in the Settings menu in the mobile web sidebar. [https://www.mediawiki.org/wiki/Moderator_Tools/Content_moderation_on_mobile_web/Preferences] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-02|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-03|en}}. It will be on all wikis from {{#time:j xg|2023-05-04|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:45, 2 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24966974 --> == Wikipedia translation of the week: 2023-19 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Nadia Ghulam]]'''<br /><small>''([[:fr:Nadia Ghulam]]) ([[:es:Nadia Ghulam]]) ([[:ca:Nadia Ghulam]])''</small> </div> Please be bold and help translate this article! ---- [[File:Nadia Ghulam (cropped).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Nadia Ghulam Dastgir''' is an Afghan woman who spent ten years posing as her dead brother to evade the Taliban's strictures against women. Her book about her experiences, written with Agnès Rotger and published in 2010, El secret del meu turbant (The Secret of My Turban), won the Prudenci Bertrana Prize for fiction. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:37, 8 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24966177 --> == Tech News: 2023-19 == <section begin="technews-2023-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/19|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] Last week, Community Tech released the first update for providing [[m:Special:MyLanguage/Community Wishlist Survey 2022/Better diff handling of paragraph splits|better diffs]], the #1 request in the 2022 Community Wishlist Survey. [[phab:T324759|This update]] adds legends and tooltips to inline diffs so that users unfamiliar with the blue and yellow highlights can better understand the type of edits made. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] When you close an image that is displayed via MediaViewer, it will now return to the wiki page instead of going back in your browser history. This feature request was [[m:Community Wishlist Survey 2023/Reading/Return to the article when closing the MediaViewer|voted #65 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T236591] * The [[mw:Special:MyLanguage/Extension:SyntaxHighlight|SyntaxHighlight]] extension now supports <bdi lang="en" dir="ltr"><code>wikitext</code></bdi> as a selected language. Old alternatives that were used to highlight wikitext, such as <bdi lang="en" dir="ltr"><code>html5</code></bdi>, <bdi lang="en" dir="ltr"><code>moin</code></bdi>, and <bdi lang="en" dir="ltr"><code>html+handlebars</code></bdi>, can now be replaced. [https://phabricator.wikimedia.org/T29828] * [[mw:Special:MyLanguage/Manual:Creating pages with preloaded text|Preloading text to new pages/sections]] now supports preloading from localized MediaWiki interface messages. [https://cs.wikipedia.org/wiki/User_talk:Martin_Urbanec_(WMF)?action=edit&section=new&preload=MediaWiki:July Here is an example] at the {{int:project-localized-name-cswiki/en}} that uses <bdi lang="zxx" dir="ltr"><code><nowiki>preload=MediaWiki:July</nowiki></code></bdi>. [https://phabricator.wikimedia.org/T330337] '''Problems''' * Graph Extension update: Foundation developers have completed upgrading the visualization software to Vega5. Existing community graphs based on Vega2 are no longer compatible. Communities need to update local graphs and templates, and shared lua modules like <bdi lang="de" dir="ltr">[[:de:Modul:Graph]]</bdi>. The [https://vega.github.io/vega/docs/porting-guide/ Vega Porting guide] provides the most comprehensive detail on migration from Vega2 and [https://www.mediawiki.org/w/index.php?title=Template:Graph:PageViews&action=history here is an example migration]. Vega5 has currently just been enabled on mediawiki.org to provide a test environment for communities. [https://phabricator.wikimedia.org/T334940#8813922] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.8|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-10|en}}. It will be on all wikis from {{#time:j xg|2023-05-11|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Until now, all new OAuth apps went through manual review. Starting this week, apps using identification-only or basic authorizations will not require review. [https://phabricator.wikimedia.org/T67750] '''Future changes''' * During the next year, MediaWiki will stop using IP addresses to identify logged-out users, and will start automatically assigning unique temporary usernames. Read more at [[m:Special:MyLanguage/IP Editing: Privacy Enhancement and Abuse Mitigation/Updates|IP Editing: Privacy Enhancement and Abuse Mitigation/Updates]]. You can [[m:Talk:IP Editing: Privacy Enhancement and Abuse Mitigation#What should it look like?|join the discussion]] about the [[m:Special:MyLanguage/IP Editing: Privacy Enhancement and Abuse Mitigation/Updates#What will temporary usernames look like?|format of the temporary usernames]]. [https://phabricator.wikimedia.org/T332805] * There will be an [[:w:en:A/B testing|A/B test]] on 10 Wikipedias where the Vector 2022 skin is the default skin. Half of logged-in desktop users will see an interface where the different parts of the page are more clearly separated. You can [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Updates/2023-05 Zebra9 A/B test|read more]]. [https://phabricator.wikimedia.org/T333180][https://phabricator.wikimedia.org/T335972] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] <code>jquery.tipsy</code> will be removed from the MediaWiki core. This will affect some user scripts. Many lines with <code>.tipsy(</code> can be commented out. <code>OO.ui.PopupWidget</code> can be used to keep things working like they are now. You can [[phab:T336019|read more]] and [[:mw:Help:Locating broken scripts|read about how to find broken scripts]]. [https://phabricator.wikimedia.org/T336019] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:36, 9 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24998636 --> == Wikipedia translation of the week: 2023-20 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Purple Day]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Epilepsy Warrior Brooch May 2018 Purple Day.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Purple Day''' is a global grassroots event that was formed with the intention to increase worldwide awareness of epilepsy, and to dispel common myths and fears of this neurological disorder. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:17, 15 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25000361 --> == Tech News: 2023-20 == <section begin="technews-2023-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/20|Translations]] are available. '''Problems''' * Citations that are automatically generated based on [[d:Q33057|ISBN]] are currently broken. This affects citations made with the [[mw:Special:MyLanguage/Help:VisualEditor/User_guide/Citations-Full#Automatic|VisualEditor Automatic tab]], and the use of the citoid API in gadgets and user scripts. Work is ongoing to restore this feature. [https://phabricator.wikimedia.org/T336298] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-17|en}}. It will be on all wikis from {{#time:j xg|2023-05-18|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-gorwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hakwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hifwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hsbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-htwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-igwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ilowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-inhwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jvwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308134] '''Future changes''' * There is a recently formed team at the Wikimedia Foundation which will be focusing on experimenting with new tools. Currently they are building [[m:Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI|a prototype ChatGPT plugin that allows information generated by ChatGPT to be properly attributed]] to the Wikimedia projects. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadget and userscript developers should replace <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> with <bdi lang="zxx" dir="ltr"><code>mediawiki.cookie</code></bdi>. The <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> library will be removed in ~1 month, and staff developers will run a script to replace any remaining uses at that time. [https://phabricator.wikimedia.org/T336018] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:45, 15 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25011501 --> == Tech News: 2023-21 == <section begin="technews-2023-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/21|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The "recent edits" time period for page watchers is now 30 days. It used to be 180 days. This was a [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Change information about the number of watchers on a page|Community Wishlist Survey proposal]]. [https://phabricator.wikimedia.org/T336250] '''Changes later this week''' * An [[mw:special:MyLanguage/Growth/Positive reinforcement#Impact|improved impact module]] will be available at Wikipedias. The impact module is a feature available to newcomers [[mw:Special:MyLanguage/Growth/Feature summary#Newcomer homepage|at their personal homepage]]. It will show their number of edits, how many readers their edited pages have, how many thanks they have received and similar things. It is also accessible by accessing Special:Impact. [https://phabricator.wikimedia.org/T336203] * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-24|en}}. It will be on all wikis from {{#time:j xg|2023-05-25|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W21"/> 16:55, 22 May 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25028325 --> == Wikipedia translation of the week: 2023-22 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Valencian Art Nouveau]]'''<br /> <small>''([[:es:Modernismo valenciano]])''</small> </div> Please be bold and help translate this article! ---- [[File:Santuario Novelda.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Valencian Art Nouveau''' (Spanish: modernismo valenciano, Valencian: modernisme valencià), is the historiographic denomination given to an art and literature movement associated with the Art Nouveau in the Valencian Community, in Spain. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:46, 29 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25074014 --> == Tech News: 2023-22 == <section begin="technews-2023-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/22|Translations]] are available. '''Recent changes''' * Citations can once again be added automatically from ISBNs, thanks to Zotero's ISBN searches. The current data sources are the Library of Congress (United States), the Bibliothèque nationale de France (French National Library), and K10plus ISBN (German repository). Additional data source searches can be [[mw:Citoid/Creating Zotero translators|proposed to Zotero]]. The ISBN labels in the [[mw:Special:MyLanguage/Help:VisualEditor/User_guide/Citations-Full#Automatic|VisualEditor Automatic tab]] will reappear later this week. [https://phabricator.wikimedia.org/T336298#8859917] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The page [[{{#special:EditWatchlist}}]] now has "{{int:watchlistedit-normal-check-all}}" options to select all the pages within a namespace. This feature request was [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Watchlist edit - "check all" checkbox|voted #161 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334252] '''Problems''' * For a few days earlier this month, the "Add interlanguage link" item in the Tools menu did not work properly. This has now been fixed. [https://phabricator.wikimedia.org/T337081] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.11|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-31|en}}. It will be on all wikis from {{#time:j xg|2023-06-01|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * VisualEditor will be switched to a new backend on [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/small.dblist small] and [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/medium.dblist medium] wikis this week. Large wikis will follow in the coming weeks. This is part of the effort to move Parsoid into MediaWiki core. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [https://phabricator.wikimedia.org/T320529] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:04, 29 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25079963 --> == Wikipedia translation of the week: 2023-23 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:pt:Alessandra Korap]]'''<br /> <small>''([[:en:Alessandra Korap]]) ''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Alessandra Korap''' is an indigenous leader and Brazilian environmental activist from the Munduruku ethnic group. Her main work is defending the demarcation of indigenous territory and denouncing the illegal exploitation and activities of the mining and logging industries. Alessandra is internationally recognized for her work. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:33, 5 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25111481 --> == Tech News: 2023-23 == <section begin="technews-2023-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/23|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Help:Extension:RealMe|RealMe]] extension allows you to mark URLs on your user page as verified for Mastodon and similar software. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] Citation and footnote editing can now be started from the reference list when using the visual editor. This feature request was [[m:Community Wishlist Survey 2023/Citations/Allow citations to be edited in the references section with VisualEditor|voted #2 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T54750] * Previously, clicking on someone else's link to Recent Changes with filters applied within the URL could unintentionally change your preference for "{{int:Rcfilters-group-results-by-page}}". This has now been fixed. [https://phabricator.wikimedia.org/T202916#8874081] '''Problems''' * For a few days last week, some tools and bots returned outdated information due to database replication problems, and may have been down entirely while it was being fixed. These issues have now been fixed. [https://phabricator.wikimedia.org/T337446] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.12|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-06|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-07|en}}. It will be on all wikis from {{#time:j xg|2023-06-08|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Bots will no longer be prevented from making edits because of URLs that match the [[mw:Special:MyLanguage/Extension:SpamBlacklist|spam blacklist]]. [https://phabricator.wikimedia.org/T313107] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:52, 5 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25114640 --> == Wikipedia translation of the week: 2023-24 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cassinga Day]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Cassinga Day''' is a national public holiday in Namibia remembering the Cassinga Massacre. Commemorated annually on 4 May, the date "remembers those (approximately 600) killed in 1978 when the South African Defence Force attacked a SWAPO base at Cassinga in southern Angola". <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:07, 12 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25111481 --> == Tech News: 2023-24 == <section begin="technews-2023-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/24|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The content attribution tools [[mw:Special:MyLanguage/Who Wrote That?|Who Wrote That?]], [[xtools:authorship|XTools Authorship]], and [[xtools:blame|XTools Blame]] now support the Dutch, German, Hungarian, Indonesian, Japanese, Polish and Portuguese Wikipedias. This was the [[m:Community Wishlist Survey 2023/Reading/Extend "Who Wrote That?" tool to more wikis|#7 wish in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334891] * The [[mw:Special:MyLanguage/Structured Data Across Wikimedia/Search Improvements#Search Preview panel|Search Preview panel]] has been deployed on four Wikipedias (Catalan, Dutch, Hungarian and Norwegian). The panel will show an image related to the article (if existing), the top sections of the article, related images (coming from MediaSearch on Commons), and eventually the sister projects associated with the article. [https://phabricator.wikimedia.org/T306341] * The [[:mw:Special:MyLanguage/Help:Extension:RealMe#Verifying_a_link_on_non-user_pages|RealMe]] extension now allows administrators to verify URLs for any page, for Mastodon and similar software. [https://phabricator.wikimedia.org/T324937] * The default project license [https://lists.wikimedia.org/hyperkitty/list/wikimediaannounce-l@lists.wikimedia.org/thread/7G6XPWZPQFLZ2JANN3ZX6RT4DVUI3HZQ/ has been officially upgraded] to CC BY-SA 4.0. The software interface messages have been updated. Communities should feel free to start updating any mentions of the old CC BY-SA 3.0 licensing within policies and related documentation pages. [https://phabricator.wikimedia.org/T319064] '''Problems''' * For three days last month, some Wikipedia pages edited with VisualEditor or DiscussionTools had an unintended <code><nowiki>__TOC__</nowiki></code> (or its localized form) added during an edit. There is [[mw:Parsoid/Deployments/T336101_followup|a listing of affected pages sorted by wiki]], that may still need to be fixed. [https://phabricator.wikimedia.org/T336101] * Currently, the "{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}" feature in VisualEditor is broken. Existing <code><nowiki>{{DEFAULTSORT:...}}</nowiki></code> keywords incorrectly appear as missing templates in VisualEditor. Developers are exploring how to fix this. In the meantime, those wishing to edit the default sortkey of a page are advised to switch to source editing. [https://phabricator.wikimedia.org/T337398] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Last week, an update to the delete form may have broken some gadgets or user scripts. If you need to manipulate (empty) the reason field, replace <bdi lang="zxx" dir="ltr"><code>#wpReason</code></bdi> with <bdi lang="zxx" dir="ltr" style="white-space: nowrap;"><code>#wpReason > input</code></bdi>. See [https://cs.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-CleanDeleteReasons.js&diff=22859956&oldid=12794189 an example fix]. [https://phabricator.wikimedia.org/T337809] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.13|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-13|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-14|en}}. It will be on all wikis from {{#time:j xg|2023-06-15|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * VisualEditor will be switched to a new backend on English Wikipedia on Monday, and all other [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/large.dblist large] wikis on Thursday. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [https://phabricator.wikimedia.org/T320529] '''Future changes''' * From 5 June to 17 July, the Foundation's [[:mw:Wikimedia Security Team|Security team]] is holding a consultation with contributors regarding a draft policy to govern the use of third-party resources in volunteer-developed gadgets and scripts. Feedback and suggestions are warmly welcome at [[m:Special:MyLanguage/Third-party resources policy|Third-party resources policy]] on meta-wiki. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:52, 12 June 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25133779 --> == Tech News: 2023-25 == <section begin="technews-2023-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/25|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Flame graphs are now available in WikimediaDebug. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/JXNQD3EHG5V5QW5UXFDPSHQG4MJ3FWJQ/][https://techblog.wikimedia.org/2023/06/08/flame-graphs-arrive-in-wikimediadebug/] '''Changes later this week''' * There is no new MediaWiki version this week. * There is now a toolbar search popup in the visual editor. You can trigger it by typing <code>\</code> or pressing <code>ctrl + shift + p</code>. It can help you quickly access most tools in the editor. [https://commons.wikimedia.org/wiki/File:Visual_editor_toolbar_search_feature.png][https://phabricator.wikimedia.org/T66905] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:09, 19 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25159510 --> == Wikipedia translation of the week: 2023-26 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Rawon]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Rawon Setan.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Rawon''' (Javanese: ꦫꦮꦺꦴꦤ꧀) is an Indonesian beef soup. Originating from East Java, rawon utilizes the black keluak nut as the main seasoning, which gives a dark color and nutty flavor to the soup. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:18, 26 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25177056 --> == Tech News: 2023-26 == <section begin="technews-2023-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/26|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Action API modules and Special:LinkSearch will now add a trailing <bdi lang="zxx" dir="ltr"><code>/</code></bdi> to all <bdi lang="zxx" dir="ltr"><code>prop=extlinks</code></bdi> responses for bare domains. This is part of the work to remove duplication in the <code>externallinks</code> database table. [https://phabricator.wikimedia.org/T337994] '''Problems''' * Last week, search was broken on Commons and Wikidata for 23 hours. [https://phabricator.wikimedia.org/T339810][https://wikitech.wikimedia.org/wiki/Incidents/2023-06-18_search_broken_on_wikidata_and_commons] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.15|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-27|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-28|en}}. It will be on all wikis from {{#time:j xg|2023-06-29|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Minerva skin now applies more predefined styles to the <bdi lang="zxx" dir="ltr"><code>.mbox-text</code></bdi> CSS class. This enables support for mbox templates that use divs instead of tables. Please make sure that the new styles won't affect other templates in your wiki. [https://gerrit.wikimedia.org/r/c/mediawiki/skins/MinervaNeue/+/930901/][https://phabricator.wikimedia.org/T339040] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadgets will now load on both desktop and mobile by default. Previously, gadgets loaded only on desktop by default. Changing this default using the <bdi lang="zxx" dir="ltr"><code>|targets=</code></bdi> parameter is also deprecated and should not be used. You should make gadgets work on mobile or disable them based on the skin (with the <bdi lang="zxx" dir="ltr"><code>|skins=</code></bdi> parameter in <bdi lang="en" dir="ltr">MediaWiki:Gadgets-definition</bdi>) rather than whether the user uses the mobile or the desktop website. Popular gadgets that create errors on mobile will be disabled by developers on the Minerva skin as a temporary solution. [https://phabricator.wikimedia.org/T127268] * All namespace tabs now have the same browser [[m:Special:MyLanguage/Help:Keyboard_shortcuts|access key]] by default. Previously, custom and extension-defined namespaces would have to have their access keys set manually on-wiki, but that is no longer necessary. [https://phabricator.wikimedia.org/T22126] * The review form of the Flagged Revisions extension now uses the standardized [[mw:Special:MyLanguage/Codex|user interface components]]. [https://phabricator.wikimedia.org/T191156] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] How media is structured in the parser's HTML output will change in the coming weeks at [[:wikitech:Deployments/Train#Thursday|group2 wikis]]. This change improves the accessibility of content. You may need to update your site-CSS, or userscripts and gadgets. There are [[mw:Special:MyLanguage/Parsoid/Parser_Unification/Media_structure/FAQ|details on what code to check, how to update the code, and where to report any related problems]]. [https://phabricator.wikimedia.org/T314318] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:19, 26 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25202311 --> == Wikipedia translation of the week: 2023-27 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hook echo]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Tornadic classic supercell radar.gif|center|300px]] <div style="text-align:left; padding: .4em;"> A '''hook echo''' is a pendant or hook-shaped weather radar signature as part of some supercell thunderstorms. It is found in the lower portions of a storm as air and precipitation flow into a mesocyclone, resulting in a curved feature of reflectivity. The echo is produced by rain, hail, or even debris being wrapped around the supercell <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:18, 3 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25241057 --> == Tech News: 2023-27 == <section begin="technews-2023-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/27|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the rolling out of the [[m:Community Wishlist Survey 2022/Multimedia and Commons/Audio links that play on click|audio links that play on click]] wishlist proposal, [https://noc.wikimedia.org/conf/highlight.php?file=dblists/small.dblist small wikis] will now be able to use the [[mw:Special:MyLanguage/Help:Extension:Phonos#Inline audio player mode|inline audio player]] that is implemented by the [[mw:Extension:Phonos|Phonos]] extension. [https://phabricator.wikimedia.org/T336763] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] From this week all gadgets automatically load on mobile and desktop sites. If you see any problems with gadgets on your wikis, please adjust the [[mw:Special:MyLanguage/Extension:Gadgets#Options|gadget options]] in your gadget definitions file. [https://phabricator.wikimedia.org/T328610] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.16|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-05|en}}. It will be on all wikis from {{#time:j xg|2023-07-06|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:51, 3 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25231546 --> == Tech News: 2023-28 == <section begin="technews-2023-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/28|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Structured Data Across Wikimedia/Section-level Image Suggestions|Section-level Image Suggestions feature]] has been deployed on seven Wikipedias (Portuguese, Russian, Indonesian, Catalan, Hungarian, Finnish and Norwegian Bokmål). The feature recommends images for articles on contributors' watchlists that are a good match for individual sections of those articles. * [[:m:Special:MyLanguage/Global AbuseFilter|Global abuse filters]] have been enabled on all Wikimedia projects, except English and Japanese Wikipedias (who opted out). This change was made following a [[:m:Requests for comment/Make global abuse filters opt-out|global request for comments]]. [https://phabricator.wikimedia.org/T341159] * [[{{#special:BlockedExternalDomains}}]] is a new tool for administrators to help fight spam. It provides a clearer interface for blocking plain domains (and their subdomains), is more easily searchable, and is faster for the software to process for each edit on the wiki. It does not support regex (for complex cases), nor URL path-matching, nor the [[MediaWiki:Spam-whitelist|MediaWiki:Spam-whitelist]], but otherwise it replaces most of the functionalities of the existing [[MediaWiki:Spam-blacklist|MediaWiki:Spam-blacklist]]. There is a Python script to help migrate all simple domains into this tool, and more feature details, within [[mw:Special:MyLanguage/Manual:BlockedExternalDomains|the tool's documentation]]. It is available at all wikis except for Meta-wiki, Commons, and Wikidata. [https://phabricator.wikimedia.org/T337431] * The WikiEditor extension was updated. It includes some of the most frequently used features of wikitext editing. In the past, many of its messages could only be translated by administrators, but now all regular translators on translatewiki can translate them. Please check [https://translatewiki.net/wiki/Special:MessageGroupStats?group=ext-wikieditor&messages=&x=D#sortable:0=asc the state of WikiEditor localization into your language], and if the "Completion" for your language shows anything less than 100%, please complete the translation. See [https://lists.wikimedia.org/hyperkitty/list/wikitech-ambassadors@lists.wikimedia.org/thread/D4YELU2DXMZ75PGELUOKXXMFF3FH45XA/ a more detailed explanation]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.17|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-12|en}}. It will be on all wikis from {{#time:j xg|2023-07-13|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * The default protocol of [[{{#special:LinkSearch}}]] and API counterparts has changed from http to both http and https. [https://phabricator.wikimedia.org/T14810] * [[{{#special:LinkSearch}}]] and its API counterparts will now search for all of the URL provided in the query. It used to be only the first 60 characters. This feature was requested fifteen years ago. [https://phabricator.wikimedia.org/T17218] '''Future changes''' * There is an experiment with a [[:w:en:ChatGPT|ChatGPT]] plugin. This is to show users where the information is coming from when they read information from Wikipedia. It has been tested by Wikimedia Foundation staff and other Wikimedians. Soon all ChatGPT plugin users can use the Wikipedia plugin. This is the same plugin which was mentioned in [[m:Special:MyLanguage/Tech/News/2023/20|Tech News 2023/20]]. [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI] * There is an ongoing discussion on a [[m:Special:MyLanguage/Third-party resources policy|proposed Third-party resources policy]]. The proposal will impact the use of third-party resources in gadgets and userscripts. Based on the ideas received so far, policy includes some of the risks related to user scripts and gadgets loading third-party resources, some best practices and exemption requirements such as code transparency and inspectability. Your feedback and suggestions are warmly welcome until July 17, 2023 on [[m:Talk:Third-party resources policy|on the policy talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:54, 10 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25278797 --> == Wikipedia translation of the week: 2023-29 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Esther Cooper Jackson]]'''<br /> <small>''([[:fr:Esther Cooper Jackson]]) ([[:simple:Esther Cooper Jackson]])''</small> </div> Please be bold and help translate this article! ---- [[File:Esther Cooper Jackson, 1968, Great Barrington.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Esther Victoria Cooper Jackson''' was an American civil rights activist and social worker. She was one of the founding editors of the magazine Freedomways. She also was an organizational and executive secretary at the Southern Negro Youth Congress. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:14, 17 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25266525 --> == Tech News: 2023-29 == <section begin="technews-2023-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/29|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] We are now serving 1% of all global user traffic from [[w:en:Kubernetes|Kubernetes]] (you can [[wikitech:MediaWiki On Kubernetes|read more technical details]]). We are planning to increment this percentage regularly. You can [[phab:T290536|follow the progress of this work]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.18|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-19|en}}. It will be on all wikis from {{#time:j xg|2023-07-20|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki [[mw:Special:MyLanguage/Help:System_message|system messages]] will now look for available local fallbacks, instead of always using the default fallback defined by software. This means wikis no longer need to override each language on the [[mw:Special:MyLanguage/Manual:Language#Fallback_languages|fallback chain]] separately. For example, English Wikipedia doesn't have to create <bdi lang="zxx" dir="ltr"><code>en-ca</code></bdi> and <bdi lang="zxx" dir="ltr"><code>en-gb</code></bdi> subpages with a transclusion of the base pages anymore. This makes it easier to maintain local overrides. [https://phabricator.wikimedia.org/T229992] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The <bdi lang="zxx" dir="ltr"><code>action=growthsetmentorstatus</code></bdi> API will be deprecated with the new MediaWiki version. Bots or scripts calling that API should use the <bdi lang="zxx" dir="ltr"><code>action=growthmanagementorlist</code></bdi> API now. [https://phabricator.wikimedia.org/T321503] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:08, 17 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25289122 --> == Wikipedia translation of the week: 2023-30 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cut of pork]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:American Pork Cuts.svg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''cuts of pork''' are the different parts of the pig which are consumed as food by humans. The terminology and extent of each cut varies from country to country. There are between four and six primal cuts, which are the large parts in which the pig is first cut: the shoulder (blade and picnic), loin, belly (spare ribs and side) and leg <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:21, 24 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25318972 --> == Tech News: 2023-30 == <section begin="technews-2023-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/30|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] On July 18, the Wikimedia Foundation launched a survey about the [[:mw:Technical_decision_making|technical decision making process]] for people who do technical work that relies on software that is maintained by the Foundation or affiliates. If this applies to you, [https://wikimediafoundation.limesurvey.net/885471 please take part in the survey]. The survey will be open for three weeks, until August 7. You can find more information in [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/Q7DUCFA75DXG3G2KHTO7CEWMLCYTSDB2/|the announcement e-mail on wikitech-l]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-26|en}}. It will be on all wikis from {{#time:j xg|2023-07-27|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:20, 25 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25332248 --> == Wikipedia translation of the week: 2023-31 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Gunhild Cross]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Gunhildkorset.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Gunhild Cross''' (Danish: Gunhildkorset), named for its first owner, Gunhild, a daughter of Svend III of Denmark, is a mid-12th-century crucifix carved in walrus tusk and with both Latin and Runic inscriptions. It is now in the collection of the National Museum of Denmark. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:48, 31 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25380210 --> == Tech News: 2023-31 == <section begin="technews-2023-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/31|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Synchronizer|Synchronizer]] tool is now available to keep Lua modules synced across Wikimedia wikis, along with [[mw:Multilingual Templates and Modules|updated documentation]] to develop global Lua modules and templates. * The tag filter on [[{{#special:NewPages}}]] and revision history pages can now be inverted. For example, you can hide edits that were made using an automated tool. [https://phabricator.wikimedia.org/T334337][https://phabricator.wikimedia.org/T334338] * The Wikipedia [[:w:en:ChatGPT|ChatGPT]] plugin experiment can now be used by ChatGPT users who can use plugins. You can participate in a [[:m:Talk:Wikimedia Foundation Annual Plan/2023-2024/Draft/Future Audiences#Announcing monthly Future Audiences open "office hours"|video call]] if you want to talk about this experiment or similar work. [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI] '''Problems''' * It was not possible to generate a PDF for pages with non-Latin characters in the title, for the last two weeks. This has now been fixed. [https://phabricator.wikimedia.org/T342442] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-01|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-02|en}}. It will be on all wikis from {{#time:j xg|2023-08-03|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Tuesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-kawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kaawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kabwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kbdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kbpwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-knwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kshwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kwwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308135] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:54, 31 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25362228 --> == Wikipedia translation of the week: 2023-32 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Polyura athamas]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Close wing mud-puddling position of Charaxes bharata (C.& R. Felder,1867) - Indian Nawab.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''''Polyura athamas''''', the common nawab, is a species of fast-flying canopy butterfly found in tropical Asia. It belongs to the Charaxinae (rajahs and nawabs) in the brush-footed butterfly family (Nymphalidae). <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 03:14, 7 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25410866 --> == Tech News: 2023-32 == <section begin="technews-2023-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/32|Translations]] are available. '''Recent changes''' * Mobile Web editors can now [[mw:Special:MyLanguage/Reading/Web/Advanced_mobile_contributions#August_1,_2023_-_Full-page_editing_added_on_mobile|edit a whole page at once]]. To use this feature, turn on "{{int:Mobile-frontend-mobile-option-amc}}" in your settings and use the "{{int:Minerva-page-actions-editfull}}" button in the "{{int:Minerva-page-actions-overflow}}" menu. [https://phabricator.wikimedia.org/T203151] '''Changes later this week''' * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:21, 7 August 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25420038 --> == Wikipedia translation of the week: 2023-33 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Women's page]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:"Doings in Pittsburg Society" The Pittsburg Press February 1, 1920.png|center|300px]] <div style="text-align:left; padding: .4em;"> The '''women's page''' (sometimes called home page or women's section) of a newspaper was a section devoted to covering news assumed to be of interest to women. Women's pages started out in the 19th century as society pages and eventually morphed into features sections in the 1970s. Although denigrated during much of that period, they had a significant impact on journalism and in their communities. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:51, 14 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-33 == <section begin="technews-2023-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/33|Translations]] are available. '''Recent changes''' * The Content translation system is no longer using Youdao's [[mw:Special:MyLanguage/Help:Content_translation/Translating/Initial_machine_translation|machine translation service]]. The service was in place for several years, but due to no usage, and availability of alternatives, it was deprecated to reduce maintenance overheads. Other services which cover the same languages are still available. [https://phabricator.wikimedia.org/T329137] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-15|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-16|en}}. It will be on all wikis from {{#time:j xg|2023-08-17|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-lawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ladwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lbewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lezwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lfnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-liwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lijwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lmowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ltgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-maiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-map_bmswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mdfwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kywiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308136] <!-- TODO replace wiki codes --> '''Future changes''' * A few gadgets/user scripts which add icons to the Minerva skin need to have their CSS updated. There are more details available including a [[phab:T344067|search for all existing instances and how to update them]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 06:00, 15 August 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25428668 --> == Wikipedia translation of the week: 2023-34 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Insect toxin]]'''<br /> <small>''([[:de:Insektengift]])''</small> </div> Please be bold and help translate this article! ---- [[File:PDB 1lmr EBI.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Insect toxins''' are various protein toxins produced by insect species. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:32, 21 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-34 == <section begin="technews-2023-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/34|Translations]] are available. '''Recent changes''' * The [https://gdrive-to-commons.toolforge.org/ GDrive to Commons Uploader] tool is now available. It enables [[m:Special:MyLanguage/GDrive to Commons Uploader|securely selecting and uploading files]] from your Google Drive directly to Wikimedia Commons. [https://phabricator.wikimedia.org/T267868] * From now on, we will announce new Wikimedia wikis in Tech News, so you can update any tools or pages. ** Since the last edition, two new wikis have been created: *** a Wiktionary in [[d:Q7121294|Pa'O]] ([[wikt:blk:|<code>wikt:blk:</code>]]) [https://phabricator.wikimedia.org/T343540] *** a Wikisource in [[d:Q34002|Sundanese]] ([[s:su:|<code>s:su:</code>]]) [https://phabricator.wikimedia.org/T343539] ** To catch up, the next most recent six wikis are: *** Wikifunctions ([[f:|<code>f:</code>]]) [https://phabricator.wikimedia.org/T275945] *** a Wiktionary in [[d:Q2891049|Mandailing]] ([[wikt:btm:|<code>wikt:btm:</code>]]) [https://phabricator.wikimedia.org/T335216] *** a Wikipedia in [[d:Q5555465|Ghanaian Pidgin]] ([[w:gpe:|<code>w:gpe:</code>]]) [https://phabricator.wikimedia.org/T335969] *** a Wikinews in [[d:Q3111668|Gungbe]] ([[n:guw:|<code>n:guw:</code>]]) [https://phabricator.wikimedia.org/T334394] *** a Wiktionary in [[d:Q33522|Kabardian]] ([[wikt:kbd:|<code>wikt:kbd:</code>]]) [https://phabricator.wikimedia.org/T333266] *** a Wikipedia in [[d:Q35570|Fante]] ([[w:fat:|<code>w:fat:</code>]]) [https://phabricator.wikimedia.org/T335016] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-22|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-23|en}}. It will be on all wikis from {{#time:j xg|2023-08-24|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] There is an existing [[mw:Stable interface policy|stable interface policy]] for MediaWiki backend code. There is a [[mw:User:Jdlrobson/Stable interface policy/frontend|proposed stable interface policy for frontend code]]. This is relevant for anyone who works on gadgets or Wikimedia frontend code. You can read it, discuss it, and let the proposer know if there are any problems. [https://phabricator.wikimedia.org/T344079] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W34"/> 15:25, 21 August 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25497111 --> == Wikipedia translation of the week: 2023-35 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Manchester Blitz]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Air Raid Damage in Britain- Manchester HU49833.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Manchester Blitz''' (also known as the Christmas Blitz) was the heavy bombing of the city of Manchester and its surrounding areas in North West England during the Second World War by the German Luftwaffe. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:16, 28 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-35 == <section begin="technews-2023-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/35|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Community Wishlist Survey 2022/Better diff handling of paragraph splits|better diff handling of paragraph splits]], improved detection of splits is being rolled out. Over the last two weeks, we deployed this support to [[wikitech:Deployments/Train#Groups|group0]] and group1 wikis. This week it will be deployed to group2 wikis. [https://phabricator.wikimedia.org/T341754] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] All [[{{#special:Contributions}}]] pages now show the user's local edit count and the account's creation date. [https://phabricator.wikimedia.org/T324166] * Wikisource users can now use the <bdi lang="zxx" dir="ltr"><code>prpbengalicurrency</code></bdi> label to denote Bengali currency characters as page numbers inside the <bdi lang="zxx" dir="ltr"><code><nowiki><pagelist></nowiki></code></bdi> tag. [https://phabricator.wikimedia.org/T268932] * Two preferences have been relocated. The preference "{{int:visualeditor-preference-visualeditor}}" is now shown on the [[Special:Preferences#mw-prefsection-editing|"{{int:prefs-editing}}" tab]] at all wikis. Previously it was shown on the "{{int:prefs-betafeatures}}" tab at some wikis. The preference "{{int:visualeditor-preference-newwikitexteditor-enable}}" is now also shown on the "{{int:prefs-editing}}" tab at all wikis, instead of the "{{int:prefs-betafeatures}}" tab. [https://phabricator.wikimedia.org/T335056][https://phabricator.wikimedia.org/T344158] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.24|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-29|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-30|en}}. It will be on all wikis from {{#time:j xg|2023-08-31|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] New signups for a Wikimedia developer account will start being pushed towards <bdi lang="en" dir="ltr">[https://idm.wikimedia.org/ idm.wikimedia.org]</bdi>, rather than going via Wikitech. [[wikitech:IDM|Further information about the new system is available]]. * All right-to-left language wikis, plus Korean, Armenian, Ukrainian, Russian, and Bulgarian Wikipedias, will have a link in the sidebar that provides a short URL of that page, using the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]]. This feature will come to more wikis in future weeks. [https://phabricator.wikimedia.org/T267921] '''Future changes''' * The removal of the [[mw:Special:MyLanguage/Extension:DoubleWiki|DoubleWiki extension]] is being discussed. This extension currently allows Wikisource users to view articles from multiple language versions side by side when the <bdi lang="zxx" dir="ltr"><code><=></code></bdi> symbol next to a specific language edition is selected. Comments on this are welcomed at [[phab:T344544|the phabricator task]]. * A proposal has been made to merge the second hidden-categories list (which appears below the wikitext editing form) with the main list of categories (which is further down the page). [[phab:T340606|More information is available on Phabricator]]; feedback is welcome! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:00, 28 August 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25510866 --> == Wikipedia translation of the week: 2023-36 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ghana Independence Act 1957]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> The '''Ghana Independence Act 1957''' is an Act of the Parliament of the United Kingdom that granted the Gold Coast fully responsible government within the British Commonwealth of Nations under the name of Ghana <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:18, 4 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-36 == <section begin="technews-2023-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/36|Translations]] are available. '''Recent changes''' * [[m:Wikisource_EditInSequence|EditInSequence]], a feature that allows users to edit pages faster on Wikisource has been moved to a Beta Feature based on community feedback. To enable it, you can navigate to the [[Special:Preferences#mw-prefsection-betafeatures|beta features tab in Preferences]]. [https://phabricator.wikimedia.org/T308098] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Special:MyLanguage/Community Wishlist Survey 2022/Generate Audio for IPA|Generate Audio for IPA]] and [[m:Community Wishlist Survey 2022/Multimedia and Commons/Audio links that play on click|Audio links that play on click]] wishlist proposals, the [[mw:Special:MyLanguage/Help:Extension:Phonos#Inline_audio_player_mode|inline audio player mode]] of [[mw:Extension:Phonos|Phonos]] has been deployed to all projects. [https://phabricator.wikimedia.org/T336763] * There is a new option for Administrators when they are changing the usergroups for a user, to add the user’s user page to their watchlist. This works both via [[{{#special:UserRights}}]] and via the API. [https://phabricator.wikimedia.org/T272294] * One new wiki has been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q34318|Talysh]] ([[w:tly:|<code>w:tly:</code>]]) [https://phabricator.wikimedia.org/T345166] '''Problems''' * The [[mw:Special:MyLanguage/Extension:LoginNotify|LoginNotify extension]] was not sending notifications since January. It has now been fixed, so going forward, you may see notifications for failed login attempts, and successful login attempts from a new device. [https://phabricator.wikimedia.org/T344785] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-05|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-06|en}}. It will be on all wikis from {{#time:j xg|2023-09-07|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-mhrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-miwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-minwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrjwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mtwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mwlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-myvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mznwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nahwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-napwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ndswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nds_nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-novwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nqowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nrmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nsowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ocwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-olowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-omwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-orwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-oswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pagwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-papwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pcdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pdcwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pflwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pihwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pmswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pnbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pntwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pswiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308137][https://phabricator.wikimedia.org/T308138] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:34, 4 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25566983 --> == Wikipedia translation of the week: 2023-37 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Betrayal trauma]]'''<br /> <small>''([[:sv:Svektrauma]]) ([[:ar:صدمة الخيانة]]) ([[:ko:배신 트라우마]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Betrayal trauma''' is defined as a trauma perpetrated by someone with whom the victim is close to and reliant upon for support and survival. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:49, 11 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-37 == <section begin="technews-2023-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/37|Translations]] are available. '''Recent changes''' * [[mw:Special:MyLanguage/ORES|ORES]], the revision evaluation service, is now using a new open-source infrastructure on all wikis except for English Wikipedia and Wikidata. These two will follow this week. If you notice any unusual results from the Recent Changes filters that are related to ORES (for example, "{{int:ores-rcfilters-damaging-title}}" and "{{int:ores-rcfilters-goodfaith-title}}"), please [[mw:Talk:Machine Learning|report them]]. [https://phabricator.wikimedia.org/T342115] * When you are logged in on one Wikimedia wiki and visit a different Wikimedia wiki, the system tries to log you in there automatically. This has been unreliable for a long time. You can now visit the login page to make the system try extra hard. If you feel that made logging in better or worse than it used to be, your feedback is appreciated. [https://phabricator.wikimedia.org/T326281] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-13|en}}. It will be on all wikis from {{#time:j xg|2023-09-14|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Special:MyLanguage/Technical decision making|Technical Decision-Making Forum Retrospective]] team invites anyone involved in the technical field of Wikimedia projects to signup to and join [[mw:Technical decision making/Listening Sessions|one of their listening sessions]] on 13 September. Another date will be scheduled later. The goal is to improve the technical decision-making processes. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Special:MyLanguage/Community Wishlist Survey 2022/Better diff handling of paragraph splits|Better diff handling of paragraph splits]] wishlist proposal, the inline switch widget in diff pages is being rolled out this week to all wikis. The inline switch will allow viewers to toggle between a unified inline or two-column diff wikitext format. [https://phabricator.wikimedia.org/T336716] '''Future changes''' * All wikis will be read-only for a few minutes on 20 September. [[m:Special:MyLanguage/Tech/Server switch|This is planned at 14:00 UTC.]] More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T345263] * The Enterprise API is launching a new feature called "[http://breakingnews-beta.enterprise.wikimedia.com/ breaking news]". Currently in BETA, this attempts to identify likely "newsworthy" topics as they are currently being written about in any Wikipedia. Your help is requested to improve the accuracy of its detection model, especially on smaller language editions, by recommending templates or identifiable editing patterns. See more information at [[mw:Special:MyLanguage/Wikimedia Enterprise/Breaking news|the documentation page]] on MediaWiki or [[m:Special:MyLanguage/Wikimedia Enterprise/FAQ#What is Breaking News|the FAQ]] on Meta. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:08, 11 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25589064 --> == Wikipedia translation of the week: 2023-38 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:es:Genocidio del Putumayo]]'''<br /> <small>''([[:en:Putumayo genocide]]) ([[:ca:Genocidi del Putumayo]])''</small></div> Please be bold and help translate this article! ---- [[File:The Putumayo - the devil's paradise, travels in the Peruvian Amazon Region and an account of the atrocities committed upon the Indians therein (1913) (14782203995).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Putumayo genocide''' is the term which is used in reference to the enslavement, massacres and ethnocide of the indigenous population of the Amazon at the hands of the Peruvian Amazon Company, specifically in the area between the Putumayo River and the Caquetá River during the Amazon rubber boom period from 1879 to 1912. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 03:38, 18 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25599361 --> == Tech News: 2023-38 == <section begin="technews-2023-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/38|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki now has a [[mw:Stable interface policy/frontend|stable interface policy for frontend code]] that more clearly defines how we deprecate MediaWiki code and wiki-based code (e.g. gadgets and user scripts). Thank you to everyone who contributed to the content and discussions. [https://phabricator.wikimedia.org/T346467][https://phabricator.wikimedia.org/T344079] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.27|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-20|en}}. It will be on all wikis from {{#time:j xg|2023-09-21|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * All wikis will be read-only for a few minutes on September 20. [[m:Special:MyLanguage/Tech/Server switch|This is planned at 14:00 UTC.]] [https://phabricator.wikimedia.org/T345263] * All wikis will have a link in the sidebar that provides a short URL of that page, using the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]]. [https://phabricator.wikimedia.org/T267921] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The team investigating the Graph Extension posted [[mw:Extension:Graph/Plans#Proposal|a proposal for reenabling it]] and they need your input. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:20, 18 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25623533 --> == Tech News: 2023-39 == <section begin="technews-2023-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/39|Translations]] are available. '''Recent changes''' * The Vector 2022 skin will now remember the pinned/unpinned status for the Table of Contents for all logged-out users. [https://phabricator.wikimedia.org/T316060] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.28|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-26|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-27|en}}. It will be on all wikis from {{#time:j xg|2023-09-28|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The ResourceLoader <bdi lang="zxx" dir="ltr"><code><nowiki>mediawiki.ui</nowiki></code></bdi> modules are now deprecated as part of the move to Vue.js and Codex. There is a [[mw:Codex/Migrating_from_MediaWiki_UI|guide for migrating from MediaWiki UI to Codex]] for any tools that use it. More [[phab:T346468|details are available in the task]] and your questions are welcome there. * Gadget definitions will have a [[mw:Special:MyLanguage/Extension:Gadgets#Options|new "namespaces" option]]. The option takes a list of namespace IDs. Gadgets that use this option will only load on pages in the given namespaces. '''Future changes''' * New variables will be added to [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]]: <code><bdi lang="zxx" dir="ltr">global_account_groups</bdi></code> and <code><bdi lang="zxx" dir="ltr">global_account_editcount</bdi></code>. They are available only when an account is being created. You can use them to prevent blocking automatic creation of accounts when users with many edits elsewhere visit your wiki for the first time. [https://phabricator.wikimedia.org/T345632][https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:AbuseFilter/Rules_format] '''Meetings''' * You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on [https://zonestamp.toolforge.org/1698426015 27 October at 17:00 (UTC)]. See [[mw:Special:MyLanguage/Wikimedia_Apps/Office_Hours#October_2023|details and how to join]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:51, 26 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25655264 --> == Tech News: 2023-40 == <section begin="technews-2023-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/40|Translations]] are available. '''Recent changes''' * There is a new [[Special:Preferences#mw-prefsection-rendering-advancedrendering|user preference]] for "{{int:tog-forcesafemode}}". This setting will make pages load without including any on-wiki JavaScript or on-wiki stylesheet pages. It can be useful for debugging broken JavaScript gadgets. [https://phabricator.wikimedia.org/T342347] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadget definitions now have a [[mw:Special:MyLanguage/Extension:Gadgets#Options|new "<var>contentModels</var>" option]]. The option takes a list of page content models, like <code><bdi lang="zxx" dir="ltr">wikitext</bdi></code> or <code><bdi lang="zxx" dir="ltr">css</bdi></code>. Gadgets that use this option will only load on pages with the given content models. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.29|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-03|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-04|en}}. It will be on all wikis from {{#time:j xg|2023-10-05|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Vector 2022 skin will no longer use the custom styles and scripts of Vector legacy (2010). The change will be made later this year or in early 2024. See [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Loading Vector 2010 scripts|how to adjust the CSS and JS pages on your wiki]]. [https://phabricator.wikimedia.org/T331679] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:27, 3 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25686930 --> == Tech News: 2023-41 == <section begin="technews-2023-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/41|Translations]] are available. '''Recent changes''' * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q33291|Fon]] ([[w:fon:|<code>w:fon:</code>]]) [https://phabricator.wikimedia.org/T347935] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.30|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-10|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-11|en}}. It will be on all wikis from {{#time:j xg|2023-10-12|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-swwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-wawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-warwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-wowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xalwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xhwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xmfwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-yiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-yowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zeawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zh_min_nanwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zuwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308139] * At some wikis, newcomers are suggested images from Commons to add to articles without any images. Starting on Tuesday, newcomers at these wikis will be able to add images to unillustrated article sections. The specific wikis are listed under "Images recommendations" [[mw:Special:MyLanguage/Growth/Deployment table|at the Growth team deployment table]]. You can [[mw:Special:MyLanguage/Help:Growth/Tools/Add an image|learn more about this feature.]] [https://phabricator.wikimedia.org/T345940] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] In the mobile web skin (Minerva) the CSS ID <bdi lang="zxx" dir="ltr"><code><nowiki>#page-actions</nowiki></code></bdi> will be replaced with <bdi lang="zxx" dir="ltr"><code><nowiki>#p-views</nowiki></code></bdi>. This change is to make it consistent with other skins and to improve support for gadgets and extensions in the mobile skin. A few gadgets may need to be updated; there are [https://phabricator.wikimedia.org/T348267 details and search-links in the task]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:39, 9 October 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25712895 --> == Wikipedia translation of the week: 2023-42 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Athyma nefte]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:VB 019 Color Sergeant UP.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''''Athyma nefte''''', the colour sergeant, is a species of brush-footed butterfly found in tropical South and Southeast Asia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:58, 16 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25693965 --> == Tech News: 2023-42 == <section begin="technews-2023-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/42|Translations]] are available. '''Recent changes''' * The [[m:Special:MyLanguage/Help:Unified login|Unified login]] system's edge login should now be fixed for some browsers (Chrome, Edge, Opera). This means that if you visit a new sister project wiki, you should be logged in automatically without the need to click "Log in" or reload the page. Feedback on whether it's working for you is welcome. [https://phabricator.wikimedia.org/T347889] * [[mw:Special:MyLanguage/Manual:Interface/Edit_notice|Edit notices]] are now available within the MobileFrontend/Minerva skin. This feature was inspired by [[w:en:Wikipedia:EditNoticesOnMobile|the gadget on English Wikipedia]]. See more details in [[phab:T316178|T316178]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-17|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-18|en}}. It will be on all wikis from {{#time:j xg|2023-10-19|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * In 3 weeks, in the Vector 2022 skin, code related to <bdi lang="zxx" dir="ltr"><code><nowiki>addPortletLink</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>#p-namespaces</nowiki></code></bdi> that was deprecated one year ago will be removed. If you notice tools that should appear next to the "Discussion" tab are then missing, please tell the gadget's maintainers to see [[phab:T347907|instructions in the Phabricator task]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:47, 16 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25745824 --> == Wikipedia translation of the week: 2023-43 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Typhoon Rusa]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Rusa 2002-08-27 0350Z.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Typhoon Rusa''' was the most powerful typhoon to strike South Korea in 43 years. It was the 21st JTWC tropical depression, the 15th named storm, and the 10th typhoon of the 2002 Pacific typhoon season. It developed on August 22 from the monsoon trough in the northwestern Pacific Ocean, well to the southeast of Japan. For several days, Rusa moved to the northwest, eventually intensifying into a powerful typhoon. On August 26, the storm moved across the Amami Islands of Japan, where Rusa left 20,000 people without power and caused two fatalities. Across Japan, the typhoon dropped torrential rainfall peaking at 902 mm (35.5 in) in Tokushima Prefecture. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:50, 23 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25693965 --> == Tech News: 2023-43 == <section begin="technews-2023-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/43|Translations]] are available. '''Recent changes''' * There is a new [[mw:Special:MyLanguage/Wikimedia Language engineering/Newsletter/2023/October|Language and internationalization newsletter]], written quarterly. It contains updates on new feature development, improvements in various language-related technical projects, and related support work. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Source map support has been enabled on all wikis. When you open the debugger in your browser's developer tools, you should be able to see the unminified JavaScript source code. [https://phabricator.wikimedia.org/T47514] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-24|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-25|en}}. It will be on all wikis from {{#time:j xg|2023-10-26|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:17, 23 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25782286 --> == Wikipedia translation of the week: 2023-44 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hein Eersel]]'''<br /> <small>''([[:nl:Hein Eersel]]) ([[:it:Hein Eersel]])''</small> </div> Please be bold and help translate this article! ---- [[File:HeinEersel.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Christiaan Hendrik "Hein" Eersel''' was a Surinamese linguist and cultural researcher. He served as Minister of Education and Population Development in the cabinet of acting Prime Minister Arthur Johan May. He was also the first chancellor of the University of Suriname. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:09, 30 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-44 == <section begin="technews-2023-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/44|Translations]] are available. '''Recent changes''' * The Structured Content team, as part of its project of [[:commons:Commons:WMF support for Commons/Upload Wizard Improvements|improving UploadWizard on Commons]], made some UX improvements to the upload step of choosing own vs not own work ([[phab:T347590|T347590]]), as well as to the licensing step for own work ([[phab:T347756|T347756]]). * The Design Systems team has released version 1.0.0 of [[wmdoc:codex/latest/|Codex]], the new design system for Wikimedia. See the [[mw:Special:MyLanguage/Design_Systems_Team/Announcing_Codex_1.0|full announcement about the release of Codex 1.0.0]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-31|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-01|en}}. It will be on all wikis from {{#time:j xg|2023-11-02|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). * Listings on category pages are sorted on each wiki for that language using a [[:w:en:International Components for Unicode|library]]. For a brief period on 2 November, changes to categories will not be sorted correctly for many languages. This is because the developers are upgrading to a new version of the library. They will then use a script to fix the existing categories. This will take a few hours or a few days depending on how big the wiki is. You can [[mw:Special:MyLanguage/Wikimedia Technical Operations/ICU announcement|read more]]. [https://phabricator.wikimedia.org/T345561][https://phabricator.wikimedia.org/T267145] * Starting November 1, the impact module (Special:Impact) will be upgraded by the Growth team. The new impact module shows newcomers more data regarding their impact on the wiki. It was tested by a few wikis during the last few months. [https://phabricator.wikimedia.org/T336203] '''Future changes''' * There is [[mw:Special:MyLanguage/Extension:Graph/Plans#Roadmap|a proposed plan]] for re-enabling the Graph Extension. You can help by reviewing this proposal and [[mw:Extension_talk:Graph/Plans#c-PPelberg_(WMF)-20231020221600-Update:_20_October|sharing what you think about it]]. * The WMF is working on making it possible for administrators to [[mw:Special:MyLanguage/Community_configuration_2.0|edit MediaWiki configuration directly]]. This is similar to previous work on Special:EditGrowthConfig. [[phab:T349757|A technical RfC is running until November 08, where you can provide feedback.]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:21, 30 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25801989 --> == Tech News: 2023-45 == <section begin="technews-2023-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/45|Translations]] are available. '''Recent changes''' * In the Vector 2022 skin, the default font-size of a number of navigational elements (tagline, tools menu, navigational links, and more) has been increased slightly to match the font size used in page content. [https://phabricator.wikimedia.org/T346062] '''Problems''' * Last week, there was a problem displaying some recent edits on [https://noc.wikimedia.org/conf/highlight.php?file=dblists/s5.dblist a few wikis], for 1-6 hours. The edits were saved but not immediately shown. This was due to a database problem. [https://phabricator.wikimedia.org/T350443] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-08|en}}. It will be on all wikis from {{#time:j xg|2023-11-09|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). * The Growth team will reassign newcomers from former mentors to [[mw:Special:MyLanguage/Growth/Structured mentor list|the currently active mentors]]. They have also changed the notification language to be more user-friendly. [https://phabricator.wikimedia.org/T330071][https://phabricator.wikimedia.org/T327493] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:06, 6 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25838105 --> == Wikipedia translation of the week: 2023-45 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Reclaim the Night]]'''<br /> <small>''([[:de:Reclaim the Night]])''</small> </div> Please be bold and help translate this article! ---- [[File:Reclaim the Night 2014.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Reclaim the Night''' is a movement started in Leeds in 1977 as part of the Women's Liberation Movement. Marches demanding that women be able to move throughout public spaces at night took place across England until the 1990s. Later, the organisation was revived and sponsors annual and national marches against rape and violence against women. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:40, 8 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Wikipedia translation of the week: 2023-46 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ishe Komborera Africa]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Ishe Komborera Africa.mp3|center|300px|]] <div style="text-align:left; padding: .4em;"> "'''Ishe Komborera Africa'''" (Shona for: God Bless Africa), also called "Ishe Komborera Zimbabwe" (Shona for: God Bless Zimbabwe), was the Zimbabwean national anthem from 1980 to 1994. It was the country's first national anthem after gaining independence in 1980. It is a translation of 19th-century South African schoolteacher Enoch Sontonga's popular African hymn "Nkosi Sikelel' iAfrika" into Zimbabwe's native Shona and Ndebele languages. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:38, 13 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-46 == <section begin="technews-2023-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/46|Translations]] are available. '''Recent changes''' * Four new wikis have been created: ** a Wikipedia in [[d:Q7598268|Moroccan Amazigh]] ([[w:zgh:|<code>w:zgh:</code>]]) [https://phabricator.wikimedia.org/T350216] ** a Wikipedia in [[d:Q35159|Dagaare]] ([[w:dga:|<code>w:dga:</code>]]) [https://phabricator.wikimedia.org/T350218] ** a Wikipedia in [[d:Q33017|Toba Batak]] ([[w:bbc:|<code>w:bbc:</code>]]) [https://phabricator.wikimedia.org/T350320] ** a Wikiquote in [[d:Q33151|Banjar]] ([[q:bjn:|<code>q:bjn:</code>]]) [https://phabricator.wikimedia.org/T350217] '''Problems''' * Last week, users who previously visited Meta-Wiki or Wikimedia Commons and then became logged out on those wikis could not log in again. The problem is now resolved. [https://phabricator.wikimedia.org/T350695] * Last week, some pop-up dialogs and menus were shown with the wrong font size. The problem is now resolved. [https://phabricator.wikimedia.org/T350544] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-15|en}}. It will be on all wikis from {{#time:j xg|2023-11-16|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). '''Future changes''' * Reference Previews are coming to many wikis as a default feature. They are popups for references, similar to the [[mw:Special:MyLanguage/Page Previews|PagePreviews feature]]. [[m:WMDE Technical Wishes/ReferencePreviews#Opt-out feature|You can opt out]] of seeing them. If you are [[Special:Preferences#mw-prefsection-gadgets|using the gadgets]] Reference Tooltips or Navigation Popups, you won’t see Reference Previews. [[phab:T282999|Deployment]] is planned for November 22, 2023. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Canary (also known as heartbeat) events will be produced into [https://stream.wikimedia.org/?doc#/streams Wikimedia event streams] from December 11. Streams users are advised to filter out these events, by discarding all events where <bdi lang="zxx" dir="ltr"><code><nowiki>meta.domain == "canary"</nowiki></code></bdi>. Updates to [[mw:Special:MyLanguage/Manual:Pywikibot|Pywikibot]] or [https://github.com/ChlodAlejandro/wikimedia-streams wikimedia-streams] will discard these events by default. [https://phabricator.wikimedia.org/T266798] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:52, 13 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25859263 --> == Wikipedia translation of the week: 2023-47 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Bhagavata Mela]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Bhagavata Mela''' is a classical Indian dance that is performed in Tamil Nadu, particularly the Thanjavur area. It is choreographed as an annual Vaishnavism tradition in Melattur and nearby regions, and celebrated as a dance-drama performance art. The dance art has roots in a historic migration of practitioners of Kuchipudi, another Indian classical dance art, from Andhra Pradesh to the kingdom of Tanjavur. The term Bhagavata, state Brandon and Banham, refers to the Hindu text Bhagavata Purana. Mela is a Sanskrit word that means "gathering, meeting of a group" and connotes a folk festival. The traditional Bhagavata Mela performance acts out the legends of Hinduism, set to the Carnatic style music. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:38, 04:07, 20 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-47 == <section begin="technews-2023-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/47|Translations]] are available. '''Changes later this week''' * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-quwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rmywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-roa_rupwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-roa_tarawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ruewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rwwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sahwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-satwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-shwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-siwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-skwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-slwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-smwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sqwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-srwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-srnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-stwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-stqwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-suwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-szlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tcywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tetwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-thwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-towiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tpiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ttwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-twwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tyvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-udmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ugwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-uzwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vecwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vepwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vlswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vowiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308141][https://phabricator.wikimedia.org/T308142][https://phabricator.wikimedia.org/T308143] * The Vector 2022 skin will have some minor visual changes to drop-down menus, column widths, and more. These changes were added to four Wikipedias last week. If no issues are found, these changes will proceed to all wikis this week. These changes will make it possible to add new menus for readability and dark mode. [[mw:Special:MyLanguage/Reading/Web/Desktop_Improvements/Updates#November_2023:_Visual_changes,_more_deployments,_and_shifting_focus|Learn more]]. [https://phabricator.wikimedia.org/T347711] '''Future changes''' * There is [[mw:Extension talk:Graph/Plans#Update: 15 November|an update on re-enabling the Graph Extension]]. To speed up the process, Vega 2 will not be supported and only [https://phabricator.wikimedia.org/T335325 some protocols] will be available at launch. You can help by sharing what you think about the plan. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:55, 21 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25884616 --> == Wikipedia translation of the week: 2023-48 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fr:Zanskari]]'''<br /> <small>''([[:en:Zaniskari]])''</small> </div> Please be bold and help translate this article! ---- [[File:Zaniskari Horse in Ladakh, India.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Zaniskari''' or '''Zanskari''' is a breed of small mountain horse or pony from Ladakh, in northern India. It is named for the Zanskar valley or region in Kargil district. It is similar to the Spiti breed of Himachal Pradesh, but is better adapted to work at high altitude. Like the Spiti, it shows similarities to the Tibetan breeds of neighbouring Tibet. It is of medium size, and is often grey in colour. The breed is considered endangered, as there are only a few hundred alive today, and a conservation programme has been started at Padum, Zanskar, in the Kargil district of Ladakh. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:44, 27 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-48 == <section begin="technews-2023-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/48|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-29|en}}. It will be on all wikis from {{#time:j xg|2023-11-30|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). There is no new MediaWiki version next week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki's JavaScript system will now allow <bdi lang="zxx" dir="ltr"><code>async</code>/<code>await</code></bdi> syntax in gadgets and user scripts. Gadget authors should remember that users' browsers may not support it, so it should be used appropriately. [https://phabricator.wikimedia.org/T343499] * The deployment of "[[mw:Special:MyLanguage/Help:Growth/Tools/Add_a_link|Add a link]]" announced [[m:Special:MyLanguage/Tech/News/2023/47|last week]] was postponed. It will resume this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:09, 27 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25906379 --> == Wikipedia translation of the week: 2023-49 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sheikh Hussein]]'''<br /> <small>''([[:fr:Sheikh Hussein]]) ([[:it:Scec Hussèn]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sheikh Hussein.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Sheikh Hussein''' is a town in south-eastern Ethiopia. The site has been recorded in the tentative list for UNESCO World Heritage List since 2011 as a religious, cultural and historical site. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:34, 4 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25921616 --> == Tech News: 2023-49 == <section begin="technews-2023-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/49|Translations]] are available. '''Recent changes''' * The spacing between paragraphs on Vector 2022 has been changed from 7px to 14px to match the size of the text. This will make it easier to distinguish paragraphs from sentences. [https://phabricator.wikimedia.org/T351754] * The "{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}" feature in VisualEditor is working again. You no longer need to switch to source editing to edit <bdi lang="zxx" dir="ltr"><code><nowiki>{{DEFAULTSORT:...}}</nowiki></code></bdi> keywords. [https://phabricator.wikimedia.org/T337398] '''Changes later this week''' * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * On 6 December, people who have the enabled the preference for "{{int:Discussiontools-preference-visualenhancements}}" will notice the [[mw:Special:MyLanguage/Talk pages project/Usability|talk page usability improvements]] appear on pages that include the <bdi lang="zxx" dir="ltr"><code><nowiki>__NEWSECTIONLINK__</nowiki></code></bdi> magic word. If you notice any issues, please [[phab:T352232|share them with the team on Phabricator]]. '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Toolforge [[wikitech:News/Toolforge Grid Engine deprecation|Grid Engine shutdown process]] will start on December 14. Maintainers of [[toolforge:grid-deprecation|tools that still use this old system]] should plan to migrate to Kubernetes, or tell the team your plans on Phabricator in the task about your tool, before that date. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/VIWWQKMSQO2ED3TVUR7KPPWRTOBYBVOA/] * Communities using [[mw:Special:MyLanguage/Structured_Discussions|Structured Discussions]] are being contacted regarding [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|the upcoming deprecation of Structured Discussions]]. You can read more about this project, and share your comments, [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|on the project's page]]. '''Events''' * Registration & Scholarship applications are now open for the [[mw:Special:MyLanguage/Wikimedia Hackathon 2024|Wikimedia Hackathon 2024]] that will take place from 3–5 May in Tallinn, Estonia. Scholarship applications are open until 5 January 2024. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:50, 4 December 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25914435 --> == Wikipedia translation of the week: 2023-50 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fr:Applaudissements aux fenêtres pendant la pandémie de Covid-19]]'''<br /> <small>''([[:es:Aplauso por los trabajadores de la salud]]) ([[:gl:Aplauso ao persoal sanitario]])''</small> </div> Please be bold and help translate this article! ---- [[File:Koronabirus konfinamendua Lasarten 2020-03-29.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> During the COVID-19 pandemic, applauding daily at a scheduled hour was a gesture of acclamation, recognition and gratitude towards health professionals in tribute to their work at the time. This habit emerged in January 2020 in Wuhan, where the pandemic originated, and then spread to several cities around the world during the quarantines and sanitary cordons ordered as preventive measures, Italy being the first one. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:26, 11 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25925561 --> == Tech News: 2023-50 == <section begin="technews-2023-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/50|Translations]] are available. '''Recent changes''' * On Wikimedia Commons, there are some minor user-interface improvements for the "choosing own vs not own work" step in the UploadWizard. This is part of the Structured Content team's project of [[:commons:Commons:WMF support for Commons/Upload Wizard Improvements|improving UploadWizard on Commons]]. [https://phabricator.wikimedia.org/T352707][https://phabricator.wikimedia.org/T352709] '''Problems''' * There was a problem showing the [[mw:Special:MyLanguage/Growth/Personalized first day/Newcomer homepage|Newcomer homepage]] feature with the "impact module" and their page-view graphs, for a few days in early December. This has now been fixed. [https://phabricator.wikimedia.org/T352352][https://phabricator.wikimedia.org/T352349] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-12-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-12-13|en}}. It will be on all wikis from {{#time:j xg|2023-12-14|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * [[File:Octicons-tools.svg|15px|link=]] The [https://wikimediafoundation.limesurvey.net/796964 2023 Developer Satisfaction Survey] is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 5 January 2024, and has an associated [[foundation:Legal:December_2023_Developer_Satisfaction_Survey|privacy statement]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:13, 12 December 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25945501 --> == Wikipedia translation of the week: 2023-51 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Jamaica Bay Wildlife Refuge]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Aerial view of Subway Island, July 2019.JPG|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Jamaica Bay Wildlife Refuge''' is a wildlife refuge in New York City managed by the National Park Service as part of Gateway National Recreation Area. It is composed of the open water and intertidal salt marshes of Jamaica Bay. It lies entirely within the boundaries of New York City, divided between the boroughs of Brooklyn to the west and Queens to the east. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:05, 18 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25951007 --> == Tech News: 2023-51 == <section begin="technews-2023-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/51|Translations]] are available. '''Tech News''' * The next issue of Tech News will be sent out on 8 January 2024 because of [[w:en:Christmas and holiday season|the holidays]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-12-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-12-20|en}}. It will be on all wikis from {{#time:j xg|2023-12-21|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). There is no new MediaWiki version next week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting December 18, it won't be possible to activate Structured Discussions on a user's own talk page using the Beta feature. The Beta feature option remains available for users who want to deactivate Structured Discussions. This is part of [[mw:Structured Discussions/Deprecation|Structured Discussions' deprecation work]]. [https://phabricator.wikimedia.org/T248309] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] There will be full support for redirects in the Module namespace. The "Move Page" feature will leave an appropriate redirect behind, and such redirects will be appropriately recognized by the software (e.g. hidden from [[{{#special:UnconnectedPages}}]]). There will also be support for [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#Renaming or moving modules|manual redirects]]. [https://phabricator.wikimedia.org/T120794] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The MediaWiki JavaScript documentation is moving to a new format. During the move, you can read the old docs using [https://doc.wikimedia.org/mediawiki-core/REL1_41/js/ version 1.41]. Feedback about [https://doc.wikimedia.org/mediawiki-core/master/js/ the new site] is welcome on the [[mw:Talk:JSDoc_WMF_theme|project talk page]]. * The Wishathon is a new initiative that encourages collaboration across the Wikimedia community to develop solutions for wishes collected through the [[m:Special:MyLanguage/Community Wishlist Survey|Community Wishlist Survey]]. The first community Wishathon will take place from 15–17 March. If you are interested in a project proposal as a user, developer, designer, or product lead, you can [[m:Special:MyLanguage/Event:WishathonMarch2024|register for the event and read more]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:18, 18 December 2023 (UTC) <!-- Message sent by User:Johan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25959059 --> == Wikipedia translation of the week: 2023-52 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Plant blindness]]'''<br /> <small>''([[:fr:Cécité botanique]]) ([[:de:Pflanzenblindheit]])''</small> </div> Please be bold and help translate this article! ---- [[File:Plant blindness 0323.png|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Plant blindness''' is an informally-proposed form of cognitive bias, which in its broadest meaning, is a human tendency to ignore plant species. This includes such phenomena as not noticing plants in the surrounding environment, not recognizing the importance of plant life to the whole biosphere and to human affairs, a philosophical view of plants as an inferior form of life to animals and/or the inability to appreciate the unique features or aesthetics of plants. Related terms include plant‐neglect, zoo-centrism, and zoo‐chauvinism. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:58, 25 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25971304 --> == Wikipedia translation of the week: 2024-02 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pax airship disaster]]'''<br /> <small>''([[:pt:Catástrofe do dirigível Pax]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sim new-mcclures-magazine 1902-09 19 5 (page 75 crop).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''''Pax''''' '''airship disaster''' was the explosion of the ''Pax'' airship on May 12, 1902, in Paris, which killed the Brazilian inventor Augusto Severo and the French mechanic Georges Saché. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 12:14, 8 January 2024 (UTC)'' </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26033876 --> == Tech News: 2024-02 == <section begin="technews-2024-W02"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/02|Translations]] are available. '''Recent changes''' * [https://mediawiki2latex.wmflabs.org/ mediawiki2latex] is a tool that converts wiki content into the formats of LaTeX, PDF, ODT, and EPUB. The code now runs many times faster due to recent improvements. There is also an optional Docker container you can [[b:de:Benutzer:Dirk_Hünniger/wb2pdf/install#Using_Docker|install]] on your local machine. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The way that Random pages are selected has been updated. This will slowly reduce the problem of some pages having a lower chance of appearing. [https://phabricator.wikimedia.org/T309477] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.13|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-10|en}}. It will be on all wikis from {{#time:j xg|2024-01-11|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/02|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W02"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:20, 9 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26026251 --> == Wikipedia translation of the week: 2024-03 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Conversion to Islam]]'''<br /> <small>''([[:fr:Conversion à l'islam]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sahadah-Topkapi-Palace.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Conversion to Islam''' is accepting Islam as a religion or faith and rejecting any other religion or irreligion. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:11, 15 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26044632 --> == Tech News: 2024-03 == <section begin="technews-2024-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/03|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Pages that use the JSON [[mw:Special:MyLanguage/Manual:ContentHandler|contentmodel]] will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. [https://phabricator.wikimedia.org/T326065] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] and personal user scripts may now use JavaScript syntax introduced in ES6 (also known as "ES2015") and ES7 ("ES2016"). MediaWiki validates the source code to protect other site functionality from syntax errors, and to ensure scripts are valid in all [[mw:Special:MyLanguage/Compatibility#Browsers|supported browsers]]. Previously, Gadgets could use the <bdi lang="zxx" dir="ltr"><code><nowiki>requiresES6</nowiki></code></bdi> option. This option is no longer needed and will be removed in the future. [https://phabricator.wikimedia.org/T75714] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Manual:Bot passwords|Bot passwords]] and [[mw:Special:MyLanguage/OAuth/Owner-only consumers|owner-only OAuth consumers]] can now be restricted to allow editing only specific pages. [https://phabricator.wikimedia.org/T349957] * You can now [[mw:Special:MyLanguage/Extension:Thanks|thank]] edits made by bots. [https://phabricator.wikimedia.org/T341388] * An update on the status of the Community Wishlist Survey for 2024 [[m:Special:MyLanguage/Community Wishlist Survey/Future Of The Wishlist/January 4, 2024 Update|has been published]]. Please read and give your feedback. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.14|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-17|en}}. It will be on all wikis from {{#time:j xg|2024-01-18|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting on January 17, it will not be possible to login to Wikimedia wikis from some specific old versions of the Chrome browser (versions 51–66, released between 2016 and 2018). Additionally, users of iOS 12, or Safari on Mac OS 10.14, may need to login to each wiki separately. [https://phabricator.wikimedia.org/T344791] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> module was deprecated and replaced with the <bdi lang="zxx" dir="ltr"><code>mediawiki.cookie</code></bdi> module last year. A script has now been run to replace any remaining uses, and this week the temporary alias will be removed. [https://phabricator.wikimedia.org/T354966] '''Future changes''' * Wikimedia Deutschland is working to [[m:WMDE Technical Wishes/Reusing references|make reusing references easier]]. They are looking for people who are interested in participating in [https://wikimedia.sslsurvey.de/User-research-into-Reusing-References-Sign-up-Form-2024/en/ individual video calls for user research in January and February]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:13, 16 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26074460 --> == Wikipedia translation of the week: 2024-04 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kinder der Landstrasse]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Kinderdlandstrasse plakat.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Kinder der Landstrasse''' (literally: Children of the Country Road) was a project implemented by the Swiss foundation Pro Juventute from 1926 to 1973. The project aimed to assimilate the itinerant Yenish people in Switzerland by forcibly removing their children from their parents and placing them in orphanages or foster homes. Approximately 590 children were affected by this program. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:02, 22 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26044632 --> == Tech News: 2024-04 == <section begin="technews-2024-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/04|Translations]] are available. '''Problems''' * A bug in UploadWizard prevented linking to the userpage of the uploader when uploading. It has now been fixed. [https://phabricator.wikimedia.org/T354529] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.15|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-24|en}}. It will be on all wikis from {{#time:j xg|2024-01-25|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:04, 23 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26096197 --> == Wikipedia translation of the week: 2024-05 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Qurm Nature Reserve]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Al-Qurm Wetlands.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Qurm Nature Reserve''' is a national nature reserve in Muscat Governorate, Oman. Located on the Gulf of Oman coast, the reserve protects a mangrove forest and the surrounding wetland in a small estuary within the urban area of Qurm. Established in 1975, the reserve has been designated as an Important Bird Area since 1994, and as a protected Ramsar site since 2013. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:03, 29 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26149847 --> == Tech News: 2024-05 == <section begin="technews-2024-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/05|Translations]] are available. '''Recent changes''' * Starting Monday January 29, all talk pages messages' timestamps will become a link. This link is a permanent link to the comment. It allows users to find the comment they are looking for, even if this comment was moved elsewhere. This will affect all wikis except for the English Wikipedia. You can read more about this change [https://diff.wikimedia.org/2024/01/29/talk-page-permalinks-dont-lose-your-threads/ on Diff] or [[mw:Special:MyLanguage/Help:DiscussionTools#Talk_pages_permalinking|on Mediawiki.org]].<!-- The Diff post will be published on Monday morning UTC--> [https://phabricator.wikimedia.org/T302011] * There are some improvements to the CAPTCHA to make it harder for spam bots and scripts to bypass it. If you have feedback on this change, please comment on [[phab:T141490|the task]]. Staff are monitoring metrics related to the CAPTCHA, as well as secondary metrics such as account creations and edit counts. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.16|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-31|en}}. It will be on all wikis from {{#time:j xg|2024-02-01|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] On February 1, a link will be added to the "Tools" menu to download a [[w:en:QR code|QR code]] that links to the page you are viewing. There will also be a new [[{{#special:QrCode}}]] page to create QR codes for any Wikimedia URL. This addresses the [[m:Community Wishlist Survey 2023/Mobile and apps/Add ability to share QR code for a page in any Wikimedia project|#19 most-voted wish]] from the [[m:Community Wishlist Survey 2023/Results|2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T329973] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] which only work in some skins have sometimes used the <bdi lang="zxx" dir="ltr"><code>targets</code></bdi> option to limit where you can use them. This will stop working this week. You should use the <bdi lang="zxx" dir="ltr"><code>skins</code></bdi> option instead. [https://phabricator.wikimedia.org/T328497] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:31, 29 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26137870 --> == Wikipedia translation of the week: 2024-06 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Timurid architecture]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Gur-e-Amir Mausolueum - Samarkand - Uzbekistan (7488414078).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Timurid architecture''' was an important stage in the architectural history of Iran and Central Asia during the late 14th and 15th centuries. The Timurid Empire (1370–1507), founded by Timur (d. 1405) and conquering most of this region, oversaw a cultural renaissance. In architecture, the Timurid dynasty patronized the construction of palaces, mausoleums, and religious monuments across the region. Their architecture is distinguished by its grand scale, luxurious decoration in tilework, and sophisticated geometric vaulting. This architectural style, along with other aspects of Timurid art, spread across the empire and subsequently influenced the architecture of other empires from the Middle East to the Indian subcontinent. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 5 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26169542 --> == Tech News: 2024-06 == <section begin="technews-2024-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/06|Translations]] are available. '''Recent changes''' *The mobile site history pages now use the same HTML as the desktop history pages. If you hear of any problems relating to mobile history usage please point them to [[phab:T353388|the phabricator task]]. *On most wikis, admins can now block users from making specific actions. These actions are: uploading files, creating new pages, moving (renaming) pages, and sending thanks. The goal of this feature is to allow admins to apply blocks that are adequate to the blocked users' activity. [[m:Special:MyLanguage/Community health initiative/Partial blocks#action-blocks|Learn more about "action blocks"]]. [https://phabricator.wikimedia.org/T242541][https://phabricator.wikimedia.org/T280531] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.17|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-06|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-07|en}}. It will be on all wikis from {{#time:j xg|2024-02-08|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Talk pages permalinks that included diacritics and non-Latin script were malfunctioning. This issue is fixed. [https://phabricator.wikimedia.org/T356199] '''Future changes''' * [[m:WMDE Technical Wishes/ReferencePreviews#24WPs|24 Wikipedias]] with [[mw:Special:MyLanguage/Reference_Tooltips|Reference Tooltips]] as a default gadget are encouraged to remove that default flag. This would make [[mw:Special:MyLanguage/Help:Reference_Previews|Reference Previews]] the new default for reference popups, leading to a more consistent experience across wikis. For [[m:WMDE Technical Wishes/ReferencePreviews#46WPs|46 Wikipedias]] with less than 4 interface admins, the change is already scheduled for mid-February, [[m:Talk:WMDE Technical Wishes/ReferencePreviews#Reference Previews to become the default for previewing references on more wikis.|unless there are concerns]]. The older Reference Tooltips gadget will still remain usable and will override this feature, if it is available on your wiki and you have enabled it in your settings. [https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews#Reference_Previews_to_become_the_default_for_previewing_references_on_more_wikis][https://phabricator.wikimedia.org/T355312] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:22, 5 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26180971 --> == Wikipedia translation of the week: 2024-07 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Adoration of the Magi (Fra Angelico and Filippo Lippi)]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Fra Angelico, Fra Filippo Lippi, The Adoration of the Magi.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''''Adoration of the Magi''''' is a tondo, or circular painting, of the Adoration of the Magi assumed to be that recorded in 1492 in the Palazzo Medici Riccardi in Florence as by Fra Angelico. It dates from the mid-15th century and is now in the National Gallery of Art in Washington D.C. Most art historians think that Filippo Lippi painted more of the original work, and that it was added to some years after by other artists, as well as including work by assistants in the workshops of both the original masters. It has been known as the Washington Tondo and Cook Tondo after Herbert Cook, and this latter name in particular continues to be used over 50 years after the painting left the Cook collection. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 07:00, 12 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26187446 --> == Tech News: 2024-07 == <section begin="technews-2024-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/07|Translations]] are available. '''Recent changes''' * The [[d:Wikidata:SPARQL query service/WDQS graph split|WDQS Graph Split experiment]] is working and loaded onto 3 test servers. The team in charge is testing the split's impact and requires feedback from WDQS users through the UI or programmatically in different channels. [https://www.wikidata.org/wiki/Wikidata_talk:SPARQL_query_service/WDQS_graph_split][https://phabricator.wikimedia.org/T356773][https://www.wikidata.org/wiki/User:Sannita_(WMF)] Users' feedback will validate the impact of various use cases and workflows around the Wikidata Query service. [https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/October_2023_scaling_update][https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Federation] '''Problems''' *There was a bug that affected the appearance of visited links when using mobile device to access wiki sites. It made the links appear black; [[phab:T356928|this issue]] is fixed. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.18|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-13|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-14|en}}. It will be on all wikis from {{#time:j xg|2024-02-15|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] As work continues on the grid engine deprecation,[https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation] tools on the grid engine will be stopped starting on February 14th, 2024. If you have tools actively migrating you can ask for an extension so they are not stopped. [https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Communication_and_support] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 05:49, 13 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26223994 --> == Wikipedia translation of the week: 2024-08 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:nl:Graf met de handjes]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Weg langs het kerkhof tegenover 1, Roermond.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The monument '''Van Gorkum-Van Aefferden''', more well known as the "'''grave with the little hands'''" is a monumental Tombstone in the Dutch city of Roermond. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:24, 19 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26260848 --> == Tech News: 2024-08 == <section begin="technews-2024-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/08|Translations]] are available. '''Recent changes''' * If you have the "{{int:Tog-enotifwatchlistpages}}" option enabled, edits by bot accounts no longer trigger notification emails. Previously, only minor edits would not trigger the notification emails. [https://phabricator.wikimedia.org/T356984] * There are changes to how user and site scripts load for [[mw:Special:MyLanguage/Skin:Vector/2022| Vector 2022]] on specific wikis. The changes impacted the following Wikis: all projects with [[mw:Special:MyLanguage/Skin:Vector|Vector legacy]] as the default skin, Wikivoyage, and Wikibooks. Other wikis will be affected over the course of the next three months. Gadgets are not impacted. If you have been affected or want to minimize the impact on your project, see [[Phab:T357580| this ticket]]. Please coordinate and take action proactively. *Newly auto-created accounts (the accounts you get when you visit a new wiki) now have the same local notification preferences as users who freshly register on that wiki. It is effected in four notification types listed in the [[phab:T353225|task's description]]. *The maximum file size when using [[c:Special:MyLanguage/Commons:Upload_Wizard|Upload Wizard]] is now 5 GiB. [https://phabricator.wikimedia.org/T191804] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-20|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-21|en}}. It will be on all wikis from {{#time:j xg|2024-02-22|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Selected tools on the grid engine have been [[wikitech:News/Toolforge_Grid_Engine_deprecation|stopped]] as we prepare to shut down the grid on March 14th, 2024. The tool's code and data have not been deleted. If you are a maintainer and you want your tool re-enabled reach out to the [[wikitech:Portal:Toolforge/About_Toolforge#Communication_and_support|team]]. Only tools that have asked for extension are still running on the grid. * The CSS <bdi lang="zxx" dir="ltr"><code>[https://developer.mozilla.org/en-US/docs/Web/CSS/filter filter]</code></bdi> property can now be used in HTML <bdi lang="zxx" dir="ltr"><code>style</code></bdi> attributes in wikitext. [https://phabricator.wikimedia.org/T308160] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:37, 19 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26254282 --> == Wikipedia translation of the week: 2024-09 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Doorway effect]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> The '''doorway effect''' is a known psychological event where a person's short-term memory declines when passing through a doorway moving from one location to another when it would not if they had remained in the same place. People experience this effect by forgetting what they were going to do, thinking about, or planning upon entering a different room. This is thought to be due to the change in one's physical environment, which is used to distinguish boundaries between remembered events: memories of events encountered in the present environment are more accessible than those beyond it. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:30, 26 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26260848 --> == Tech News: 2024-09 == <section begin="technews-2024-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/09|Translations]] are available. '''Recent changes''' * The [[mw:Special:MyLanguage/VisualEditor_on_mobile|mobile visual editor]] is now the default editor for users who never edited before, at a small group of wikis. [[mw:Special:MyLanguage/VisualEditor_on_mobile/VE_mobile_default#A/B_test_results| Research ]] shows that users using this editor are slightly more successful publishing the edits they started, and slightly less successful publishing non-reverted edits. Users who defined the wikitext editor as their default on desktop will get the wikitext editor on mobile for their first edit on mobile as well. [https://phabricator.wikimedia.org/T352127] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Special:MyLanguage/ResourceLoader/Core modules#mw.config|mw.config]] value <code>wgGlobalGroups</code> now only contains groups that are active in the wiki. Scripts no longer have to check whether the group is active on the wiki via an API request. A code example of the above is: <bdi lang="zxx" dir="ltr"><code>if (/globalgroupname/.test(mw.config.get("wgGlobalGroups")))</code></bdi>. [https://phabricator.wikimedia.org/T356008] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-27|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-28|en}}. It will be on all wikis from {{#time:j xg|2024-02-29|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * The right to change [[mw:Special:MyLanguage/Manual:Tags|edit tags]] (<bdi lang="zxx" dir="ltr"><code>changetags</code></bdi>) will be removed from users in Wikimedia sites, keeping it by default for admins and bots only. Your community can ask to retain the old configuration on your wiki before this change happens. Please indicate in [[phab:T355639|this ticket]] to keep it for your community before the end of March 2024. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:23, 26 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26294125 --> == Wikipedia translation of the week: 2024-10 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sissieretta Jones]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:1899 poster of Mme. M. Sissieretta Jones.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Matilda Sissieretta Joyner Jones''' (January 5, 1868, or 1869 – June 24, 1933) was an American soprano. She sometimes was called "The Black Patti" in reference to Italian opera singer Adelina Patti. Jones' repertoire included grand opera, light opera, and popular music <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 4 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26313143 --> == Tech News: 2024-10 == <section begin="technews-2024-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/10|Translations]] are available. '''Recent changes''' * The <bdi lang="zxx" dir="ltr"><code>Special:Book</code></bdi> page (as well as the associated "Create a book" functionality) provided by the old [[mw:Special:MyLanguage/Extension:Collection|Collection extension]] has been removed from all Wikisource wikis, as it was broken. This does not affect the ability to download normal books, which is provided by the [[mw:Special:MyLanguage/Extension:Wikisource|Wikisource extension]]. [https://phabricator.wikimedia.org/T358437] * [[m:Wikitech|Wikitech]] now uses the next-generation [[mw:Special:MyLanguage/Parsoid|Parsoid]] wikitext parser by default to generate all pages in the Talk namespace. Report any problems on the [[mw:Talk:Parsoid/Parser_Unification/Known_Issues|Known Issues discussion page]]. You can use the [[mw:Special:MyLanguage/Extension:ParserMigration|ParserMigration]] extension to control the use of Parsoid; see the [[mw:Special:MyLanguage/Help:Extension:ParserMigration|ParserMigration help documentation]] for more details. * Maintenance on [https://etherpad.wikimedia.org etherpad] is completed. If you encounter any issues, please indicate in [[phab:T316421|this ticket]]. * [[File:Octicons-tools.svg|12px|link=|alt=| Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] allow interface admins to create custom features with CSS and JavaScript. The <bdi lang="zxx" dir="ltr"><code>Gadget</code></bdi> and <bdi lang="zxx" dir="ltr"><code>Gadget_definition</code></bdi> namespaces and <bdi lang="zxx" dir="ltr"><code>gadgets-definition-edit</code></bdi> user right were reserved for an experiment in 2015, but were never used. These were visible on Special:Search and Special:ListGroupRights. The unused namespaces and user rights are now removed. No pages are moved, and no changes need to be made. [https://phabricator.wikimedia.org/T31272] * A usability improvement to the "Add a citation" in Wikipedia workflow has been made, the insert button was moved to the popup header. [https://phabricator.wikimedia.org/T354847] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.21|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-05|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-06|en}}. It will be on all wikis from {{#time:j xg|2024-03-07|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * All wikis will be read-only for a few minutes on March 20. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T358233] * The HTML markup of headings and section edit links will be changed later this year to improve accessibility. See [[mw:Special:MyLanguage/Heading_HTML_changes|Heading HTML changes]] for details. The new markup will be the same as in the new Parsoid wikitext parser. You can test your gadget or stylesheet with the new markup if you add <bdi lang="zxx" dir="ltr"><code>?useparsoid=1</code></bdi> to your URL ([[mw:Special:MyLanguage/Help:Extension:ParserMigration#Selecting_a_parser_using_a_URL_query_string|more info]]) or turn on Parsoid read views in your user options ([[mw:Special:MyLanguage/Help:Extension:ParserMigration#Enabling_via_user_preference|more info]]). * '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:47, 4 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26329807 --> == Wikipedia translation of the week: 2024-11 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Preventative Coup of November 11]]'''<br /> <small>''([[:es:Golpe de Estado en Brasil de 1955]])''</small> </div> Please be bold and help translate this article! ---- [[File:Exército na casa de Café Filho.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Preventative Coup of November 11''' sometimes called the '''1955 Brazilian coup d'état''' or referred to as an "anti-coup" or a "counter-coup" (Portuguese: ''Novembrada, Movimento de 11 de Novembro, Contragolpe, Golpe Preventivo do Marechal Lott'') was a series of military and political events led by Henrique Teixeira Lott that resulted in Nereu Ramos assuming the presidency of Brazil until being peacefully succeeded by Juscelino Kubitschek a few months later. The bloodless coup removed Carlos Luz from the presidency because he was suspected of plotting to prevent Kubitschek from taking office. As a result of the tensions, Brazil had three presidents in the span of a single week. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 11 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26366849 --> == Tech News: 2024-11 == <section begin="technews-2024-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/11|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-13|en}}. It will be on all wikis from {{#time:j xg|2024-03-14|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * After consulting with various communities, the line height of the text on the [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva skin]] will be increased to its previous value of 1.65. Different options for typography can also be set using the options in the menu, as needed. [https://phabricator.wikimedia.org/T358498] *The active link color in [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva]] will be changed to provide more consistency with our other platforms and best practices. [https://phabricator.wikimedia.org/T358516] * [[c:Special:MyLanguage/Commons:Structured data|Structured data on Commons]] will no longer ask whether you want to leave the page without saving. This will prevent the “information you’ve entered may not be saved” popups from appearing when no information have been entered. It will also make file pages on Commons load faster in certain cases. However, the popups will be hidden even if information has indeed been entered. If you accidentally close the page before saving the structured data you entered, that data will be lost. [https://phabricator.wikimedia.org/T312315] '''Future changes''' * All wikis will be read-only for a few minutes on March 20. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T358233][https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:04, 11 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26374013 --> == Wikipedia translation of the week: 2024-12 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hojang Taret]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Hojang Taret''' is a classical Meitei language play based on Euripides's ancient Greek tragedy The Phoenician Women. It is directed by Oasis Sougaijam and produced by The Umbilical Theatre in Imphal, Kangleipak. It depicts the moral ambiguities of conflict between brothers resulting to the ruination of the ancient city of Thebes. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 18 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26366849 --> == Tech News: 2024-12 == <section begin="technews-2024-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/12|Translations]] are available. '''Recent changes''' * The notice "Language links are at the top of the page" that appears in the [[mw:Special:MyLanguage/Skin:Vector/2022|Vector 2022 skin]] main menu has been removed now that users have learned the new location of the Language switcher. [https://phabricator.wikimedia.org/T353619] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[m:Special:MyLanguage/IP_Editing:_Privacy_Enhancement_and_Abuse_Mitigation/IP_Info_feature|IP info feature]] displays data from Spur, an IP addresses database. Previously, the only data source for this feature was MaxMind. Now, IP info is more useful for patrollers. [https://phabricator.wikimedia.org/T341395] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Toolforge Grid Engine services have been shut down after the final migration process from Grid Engine to Kubernetes. [https://wikitech.wikimedia.org/wiki/Obsolete:Toolforge/Grid][https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation][https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/] * Communities can now customize the default reasons for undeleting a page by creating [[MediaWiki:Undelete-comment-dropdown]]. [https://phabricator.wikimedia.org/T326746] '''Problems''' * [[m:Special:MyLanguage/WMDE_Technical_Wishes/RevisionSlider|RevisionSlider]] is an interface to interactively browse a page's history. Users in [[mw:Special:MyLanguage/Extension:RevisionSlider/Developing_a_RTL-accessible_feature_in_MediaWiki_-_what_we%27ve_learned_while_creating_the_RevisionSlider|right-to-left]] languages reported RevisionSlider reacting wrong to mouse clicks. This should be fixed now. [https://phabricator.wikimedia.org/T352169] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-20|en}}. It will be on all wikis from {{#time:j xg|2024-03-21|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * All wikis will be read-only for a few minutes on March 20. This is planned at [https://zonestamp.toolforge.org/1710943200 14:00 UTC]. [https://phabricator.wikimedia.org/T358233][https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:40, 18 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26410165 --> == Wikipedia translation of the week: 2024-13 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Magna Lykseth-Skogman]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Magna Lykseth in Tristan och Isolde at Kungliga Operan 1909 - SMV - GL164.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Magna Elvine Lykseth-Skogman''' (6 February 1874 – 13 November 1949), also known as Magna Lykseth-Schjerven, was a Norwegian-born Swedish operatic soprano. After making her début at the Royal Swedish Opera in 1901 as Santuzza in Cavalleria rusticana, she was engaged there until 1918 becoming the company's prima donna. She performed leading roles in a wide range of operas but is remembered in particular for her Wagnerian interpretations, creating Brünnhilde in the Swedish premières of Siegfried and Götterdämmerung, and Isolde in 1909. Considered to be one of the most outstanding Swedish opera singers of her generation, she was awarded the Litteris et Artibus medal in 1907 and became a member of the Royal Swedish Academy of Music in 1912 <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:00, 25 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26447450 --> == Tech News: 2024-13 == <section begin="technews-2024-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/13|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] An update was made on March 18th 2024 to how various projects load site, user JavaScript and CSS in [[mw:Special:MyLanguage/Skin:Vector/2022|Vector 2022 skin]]. A [[phab:T360384|checklist]] is provided for site admins to follow. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.24|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-26|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-27|en}}. It will be on all wikis from {{#time:j xg|2024-03-28|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:57, 25 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26446209 --> == Wikipedia translation of the week: 2024-14 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lidder Valley]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Pahalgam Valley.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Lidder Valley''' or Liddar Valley is a Himalayan sub-valley that forms the southeastern corner of Anantnag district in Indian-administered Kashmir. The Lidder River flows down the valley. The entrance to the valley lies 7 km northeast from Anantnag town and 62 km southeast from Srinagar, the summer capital of Jammu and Kashmir. It is a 40-km-long gorge valley with an average width of 3 km. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:15, 1 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26509189 --> == Tech News: 2024-14 == <section begin="technews-2024-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/14|Translations]] are available. '''Recent changes''' * Users of the [[mw:Special:MyLanguage/Reading/Web/Accessibility_for_reading|reading accessibility]] beta feature will notice that the default line height for the standard and large text options has changed. [https://phabricator.wikimedia.org/T359030] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-02|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-03|en}}. It will be on all wikis from {{#time:j xg|2024-04-04|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * The Wikimedia Foundation has an annual plan. The annual plan decides what the Wikimedia Foundation will work on. You can now read [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2024-2025/Product & Technology OKRs#Draft Key Results|the draft key results]] for the Product and Technology department. They are suggestions for what results the Foundation wants from big technical changes from July 2024 to June 2025. You can [[m:Talk:Wikimedia Foundation Annual Plan/2024-2025/Product & Technology OKRs|comment on the talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:36, 2 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26462933 --> == Wikipedia translation of the week: 2024-15 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Operation Kraai]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Overzicht van het vliegveld te Djokja vanuit de 'Control Tower', Bestanddeelnr 5128.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Operation Kraai''' (Operation Crow) was a Dutch military offensive against the de facto Republic of Indonesia in December 1948 after negotiations failed. With the advantage of surprise the Dutch managed to capture the Indonesian Republic's temporary capital, Yogyakarta, and seized Indonesian leaders such as de facto Republican President Sukarno. This apparent military success was however followed by guerrilla warfare, while the violation of the Renville Agreement ceasefire diplomatically isolated the Dutch, leading to the Dutch–Indonesian Round Table Conference and recognition of the United States of Indonesia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:47, 8 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26550154 --> == Tech News: 2024-15 == <section begin="technews-2024-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/15|Translations]] are available. '''Recent changes''' * Web browsers can use tools called [[:w:en:Browser extension|extensions]]. There is now a Chrome extension called [[m:Future Audiences/Experiment:Citation Needed|Citation Needed]] which you can use to see if an online statement is supported by a Wikipedia article. This is a small experiment to see if Wikipedia can be used this way. Because it is a small experiment, it can only be used in Chrome in English. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] A new [[mw:Special:MyLanguage/Help:Edit Recovery|Edit Recovery]] feature has been added to all wikis, available as a [[Special:Preferences#mw-prefsection-editing|user preference]]. Once you enable it, your in-progress edits will be stored in your web browser, and if you accidentally close an editing window or your browser or computer crashes, you will be prompted to recover the unpublished text. Please leave any feedback on the [[m:Special:MyLanguage/Talk:Community Wishlist Survey 2023/Edit-recovery feature|project talk page]]. This was the #8 wish in the 2023 Community Wishlist Survey. * Initial results of [[mw:Special:MyLanguage/Edit check|Edit check]] experiments [[mw:Special:MyLanguage/Edit_check#4_April_2024|have been published]]. Edit Check is now deployed as a default feature at [[phab:T342930#9538364|the wikis that tested it]]. [[mw:Talk:Edit check|Let us know]] if you want your wiki to be part of the next deployment of Edit check. [https://phabricator.wikimedia.org/T342930][https://phabricator.wikimedia.org/T361727] * Readers using the [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva skin]] on mobile will notice there has been an improvement in the line height across all typography settings. [https://phabricator.wikimedia.org/T359029] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-10|en}}. It will be on all wikis from {{#time:j xg|2024-04-11|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * New accounts and logged-out users will get the [[mw:Special:MyLanguage/VisualEditor|visual editor]] as their default editor on mobile. This deployment is made at all wikis except for the English Wikipedia. [https://phabricator.wikimedia.org/T361134] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:38, 8 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26564838 --> == Wikipedia translation of the week: 2024-16 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ru:Павильон Росси]]'''<br /> <small>''([[:en:Rossi Pavilion]])&#32;([[:fr:Pavillon Rossi]])''</small> </div> Please be bold and help translate this article! ---- [[File:Rossi's Pavilion in Mikhailovsky Garden. Saint-Petersburg. 1825..jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Rossi Pavilion''' (Russian: Павильон Росси) is a pavilion on the bank of the Moyka River in the Mikhailovsky Garden in Saint Petersburg. It was designed by architect Carlo Rossi in the early 1820s and built in 1825 during his redevelopment of the garden. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:53, 15 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26565118 --> == Tech News: 2024-16 == <section begin="technews-2024-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/16|Translations]] are available. '''Problems''' * Between 2 April and 8 April, on wikis using [[mw:Special:MyLanguage/Extension:FlaggedRevs|Flagged Revisions]], the "{{Int:tag-mw-reverted}}" tag was not applied to undone edits. In addition, page moves, protections and imports were not autoreviewed. This problem is now fixed. [https://phabricator.wikimedia.org/T361918][https://phabricator.wikimedia.org/T361940] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-17|en}}. It will be on all wikis from {{#time:j xg|2024-04-18|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[mw:Special:MyLanguage/Help:Magic words#DEFAULTSORT|Default category sort keys]] will now affect categories added by templates placed in [[mw:Special:MyLanguage/Help:Cite|footnotes]]. Previously footnotes used the page title as the default sort key even if a different default sort key was specified (category-specific sort keys already worked). [https://phabricator.wikimedia.org/T40435] * A new variable <bdi lang="zxx" dir="ltr"><code>page_last_edit_age</code></bdi> will be added to [[Special:AbuseFilter|abuse filters]]. It tells how many seconds ago the last edit to a page was made. [https://phabricator.wikimedia.org/T269769] '''Future changes''' * Volunteer developers are kindly asked to update the code of their tools and features to handle [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]]. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers/2024-04 CTA|Learn more]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Four database fields will be removed from database replicas (including [[quarry:|Quarry]]). This affects only the <bdi lang="zxx" dir="ltr"><code>abuse_filter</code></bdi> and <bdi lang="zxx" dir="ltr"><code>abuse_filter_history</code></bdi> tables. Some queries might need to be updated. [https://phabricator.wikimedia.org/T361996] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:29, 15 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26564838 --> == Wikipedia translation of the week: 2024-17 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Devorà Ascarelli]]'''<br /> <small>''([[:it:Debora Ascarelli]])&#32;([[:es:Devorà Ascarelli]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Devorà Ascarelli''' was a 16th-century Italian poet living in Rome, Italy. Ascarelli may have been the first Jewish woman to have a book of her own work published. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:35, 22 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-17 == <section begin="technews-2024-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/17|Translations]] are available. '''Recent changes''' * Starting this week, newcomers editing Wikipedia [[mw:Special:MyLanguage/Growth/Positive reinforcement#Leveling up 3|will be encouraged]] to try structured tasks. [[mw:Special:MyLanguage/Growth/Feature summary#Newcomer tasks|Structured tasks]] have been shown to [[mw:Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add a link/Experiment analysis, December 2021|improve newcomer activation and retention]]. [https://phabricator.wikimedia.org/T348086] * You can [[m:Special:MyLanguage/Coolest Tool Award|nominate your favorite tools]] for the fifth edition of the Coolest Tool Award. Nominations will be open until May 10. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-24|en}}. It will be on all wikis from {{#time:j xg|2024-04-25|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * This is the last warning that by the end of May 2024 the Vector 2022 skin will no longer share site and user scripts/styles with old Vector. For user-scripts that you want to keep using on Vector 2022, copy the contents of [[{{#special:MyPage}}/vector.js]] to [[{{#special:MyPage}}/vector-2022.js]]. There are [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Loading Vector 2010 scripts|more technical details]] available. Interface administrators who foresee this leading to lots of technical support questions may wish to send a mass message to your community, as was done on French Wikipedia. [https://phabricator.wikimedia.org/T362701] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:28, 22 April 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26647188 --> == Wikipedia translation of the week: 2024-18 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:1989 Serbian general election]]'''<br /> <small>''([[:sr:Председнички избори у Србији 1989.]])&#32;([[:vi:Tổng tuyển cử Serbia 1989]])''</small></div> Please be bold and help translate this article! ---- [[File:Parliament of SR Serbia (1989–1991).svg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''General elections were held in Serbia''', a constituent federal unit of SFR Yugoslavia, on 12 November 1989 to elect the president of the presidency of the Socialist Republic of Serbia and delegates of the Assembly of SR Serbia. Voting for delegates also took place on 10 and 30 November 1989. In addition to the general elections, local elections were held simultaneously. These were the first direct elections conducted after the adoption of the 1974 Yugoslav Constitution and the delegate electoral system, and the last elections conducted under a one-party system. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:32, 29 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-18 == <section begin="technews-2024-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/18|Translations]] are available. '''Recent changes''' [[File:Talk_pages_default_look_(April_2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages changed for the following wikis: {{int:project-localized-name-azwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-idwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-thwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ukwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-viwiki/en}}. These wikis participated to a test, where 50% of users got the new design, for one year. As this test [[Mw:Special:MyLanguage/Talk pages project/Usability/Analysis|gave positive results]], the new design is deployed on these wikis as the default design. It is possible to opt-out these changes [[Special:Preferences#mw-prefsection-editing|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). The deployment will happen at all wikis in the coming weeks. [https://phabricator.wikimedia.org/T341491] * Seven new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q33014|Betawi]] ([[w:bew:|<code>w:bew:</code>]]) [https://phabricator.wikimedia.org/T357866] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35708|Kusaal]] ([[w:kus:|<code>w:kus:</code>]]) [https://phabricator.wikimedia.org/T359757] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35513|Igala]] ([[w:igl:|<code>w:igl:</code>]]) [https://phabricator.wikimedia.org/T361644] ** a {{int:project-localized-name-group-wiktionary}} in [[d:Q33541|Karakalpak]] ([[wikt:kaa:|<code>wikt:kaa:</code>]]) [https://phabricator.wikimedia.org/T362135] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q9228|Burmese]] ([[s:my:|<code>s:my:</code>]]) [https://phabricator.wikimedia.org/T361085] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q9237|Malay]] ([[s:ms:|<code>s:ms:</code>]]) [https://phabricator.wikimedia.org/T363039] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q8108|Georgian]] ([[s:ka:|<code>s:ka:</code>]]) [https://phabricator.wikimedia.org/T363085] * You can now [https://translatewiki.net/wiki/Support#Early_access:_Watch_Message_Groups_on_Translatewiki.net watch message groups/projects] on [[m:Special:MyLanguage/translatewiki.net|Translatewiki.net]]. Initially, this feature will notify you of added or deleted messages in these groups. [https://phabricator.wikimedia.org/T348501] * Dark mode is now available on all wikis, on mobile web for logged-in users who opt into the [[Special:MobileOptions|advanced mode]]. This is the early release of the feature. Technical editors are invited to [https://night-mode-checker.wmcloud.org/ check for accessibility issues on wikis]. See [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-04|more detailed guidelines]]. '''Problems''' * [[mw:Special:MyLanguage/Help:Extension:Kartographer|Kartographer]] maps can use an alternative visual style without labels, by using <bdi lang="zxx" dir="ltr"><code><nowiki>mapstyle="osm"</nowiki></code></bdi>. This wasn't working in previews, creating the wrong impression that it wasn't supported. This has now been fixed. [https://phabricator.wikimedia.org/T362531] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-01|en}}. It will be on all wikis from {{#time:j xg|2024-05-02|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:34, 30 April 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26689057 --> == Wikipedia translation of the week: 2024-19 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Heinrich Bünting]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Heinrich Bünting''' (1545 – 1606) was a Protestant pastor and theologian. He is best known for his book of woodcut maps titled Itinerarium Sacrae Scripturae (Travel book through Holy Scripture) first published in 1581. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 6 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-19 == <section begin="technews-2024-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/19|Translations]] are available. '''Recent changes''' [[File:Talk_pages_default_look_(April_2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages changed for all wikis, except for Commons, Wikidata and most Wikipedias ([[m:Special:MyLanguage/Tech/News/2024/18|a few]] have already received this design change). You can read the detail of the changes [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. It is possible to opt-out these changes [[Special:Preferences#mw-prefsection-editing|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). The deployment will happen at remaining wikis in the coming weeks. [https://phabricator.wikimedia.org/T352087][https://phabricator.wikimedia.org/T319146] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Interface admins now have greater control over the styling of article components on mobile with the introduction of the <code>SiteAdminHelper</code>. More information on how styles can be disabled can be found [[mw:Special:MyLanguage/Extension:WikimediaMessages#Site_admin_helper|at the extension's page]]. [https://phabricator.wikimedia.org/T363932] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] has added article body sections in JSON format and a curated short description field to the existing parsed Infobox. This expansion to the API is also available via Wikimedia Cloud Services. [https://enterprise.wikimedia.com/blog/article-sections-and-description/] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-08|en}}. It will be on all wikis from {{#time:j xg|2024-05-09|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * When you look at the Special:Log page, the first view is labelled "All public logs", but it only shows some logs. This label will now say "Main public logs". [https://phabricator.wikimedia.org/T237729] '''Future changes''' * A new service will be built to replace [[mw:Special:MyLanguage/Extension:Graph|Extension:Graph]]. Details can be found in [[mw:Special:MyLanguage/Extension:Graph/Plans|the latest update]] regarding this extension. * Starting May 21, English Wikipedia and German Wikipedia will get the possibility to activate "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]". This is part of the [[phab:T304110|progressive deployment of this tool to all Wikipedias]]. These communities can [[mw:Special:MyLanguage/Growth/Community configuration|activate and configure the feature locally]]. [https://phabricator.wikimedia.org/T308144] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:45, 6 May 2024 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26729363 --> == Wikipedia translation of the week: 2024-20 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:var(--background-color-backdrop-dark, #DDDDDD); border:1px solid #BBBBBB; color:var(--color-inverted, #000000); padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ruyan (district)]]'''<br /> <small>''([[:fa:رویان (طبرستان)]])''</small> </div> Please be bold and help translate this article! ---- [[File:Northern Iran and its surroundings during the Iranian intermezzo.svg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Ruyan''' (Persian: رویان), later known as Rustamdar (رستمدار), was the name of a mountainous district that encompassed the western part of Tabaristan/Mazandaran, a region on the Caspian coast of northern Iran. In Iranian mythology, Ruyan appears as one of the places that the legendary archer Arash shot his arrow from, reaching the edge of Khorasan to mark the border between Iran and Turan. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:39, 13 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26755244 --> == Tech News: 2024-20 == <section begin="technews-2024-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/20|Translations]] are available. '''Recent changes''' * On Wikisource there is a special page listing pages of works without corresponding scan images. Now you can use the new magic word <bdi lang="zxx" dir="ltr"><code>__EXPECTWITHOUTSCANS__</code></bdi> to exclude certain pages (list of editions or translations of works) from that list. [https://phabricator.wikimedia.org/T344214] * If you use the [[Special:Preferences#mw-prefsection-editing|user-preference]] "{{int:tog-uselivepreview}}", then the template-page feature "{{int:Templatesandbox-editform-legend}}" will now also work without reloading the page. [https://phabricator.wikimedia.org/T136907] * [[mw:Special:Mylanguage/Extension:Kartographer|Kartographer]] maps can now specify an alternative text via the <bdi lang="zxx" dir="ltr"><code><nowiki>alt=</nowiki></code></bdi> attribute. This is identical in usage to the <bdi lang="zxx" dir="ltr"><code><nowiki>alt=</nowiki></code></bdi> attribute in the [[mw:Special:MyLanguage/Help:Images#Syntax|image and gallery syntax]]. An exception for this feature is wikis like Wikivoyage where the miniature maps are interactive. [https://phabricator.wikimedia.org/T328137] * The old [[mw:Special:MyLanguage/Extension:GuidedTour|Guided Tour]] for the "[[mw:Special:MyLanguage/Edit Review Improvements/New filters for edit review|New Filters for Edit Review]]" feature has been removed. It was created in 2017 to show people with older accounts how the interface had changed, and has now been seen by most of the intended people. [https://phabricator.wikimedia.org/T217451] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-15|en}}. It will be on all wikis from {{#time:j xg|2024-05-16|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[{{#special:search}}]] results page will now use CSS flex attributes, for better accessibility, instead of a table. If you have a gadget or script that adjusts search results, you should update your script to the new HTML structure. [https://phabricator.wikimedia.org/T320295] '''Future changes''' * In the Vector 2022 skin, main pages will be displayed at full width (like special pages). The goal is to keep the number of characters per line large enough. This is related to the coming changes to typography in Vector 2022. [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates|Learn more]]. [https://phabricator.wikimedia.org/T357706] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Two columns of the <bdi lang="zxx" dir="ltr"><code>[[mw:Special:MyLanguage/Manual:pagelinks table|pagelinks]]</code></bdi> database table (<bdi lang="zxx" dir="ltr"><code>pl_namespace</code></bdi> and <bdi lang="zxx" dir="ltr"><code>pl_title</code></bdi>) are being dropped soon. Users must use two columns of the new <bdi lang="zxx" dir="ltr"><code>[[mw:special:MyLanguage/Manual:linktarget table|linktarget]]</code></bdi> table instead (<bdi lang="zxx" dir="ltr"><code>lt_namespace</code></bdi> and <bdi lang="zxx" dir="ltr"><code>lt_title</code></bdi>). In your existing SQL queries: *# Replace <bdi lang="zxx" dir="ltr"><code>JOIN pagelinks</code></bdi> with <bdi lang="zxx" dir="ltr"><code>JOIN linktarget</code></bdi> and <bdi lang="zxx" dir="ltr"><code>pl_</code></bdi> with <bdi lang="zxx" dir="ltr"><code>lt_</code></bdi> in the <bdi lang="zxx" dir="ltr"><code>ON</code></bdi> statement *# Below that add <bdi lang="zxx" dir="ltr"><code>JOIN pagelinks ON lt_id = pl_target_id</code></bdi> ** See <bdi lang="en" dir="ltr">[[phab:T222224]]</bdi> for technical reasoning. [https://phabricator.wikimedia.org/T222224][https://phabricator.wikimedia.org/T299947] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:59, 13 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26762074 --> == Wikipedia translation of the week: 2024-21 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Turlough (lake)]]'''<br /> <small>''([[:de:Turlough]])&#32;([[:no:Turlough]])''</small> </div> Please be bold and help translate this article! ---- [[File:Carran Turlough.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''turlough''' is a seasonal or periodic water body found mostly in limestone karst areas of Ireland, west of the River Shannon. [...] The water bodies fill and empty with the changes in the level of the water table, usually being very low or empty during summer and autumn and full in the winter. As groundwater levels drop the water drains away underground through cracks in the karstic limestone. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:31, 20 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26789673 --> == Tech News: 2024-21 == <section begin="technews-2024-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/21|Translations]] are available. '''Recent changes''' * The [[mw:Special:MyLanguage/Extension:Nuke|Nuke]] feature, which enables administrators to mass delete pages, will now correctly delete pages which were moved to another title. [https://phabricator.wikimedia.org/T43351] * New changes have been made to the UploadWizard in Wikimedia Commons: the overall layout has been improved, by following new styling and spacing for the form and its fields; the headers and helper text for each of the fields was changed; the Caption field is now a required field, and there is an option for users to copy their caption into the media description. [https://commons.wikimedia.org/wiki/Commons:WMF_support_for_Commons/Upload_Wizard_Improvements#Changes_to_%22Describe%22_workflow][https://phabricator.wikimedia.org/T361049] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.6|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-22|en}}. It will be on all wikis from {{#time:j xg|2024-05-23|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML used to render all headings [[mw:Heading_HTML_changes|is being changed to improve accessibility]]. It will change on 22 May in some skins (Timeless, Modern, CologneBlue, Nostalgia, and Monobook). Please test gadgets on your wiki on these skins and [[phab:T13555|report any related problems]] so that they can be resolved before this change is made in all other skins. The developers are also considering the introduction of a [[phab:T337286|Gadget API for adding buttons to section titles]] if that would be helpful to tool creators, and would appreciate any input you have on that. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W21"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:04, 20 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26786311 --> == Wikipedia translation of the week: 2024-22 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Geiranger Church]]'''<br /> <small>''([[:no:Geiranger kirke]])''</small> </div> Please be bold and help translate this article! ---- [[File:Iglesia parroquial, Geiranger, Noruega, 2019-09-07, DD 84-97 PAN.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Geiranger Church''' (Norwegian: Geiranger kyrkje) is a parish church of the Church of Norway in Stranda Municipality in Møre og Romsdal county, Norway. It is located in the village of Geiranger, and the end of the famous Geirangerfjorden. It is the church for the Geiranger parish which is part of the Nordre Sunnmøre prosti (deanery) in the Diocese of Møre. The white, wooden church was built in an octagonal design in 1842 using plans drawn up by the architect Hans Klipe. The church seats about 165 people. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:48, 27 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26828106 --> == Tech News: 2024-22 == <section begin="technews-2024-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/22|Translations]] are available. '''Recent changes''' * Several bugs related to the latest updates to the UploadWizard on Wikimedia Commons have been fixed. For more information, see [[:phab:T365107|T365107]] and [[:phab:T365119|T365119]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] In March 2024 a new [[mw:ResourceLoader/Core_modules#addPortlet|addPortlet]] API was added to allow gadgets to create new portlets (menus) in the skin. In certain skins this can be used to create dropdowns. Gadget developers are invited to try it and [[phab:T361661|give feedback]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Some CSS in the Minerva skin has been removed to enable easier community configuration. Interface editors should check the rendering on mobile devices for aspects related to the classes: <bdi lang="zxx" dir="ltr"><code>.collapsible</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.multicol</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.reflist</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.coordinates</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.topicon</code></bdi>. [[phab:T361659|Further details are available on replacement CSS]] if it is needed. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-29|en}}. It will be on all wikis from {{#time:j xg|2024-05-30|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * When you visit a wiki where you don't yet have a local account, local rules such as edit filters can sometimes prevent your account from being created. Starting this week, MediaWiki takes your global rights into account when evaluating whether you can override such local rules. [https://phabricator.wikimedia.org/T316303] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:15, 28 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26832205 --> == Wikipedia translation of the week: 2024-23 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Guillermo Larrazábal]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Guillermo Larrazábal Arzubide''' (10 February 1907 – 1983) was a Spanish stained glass artist who was active in Ecuador. He is considered Ecuador's most important stained glass artist. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:14, 3 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26828106 --> == Tech News: 2024-23 == <section begin="technews-2024-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/23|Translations]] are available. '''Recent changes''' * It is now possible for local administrators to add new links to the bottom of the site Tools menu without JavaScript. [[mw:Manual:Interface/Sidebar#Add or remove toolbox sections|Documentation is available]]. [https://phabricator.wikimedia.org/T6086] * The message name for the definition of the tracking category of WikiHiero has changed from "<bdi lang="zxx" dir="ltr"><code>MediaWiki:Wikhiero-usage-tracking-category</code></bdi>" to "<bdi lang="zxx" dir="ltr"><code>MediaWiki:Wikihiero-usage-tracking-category</code></bdi>". [https://gerrit.wikimedia.org/r/c/mediawiki/extensions/wikihiero/+/1035855] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q5317225|Kadazandusun]] ([[w:dtp:|<code>w:dtp:</code>]]) [https://phabricator.wikimedia.org/T365220] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.8|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-05|en}}. It will be on all wikis from {{#time:j xg|2024-06-06|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * Next week, on wikis with the Vector 2022 skin as the default, logged-out desktop users will be able to choose between different font sizes. The default font size will also be increased for them. This is to make Wikimedia projects easier to read. [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-06 deployments|Learn more]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:35, 3 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26844397 --> == Tech News: 2024-24 == <section begin="technews-2024-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/24|Translations]] are available. '''Recent changes''' * The software used to render SVG files has been updated to a new version, fixing many longstanding bugs in SVG rendering. [https://phabricator.wikimedia.org/T265549] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML used to render all headings [[mw:Heading HTML changes|is being changed to improve accessibility]]. It was changed last week in some skins (Vector legacy and Minerva). Please test gadgets on your wiki on these skins and [[phab:T13555|report any related problems]] so that they can be resolved before this change is made in Vector-2022. The developers are still considering the introduction of a [[phab:T337286|Gadget API for adding buttons to section titles]] if that would be helpful to tool creators, and would appreciate any input you have on that. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML markup used for citations by [[mw:Special:MyLanguage/Parsoid|Parsoid]] changed last week. In places where Parsoid previously added the <bdi lang="zxx" dir="ltr"><code>mw-reference-text</code></bdi> class, Parsoid now also adds the <bdi lang="zxx" dir="ltr"><code>reference-text</code></bdi> class for better compatibility with the legacy parser. [[mw:Specs/HTML/2.8.0/Extensions/Cite/Announcement|More details are available]]. [https://gerrit.wikimedia.org/r/1036705] '''Problems''' * There was a bug with the Content Translation interface that caused the tools menus to appear in the wrong location. This has now been fixed. [https://phabricator.wikimedia.org/T366374] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-12|en}}. It will be on all wikis from {{#time:j xg|2024-06-13|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The new version of MediaWiki includes another change to the HTML markup used for citations: [[mw:Special:MyLanguage/Parsoid|Parsoid]] will now generate a <bdi lang="zxx" dir="ltr"><code><nowiki><span class="mw-cite-backlink"></nowiki></code></bdi> wrapper for both named and unnamed references for better compatibility with the legacy parser. Interface administrators should verify that gadgets that interact with citations are compatible with the new markup. [[mw:Specs/HTML/2.8.0/Extensions/Cite/Announcement|More details are available]]. [https://gerrit.wikimedia.org/r/1035809] * On multilingual wikis that use the <bdi lang="zxx" dir="ltr"><code><nowiki><translate></nowiki></code></bdi> system, there is a feature that shows potentially-outdated translations with a pink background until they are updated or confirmed. From this week, confirming translations will be logged, and there is a new user-right that can be required for confirming translations if the community [[m:Special:MyLanguage/Requesting wiki configuration changes|requests it]]. [https://phabricator.wikimedia.org/T49177] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:20, 10 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26893898 --> == Wikipedia translation of the week: 2024-25 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:de:Magdalena Zeger]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Magdalena Zeger''' ([mak.da.ˈleː.na ˈt͡seː.gɐ], * 1491; † 16. January 1568 in Kolding) was a calendar maker, astronomer and astrologist. Her Hamburg almanacs and forecasts from 1561 and 1563 have been preserved. Zeger's calendars are the first independent publications by a woman in the field of astronomy. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:29, 17 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26940351 --> == Tech News: 2024-25 == <section begin="technews-2024-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/25|Translations]] are available. '''Recent changes''' * People who attempt to add an external link in the visual editor will now receive immediate feedback if they attempt to link to a domain that a project has decided to block. Please see [[mw:Special:MyLanguage/Edit_check#11_June_2024|Edit check]] for more details. [https://phabricator.wikimedia.org/T366751] * The new [[mw:Special:MyLanguage/Extension:CommunityConfiguration|Community Configuration extension]] is available [[testwiki:Special:CommunityConfiguration|on Test Wikipedia]]. This extension allows communities to customize specific features to meet their local needs. Currently only Growth features are configurable, but the extension will support other [[mw:Special:MyLanguage/Community_configuration#Use_cases|Community Configuration use cases]] in the future. [https://phabricator.wikimedia.org/T323811][https://phabricator.wikimedia.org/T360954] * The dark mode [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] is now available on category and help pages, as well as more special pages. There may be contrast issues. Please report bugs on the [[mw:Talk:Reading/Web/Accessibility_for_reading|project talk page]]. [https://phabricator.wikimedia.org/T366370] '''Problems''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Cloud Services tools were not available for 25 minutes last week. This was caused by a faulty hardware cable in the data center. [https://wikitech.wikimedia.org/wiki/Incidents/2024-06-11_WMCS_Ceph] * Last week, styling updates were made to the Vector 2022 skin. This caused unforeseen issues with templates, hatnotes, and images. Changes to templates and hatnotes were reverted. Most issues with images were fixed. If you still see any, [[phab:T367463|report them here]]. [https://phabricator.wikimedia.org/T367480] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-19|en}}. It will be on all wikis from {{#time:j xg|2024-06-20|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting June 18, the [[mw:Special:MyLanguage/Help:Edit check#ref|Reference Edit Check]] will be deployed to [[phab:T361843|a new set of Wikipedias]]. This feature is intended to help newcomers and to assist edit-patrollers by inviting people who are adding new content to a Wikipedia article to add a citation when they do not do so themselves. During [[mw:Special:MyLanguage/Edit_check#Reference_Check_A/B_Test|a test at 11 wikis]], the number of citations added [https://diff.wikimedia.org/?p=127553 more than doubled] when Reference Check was shown to people. Reference Check is [[mw:Special:MyLanguage/Edit check/Configuration|community configurable]]. [https://phabricator.wikimedia.org/T361843]<!-- NOTE: THE DIFF BLOG WILL BE PUBLISHED ON MONDAY --> * [[m:Special:MyLanguage/Mailing_lists|Mailing lists]] will be unavailable for roughly two hours on Tuesday 10:00–12:00 UTC. This is to enable migration to a new server and upgrade its software. [https://phabricator.wikimedia.org/T367521] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:49, 17 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26911987 --> == Wikipedia translation of the week: 2024-26 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Koreans in Micronesia]]'''<br /> <small>''([[:zh:朝鮮裔密克羅尼西亞人]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Koreans in Micronesia''' used to form a significant population before World War II, when most of the region was ruled as the South Seas Mandate of the Empire of Japan; for example, they formed 7.3% of the population of Palau in 1943. However, after the area came under the control of the United States as the Trust Territory of the Pacific Islands, most Koreans returned to their homeland. As of 2013, about seven thousand South Korean expatriates & immigrants and Korean Americans reside in the Marianas (Guam and the Commonwealth of the Northern Mariana Islands), which have remained under U.S. control, while only around two hundred South Korean expatriates reside in the independent countries of Micronesia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 04:03, 24 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26940351 --> == Tech News: 2024-26 == <section begin="technews-2024-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/26|Translations]] are available. '''Recent changes''' * Editors will notice that there have been some changes to the background color of text in the diff view, and the color of the byte-change numbers, last week. These changes are intended to make text more readable in both light mode and dark mode, and are part of a larger effort to increase accessibility. You can share your comments or questions [[mw:Talk:Reading/Web/Accessibility for reading|on the project talkpage]]. [https://phabricator.wikimedia.org/T361717] * The text colors that are used for visited-links, hovered-links, and active-links, were also slightly changed last week to improve their accessibility in both light mode and dark mode. [https://phabricator.wikimedia.org/T366515] '''Problems''' * You can [[mw:Special:MyLanguage/Help:DiscussionTools#Talk pages permalinking|copy permanent links to talk page comments]] by clicking on a comment's timestamp. [[mw:Talk pages project/Permalinks|This feature]] did not always work when the topic title was very long and the link was used as a wikitext link. This has been fixed. Thanks to Lofhi for submitting the bug. [https://phabricator.wikimedia.org/T356196] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.11|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-26|en}}. It will be on all wikis from {{#time:j xg|2024-06-27|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting 26 June, all talk pages messages' timestamps will become a link at English Wikipedia, making this feature available for you to use at all wikis. This link is a permanent link to the comment. It allows users to find the comment they were linked to, even if this comment has since been moved elsewhere. You can read more about this feature [[DiffBlog:/2024/01/29/talk-page-permalinks-dont-lose-your-threads/|on Diff]] or [[mw:Special:MyLanguage/Help:DiscussionTools#Talk pages permalinking|on Mediawiki.org]]. [https://phabricator.wikimedia.org/T365974] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:33, 24 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26989424 --> == Wikipedia translation of the week: 2024-27 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Roller printing on textiles]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Silverstudio.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Roller printing''' on fabrics is a textile printing process patented by Thomas Bell of Scotland in 1783 in an attempt to reduce the cost of the earlier copperplate printing. This method was used in Lancashire fabric mills to produce cotton dress fabrics from the 1790s, most often reproducing small monochrome patterns characterized by striped motifs and tiny dotted patterns called "machine grounds". Improvements in the technology resulted in more elaborate roller prints in bright, rich colours from the 1820s; Turkey red and chrome yellow were particularly popular. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:44, 1 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-27 == <section begin="technews-2024-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/27|Translations]] are available. '''Recent changes''' * Over the next three weeks, dark mode will become available for all users, both logged-in and logged-out, starting with the mobile web version. This fulfils one of the [[m:Special:MyLanguage/Community_Wishlist_Survey_2023/Reading/Dark_mode|top-requested community wishes]], and improves low-contrast reading and usage in low-light settings. As part of these changes, dark mode will also work on User-pages and Portals. There is more information in [[mw:Special:MyLanguage/Reading/Web/Accessibility_for_reading/Updates#June_2024:_Typography_and_dark_mode_deployments,_new_global_preferences|the latest Web team update]]. [https://phabricator.wikimedia.org/T366364] * Logged-in users can now set [[m:Special:GlobalPreferences#mw-prefsection-rendering-skin-skin-prefs|global preferences for the text-size and dark-mode]], thanks to a combined effort across Foundation teams. This allows Wikimedians using multiple wikis to set up a consistent reading experience easily, for example by switching between light and dark mode only once for all wikis. [https://phabricator.wikimedia.org/T341278] * If you use a very old web browser some features might not work on the Wikimedia wikis. This affects Internet Explorer 11 and versions of Chrome, Firefox and Safari older than 2016. This change makes it possible to use new [[d:Q46441|CSS]] features and to send less code to all readers. [https://phabricator.wikimedia.org/T288287][https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:How_to_make_a_MediaWiki_skin#Using_CSS_variables_for_supporting_different_themes_e.g._dark_mode] * Wikipedia Admins can customize local wiki configuration options easily using [[mw:Special:MyLanguage/Community Configuration|Community Configuration]]. Community Configuration was created to allow communities to customize how some features work, because each language wiki has unique needs. At the moment, admins can configure [[mw:Special:MyLanguage/Growth/Feature_summary|Growth features]] on their home wikis, in order to better recruit and retain new editors. More options will be provided in the coming months. [https://phabricator.wikimedia.org/T366458] * Editors interested in language issues that are related to [[w:en:Unicode|Unicode standards]], can now discuss those topics at [[mw:Talk:WMF membership with Unicode Consortium|a new conversation space in MediaWiki.org]]. The Wikimedia Foundation is now a [[mw:Special:MyLanguage/WMF membership with Unicode Consortium|member of the Unicode Consortium]], and the coordination group can collaboratively review the issues discussed and, where appropriate, bring them to the attention of the Unicode Consortium. * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q2891049|Mandailing]] ([[w:btm:|<code>w:btm:</code>]]) [https://phabricator.wikimedia.org/T368038] '''Problems''' * Editors can once again click on links within the visual editor's citation-preview, thanks to a bug fix by the Editing Team. [https://phabricator.wikimedia.org/T368119] '''Future changes''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 2 weeks. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:59, 1 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27038456 --> == Wikipedia translation of the week: 2024-28 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:simple:India naming dispute]]'''<br /> <small>''([[:ur:انڈیا نام کا تنازعہ]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''India naming dispute''' in 1947 refers to the argument over the use of the name India during and after the partition of British Raj, between the countries of Pakistan and the Republic of India. This dispute involved key figures such as Lord Mountbatten, the last Viceroy of British Raj, and Muhammad Ali Jinnah, the leader of the Muslim League and a founder of Pakistan. By 1947, the British Raj was going to be divided into two new nation states – Hindustan and Pakistan. Jinnah was initially convinced that Hindustan would not use the term India, since it lacked indigenous pedigree, etymologically and historically India meant the Indus Valley (modern-Pakistan). He also opposed the use of the name India as it would cause confusion regarding history. The disagreement had significant implications for national identity and international recognition. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 8 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-28 == <section begin="technews-2024-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/28|Translations]] are available. '''Recent changes''' * At the Wikimedia Foundation a new task force was formed to replace the disabled Graph with [[mw:Special:MyLanguage/Extension:Chart/Project|more secure, easy to use, and extensible Chart]]. You can [[mw:Special:MyLanguage/Newsletter:Chart Project|subscribe to the newsletter]] to get notified about new project updates and other news about Chart. * The [[m:Special:MyLanguage/CampaignEvents|CampaignEvents]] extension is now available on Meta-wiki, Igbo Wikipedia, and Swahili Wikipedia, and can be requested on your wiki. This extension helps in managing and making events more visible, giving Event organizers the ability to use tools like the Event registration tool. To learn more about the deployment status and how to request this extension for your wiki, visit the [[m:Special:MyLanguage/CampaignEvents/Deployment_status|CampaignEvents page on Meta-wiki]]. * Editors using the iOS Wikipedia app who have more than 50 edits can now use the [[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits#Add an image|Add an Image]] feature. This feature presents opportunities for small but useful contributions to Wikipedia. * Thank you to [[mw:MediaWiki Product Insights/Contributor retention and growth/Celebration|all of the authors]] who have contributed to MediaWiki Core. As a result of these contributions, the [[mw:MediaWiki Product Insights/Contributor retention and growth|percentage of authors contributing more than 5 patches has increased by 25% since last year]], which helps ensure the sustainability of the platform for the Wikimedia projects. '''Problems''' * A problem with the color of the talkpage tabs always showing as blue, even for non-existent pages which should have been red, affecting the Vector 2022 skin, [[phab:T367982|has been fixed]]. '''Future changes''' * The Trust and Safety Product team wants to introduce [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] with as little disruption to tools and workflows as possible. Volunteer developers, including gadget and user-script maintainers, are kindly asked to update the code of their tools and features to handle temporary accounts. The team has [[mw:Trust and Safety Product/Temporary Accounts/For developers|created documentation]] explaining how to do the update. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers/2024-04 CTA|Learn more]]. '''Tech News survey''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 1 more week. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:32, 8 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27080357 --> == Wikipedia translation of the week: 2024-29 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Adumu]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Maasai 2012 05 31 2782 (7522645058).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Adumu''', is a type of dance that the Maasai people of Kenya and Tanzania practice. Young Maasai warriors generally perform the energetic and acrobatic dance at ceremonial occasions including weddings, religious rites, and other significant cultural events. The Adumu dance is characterized by a sequence of jumps performed by the dancers, who stand in a circle and alternately jump while keeping their bodies as straight and upright as possible. In addition to wearing vividly colored shúkàs (clothes) and beaded jewelry, the dancers are typically clad in traditional Maasai costume. Traditional Maasai songs and chants are also performed during the dance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:15, 15 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-29 == <section begin="technews-2024-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/29|Translations]] are available. '''Tech News survey''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 3 more days. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia developers can now officially continue to use both [[mw:Special:MyLanguage/Gerrit|Gerrit]] and [[mw:Special:MyLanguage/GitLab|GitLab]], due to a June 24 decision by the Wikimedia Foundation to support software development on both platforms. Gerrit and GitLab are both code repositories used by developers to write, review, and deploy the software code that supports the MediaWiki software that the wiki projects are built on, as well as the tools used by editors to create and improve content. This decision will safeguard the productivity of our developers and prevent problems in code review from affecting our users. More details are available in the [[mw:GitLab/Migration status|Migration status]] page. * The Wikimedia Foundation seeks applicants for the [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal|Product and Technology Advisory Council]] (PTAC). This group will bring technical contributors and Wikimedia Foundation together to co-define a more resilient, future-proof technological platform. Council members will evaluate and consult on the movement's product and technical activities, so that we develop multi-generational projects. We are looking for a range of technical contributors across the globe, from a variety of Wikimedia projects. [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal#Joining the PTAC as a technical volunteer|Please apply here by August 10]]. * Editors with rollback user-rights who use the Wikipedia App for Android can use the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Anti Vandalism|Edit Patrol]] features. These features include a new feed of Recent Changes, related links such as Undo and Rollback, and the ability to create and save a personal library of user talk messages to use while patrolling. If your wiki wants to make these features available to users who do not have rollback rights but have reached a certain edit threshold, [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android#Contact us|you can contact the team]]. You can [[diffblog:2024/07/10/ِaddressing-vandalism-with-a-tap-the-journey-of-introducing-the-patrolling-feature-in-the-mobile-app/|read more about this project on Diff blog]]. * Editors who have access to [[m:Special:MyLanguage/The_Wikipedia_Library|The Wikipedia Library]] can once again use non-open access content in SpringerLinks, after the Foundation [[phab:T368865|contacted]] them to restore access. You can read more about [[m:Tech/News/Recently_resolved_community_tasks|this and 21 other community-submitted tasks that were completed last week]]. '''Changes later this week''' * This week, [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-07 deployments|dark mode will be available on a number of Wikipedias]], both desktop and mobile, for logged-in and logged-out users. Interface admins and user script maintainers are encouraged to check gadgets and user scripts in the dark mode, to find any hard-coded colors and fix them. There are some [[mw:Special:MyLanguage/Recommendations for night mode compatibility on Wikimedia wikis|recommendations for dark mode compatibility]] to help. '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Next week, functionaries, volunteers maintaining tools, and software development teams are invited to test the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] feature on testwiki. Temporary accounts is a feature that will help improve privacy on the wikis. No further temporary account deployments are scheduled yet. Please [[mw:Talk:Trust and Safety Product/Temporary Accounts|share your opinions and questions on the project talk page]]. [https://phabricator.wikimedia.org/T348895] * Editors who upload files cross-wiki, or teach other people how to do so, may wish to join a Wikimedia Commons discussion. The Commons community is discussing limiting who can upload files through the cross-wiki upload/Upload dialog feature to users auto-confirmed on Wikimedia Commons. This is due to the large amount of copyright violations uploaded this way. There is a short summary at [[c:Special:MyLanguage/Commons:Cross-wiki upload|Commons:Cross-wiki upload]] and [[c:Commons:Village pump/Proposals#Deactivate cross-wiki uploads for new users|discussion at Commons:Village Pump]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' You can also get other news from the [[m:Special:MyLanguage/Wikimedia Foundation Bulletin|Wikimedia Foundation Bulletin]]. </div><section end="technews-2024-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:31, 16 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27124561 --> == Wikipedia translation of the week: 2024-30 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Rathaus-Glockenspiel]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:2019-11-16, Glockenspiel, Neues Münchner Rathaus, IMG 7463 edit Christoph Braun.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Rathaus-Glockenspiel''' is a large mechanical clock located in Marienplatz Square, in the heart of Munich, Germany. Famous for its life-size characters, the clock twice daily re-enacts scenes from Munich's history. First is the story of the marriage of Duke Wilhelm V to Renata of Lorraine in 1568, followed by the story of the Schäfflerstanz, also known as the coopers' dance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 22 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-30 == <section begin="technews-2024-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/30|Translations]] are available. '''Feature News''' * Stewards can now [[:m:Special:MyLanguage/Global_blocks|globally block]] accounts. Before [[phab:T17294|the change]] only IP addresses and IP ranges could be blocked globally. Global account blocks are useful when the blocked user should not be logged out. [[:m:Special:MyLanguage/Global_locks|Global locks]] (a similar tool logging the user out of their account) are unaffected by this change. The new global account block feature is related to the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] project, which is a new type of user account that replaces IP addresses of unregistered editors that are no longer made public. * Later this week, Wikimedia site users will notice that the Interface of [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs]] (also known as "Pending Changes") is improved and consistent with the rest of the MediaWiki interface and [[mw:Special:MyLanguage/Codex|Wikimedia's design system]]. The FlaggedRevs interface experience on mobile and [[mw:Special:MyLanguage/Skin:MinervaNeue|Minerva skin]] was inconsistent before it was fixed and ported to [[mw:Special:MyLanguage/Codex|Codex]] by the WMF Growth team and some volunteers. [https://phabricator.wikimedia.org/T191156] * Wikimedia site users can now submit account vanishing requests via [[m:Special:GlobalVanishRequest|GlobalVanishRequest]]. This feature is used when a contributor wishes to stop editing forever. It helps you hide your past association and edit to protect your privacy. Once processed, the account will be locked and renamed. [https://phabricator.wikimedia.org/T367329] * Have you tried monitoring and addressing vandalism in Wikipedia using your phone? [https://diff.wikimedia.org/2024/07/10/%d9%90addressing-vandalism-with-a-tap-the-journey-of-introducing-the-patrolling-feature-in-the-mobile-app/ A Diff blog post on Patrolling features in the Mobile App] highlights some of the new capabilities of the feature, including swiping through a feed of recent changes and a personal library of user talk messages for use when patrolling from your phone. * Wikimedia contributors and GLAM (galleries, libraries, archives, and museums) organisations can now learn and measure the impact Wikimedia Commons is having towards creating quality encyclopedic content using the [https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/reference/commons.html Commons Impact Metrics] analytics dashboard. The dashboard offers organizations analytics on things like monthly edits in a category, the most viewed files, and which Wikimedia articles are using Commons images. As a result of these new data dumps, GLAM organisation can more reliably measure their return on investment for programs bringing content into the digital Commons. [https://diff.wikimedia.org/2024/07/19/commons-impact-metrics-now-available-via-data-dumps-and-api/] '''Project Updates''' * Come share your ideas for improving the wikis on the newly reopened [[m:Special:MyLanguage/Community Wishlist|Community Wishlist]]. The Community Wishlist is Wikimedia’s forum for volunteers to share ideas (called wishes) to improve how the wikis work. The new version of the wishlist is always open, works with both wikitext and Visual Editor, and allows wishes in any language. '''Learn more''' * Have you ever wondered how Wikimedia software works across over 300 languages? This is 253 languages more than the Google Chrome interface, and it's no accident. The Language and Product Localization Team at the Wikimedia Foundation supports your work by adapting all the tools and interfaces in the MediaWiki software so that contributors in our movement who translate pages and strings can translate them and have the sites in all languages. Read more about the team and their upcoming work on [https://diff.wikimedia.org/2024/07/17/building-towards-a-robust-multilingual-knowledge-ecosystem-for-the-wikimedia-movement/ Diff]. * How can Wikimedia build innovative and experimental products while maintaining such heavily used websites? A recent [https://diff.wikimedia.org/2024/07/09/on-the-value-of-experimentation/ blog post] by WMF staff Johan Jönsson highlights the work of the [[m:Future Audiences#Objectives and Key Results|WMF Future Audience initiative]], where the goal is not to build polished products but test out new ideas, such as a [[m:Future_Audiences/Experiments: conversational/generative AI|ChatGPT plugin]] and [[m:Future_Audiences/Experiment:Add a Fact|Add a Fact]], to help take Wikimedia into the future. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' You can also get other news from the [[m:Special:MyLanguage/Wikimedia Foundation Bulletin|Wikimedia Foundation Bulletin]]. </div><section end="technews-2024-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:05, 23 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27142915 --> == Wikipedia translation of the week: 2024-31 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Nederlandsche Cocaïnefabriek]]'''<br /> <small>''([[:es:Nederlandsche Cocaïnefabriek]])&#32;([[:nl:Nederlandsche Cocaïnefabriek]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Nederlandsche Cocainefabriek Schinkelstraat Amsterdam architect HH Baanders 1902.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Nederlandsche Cocaïnefabriek''' (Dutch pronunciation: [ˈneːdərlɑntsə koːkaːˈinəfaːˌbrik]; English: Dutch Cocaine Factory) or NCF was an Amsterdam-based company producing cocaine for medical purposes in the 20th century. It imported its raw materials mainly from the Dutch East Indies and sold its products across Europe, making good profits especially in the early years of World War I. The NCF produced morphine, heroin and ephedrine as well. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:44, 29 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27150339 --> == Tech News: 2024-31 == <section begin="technews-2024-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/31|Translations]] are available. '''Feature news''' * Editors using the Visual Editor in languages that use non-Latin characters for numbers, such as Hindi, Manipuri and Eastern Arabic, may notice some changes in the formatting of reference numbers. This is a side effect of preparing a new sub-referencing feature, and will also allow fixing some general numbering issues in Visual Editor. If you notice any related problems on your wiki, please share details at the [[m:Talk:WMDE Technical Wishes/Sub-referencing|project talkpage]]. '''Bugs status''' * Some logged-in editors were briefly unable to edit or load pages last week. [[phab:T370304|These errors]] were mainly due to the addition of new [[mw:Special:MyLanguage/Help:Extension:Linter|linter]] rules which led to caching problems. Fixes have been applied and investigations are continuing. * Editors can use the [[mw:Special:MyLanguage/Trust and Safety Product/IP Info|IP Information tool]] to get information about IP addresses. This tool is available as a Beta Feature in your preferences. The tool was not available for a few days last week, but is now working again. Thank you to Shizhao for filing the bug report. You can read about that, and [[m:Tech/News/Recently resolved community tasks#2024-07-25|28 other community-submitted tasks]] that were resolved last week. '''Project updates''' * There are new features and improvements to Phabricator from the Release Engineering and Collaboration Services teams, and some volunteers, including: the search systems, the new task creation system, the login systems, the translation setup which has resulted in support for more languages (thanks to Pppery), and fixes for many edge-case errors. You can [[phab:phame/post/view/316/iterative_improvements/|read details about these and other improvements in this summary]]. * There is an [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|update on the Charts project]]. The team has decided which visualization library to use, which chart types to start focusing on, and where to store chart definitions. * One new wiki has been created: a {{int:project-localized-name-group-wikivoyage}} in [[d:Q9056|Czech]] ([[voy:cs:|<code>voy:cs:</code>]]) [https://phabricator.wikimedia.org/T370905] '''Learn more''' * There is a [[diffblog:2024/07/26/the-journey-to-open-our-first-data-center-in-south-america/|new Wikimedia Foundation data center]] in São Paulo, Brazil which helps to reduce load times. * There is new [[diffblog:2024/07/22/the-perplexing-process-of-uploading-images-to-wikipedia/|user research]] on problems with the process of uploading images. * Commons Impact Metrics are [[diffblog:2024/07/19/commons-impact-metrics-now-available-via-data-dumps-and-api/|now available]] via data dumps and API. * The latest quarterly [[mw:Technical Community Newsletter/2024/July|Technical Community Newsletter]] is now available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:11, 29 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27164109 --> == Wikipedia translation of the week: 2024-32 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Suffrage drama]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pamphlet from NAWSA for women's suffrage plays, page 1.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Suffrage drama''' (also known as suffrage plays or suffrage theatre) is a form of dramatic literature that emerged during the British women's suffrage movement in the early twentieth century. Suffrage performances lasted approximately from 1907-1914. Many suffrage plays called for a predominant or all female cast. Suffrage plays served to reveal issues behind the suffrage movement. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 5 August 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27150339 --> == Tech News: 2024-32 == <section begin="technews-2024-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/32|Translations]] are available. '''Feature news''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Two new parser functions will be available this week: <code><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic_words#dir|#dir]]<nowiki>}}</nowiki></code> and <code><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic_words#bcp47|#bcp47]]<nowiki>}}</nowiki></code>. These will reduce the need for <code>Template:Dir</code> and <code>Template:BCP47</code> on Commons and allow us to [[phab:T343131|drop 100 million rows]] from the "what links here" database. Editors at any wiki that use these templates, can help by replacing the templates with these new functions. The templates at Commons will be updated during the Hackathon at Wikimania. [https://phabricator.wikimedia.org/T359761][https://phabricator.wikimedia.org/T366623] * Communities can request the activation of the visual editor on entire namespaces where discussions sometimes happen (for instance ''Wikipedia:'' or ''Wikisource:'' namespaces) if they understand the [[mw:Special:MyLanguage/Help:VisualEditor/FAQ#WPNS|known limitations]]. For discussions, users can already use [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]] in these namespaces. * The tracking category "Pages using Timeline" has been renamed to "Pages using the EasyTimeline extension" [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ATimeline-tracking-category&namespace=8 in TranslateWiki]. Wikis that have created the category locally should rename their local creation to match. '''Project updates''' * Editors who help to organize WikiProjects and similar on-wiki collaborations, are invited to share ideas and examples of successful collaborations with the Campaigns and Programs teams. You can fill out [[m:Special:MyLanguage/Campaigns/WikiProjects|a brief survey]] or share your thoughts [[m:Talk:Campaigns/WikiProjects|on the talkpage]]. The teams are particularly looking for details about successful collaborations on non-English wikis. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The new parser is being rolled out on {{int:project-localized-name-group-wikivoyage}} wikis over the next few months. The {{int:project-localized-name-enwikivoyage}} and {{int:project-localized-name-hewikivoyage}} were [[phab:T365367|switched]] to Parsoid last week. For more information, see [[mw:Parsoid/Parser_Unification|Parsoid/Parser Unification]]. '''Learn more''' * There will be more than 200 sessions at Wikimania this week. Here is a summary of some of the [[diffblog:2024/08/05/interested-in-product-and-tech-here-are-some-wikimania-sessions-you-dont-want-to-miss/|key sessions related to the product and technology area]]. * The latest [[m:Special:MyLanguage/Wikimedia Foundation Bulletin/2024/07-02|Wikimedia Foundation Bulletin]] is available. * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2024/July|Language and Internationalization newsletter]] is available. It includes: New design previews for Translatable pages; Updates about MinT for Wiki Readers; the release of Translation dumps; and more. * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/31|Growth newsletter]] is available. * The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/July 2024|MediaWiki Product Insights newsletter]] is available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:44, 5 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27233905 --> == Wikipedia translation of the week: 2024-33 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Karatgurk]]'''<br /> <small>''([[:it:Karatgurk]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In the Australian Aboriginal mythology of the Aboriginal people of south-eastern Australian state of Victoria, the '''Karatgurk''' were seven sisters who represented the constellation known in western astronomy as the Pleiades. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 12 August 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27264174 --> == Tech News: 2024-33 == <section begin="technews-2024-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/33|Translations]] are available. '''Feature news''' * [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]] editors and maintainers can now [[mw:Special:MyLanguage/Extension:AbuseFilter/Actions#Show a CAPTCHA|make a CAPTCHA show if a filter matches an edit]]. This allows communities to quickly respond to spamming by automated bots. [https://phabricator.wikimedia.org/T20110] * [[m:Special:MyLanguage/Stewards|Stewards]] can now specify if global blocks should prevent account creation. Before [[phab:T17273|this change]] by the [[mw:Special:MyLanguage/Trust and Safety Product|Trust and Safety Product]] Team, all global blocks would prevent account creation. This will allow stewards to reduce the unintended side-effects of global blocks on IP addresses. '''Project updates''' * [[wikitech:Help talk:Toolforge/Toolforge standards committee#August_2024_committee_nominations|Nominations are open on Wikitech]] for new members to refresh the [[wikitech:Help:Toolforge/Toolforge standards committee|Toolforge standards committee]]. The committee oversees the Toolforge [[wikitech:Help:Toolforge/Right to fork policy|Right to fork policy]] and [[wikitech:Help:Toolforge/Abandoned tool policy|Abandoned tool policy]] among other duties. Nominations will remain open until at least 2024-08-26. * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q2880037|West Coast Bajau]] ([[w:bdr:|<code>w:bdr:</code>]]) [https://phabricator.wikimedia.org/T371757] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:22, 12 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27253654 --> == Wikipedia translation of the week: 2024-34 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:B1 (classification)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''B1''' is a medical-based Paralympic classification for blind sport. Athletes in this classification are totally or almost totally blind. It is used by a number of blind sports including blind tennis, para-alpine skiing, para-Nordic skiing, blind cricket, blind golf, five-a-side football, goalball and judo. Some other sports, including adaptive rowing, athletics and swimming, have equivalents to this class. The B1 classification was first created by the IBSA in the 1970s, and has largely remained unchanged since despite an effort by the International Paralympic Committee (IPC) to move towards a more functional and evidence-based classification system. Classification is often handled on the international level by the International Blind Sports Federation (IBSA) but it sometimes handled by national sport federations. There are exceptions for sports like athletics and cycling, where classification is handled by their own governing bodies. Equipment utilized by competitors in this class may differ from sport to sport, and may include sighted guides, guide rails, beeping balls and clapsticks. There may be some modifications related to equipment and rules to specifically address needs of competitors in this class to allow them to compete in specific sports. Some sports specifically do not allow a guide, whereas cycling and skiing require one. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 19 August 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27278917 --> == Tech News: 2024-34 == <section begin="technews-2024-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/34|Translations]] are available. '''Feature news''' * Editors who want to re-use references but with different details such as page numbers, will be able to do so by the end of 2024, using a new [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#Sub-referencing in a nutshell|sub-referencing]] feature. You can read more [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|about the project]] and [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#Test|how to test the prototype]]. * Editors using tracking categories to identify which pages use specific extensions may notice that six of the categories have been renamed to make them more easily understood and consistent. These categories are automatically added to pages that use specialized MediaWiki extensions. The affected names are for: [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Aintersection-category&namespace=8 DynamicPageList], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Akartographer-tracking-category&namespace=8 Kartographer], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Aphonos-tracking-category&namespace=8 Phonos], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Arss-tracking-category&namespace=8 RSS], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Ascore-use-category&namespace=8 Score], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Awikihiero-usage-tracking-category&namespace=8 WikiHiero]. Wikis that have created the category locally should rename their local creation to match. Thanks to Pppery for these improvements. [https://phabricator.wikimedia.org/T347324] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Technical volunteers who edit modules and want to get a list of the categories used on a page, can now do so using the <code><bdi lang="zxx" dir="ltr">categories</bdi></code> property of <code><bdi lang="zxx" dir="ltr">[[mediawikiwiki:Special:MyLanguage/Extension:Scribunto/Lua reference manual#Title objects|mw.title objects]]</bdi></code>. This enables wikis to configure workflows such as category-specific edit notices. Thanks to SD001 for these improvements. [https://phabricator.wikimedia.org/T50175][https://phabricator.wikimedia.org/T85372] '''Bugs status''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Your help is needed to check if any pages need to be moved or deleted. A maintenance script was run to clean up unreachable pages (due to Unicode issues or introduction of new namespaces/namespace aliases). The script tried to find appropriate names for the pages (e.g. by following the Unicode changes or by moving pages whose titles on Wikipedia start with <code>Talk:WP:</code> so that their titles start with <code>Wikipedia talk:</code>), but it may have failed for some pages, and moved them to <bdi lang="zxx" dir="ltr">[[Special:PrefixIndex/T195546/]]</bdi> instead. Your community should check if any pages are listed there, and move them to the correct titles, or delete them if they are no longer needed. A full log (including pages for which appropriate names could be found) is available in [[phab:P67388]]. * Editors who volunteer as [[mw:Special:MyLanguage/Help:Growth/Mentorship|mentors]] to newcomers on their wiki are once again able to access lists of potential mentees who they can connect with to offer help and guidance. This functionality was restored thanks to [[phab:T372164|a bug fix]]. Thank you to Mbch331 for filing the bug report. You can read about that, and 18 other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Project updates''' * The application deadline for the [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal|Product & Technology Advisory Council]] (PTAC) has been extended to September 16. Members will help by providing advice to Foundation Product and Technology leadership on short and long term plans, on complex strategic problems, and help to get feedback from more contributors and technical communities. Selected members should expect to spend roughly 5 hours per month for the Council, during the one year pilot. Please consider applying, and spread the word to volunteers you think would make a positive contribution to the committee. '''Learn more''' * The [[m:Special:MyLanguage/Coolest Tool Award#2024 Winners|2024 Coolest Tool Awards]] were awarded at Wikimania, in seven categories. For example, one award went to the ISA Tool, used for adding structured data to files on Commons, which was recently improved during the [[m:Event:Wiki Mentor Africa ISA Hackathon 2024|Wiki Mentor Africa Hackathon]]. You can see video demonstrations of each tool at the awards page. Congratulations to this year's recipients, and thank you to all tool creators and maintainers. * The latest [[m:Special:MyLanguage/Wikimedia Foundation Bulletin/2024/08-01|Wikimedia Foundation Bulletin]] is available, and includes some highlights from Wikimania, an upcoming Language community meeting, and other news from the movement. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W34"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:54, 20 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27307284 --> == Wikipedia translation of the week: 2024-35 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Erzi (village)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Caucasus, Ingushetia, Ингушские боевые и смотровые башни, горы Кавказа.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Erzi''' (Russian: Эрзи; Ingush: Аьрзи, romanized: Ärzi, lit. 'Eagle') is a medieval village (aul) in the Dzheyrakhsky District of Ingushetia. It is part of the rural settlement (administrative center) of Olgeti. The entire territory of the settlement is included in the Dzheyrakh-Assa State Historical-Architectural and Natural Museum-Reserve and is under state protection. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:19, 26 August 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27345183 --> == Tech News: 2024-35 == <section begin="technews-2024-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/35|Translations]] are available. '''Feature news''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Administrators can now test the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] feature on test2wiki. This was done to allow cross-wiki testing of temporary accounts, for when temporary accounts switch between projects. The feature was enabled on testwiki a few weeks ago. No further temporary account deployments are scheduled yet. Temporary Accounts is a project to create a new type of user account that replaces IP addresses of unregistered editors which are no longer made public. Please [[mw:Talk:Trust and Safety Product/Temporary Accounts|share your opinions and questions on the project talk page]]. * Later this week, editors at wikis that use [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs]] (also known as "Pending Changes") may notice that the indicators at the top of articles have changed. This change makes the system more consistent with the rest of the MediaWiki interface. [https://phabricator.wikimedia.org/T191156] '''Bugs status''' * Editors who use the 2010 wikitext editor, and use the Character Insert buttons, will [[phab:T361465|no longer]] experience problems with the buttons adding content into the edit-summary instead of the edit-window. You can read more about that, and 26 other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Project updates''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Please review and vote on [[m:Special:MyLanguage/Community Wishlist/Focus areas|Focus Areas]], which are groups of wishes that share a problem. Focus Areas were created for the newly reopened Community Wishlist, which is now open year-round for submissions. The first batch of focus areas are specific to moderator workflows, around welcoming newcomers, minimizing repetitive tasks, and prioritizing tasks. Once volunteers have reviewed and voted on focus areas, the Foundation will then review and select focus areas for prioritization. * Do you have a project and are willing to provide a three (3) month mentorship for an intern? [[mw:Special:MyLanguage/Outreachy|Outreachy]] is a twice a year program for people to participate in a paid internship that will start in December 2024 and end in early March 2025, and they need mentors and projects to work on. Projects can be focused on coding or non-coding (design, documentation, translation, research). See the Outreachy page for more details, and a list of past projects since 2013. '''Learn more''' * If you're curious about the product and technology improvements made by the Wikimedia Foundation last year, read [[diffblog:2024/08/21/wikimedia-foundation-product-technology-improving-the-user-experience/|this recent highlights summary on Diff]]. * To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Ohrid - Day 2 - Community Configuration - Shaping On-Wiki Functionality Together.webm|Community Configuration - Shaping On-Wiki Functionality Together]] (55 mins) - about the [[mw:Special:MyLanguage/Community Configuration|Community Configuration]] project. ** [[c:File:Wikimania 2024 - Belgrade - Day 1 - Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views.webm|Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views]] (30 mins) - an overview for both technical and non technical audiences, covering some of the challenges and open questions, related to the [[mw:MediaWiki Product Insights|platform evolution, stewardship and developer experiences]] research. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:34, 26 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27341211 --> == Tech News: 2024-36 == <section begin="technews-2024-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/36|Translations]] are available. '''Weekly highlight''' * Editors and volunteer developers interested in data visualisation can now test the new software for charts. Its early version is available on beta Commons and beta Wikipedia. This is an important milestone before making charts available on regular wikis. You can [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|read more about this project update]] and help to test the charts. '''Feature news''' * Editors who use the [[{{#special:Unusedtemplates}}]] page can now filter out pages which are expected to be there permanently, such as sandboxes, test-cases, and templates that are always substituted. Editors can add the new magic word [[mw:Special:MyLanguage/Help:Magic words#EXPECTUNUSEDTEMPLATE|<code dir="ltr"><nowiki>__EXPECTUNUSEDTEMPLATE__</nowiki></code>]] to a template page to hide it from the listing. Thanks to Sophivorus and DannyS712 for these improvements. [https://phabricator.wikimedia.org/T184633] * Editors who use the New Topic tool on discussion pages, will [[phab:T334163|now be reminded]] to add a section header, which should help reduce the quantity of newcomers who add sections without a header. You can read more about that, and {{formatnum:28}} other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. * Last week, some Toolforge tools had occasional connection problems. The cause is still being investigated, but the problems have been resolved for now. [https://phabricator.wikimedia.org/T373243] * Translation administrators at multilingual wikis, when editing multiple translation units, can now easily mark which changes require updates to the translation. This is possible with the [[phab:T298852#10087288|new dropdown menu]]. '''Project updates''' * A new draft text of a policy discussing the use of Wikimedia's APIs [[m:Special:MyLanguage/API Policy Update 2024|has been published on Meta-Wiki]]. The draft text does not reflect a change in policy around the APIs; instead, it is an attempt to codify existing API rules. Comments, questions, and suggestions are welcome on [[m:Talk:API Policy Update 2024|the proposed update’s talk page]] until September 13 or until those discussions have concluded. '''Learn more''' * To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Ohrid - Day 2 - Charts, the successor of Graphs - A secure and extensible tool for data visualization.webm|Charts, the successor of Graphs - A secure and extensible tool for data visualization]] (25 mins) – about the above-mentioned Charts project. ** [[c:File:Wikimania 2024 - Ohrid - Day 3 - State of Language Technology and Onboarding at Wikimedia.webm|State of Language Technology and Onboarding at Wikimedia]] (90 mins) – about some of the language tools that support Wikimedia sites, such as [[mw:Special:MyLanguage/Content translation|Content]]/[[mw:Special:MyLanguage/Content translation/Section translation|Section Translation]], [[mw:Special:MyLanguage/MinT|MinT]], and LanguageConverter; also the current state and future of languages onboarding. [https://phabricator.wikimedia.org/T368772] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:08, 3 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27390268 --> == Wikipedia translation of the week: 2024-37 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cappadocian calendar]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Cappadocian calendar''' was a solar calendar that was derived from the Persian Zoroastrian calendar. It is named after the historic region Cappadocia in present-day Turkey, where it was used. The calendar, which had 12 months of 30 days each and five epagomenal days, originated between 550 and 330 BC, when Cappadocia was part of the Persian Achaemenid Empire. The Cappadocian calendar was identical to the Zoroastrian calendar; this can be seen in its structure, in the Avestan names and in the order of the months. The Cappadocian calendar reflects the Iranian cultural influence in the region. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:42, 9 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27357319 --> == Tech News: 2024-37 == <section begin="technews-2024-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/37|Translations]] are available. '''Feature news''' * Starting this week, the standard [[mw:Special:MyLanguage/Extension:CodeMirror|syntax highlighter]] will receive new colors that make them compatible in dark mode. This is the first of many changes to come as part of a major upgrade to syntax highlighting. You can learn more about what's to come on the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|help page]]. [https://phabricator.wikimedia.org/T365311][https://phabricator.wikimedia.org/T259059] * Editors of wikis using Wikidata will now be notified of only relevant Wikidata changes in their watchlist. This is because the Lua functions <bdi lang="zxx" dir="ltr"><code>entity:getSitelink()</code></bdi> and <bdi lang="zxx" dir="ltr"><code>mw.wikibase.getSitelink(qid)</code></bdi> will have their logic unified for tracking different aspects of sitelinks to reduce junk notifications from [[m:Wikidata For Wikimedia Projects/Projects/Watchlist Wikidata Sitelinks Tracking|inconsistent sitelinks tracking]]. [https://phabricator.wikimedia.org/T295356] '''Project updates''' * Users of all Wikis will have access to Wikimedia sites as read-only for a few minutes on September 25, starting at 15:00 UTC. This is a planned datacenter switchover for maintenance purposes. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T370962] * Contributors of [[phab:T363538#10123348|11 Wikipedias]], including English will have a new <bdi lang="zxx" dir="ltr"><code>MOS</code></bdi> namespace added to their Wikipedias. This improvement ensures that links beginning with <bdi lang="zxx" dir="ltr"><code>MOS:</code></bdi> (usually shortcuts to the [[w:en:Wikipedia:Manual of Style|Manual of Style]]) are not broken by [[w:en:Mooré|Mooré]] Wikipedia (language code <bdi lang="zxx" dir="ltr"><code>mos</code></bdi>). [https://phabricator.wikimedia.org/T363538] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 9 September 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27424457 --> == Tech News: 2024-38 == <section begin="technews-2024-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/38|Translations]] are available. '''Improvements and Maintenance''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Editors interested in templates can help by reading the latest Wishlist focus area, [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template recall and discovery]], and share your feedback on the talkpage. This input helps the Community Tech team to decide the right technical approach to build. Everyone is also encouraged to continue adding [[m:Special:MyLanguage/Community Wishlist|new wishes]]. * The new automated [[{{#special:NamespaceInfo}}]] page helps editors understand which [[mw:Special:MyLanguage/Help:Namespaces|namespaces]] exist on each wiki, and some details about how they are configured. Thanks to DannyS712 for these improvements. [https://phabricator.wikimedia.org/T263513] * [[mw:Special:MyLanguage/Help:Edit check#Reference check|References Check]] is a feature that encourages editors to add a citation when they add a new paragraph to a Wikipedia article. For a short time, the corresponding tag "Edit Check (references) activated" was erroneously being applied to some edits outside of the main namespace. This has been fixed. [https://phabricator.wikimedia.org/T373692] * It is now possible for a wiki community to change the order in which a page’s categories are displayed on their wiki. By default, categories are displayed in the order they appear in the wikitext. Now, wikis with a consensus to do so can [[m:Special:MyLanguage/Requesting wiki configuration changes|request]] a configuration change to display them in alphabetical order. [https://phabricator.wikimedia.org/T373480] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Tool authors can now access ToolsDB's [[wikitech:Portal:Data Services#ToolsDB|public databases]] from both [[m:Special:MyLanguage/Research:Quarry|Quarry]] and [[wikitech:Superset|Superset]]. Those databases have always been accessible to every [[wikitech:Portal:Toolforge|Toolforge]] user, but they are now more broadly accessible, as Quarry can be accessed by anyone with a Wikimedia account. In addition, Quarry's internal database can now be [[m:Special:MyLanguage/Research:Quarry#Querying Quarry's own database|queried from Quarry itself]]. This database contains information about all queries that are being run and starred by users in Quarry. This information was already public through the web interface, but you can now query it using SQL. You can read more about that, and {{formatnum:20}} other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. * Any pages or tools that still use the very old CSS classes <bdi lang="zxx" dir="ltr"><code>mw-message-box</code></bdi> need to be updated. These old classes will be removed next week or soon afterwards. Editors can use a [https://global-search.toolforge.org/?q=mw-message-box&regex=1&namespaces=&title= global-search] to determine what needs to be changed. It is possible to use the newer <bdi lang="zxx" dir="ltr"><code>cdx-message</code></bdi> group of classes as a replacement (see [https://doc.wikimedia.org/codex/latest/components/demos/message.html#css-only-version the relevant Codex documentation], and [https://meta.wikimedia.org/w/index.php?title=Tech/Header&diff=prev&oldid=27449042 an example update]), but using locally defined onwiki classes would be best. [https://phabricator.wikimedia.org/T374499] '''Technical project updates''' * Next week, all Wikimedia wikis will be read-only for a few minutes. This will start on September 25 at [https://zonestamp.toolforge.org/1727276400 15:00 UTC]. This is a planned datacenter switchover for maintenance purposes. [[m:Special:MyLanguage/Tech/Server switch|This maintenance process also targets other services.]] The previous switchover took 3 minutes, and the Site Reliability Engineering teams use many tools to make sure that this essential maintenance work happens as quickly as possible. [https://phabricator.wikimedia.org/T370962] '''Tech in depth''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/August 2024|MediaWiki Product Insights newsletter]] is available. This edition includes details about: research about [[mw:Special:MyLanguage/Manual:Hooks|hook]] handlers to help simplify development, research about performance improvements, work to improve the REST API for end-users, and more. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Auditorium Kyiv - Day 4 - Hackathon Showcase.webm|Hackathon Showcase]] (45 mins) - 19 short presentations by some of the Hackathon participants, describing some of the projects they worked on, such as automated testing of maintenance scripts, a video-cutting command line tool, and interface improvements for various tools. There are [[phab:T369234|more details and links available]] in the Phabricator task. ** [[c:File:Co-Creating a Sustainable Future for the Toolforge Ecosystem.webm|Co-Creating a Sustainable Future for the Toolforge Ecosystem]] (40 mins) - a roundtable discussion for tool-maintainers, users, and supporters of Toolforge about how to make the platform sustainable and how to evaluate the tools available there. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:03, 17 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27460876 --> == Wikipedia translation of the week: 2024-39 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Independence Day (Albania)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Independence Day''' (Albanian: Dita e Pavarësisë) is a public holiday in Albania observed on 28 November. It commemorates the Albanian Declaration of Independence (from the Ottoman Empire), which was ratified by the All-Albanian Congress on 28 November 1912, establishing the state of Albania. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:29, 23 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27456350 --> == Tech News: 2024-39 == <section begin="technews-2024-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/39|Translations]] are available. '''Weekly highlight''' * All wikis will be [[m:Special:MyLanguage/Tech/Server switch|read-only]] for a few minutes on Wednesday September 25 at [https://zonestamp.toolforge.org/1727276400 15:00 UTC]. Reading the wikis will not be interrupted, but editing will be paused. These twice-yearly processes allow WMF's site reliability engineering teams to remain prepared to keep the wikis functioning even in the event of a major interruption to one of our data centers. '''Updates for editors''' [[File:Add alt text from a halfsheet, with the article behind.png|thumb|A screenshot of the interface for the Alt Text suggested-edit feature]] * Editors who use the iOS Wikipedia app in Spanish, Portuguese, French, or Chinese, may see the [[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits project/Alt Text Experiment|Alt Text suggested-edit experiment]] after editing an article, or completing a suggested edit using "[[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits project#Hypothesis 2 Add an Image Suggested Edit|Add an image]]". Alt-text helps people with visual impairments to read Wikipedia articles. The team aims to learn if adding alt-text to images is a task that editors can be successful with. Please share any feedback on [[mw:Talk:Wikimedia Apps/iOS Suggested edits project/Alt Text Experiment|the discussion page]]. * The Codex color palette has been updated with new and revised colors for the MediaWiki user interfaces. The [[mw:Special:MyLanguage/Design System Team/Color/Design documentation#Updates|most noticeable changes]] for editors include updates for: dark mode colors for Links and for quiet Buttons (progressive and destructive), visited Link colors for both light and dark modes, and background colors for system-messages in both light and dark modes. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] It is now possible to include clickable wikilinks and external links inside code blocks. This includes links that are used within <code><nowiki><syntaxhighlight></nowiki></code> tags and on code pages (JavaScript, CSS, Scribunto and Sanitized CSS). Uses of template syntax <code><nowiki>{{…}}</nowiki></code> are also linked to the template page. Thanks to SD0001 for these improvements. [https://phabricator.wikimedia.org/T368166] * Two bugs were fixed in the [[m:Special:MyLanguage/Account vanishing|GlobalVanishRequest]] system by improving the logging and by removing an incorrect placeholder message. [https://phabricator.wikimedia.org/T370595][https://phabricator.wikimedia.org/T372223] * View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] From [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]]: ** The API now enables 5,000 on-demand API requests per month and twice-monthly HTML snapshots freely (gratis and libre). More information on the updates and also improvements to the software development kits (SDK) are explained on [https://enterprise.wikimedia.com/blog/enhanced-free-api/ the project's blog post]. While Wikimedia Enterprise APIs are designed for high-volume commercial reusers, this change enables many more community use-cases to be built on the service too. ** The Snapshot API (html dumps) have added beta Structured Contents endpoints ([https://enterprise.wikimedia.com/blog/structured-contents-snapshot-api/ blog post on that]) as well as released two beta datasets (English and French Wikipedia) from that endpoint to Hugging Face for public use and feedback ([https://enterprise.wikimedia.com/blog/hugging-face-dataset/ blog post on that]). These pre-parsed data sets enable new options for researchers, developers, and data scientists to use and study the content. '''In depth''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The Wikidata Query Service (WDQS) is used to get answers to questions using the Wikidata data set. As Wikidata grows, we had to make a major architectural change so that WDQS could remain performant. As part of the [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS graph split|WDQS Graph Split project]], we have new SPARQL endpoints available for serving the "[https://query-scholarly.wikidata.org scholarly]" and "[https://query-main.wikidata.org main]" subgraphs of Wikidata. The [http://query.wikidata.org query.wikidata.org endpoint] will continue to serve the full Wikidata graph until March 2025. After this date, it will only serve the main graph. For more information, please see [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/September 2024 scaling update|the announcement on Wikidata]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:37, 23 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27493779 --> == Wikipedia translation of the week: 2024-40 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Wildlife of Bahrain]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Birds in Al-Areen Wildlife Park.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The wildlife of the archipelago of Bahrain, is more varied than might be expected of this small group of islands in the Persian Gulf. Apart from a strip of the north and west of the main island, where crops are grown with irrigation, the land is arid. With a very hot dry summer, a mild winter, and brackish groundwater, the plants need adaptations in order to survive. Nevertheless, 196 species of higher plant have been recorded here, as well as about seventeen species of terrestrial mammals, many birds and reptiles, and many migratory birds visit the islands in autumn and spring. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 30 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27456350 --> == Tech News: 2024-40 == <section begin="technews-2024-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/40|Translations]] are available. '''Updates for editors''' * Readers of [[phab:T375401|42 more wikis]] can now use Dark Mode. If the option is not yet available for logged-out users of your wiki, this is likely because many templates do not yet display well in Dark Mode. Please use the [https://night-mode-checker.wmcloud.org/ night-mode-checker tool] if you are interested in helping to reduce the number of issues. The [[mw:Special:MyLanguage/Recommendations for night mode compatibility on Wikimedia wikis|recommendations page]] provides guidance on this. Dark Mode is enabled on additional wikis once per month. * Editors using the 2010 wikitext editor as their default can access features from the 2017 wikitext editor by adding <code dir=ltr>?veaction=editsource</code> to the URL. If you would like to enable the 2017 wikitext editor as your default, it can be set in [[Special:Preferences#mw-input-wpvisualeditor-newwikitext|your preferences]]. [https://phabricator.wikimedia.org/T239796] * For logged-out readers using the Vector 2022 skin, the "donate" link has been moved from a collapsible menu next to the content area into a more prominent top menu, next to "Create an account". This restores the link to the level of prominence it had in the Vector 2010 skin. [[mw:Readers/2024 Reader and Donor Experiences#Donor Experiences (Key Result WE 3.2 and the related hypotheses)|Learn more]] about the changes related to donor experiences. [https://phabricator.wikimedia.org/T373585] * The CampaignEvents extension provides tools for organizers to more easily manage events, communicate with participants, and promote their events on the wikis. The extension has been [[m:Special:MyLanguage/CampaignEvents/Deployment status|enabled]] on Arabic Wikipedia, Igbo Wikipedia, Swahili Wikipedia, and Meta-Wiki. [[w:zh:Wikipedia:互助客栈/其他#引進CampaignEvents擴充功能|Chinese Wikipedia has decided]] to enable the extension, and discussions on the extension are in progress [[w:es:Wikipedia:Votaciones/2024/Sobre la política de Organizadores de Eventos|on Spanish Wikipedia]] and [[d:Wikidata:Project chat#Enabling the CampaignEvents Extention on Wikidata|on Wikidata]]. To learn how to enable the extension on your wiki, you can visit [[m:Special:MyLanguage/CampaignEvents|the CampaignEvents page on Meta-Wiki]]. * View all {{formatnum:22}} community-submitted {{PLURAL:22|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers with an account on Wikitech-wiki should [[wikitech:Wikitech/SUL-migration|check if any action is required]] for their accounts. The wiki is being changed to use the single-user-login (SUL) system, and other configuration changes. This change will help reduce the overall complexity for the weekly software updates across all our wikis. '''In depth''' * The [[m:Special:MyLanguage/Tech/Server switch|server switch]] was completed successfully last week with a read-only time of [[wikitech:Switch Datacenter#Past Switches|only 2 minutes 46 seconds]]. This periodic process makes sure that engineers can switch data centers and keep all of the wikis available for readers, even if there are major technical issues. It also gives engineers a chance to do maintenance and upgrades on systems that normally run 24 hours a day, and often helps to reveal weaknesses in the infrastructure. The process involves dozens of software services and hundreds of hardware servers, and requires multiple teams working together. Work over the past few years has reduced the time from 17 minutes down to 2–3 minutes. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/66ZW7B2MG63AESQVTXDIFQBDBS766JGW/] '''Meetings and events''' * October 4–6: [[m:Special:MyLanguage/WikiIndaba conference 2024|WikiIndaba Conference's Hackathon]] in Johannesburg, South Africa * November 4–6: [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2024|MediaWiki Users and Developers Conference Fall 2024]] in Vienna, Austria '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:21, 30 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27530062 --> == Tech News: 2024-41 == <section begin="technews-2024-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/41|Translations]] are available. '''Weekly highlight''' * Communities can now request installation of [[mw:Special:MyLanguage/Moderator Tools/Automoderator|Automoderator]] on their wiki. Automoderator is an automated anti-vandalism tool that reverts bad edits based on scores from the new "Revert Risk" machine learning model. You can [[mw:Special:MyLanguage/Extension:AutoModerator/Deploying|read details about the necessary steps]] for installation and configuration. [https://phabricator.wikimedia.org/T336934] '''Updates for editors''' * Translators in wikis where [[mw:Special:MyLanguage/Content translation/Section translation#Try the tool|the mobile experience of Content Translation is available]], can now customize their articles suggestion list from 41 filtering options when using the tool. This topic-based article suggestion feature makes it easy for translators to self-discover relevant articles based on their area of interest and translate them. You can [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions try it with your mobile device]. [https://phabricator.wikimedia.org/T368422] * View all {{formatnum:12}} community-submitted {{PLURAL:12|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * It is now possible for <bdi lang="zxx" dir="ltr"><code><nowiki><syntaxhighlight></nowiki></code></bdi> code blocks to offer readers a "Copy" button if the <bdi lang="zxx" dir="ltr"><code><nowiki>copy=1</nowiki></code></bdi> attribute is [[mw:Special:MyLanguage/Extension:SyntaxHighlight#copy|set on the tag]]. Thanks to SD0001 for these improvements. [https://phabricator.wikimedia.org/T40932] * Customized copyright footer messages on all wikis will be updated. The new versions will use wikitext markup instead of requiring editing raw HTML. [https://phabricator.wikimedia.org/T375789] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Later this month, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] will be rolled out on several pilot wikis. The final list of the wikis will be published in the second half of the month. If you maintain any tools, bots, or gadgets on [[phab:T376499|these 11 wikis]], and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|Guidance on how to update the code is available]]. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Rate limiting has been enabled for the code review tools [[Wikitech:Gerrit|Gerrit]] and [[Wikitech:GitLab|GitLab]] to address ongoing issues caused by malicious traffic and scraping. Clients that open too many concurrent connections will be restricted for a few minutes. This rate limiting is managed through [[Wikitech:nftables|nftables]] firewall rules. For more details, see Wikitech's pages on [[Wikitech:Firewall#Throttling with nftables|Firewall]], [[Wikitech:GitLab/Abuse and rate limiting|GitLab limits]] and [[Wikitech:Gerrit/Operations#Throttling IPs|Gerrit operations]]. * Five new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q49224|Komering]] ([[w:kge:|<code>w:kge:</code>]]) [https://phabricator.wikimedia.org/T374813] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q36096|Mooré]] ([[m:mos:|<code>m:mos:</code>]]) [https://phabricator.wikimedia.org/T374641] ** a {{int:project-localized-name-group-wiktionary}} in [[d:Q36213|Madurese]] ([[wikt:mad:|<code>wikt:mad:</code>]]) [https://phabricator.wikimedia.org/T374968] ** a {{int:project-localized-name-group-wikiquote}} in [[d:Q2501174|Gorontalo]] ([[q:gor:|<code>q:gor:</code>]]) [https://phabricator.wikimedia.org/T375088] ** a {{int:project-localized-name-group-wikinews}} in [[d:Q56482|Shan]] ([[n:shn:|<code>n:shn:</code>]]) [https://phabricator.wikimedia.org/T375430] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:43, 7 October 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27557422 --> == Wikipedia translation of the week: 2024-42 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Little Danes experiment]]'''<br /> <small>''([[:fa:آزمایش دانمارکی‌های کوچک]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Children play at a Danish Red Cross-run orphanage in Greenland.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''little Danes experiment''' was a 1951 Danish operation where 22 Greenlandic Inuit children were sent to Danish foster families in an attempt to re-educate them as "little Danes". While the children were all supposed to be orphans, most were not. Six children were adopted while in Denmark, and sixteen returned to Greenland, only to be placed in Danish-speaking orphanages and never live with their families again. Half of the children experienced mental health disturbances, and half of them died in young adulthood. The government of Denmark officially apologised in 2020, after several years of demands from Greenlandic officials. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:16, 14 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27572997 --> == Tech News: 2024-42 == <section begin="technews-2024-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/42|Translations]] are available. '''Updates for editors''' * The Structured Discussion extension (also known as Flow) is starting to be removed. This extension is unmaintained and causes issues. It will be replaced by [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]], which is used on any regular talk page. [[mw:Special:MyLanguage/Structured Discussions/Deprecation#Deprecation timeline|A first set of wikis]] are being contacted. These wikis are invited to stop using Flow, and to move all Flow boards to sub-pages, as archives. At these wikis, a script will move all Flow pages that aren't a sub-page to a sub-page automatically, starting on 22 October 2024. On 28 October 2024, all Flow boards at these wikis will be set in read-only mode. [https://www.mediawiki.org/wiki/Structured_Discussions/Deprecation][https://phabricator.wikimedia.org/T370722] * WMF's Search Platform team is working on making it easier for readers to perform text searches in their language. A [[phab:T332342|change last week]] on over 30 languages makes it easier to find words with accents and other diacritics. This applies to both full-text search and to types of advanced search such as the <bdi lang="en" dir="ltr">''hastemplate''</bdi> and <bdi lang="en" dir="ltr">''incategory''</bdi> keywords. More technical details (including a few other minor search upgrades) are available. [https://www.mediawiki.org/wiki/User:TJones_%28WMF%29/Notes/Language_Analyzer_Harmonization_Notes#ASCII-folding/ICU-folding_%28T332342%29] * View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[mw:Special:MyLanguage/Help:Edit check|EditCheck]] was installed at Russian Wikipedia, and fixes were made for some missing user interface styles. '''Updates for technical contributors''' * Editors who use the Toolforge tool [[toolforge:copyvios|Earwig's Copyright Violation Detector]] will now be required to log in with their Wikimedia account before running checks using the "search engine" option. This change is needed to help prevent external bots from misusing the system. Thanks to Chlod for these improvements. [https://en.wikipedia.org/wiki/Wikipedia_talk:New_pages_patrol/Reviewers#Authentication_is_now_required_for_search_engine_checks_on_Earwig's_Copyvio_Tool] * [[m:Special:MyLanguage/Phabricator|Phabricator]] users can create tickets and add comments on existing tickets via Email again. [[mw:Special:MyLanguage/Phabricator/Help#Using email|Sending email to Phabricator]] has been fixed. [https://phabricator.wikimedia.org/T356077] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Some HTML elements in the interface are now wrapped with a <code><nowiki><bdi></nowiki></code> element, to make our HTML output more aligned with Web standards. More changes like this will be coming in future weeks. This change might break some tools that rely on the previous HTML structure of the interface. Note that relying on the HTML structure of the interface is [[mw:Special:MyLanguage/Stable interface policy/Frontend#What is not stable?|not recommended]] and might break at any time. [https://phabricator.wikimedia.org/T375975] '''In depth''' * The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/September 2024|MediaWiki Product Insights newsletter]] is available. This edition includes: updates on Wikimedia's authentication system, research to simplify feature development in the MediaWiki platform, updates on Parser Unification and MathML rollout, and more. * The latest quarterly [[mw:Technical Community Newsletter/2024/October|Technical Community Newsletter]] is now available. This edition include: research about improving topic suggestions related to countries, improvements to PHPUnit tests, and more. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:22, 14 October 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27597254 --> == Wikipedia translation of the week: 2024-43 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kharayeb]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Muharram 1Oth-Ashouraa 2007 in Kharayeb - panoramio.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Kharayeb''' (Arabic: الخرايب) is a historic town in the Sidon District in the South Governorate, Lebanon. The town is 77 km (48 mi) south of Beirut, and stands at an average altitude of 190 m (620 ft) above sea level. The town boasts a rich historical legacy, with archaeological excavations revealing a complex settlement history spanning from Prehistory to the Ottoman period. Notably, Kharayeb's origins can be traced back to the Persian period (539–330 BC), when it played a pivotal role in the region's agricultural and economic landscape, culminating in the construction of its Phoenician temple around the 6th century BC. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:38, 21 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27572997 --> == Tech News: 2024-43 == <section begin="technews-2024-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/43|Translations]] are available. '''Weekly highlight''' * The Mobile Apps team has released an [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Navigation Refresh#Phase 1: Creating a user Profile Menu (T373714)|update]] to the iOS app's navigation, and it is now available in the latest App store version. The team added a new Profile menu that allows for easy access to editor features like Notifications and Watchlist from the Article view, and brings the "Donate" button into a more accessible place for users who are reading an article. This is the first phase of a larger planned [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Navigation Refresh|navigation refresh]] to help the iOS app transition from a primarily reader-focused app, to an app that fully supports reading and editing. The Wikimedia Foundation has added more editing features and support for on-wiki communication based on volunteer requests in recent years. [[File:IOS App Navigation refresh first phase 05.png|thumb|iOS Wikipedia App's profile menu and contents]] '''Updates for editors''' * Wikipedia readers can now download a browser extension to experiment with some early ideas on potential features that recommend articles for further reading, automatically summarize articles, and improve search functionality. For more details and to stay updated, check out the Web team's [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments|Content Discovery Experiments page]] and [[mw:Special:MyLanguage/Newsletter:Web team's projects|subscribe to their newsletter]]. * Later this month, logged-out editors of [[phab:T376499|these 12 wikis]] will start to have [[mw:Special:Mylanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] created. The list may slightly change - some wikis may be removed but none will be added. Temporary account is a new [[mw:Special:MyLanguage/User account types|type of user account]]. It enhances the logged-out editors' privacy and makes it easier for community members to communicate with them. If you maintain any tools, bots, or gadgets on these 12 wikis, and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|Guidance on how to update the code is available]]. Read more about the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|deployment plan across all wikis]]. * View all {{formatnum:33}} community-submitted {{PLURAL:33|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[w:nr:Main Page|South Ndebele]], [[w:rsk:Главни бок|Pannonian Rusyn]], [[w:ann:Uwu|Obolo]], [[w:iba:Lambar Keterubah|Iban]] and [[w:tdd:ᥞᥨᥝᥴ ᥘᥣᥲ ᥖᥥᥰ|Tai Nüa]] Wikipedia languages were created last week. [https://www.wikidata.org/wiki/Q36785][https://www.wikidata.org/wiki/Q35660][https://www.wikidata.org/wiki/Q36614][https://www.wikidata.org/wiki/Q33424][https://www.wikidata.org/wiki/Q36556] * It is now possible to create functions on Wikifunctions using Wikidata lexemes, through the new [[f:Z6005|Wikidata lexeme type]] launched last week. When you go to one of these functions, the user interface provides a lexeme selector that helps you pick a lexeme from Wikidata that matches the word you type. After hitting run, your selected lexeme is retrieved from Wikidata, transformed into a Wikidata lexeme type, and passed into the selected function. Read more about this in [[f:Special:MyLanguage/Wikifunctions:Status updates/2024-10-17#Function of the Week: select representation from lexeme|the latest Wikifunctions newsletter]]. '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Users of the Wikimedia sites can now format dates more easily in different languages with the new <code dir="ltr">{{[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##timef|#timef]]:…}}</code> parser function. For example, <code dir="ltr"><nowiki>{{#timef:now|date|en}}</nowiki></code> will show as "<bdi lang="en" dir="ltr">{{#timef:now|date|en}}</bdi>". Previously, <code dir="ltr"><nowiki>{{#time:…}}</nowiki></code> could be used to format dates, but this required knowledge of the order of the time and date components and their intervening punctuation. <code dir="ltr">#timef</code> (or <code dir="ltr">#timefl</code> for local time) provides access to the standard date formats that MediaWiki uses in its user interface. This may help to simplify some templates on multi-lingual wikis like Commons and Meta. [https://phabricator.wikimedia.org/T223772][https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:ParserFunctions##timef] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Commons and Meta users can now efficiently [[mw:Special:MyLanguage/Help:Magic words#Localization|retrieve the user's language]] using <code dir="ltr"><nowiki>{{USERLANGUAGE}}</nowiki></code> instead of using <code dir="ltr"><nowiki>{{int:lang}}</nowiki></code>. [https://phabricator.wikimedia.org/T4085] * The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Tech Advisory Council]] (PTAC) now has its pilot members with representation across Africa, Asia, Europe, North America and South America. They will work to address the [[Special:MyLanguage/Movement Strategy/Initiatives/Technology Council|Movement Strategy's Technology Council]] initiative of having a co-defined and more resilient technological platform. [https://meta.wikimedia.org/wiki/Movement_Strategy/Initiatives/Technology_Council] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/32|Growth newsletter]] is available. It includes: an upcoming Newcomer Homepage Community Updates module, new Community Configuration options, and details on new projects. * The Wikimedia Foundation is [[mw:Special:MyLanguage/Wikimedia Security Team#CNA Partnership|now an official partner of the CVE program]], which is an international effort to catalog publicly disclosed cybersecurity vulnerabilities. This partnership will allow the Security Team to instantly publish [[w:en:Common Vulnerabilities and Exposures|common vulnerabilities and exposures]] (CVE) records that are affecting MediaWiki core, extensions, and skins, along with any other code the Foundation is a steward of. * The [[m:Special:MyLanguage/Community Wishlist|Community Wishlist]] is now [[m:Community Wishlist/Updates#October 16, 2024: Conversations Made Easier: Machine-Translated Wishes Are Here!|testing machine translations]] for Wishlist content. Volunteers can now read machine-translated versions of wishes and dive into discussions even before translators arrive to translate content. '''Meetings and events''' * 24 October - Wiki Education Speaker Series Webinar - [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/N4XTB4G55BUY3M3PNGUAKQWJ7A4UOPAK/ Open Source Tech: Building the Wiki Education Dashboard], featuring Wikimedia interns and a Web developer in the panel. * 20–22 December 2024 - [[m:Special:MyLanguage/Indic Wikimedia Hackathon Bhubaneswar 2024|Indic Wikimedia Hackathon Bhubaneswar 2024]] in Odisha, India. A hackathon for community members, including developers, designers and content editors, to build technical solutions that improve contributors' experiences. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:53, 21 October 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27634672 --> == Wikipedia translation of the week: 2024-44 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Christmas horror]]'''<br /> <small>''([[:es:Terror navideño]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Christmascarol1843 -- 169.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Christmas horror''' is a fiction genre and film genre that incorporates horror elements into a seasonal setting. It is popular in multiple countries. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 28 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27647428 --> == Tech News: 2024-44 == <section begin="technews-2024-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/44|Translations]] are available. '''Updates for editors''' * Later in November, the Charts extension will be deployed to the test wikis in order to help identify and fix any issue. A security review is underway to then enable deployment to pilot wikis for broader testing. You can read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates#October 2024: Working towards production deployment|the October project update]] and see the [https://en.wikipedia.beta.wmflabs.org/wiki/Charts latest documentation and examples on Beta Wikipedia]. * View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[w:en:PediaPress|Pediapress.com]], an external service that creates books from Wikipedia, can now use [[mw:Special:MyLanguage/Wikimedia Maps|Wikimedia Maps]] to include existing pre-rendered infobox map images in their printed books on Wikipedia. [https://phabricator.wikimedia.org/T375761] '''Updates for technical contributors''' * Wikis can use [[:mw:Special:MyLanguage/Extension:GuidedTour|the Guided Tour extension]] to help newcomers understand how to edit. The Guided Tours extension now works with [[mw:Special:MyLanguage/Manual:Dark mode|dark mode]]. Guided Tour maintainers can check their tours to see that nothing looks odd. They can also set <code>emitTransitionOnStep</code> to <code>true</code> to fix an old bug. They can use the new flag <code>allowAutomaticBack</code> to avoid back-buttons they don't want. [https://phabricator.wikimedia.org/T73927#10241528] * Administrators in the Wikimedia projects who use the [[mw:Special:MyLanguage/Help:Extension:Nuke|Nuke Extension]] will notice that mass deletions done with this tool have the "Nuke" tag. This change will make reviewing and analyzing deletions performed with the tool easier. [https://phabricator.wikimedia.org/T366068] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:57, 28 October 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27668811 --> == Wikipedia translation of the week: 2024-45 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Placenta cake]]'''<br /> <small>''([[:simple:Placenta cake]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Bucharest, Greek pie-maker, 1880.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Placenta cake''' is a dish from ancient Greece and Rome consisting of many dough layers interspersed with a mixture of cheese and honey and flavored with bay leaves, baked and then covered in honey. The dessert is mentioned in classical texts such as the Greek poems of Archestratos and Antiphanes, as well as the De agri cultura of Cato the Elder. It is often seen as the predecessor of baklava and börek. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:16, 4 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27647428 --> == Tech News: 2024-45 == <section begin="technews-2024-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/45|Translations]] are available. '''Updates for editors''' * Stewards can now make [[m:Special:MyLanguage/Global blocks|global account blocks]] cause global [[mw:Special:MyLanguage/Autoblock|autoblocks]]. This will assist stewards in preventing abuse from users who have been globally blocked. This includes preventing globally blocked temporary accounts from exiting their session or switching browsers to make subsequent edits for 24 hours. Previously, temporary accounts could exit their current session or switch browsers to continue editing. This is an anti-abuse tool improvement for the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] project. You can read more about the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|progress on key features for temporary accounts]]. [https://phabricator.wikimedia.org/T368949] * Wikis that have the [[m:Special:MyLanguage/CampaignEvents/Deployment status|CampaignEvents extension enabled]] can now use the [[m:Special:MyLanguage/Campaigns/Foundation Product Team/Event list#October 29, 2024: Collaboration List launched|Collaboration List]] feature. This list provides a new, easy way for contributors to learn about WikiProjects on their wikis. Thanks to the Campaign team for this work that is part of [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2024-2025/Product %26 Technology OKRs#WE KRs|the 2024/25 annual plan]]. If you are interested in bringing the CampaignEvents extension to your wiki, you can [[m:Special:MyLanguage/CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|follow these steps]] or you can reach out to User:Udehb-WMF for help. * The text color for red links will be slightly changed later this week to improve their contrast in light mode. [https://phabricator.wikimedia.org/T370446] * View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, on multilingual wikis, users [[phab:T216368|can now]] hide translations from the WhatLinksHere special page. '''Updates for technical contributors''' * XML [[m:Special:MyLanguage/Data dumps|data dumps]] have been temporarily paused whilst a bug is investigated. [https://lists.wikimedia.org/hyperkitty/list/xmldatadumps-l@lists.wikimedia.org/message/BXWJDPO5QI2QMBCY7HO36ELDCRO6HRM4/] '''In depth''' * Temporary Accounts have been deployed to six wikis; thanks to the Trust and Safety Product team for [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|this work]], you can read about [[phab:T340001|the deployment plans]]. Beginning next week, Temporary Accounts will also be enabled on [[phab:T378336|seven other projects]]. If you are active on these wikis and need help migrating your tools, please reach out to [[m:User:Udehb-WMF|User:Udehb-WMF]] for assistance. * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2024/October|Language and Internationalization newsletter]] is available. It includes: New languages supported in translatewiki or in MediaWiki; New keyboard input methods for some languages; details about recent and upcoming meetings, and more. '''Meetings and events''' * [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2024|MediaWiki Users and Developers Conference Fall 2024]] is happening in Vienna, Austria and online from 4 to 6 November 2024. The conference will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:51, 4 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27693917 --> == Wikipedia translation of the week: 2024-46 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Trisomy 16]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Chromosome 16.svg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Trisomy 16''' is a chromosomal abnormality in which there are 3 copies of chromosome 16 rather than two. It is the most common trisomy leading to miscarriage and the second most common chromosomal cause of it, closely following X-chromosome monosomy. About 6% of miscarriages have trisomy 16. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:09, 11 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27708700 --> == Tech News: 2024-46 == <section begin="technews-2024-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/46|Translations]] are available. '''Updates for editors''' * On wikis with the [[mw:Special:MyLanguage/Help:Extension:Translate|Translate extension]] enabled, users will notice that the FuzzyBot will now automatically create translated versions of categories used on translated pages. [https://phabricator.wikimedia.org/T285463] * View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the submitted task to use the [[mw:Special:MyLanguage/Extension:SecurePoll|SecurePoll extension]] for English Wikipedia's special [[w:en:Wikipedia:Administrator elections|administrator election]] was resolved on time. [https://phabricator.wikimedia.org/T371454] '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] In <code dir="ltr">[[mw:MediaWiki_1.44/wmf.2|1.44.0-wmf-2]]</code>, the logic of Wikibase function <code>getAllStatements</code> changed to behave like <code>getBestStatements</code>. Invoking the function now returns a copy of values which are immutable. [https://phabricator.wikimedia.org/T270851] * [https://en.wikipedia.org/api/rest_v1/ Wikimedia REST API] users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. The API will be rerouting some page content endpoints from RESTbase to the newer [[mw:Special:MyLanguage/API:REST API|MediaWiki REST API]] endpoints. The [[phab:T374683|impacted endpoints]] include getting page/revision metadata and rendered HTML content. These changes will be available on testwiki later this week, with other projects to follow. This change should not affect existing functionality, but active users of the impacted endpoints should verify behavior on testwiki, and raise any concerns on the related [[phab:T374683|Phabricator ticket]]. '''In depth''' * Admins and users of the Wikimedia projects [[mw:Special:MyLanguage/Moderator_Tools/Automoderator#Usage|where Automoderator is enabled]] can now monitor and evaluate important metrics related to Automoderator's actions. [https://superset.wmcloud.org/superset/dashboard/unified-automoderator-activity-dashboard/ This Superset dashboard] calculates and aggregates metrics about Automoderator's behaviour on the projects in which it is deployed. Thanks to the Moderator Tools team for this Dashboard; you can visit [[mw:Special:MyLanguage/Moderator Tools/Automoderator/Unified Activity Dashboard|the documentation page]] for more information about this work. [https://phabricator.wikimedia.org/T369488] '''Meetings and events''' * 21 November 2024 ([[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 8:00 UTC|8:00 UTC]] & [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 16:00 UTC|16:00 UTC]]) - [[c:Commons:WMF support for Commons/Commons community calls|Community call]] with Wikimedia Commons volunteers and stakeholders to help prioritize support efforts for 2025-2026 Fiscal Year. The theme of this call is how content should be organised on Wikimedia Commons. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:08, 12 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27732268 --> == Wikipedia translation of the week: 2024-47 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Boana platanera]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Rana platanera - Boana platanera.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Boana platanera''''', commonly known as the banana tree dwelling frog, is a species of tree frog in the family Hylidae. It is distributed within Venezuela, Colombia, Panama, and Trinidad and Tobago. Boana platanera was described in 2021, and individuals of the species were previously classified as Boana crepitans or Boana xerophylla. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:53, 18 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27735014 --> == Tech News: 2024-47 == <section begin="technews-2024-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/47|Translations]] are available. '''Updates for editors''' * Users of Wikimedia sites will now be warned when they create a [[mw:Special:MyLanguage/Help:Redirects|redirect]] to a page that doesn't exist. This will reduce the number of broken redirects to red links in our projects. [https://phabricator.wikimedia.org/T326057] * View all {{formatnum:42}} community-submitted {{PLURAL:42|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[mw:Special:MyLanguage/Manual:Pywikibot/Overview|Pywikibot]], which automates work on MediaWiki sites, was upgraded to 9.5.0 on Toolforge. [https://phabricator.wikimedia.org/T378676] '''Updates for technical contributors''' * On wikis that use the [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs extension]], pages created or moved by users with the appropriate permissions are marked as flagged automatically. This feature has not been working recently, and changes fixing it should be deployed this week. Thanks to Daniel and Wargo for working on this. [https://phabricator.wikimedia.org/T379218][https://phabricator.wikimedia.org/T368380] '''In depth''' * There is a new [https://diff.wikimedia.org/2024/11/05/say-hi-to-temporary-accounts-easier-collaboration-with-logged-out-editors-with-better-privacy-protection Diff post] about Temporary Accounts, available in more than 15 languages. Read it to learn about what Temporary Accounts are, their impact on different groups of users, and the plan to introduce the change on all wikis. '''Meetings and events''' * Technical volunteers can now register for the [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]], which will take place in Istanbul, Turkey. [https://pretix.eu/wikimedia/hackathon2025/ Application for travel and accommodation scholarships] is open from '''November 12 to December 10 2024'''. The registration for the event will close in mid-April 2025. The Wikimedia Hackathon is an annual gathering that unites the global technical community to collaborate on existing projects and explore new ideas. * Join the [[C:Special:MyLanguage/Commons:WMF%20support%20for%20Commons/Commons%20community%20calls|Wikimedia Commons community calls]] this week to help prioritize support for Commons which will be planned for 2025–2026. The theme will be how content should be organised on Wikimedia Commons. This is an opportunity for volunteers who work on different things to come together and talk about what matters for the future of the project. The calls will take place '''November 21, 2024, [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 8:00 UTC|8:00 UTC]] and [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 16:00 UTC|16:00 UTC]]'''. * A [[mw:Special:MyLanguage/Wikimedia_Language_and_Product_Localization/Community meetings#29 November 2024|Language community meeting]] will take place '''November 29, 16:00 UTC''' to discuss updates and technical problem-solving. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:01, 19 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27806858 --> == Wikipedia translation of the week: 2024-48 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Wang Su-bok]]'''<br /> <small>''([[:fa:وانگ سو بوک]])&#32;([[:ko:왕수복]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Wang Su-bok''' was a singer from North Korea, who was the most popular singer in Japanese-occupied Korea in 1935. She was credited as a ground-breaking female artist, whose work led the way for the modern K-pop phenomenon. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 25 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-48 == <section begin="technews-2024-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/48|Translations]] are available. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new version of the standard wikitext editor-mode [[mw:Special:MyLanguage/Extension:CodeMirror|syntax highlighter]] will be available as a [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] later this week. This brings many new features and bug fixes, including right-to-left support, [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Template folding|template folding]], [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Autocompletion|autocompletion]], and an improved search panel. You can learn more on the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|help page]]. * The 2010 wikitext editor now supports common keyboard shortcuts such <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>B</code></bdi> for bold and <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>I</code></bdi> for italics. A full [[mw:Help:Extension:WikiEditor#Keyboard shortcuts|list of all six shortcuts]] is available. Thanks to SD0001 for this improvement. [https://phabricator.wikimedia.org/T62928] * Starting November 28, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: <bdi>bswiki</bdi>{{int:comma-separator/en}}<bdi>elwiki</bdi>{{int:comma-separator/en}}<bdi>euwiki</bdi>{{int:comma-separator/en}}<bdi>fawiki</bdi>{{int:comma-separator/en}}<bdi>fiwiki</bdi>{{int:comma-separator/en}}<bdi>frwikiquote</bdi>{{int:comma-separator/en}}<bdi>frwikisource</bdi>{{int:comma-separator/en}}<bdi>frwikiversity</bdi>{{int:comma-separator/en}}<bdi>frwikivoyage</bdi>{{int:comma-separator/en}}<bdi>idwiki</bdi>{{int:comma-separator/en}}<bdi>lvwiki</bdi>{{int:comma-separator/en}}<bdi>plwiki</bdi>{{int:comma-separator/en}}<bdi>ptwiki</bdi>{{int:comma-separator/en}}<bdi>urwiki</bdi>{{int:comma-separator/en}}<bdi>viwikisource</bdi>{{int:comma-separator/en}}<bdi>zhwikisource</bdi>. This is done as part of [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|StructuredDiscussions deprecation work]]. If you need any assistance to archive your page in advance, please contact [[m:User:Trizek (WMF)|Trizek (WMF)]]. * View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a user creating a new AbuseFilter can now only set the filter to "protected" [[phab:T377765|if it includes a protected variable]]. '''Updates for technical contributors''' * The [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]], which can be used in JavaScript, CSS, JSON, and Lua pages, [[phab:T377663|now offers]] live autocompletion. Thanks to SD0001 for this improvement. The feature can be temporarily disabled on a page by pressing <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>,</code></bdi> and un-selecting "<bdi lang="en" dir="ltr">Live Autocompletion</bdi>". * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Tool-maintainers who use the Graphite system for tracking metrics, need to migrate to the newer Prometheus system. They can check [https://grafana.wikimedia.org/d/K6DEOo5Ik/grafana-graphite-datasource-utilization?orgId=1 this dashboard] and the list in the Description of the [[phab:T350592|task T350592]] to see if their tools are listed, and they should claim metrics and dashboards connected to their tools. They can then disable or migrate all existing metrics by following the instructions in the task. The Graphite service will become read-only in April. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/KLUV4IOLRYXPQFWD6WKKJUHMWE77BMSZ/] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The [[mw:Special:MyLanguage/NewPP parser report|New PreProcessor parser performance report]] has been fixed to give an accurate count for the number of Wikibase entities accessed. It had previously been resetting after 400 entities. [https://phabricator.wikimedia.org/T279069] '''Meetings and events''' * A [[mw:Special:MyLanguage/Wikimedia_Language_and_Product_Localization/Community meetings#29 November 2024|Language community meeting]] will take place November 29 at [https://zonestamp.toolforge.org/1732896000 16:00 UTC]. There will be presentations on topics like developing language keyboards, the creation of the Mooré Wikipedia, the language support track at [[m:Wiki Indaba|Wiki Indaba]], and a report from the Wayuunaiki community on their experiences with the Incubator and as a new community over the last 3 years. This meeting will be in English and will also have Spanish interpretation. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:42, 25 November 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27847039 --> == Wikipedia translation of the week: 2024-49 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Storm Filomena]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Spain’s chilly blanket ESA22415247.jpeg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Storm Filomena''' was an extratropical cyclone in early January 2021 that was most notable for bringing unusually heavy snowfall to parts of Spain, with Madrid recording its heaviest snowfall in over a century, and with Portugal being hit less severely. The eighth named storm of the 2020–21 European windstorm season, Filomena formed over the Atlantic Ocean close to the Canary Islands on 7 January, subsequently taking a slow track north-eastwards towards the Iberian Peninsula and then eastwards across the Mediterranean Sea. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:48, 2 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-49 == <section begin="technews-2024-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/49|Translations]] are available. '''Updates for editors''' * Two new parser functions were added this week. The <code dir="ltr"><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic words#interwikilink|#interwikilink]]<nowiki>}}</nowiki></code> function adds an [[mw:Special:MyLanguage/Help:Links#Interwiki links|interwiki link]] and the <code dir="ltr"><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic words#interlanguagelink|#interlanguagelink]]<nowiki>}}</nowiki></code> function adds an [[mw:Special:MyLanguage/Help:Links#Interlanguage links|interlanguage link]]. These parser functions are useful on wikis where namespaces conflict with interwiki prefixes. For example, links beginning with <bdi lang="zxx" dir="ltr"><code>MOS:</code></bdi> on English Wikipedia [[phab:T363538|conflict with the <code>mos</code> language code prefix of Mooré Wikipedia]]. * Starting this week, Wikimedia wikis no longer support connections using old RSA-based HTTPS certificates, specifically rsa-2048. This change is to improve security for all users. Some older, unsupported browser or smartphone devices will be unable to connect; Instead, they will display a connectivity error. See the [[wikitech:HTTPS/Browser_Recommendations|HTTPS Browser Recommendations page]] for more-detailed information. All modern operating systems and browsers are always able to reach Wikimedia projects. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/CTYEHVNSXUD3NFAAMG3BLZVTVQWJXJAH/] * Starting December 16, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: <bdi>arwiki</bdi>{{int:comma-separator/en}}<bdi>cawiki</bdi>{{int:comma-separator/en}}<bdi>frwiki</bdi>{{int:comma-separator/en}}<bdi>mediawikiwiki</bdi>{{int:comma-separator/en}}<bdi>orwiki</bdi>{{int:comma-separator/en}}<bdi>wawiki</bdi>{{int:comma-separator/en}}<bdi>wawiktionary</bdi>{{int:comma-separator/en}}<bdi>wikidatawiki</bdi>{{int:comma-separator/en}}<bdi>zhwiki</bdi>. This is done as part of [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|StructuredDiscussions deprecation work]]. If you need any assistance to archive your page in advance, please contact [[m:User:Trizek (WMF)|Trizek (WMF)]]. [https://phabricator.wikimedia.org/T380910] * This month the Chart extension was deployed to production and is now available on Commons and Testwiki. With the security review complete, pilot wiki deployment is expected to start in the first week of December. You can see a working version [[testwiki:Charts|on Testwiki]] and read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|the November project update]] for more details. * View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug with the "Download as PDF" system was fixed. [https://phabricator.wikimedia.org/T376438] '''Updates for technical contributors''' * In late February, temporary accounts will be rolled out on at least 10 large wikis. This deployment will have a significant effect on the community-maintained code. This is about Toolforge tools, bots, gadgets, and user scripts that use IP address data or that are available for logged-out users. The Trust and Safety Product team wants to identify this code, monitor it, and assist in updating it ahead of the deployment to minimize disruption to workflows. The team asks technical editors and volunteer developers to help identify such tools by adding them to [[mw:Trust and Safety Product/Temporary Accounts/For developers/Impacted tools|this list]]. In addition, review the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|updated documentation]] to learn how to adjust the tools. Join the discussions on the [[mw:Talk:Trust and Safety Product/Temporary Accounts|project talk page]] or in the [[discord:channels/221049808784326656/1227616742340034722|dedicated thread]] on the [[w:Wikipedia:Discord|Wikimedia Community Discord server (in English)]] for support and to share feedback. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:23, 2 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27873992 --> == Wikipedia translation of the week: 2024-50 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Syrian literature]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Poem about Baybars page 1 from Hakawati book.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Syrian literature''' is modern fiction written or orally performed in Arabic by writers from Syria since the independence of the Syrian Arab Republic in 1946. It is part of the historically and geographically wider Arabic literature. The modern states of Syria, Lebanon, Jordan, Israel as well as the Palestinian autonomous areas only came into being in the mid-20th century. Therefore, Syrian literature has since been referred to by literary scholarship as the national literature of the Syrian Arab Republic, as well as the works created in Arabic by Syrian writers in the diaspora. This literature has been influenced by the country's political history, the literature of other Arabic-speaking countries and, especially in its early days, by French literature. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 9 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-50 == <section begin="technews-2024-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/50|Translations]] are available. '''Weekly highlight''' * Technical documentation contributors can find updated resources, and new ways to connect with each other and the Wikimedia Technical Documentation Team, at the [[mw:Special:MyLanguage/Documentation|Documentation hub]] on MediaWiki.org. This page links to: resources for writing and improving documentation, a new <bdi lang="zxx" dir="ltr">#wikimedia-techdocs</bdi> IRC channel on libera.chat, a listing of past and upcoming documentation events, and ways to request a documentation consultation or review. If you have any feedback or ideas for improvements to the documentation ecosystem, please [[mw:Wikimedia Technical Documentation Team#Contact us|contact the Technical Documentation Team]]. '''Updates for editors''' [[File:Edit Check on Desktop.png|thumb|Layout change for the Edit Check feature]] * Later this week, [[mw:Special:MyLanguage/Edit check|Edit Check]] will be relocated to a sidebar on desktop. Edit check is the feature for new editors to help them follow policies and guidelines. This layout change creates space to present people with [[mw:Edit check#1 November 2024|new Checks]] that appear ''while'' they are typing. The [[mw:Special:MyLanguage/Edit check#Reference Check A/B Test|initial results]] show newcomers encountering Edit Check are 2.2 times more likely to publish a new content edit that includes a reference and is not reverted. * The Chart extension, which enables editors to create data visualizations, was successfully made available on MediaWiki.org and three pilot wikis (Italian, Swedish, and Hebrew Wikipedias). You can see a working examples [[testwiki:Charts|on Testwiki]] and read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|the November project update]] for more details. * Translators in wikis where the [[mw:Special:MyLanguage/Content translation/Section translation#Try the tool|mobile experience of Content Translation is available]], can now discover articles in Wikiproject campaigns of their interest from the "[https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=specialcx&filter-type=automatic&filter-id=collections&active-list=suggestions&from=es&to=en All collection]" category in the articles suggestion feature. Wikiproject Campaign organizers can use this feature, to help translators to discover articles of interest, by adding the <code dir=ltr><nowiki><page-collection> </page-collection></nowiki></code> tag to their campaign article list page on Meta-wiki. This will make those articles discoverable in the Content Translation tool. For more detailed information on how to use the tool and tag, please refer to [[mw:Special:MyLanguage/Translation suggestions: Topic-based & Community-defined lists/How to use the features|the step-by-step guide]]. [https://phabricator.wikimedia.org/T378958] * The [[mw:Special:MyLanguage/Extension:Nuke|Nuke]] feature, which enables administrators to mass delete pages, now has a [[phab:T376379#10310998|multiselect filter for namespace selection]]. This enables users to select multiple specific namespaces, instead of only one or all, when fetching pages for deletion. * The Nuke feature also now [[phab:T364225#10371365|provides links]] to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions. Thanks to Chlod and the Moderator Tools team for both of these improvements. [https://phabricator.wikimedia.org/T364225#10371365] * The Editing Team is working on making it easier to populate citations from archive.org using the [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|Citoid]] tool, the auto-filled citation generator. They are asking communities to add two parameters preemptively, <code dir=ltr>archiveUrl</code> and <code dir=ltr>archiveDate</code>, within the TemplateData for each citation template using Citoid. You can see an [https://en.wikipedia.org/w/index.php?title=Template%3ACite_web%2Fdoc&diff=1261320172&oldid=1260788022 example of a change in a template], and a [https://global-search.toolforge.org/?namespaces=10&q=%5C%22citoid%5C%22%3A%20%5C%7B&regex=1&title= list of all relevant templates]. [https://phabricator.wikimedia.org/T374831] * One new wiki has been created: a {{int:project-localized-name-group-wikivoyage}} in [[d:Q9240|Indonesian]] ([[voy:id:|<code>voy:id:</code>]]) [https://phabricator.wikimedia.org/T380726] * Last week, all wikis had problems serving pages to logged-in users and some logged-out users for 30–45 minutes. This was caused by a database problem, and investigation is ongoing. [https://www.wikimediastatus.net/incidents/3g2ckc7bp6l9] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug in the [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add Link]] feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases. [https://phabricator.wikimedia.org/T380455][https://phabricator.wikimedia.org/T380329] '''Updates for technical contributors''' * [[mw:Special:MyLanguage/Codex|Codex]], the design system for Wikimedia, now has an early-stage [[gitiles:design/codex-php|implementation in PHP]]. It is available for general use in MediaWiki extensions and Toolforge apps through [https://packagist.org/packages/wikimedia/codex Composer], with use in MediaWiki core coming soon. More information is available in [[wmdoc:design-codex-php/main/index.html|the documentation]]. Thanks to Doğu for the inspiration and many contributions to the library. [https://phabricator.wikimedia.org/T379662] * [https://en.wikipedia.org/api/rest_v1/ Wikimedia REST API] users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. On December 4, the MediaWiki Interfaces team began rerouting page/revision metadata and rendered HTML content endpoints on [[testwiki:|testwiki]] from RESTbase to comparable MediaWiki REST API endpoints. The team encourages active users of these endpoints to verify their tool's behavior on testwiki and raise any concerns on the related [[phab:T374683|Phabricator ticket]] before the end of the year, as they intend to roll out the same change across all Wikimedia projects in early January. These changes are part of the work to replace the outdated [[mw:RESTBase/deprecation|RESTBase]] system. * The [https://wikimediafoundation.limesurvey.net/986172 2024 Developer Satisfaction Survey] is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 3 January 2025, and has an associated [[foundation:Legal:Developer Satisfaction Survey 2024 Privacy Statement|privacy statement]]. * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Meetings and events''' * The next meeting in the series of [[c:Commons:WMF support for Commons/Commons community calls|Wikimedia Foundation discussions with the Wikimedia Commons community]] will take place on [[m:Event:Commons community discussion - 12 December 2024 08:00 UTC|December 12 at 8:00 UTC]] and [[m:Event:Commons community discussion - 12_December 2024 16:00 UTC|at 16:00 UTC]]. The topic of this call is new media and new contributors. Contributors from all wikis are welcome to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:16, 9 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27919424 --> == Wikipedia translation of the week: 2024-51 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Mars ocean theory]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:AncientMars.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Mars ocean theory''' states that nearly a third of the surface of Mars was covered by an ocean of liquid water early in the planet's geologic history. This primordial ocean, dubbed Paleo-Ocean or Oceanus Borealis (/oʊˈsiːənəs ˌbɒriˈælɪs/ oh-SEE-ə-nəs BORR-ee-AL-iss), would have filled the basin Vastitas Borealis in the northern hemisphere, a region that lies 4–5 km (2.5–3 miles) below the mean planetary elevation, at a time period of approximately 4.1–3.8 billion years ago. Evidence for this ocean includes geographic features resembling ancient shorelines, and the chemical properties of the Martian soil and atmosphere <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:44, 16 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27933909 --> == Tech News: 2024-51 == <section begin="technews-2024-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/51|Translations]] are available. '''Weekly highlight''' * Interested in improving event management on your home wiki? The [[m:Special:MyLanguage/CampaignEvents|CampaignEvents extension]] offers organizers features like event registration management, event/wikiproject promotion, finding potential participants, and more - all directly on-wiki. If you are an organizer or think your community would benefit from this extension, start a discussion to enable it on your wiki today. To learn more about how to enable this extension on your wiki, visit the [[m:CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|deployment status page]]. '''Updates for editors''' * Users of the iOS Wikipedia App in Italy and Mexico on the Italian, Spanish, and English Wikipedias, can see a [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Personalized Wikipedia Year in Review|personalized Year in Review]] with insights based on their reading and editing history. * Users of the Android Wikipedia App in Sub-Saharan Africa and South Asia can see the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Rabbit Holes|Rabbit Holes]] feature. This feature shows a suggested search term in the Search bar based on the current article being viewed, and a suggested reading list generated from the user’s last two visited articles. * The [[m:Special:MyLanguage/Global reminder bot|global reminder bot]] is now active and running on nearly 800 wikis. This service reminds most users holding temporary rights when they are about to expire, so that they can renew should they want to. See [[m:Global reminder bot/Technical details|the technical details page]] for more information. * The next issue of Tech News will be sent out on 13 January 2025 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was [[phab:T374988|fixed]] in the Android Wikipedia App which had caused translatable SVG images to show the wrong language when they were tapped. '''Updates for technical contributors''' * There is no new MediaWiki version next week. The next deployments will start on 14 January. [https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar/2025] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:25, 16 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27942374 --> == Wikipedia translation of the week: 2024-52 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2023 Slovenia floods]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Sava v Tacnu 4. avgusta ob 16h.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> In August 2023, major floods occurred in large part of Slovenia and neighbouring areas of Austria and Croatia due to heavy rain. Amongst others, the level of rivers Sava, Mur and Drava was exceptionally high. Several settlements and transport links in Slovene Littoral, Upper Carniola and Slovenian Carinthia were flooded. Due to the amount of rain, the streams in Idrija, Cerkno and Škofja Loka Hills overflowed. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:55, 23 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27933909 --> == Wikipedia translation of the week: 2025-01 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Uganda Railways Corporation]]'''<br /> <small>''([[:de:Schienenverkehr in Uganda]])&#32;([[:no:Uganda Railways Corporation]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:9620 mit Güterzug.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Uganda Railways Corporation''' (URC) is the parastatal railway of Uganda. It was formed after the breakup of the East African Railways Corporation (EARC) in 1977 when it took over the Ugandan part of the East African railways. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:37, 30 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28019313 --> == Wikipedia translation of the week: 2025-02 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Internment of Japanese Canadians]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Japanese road camp.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> From 1942 to 1949, Canada forcibly relocated and incarcerated over 22,000 Japanese Canadians—comprising over 90% of the total Japanese Canadian population—from British Columbia in the name of "national security". The majority were Canadian citizens by birth and were targeted based on their ancestry. This decision followed the events of the Japanese Empire's war in the Pacific against the Western Allies, such as the invasion of Hong Kong, the attack on Pearl Harbor in Hawaii, and the Fall of Singapore which led to the Canadian declaration of war on Japan during World War II. Similar to the actions taken against Japanese Americans in neighbouring United States, this forced relocation subjected many Japanese Canadians to government-enforced curfews and interrogations, job and property losses, and forced repatriation to Japan <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:56, 6 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28070038 --> == Wikipedia translation of the week: 2025-03 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Christmas seals]]'''<br /> <small>''([[:no:Julemerke]])&#32;([[:ru:Рождественская виньетка]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:1915 US Christmas Seal.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Christmas seals''' are adhesive labels that are similar in appearance to postage stamps that are sold then affixed to mail during the Christmas season to raise funds and awareness for charitable programs. Christmas seals have become particularly associated with lung diseases such as tuberculosis, and with child welfare in general. They were first issued in Denmark beginning in 1904, with Sweden and Iceland following with issues that same year. Thereafter the use of Christmas seals proved to be popular and spread quickly around the world, with 130 countries producing their own issues. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 13 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28086717 --> == Tech News: 2025-03 == <section begin="technews-2025-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/03|Translations]] are available. '''Weekly highlight''' * The Single User Login system is being updated over the next few months. This is the system which allows users to fill out the login form on one Wikimedia site and get logged in on all others at the same time. It needs to be updated because of the ways that browsers are increasingly restricting cross-domain cookies. To accommodate these restrictions, login and account creation pages will move to a central domain, but it will still appear to the user as if they are on the originating wiki. The updated code will be enabled this week for users on test wikis. This change is planned to roll out to all users during February and March. See [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3#Deployment|the SUL3 project page]] for more details and a timeline. '''Updates for editors''' * On wikis with [[mw:Special:MyLanguage/Extension:PageAssessments|PageAssessments]] installed, you can now [[mw:Special:MyLanguage/Extension:PageAssessments#Search|filter search results]] to pages in a given WikiProject by using the <code dir=ltr>inproject:</code> keyword. (These wikis: {{int:project-localized-name-arwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwikivoyage/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-huwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zhwiki/en}}) [https://phabricator.wikimedia.org/T378868] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q34129|Tigre]] ([[w:tig:|<code>w:tig:</code>]]) [https://phabricator.wikimedia.org/T381377] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:35}} community-submitted {{PLURAL:35|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a bug with updating a user's edit-count after making a rollback edit, which is now fixed. [https://phabricator.wikimedia.org/T382592] '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. Starting the week of January 13, we will begin rerouting [[phab:T374683|some page content endpoints]] from RESTbase to the newer MediaWiki REST API endpoints for all wiki projects. This change was previously available on testwiki and should not affect existing functionality, but active users of the impacted endpoints may raise issues directly to the [[phab:project/view/6931/|MediaWiki Interfaces Team]] in Phabricator if they arise. * Toolforge tool maintainers can now share their feedback on Toolforge UI, an initiative to provide a web platform that allows creating and managing Toolforge tools through a graphic interface, in addition to existing command-line workflows. This project aims to streamline active maintainers’ tasks, as well as make registration and deployment processes more accessible for new tool creators. The initiative is still at a very early stage, and the Cloud Services team is in the process of collecting feedback from the Toolforge community to help shape the solution to their needs. [[wikitech:Wikimedia Cloud Services team/EnhancementProposals/Toolforge UI|Read more and share your thoughts about Toolforge UI]]. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] For tool and library developers who use the OAuth system: The identity endpoint used for [[mw:Special:MyLanguage/OAuth/For Developers#Identifying the user|OAuth 1]] and [[mw:Special:MyLanguage/OAuth/For Developers#Identifying the user 2|OAuth 2]] returned a JSON object with an integer in its <code>sub</code> field, which was incorrect (the field must always be a string). This has been fixed; the fix will be deployed to Wikimedia wikis on the week of January 13. [https://phabricator.wikimedia.org/T382139] * Many wikis currently use [[:mw:Parsoid/Parser Unification/Cite CSS|Cite CSS]] to render custom footnote markers in Parsoid output. Starting January 20 these rules will be disabled, but the developers ask you to ''not'' clean up your <bdi lang="en" dir="ltr">[[MediaWiki:Common.css]]</bdi> until February 20 to avoid issues during the migration. Your wikis might experience some small changes to footnote markers in Visual Editor and when using experimental Parsoid read mode, but if there are changes these are expected to bring the rendering in line with the legacy parser output. [https://phabricator.wikimedia.org/T370027] '''Meetings and events''' * The next meeting in the series of [[c:Special:MyLanguage/Commons:WMF support for Commons/Commons community calls|Wikimedia Foundation Community Conversations with the Wikimedia Commons community]] will take place on [[m:Special:MyLanguage/Event:Commons community discussion - 15 January 2025 08:00 UTC|January 15 at 8:00 UTC]] and [[m:Special:MyLanguage/Event:Commons community discussion - 15 January 2025 16:00 UTC|at 16:00 UTC]]. The topic of this call is defining the priorities in tool investment for Commons. Contributors from all wikis, especially users who are maintaining tools for Commons, are welcome to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:42, 14 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28048614 --> == Wikipedia translation of the week: 2025-04 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2010 Nagorno-Karabakh clashes]]'''<br /> <small>''([[:it:Scontri del Nagorno Karabakh del 2010]])&#32;([[:tr:2010 Dağlık Karabağ çatışmaları]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''2010 Nahorno karabakh war''' were a series of exchanges of gunfire that took place on February 18 on the line of contact dividing Azerbaijani and the Karabakh Armenian military forces. Azerbaijan accused the Armenian forces of firing on the Azerbaijani positions near Tap Qaraqoyunlu, Qızıloba, Qapanlı, Yusifcanlı and Cavahirli villages, as well as in uplands of Agdam Rayon with small arms fire including snipers. As a result, three Azerbaijani soldiers were killed and one wounded. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:20, 20 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28099770 --> == Tech News: 2025-04 == <section begin="technews-2025-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/04|Translations]] are available. '''Updates for editors''' * Administrators can mass-delete multiple pages created by a user or IP address using [[mw:Special:MyLanguage/Extension:Nuke|Extension:Nuke]]. It previously only allowed deletion of pages created in the last 30 days. It can now delete pages from the last 90 days, provided it is targeting a specific user or IP address. [https://phabricator.wikimedia.org/T380846] * On [[phab:P72148|wikis that use]] the [[mw:Special:MyLanguage/Help:Patrolled edits|Patrolled edits]] feature, when the rollback feature is used to revert an unpatrolled page revision, that revision will now be marked as "manually patrolled" instead of "autopatrolled", which is more accurate. Some editors that use [[mw:Special:MyLanguage/Help:New filters for edit review/Filtering|filters]] on Recent Changes may need to update their filter settings. [https://phabricator.wikimedia.org/T302140] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Visual Editor's "Insert link" feature did not always suggest existing pages properly when an editor started typing, which has now been [[phab:T383497|fixed]]. '''Updates for technical contributors''' * The Structured Discussion extension (also known as Flow) is being progressively removed from the wikis. This extension is unmaintained and causes issues. It will be replaced by [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]], which is used on any regular talk page. [[mw:Special:MyLanguage/Structured Discussions/Deprecation#Deprecation timeline|The last group of wikis]] ({{int:project-localized-name-cawikiquote/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiwikimedia/en}}{{int:comma-separator/en}}{{int:project-localized-name-gomwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kabwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwikibooks/en}}{{int:comma-separator/en}}{{int:project-localized-name-sewikimedia/en}}) will soon be contacted. If you have questions about this process, please ping [[m:User:Trizek (WMF)|Trizek (WMF)]] at your wiki. [https://phabricator.wikimedia.org/T380912] * The latest quarterly [[mw:Technical_Community_Newsletter/2025/January|Technical Community Newsletter]] is now available. This edition includes: updates about services from the Data Platform Engineering teams, information about Codex from the Design System team, and more. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:37, 21 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28129769 --> == Wikipedia translation of the week: 2025-05 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Jinnah's birthday]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Yorkstatue.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Jinnah's Birthday''', officially Quaid-e-Azam Day and sometimes known as Quaid Day, is a public holiday in Pakistan observed annually on 25 December to celebrate the birthday of the founder of Pakistan, Muhammad Ali Jinnah, known as Quaid-i-Azam ("Great Leader"). A major holiday, commemorations for Jinnah began during his lifetime in 1942, and have continued ever since. The event is primarily observed by the government and the citizens of the country where the national flag is hoisted at major architectural structures such as private and public buildings, particularly at the top of Quaid-e-Azam House in Karachi. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:30, 27 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28156501 --> == Tech News: 2025-05 == <section begin="technews-2025-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/05|Translations]] are available. '''Weekly highlight''' * Patrollers and admins - what information or context about edits or users could help you to make patroller or admin decisions more quickly or easily? The Wikimedia Foundation wants to hear from you to help guide its upcoming annual plan. Please consider sharing your thoughts on this and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|13 other questions]] to shape the technical direction for next year. '''Updates for editors''' * iOS Wikipedia App users worldwide can now access a [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Personalized Wikipedia Year in Review/How your data is used|personalized Year in Review]] feature, which provides insights based on their reading and editing history on Wikipedia. This project is part of a broader effort to help welcome new readers as they discover and interact with encyclopedic content. * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Edit patrollers now have a new feature available that can highlight potentially problematic new pages. When a page is created with the same title as a page which was previously deleted, a tag ('Recreated') will now be added, which users can filter for in [[{{#special:RecentChanges}}]] and [[{{#special:NewPages}}]]. [https://phabricator.wikimedia.org/T56145] * Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (a [[mw:Special:MyLanguage/Help:Redirects#Double redirects|double redirect]]). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement. [https://phabricator.wikimedia.org/T326056] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia wikis allow [[w:en:WebAuthn|WebAuthn]]-based second factor checks (such as hardware tokens) during login, but the feature is [[m:Community Wishlist Survey 2023/Miscellaneous/Fix security key (WebAuthn) support|fragile]] and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout of [[mw:MediaWiki Platform Team/SUL3|SUL3]] (single user login version 3). Existing keys are unaffected. [https://phabricator.wikimedia.org/T378402] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * For developers that use the [[wikitech:Data Platform/Data Lake/Edits/MediaWiki history dumps|MediaWiki History dumps]]: The Data Platform Engineering team has added a couple of new fields to these dumps, to support the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] initiative. If you maintain software that reads those dumps, please review your code and the updated documentation, since the order of the fields in the row will change. There will also be one field rename: in the <bdi lang="zxx" dir="ltr"><code>mediawiki_user_history</code></bdi> dump, the <bdi lang="zxx" dir="ltr"><code>anonymous</code></bdi> field will be renamed to <bdi lang="zxx" dir="ltr"><code>is_anonymous</code></bdi>. The changes will take effect with the next release of the dumps in February. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/LKMFDS62TXGDN6L56F4ABXYLN7CSCQDI/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:15, 27 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28149374 --> == Wikipedia translation of the week: 2025-06 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:French conquest of Corsica]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Bataille de Ponte Novu.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''French conquest of Corsica''' was a successful expedition by French forces of the Kingdom of France under Comte de Vaux, against Corsican forces under Pasquale Paoli of the Corsican Republic. The expedition was launched in May 1768, in the aftermath of the Seven Years' War. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:20, 3 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28200320 --> == Tech News: 2025-06 == <section begin="technews-2025-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/06|Translations]] are available. '''Updates for editors''' * Editors who use the "Special characters" editing-toolbar menu can now see the 32 special characters you have used most recently, across editing sessions on that wiki. This change should help make it easier to find the characters you use most often. The feature is in both the 2010 wikitext editor and VisualEditor. [https://phabricator.wikimedia.org/T110722] * Editors using the 2010 wikitext editor can now create sublists with correct indentation by selecting the line(s) you want to indent and then clicking the toolbar buttons.[https://phabricator.wikimedia.org/T380438] You can now also insert <code><nowiki><code></nowiki></code> tags using a new toolbar button.[https://phabricator.wikimedia.org/T383010] Thanks to user stjn for these improvements. * Help is needed to ensure the [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|citation generator]] works properly on each wiki. ** (1) Administrators should update the local versions of the page <code dir=ltr>MediaWiki:Citoid-template-type-map.json</code> to include entries for <code dir=ltr>preprint</code>, <code dir=ltr>standard</code>, and <code dir=ltr>dataset</code>; Here are example diffs to replicate [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&diff=1189164774&oldid=1165783565 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&diff=1270832208&oldid=1270828390 for 'standard' and 'dataset']. ** (2.1) If the citoid map in the citation template used for these types of references is missing, [[mediawikiwiki:Citoid/Enabling Citoid on your wiki#Step 2.a: Create a 'citoid' maps value for each citation template|one will need to be added]]. (2.2) If the citoid map does exist, the TemplateData will need to be updated to include new field names. Here are example updates [https://en.wikipedia.org/w/index.php?title=Template%3ACitation%2Fdoc&diff=1270829051&oldid=1262470053 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=Template%3ACitation%2Fdoc&diff=1270831369&oldid=1270829480 for 'standard' and 'dataset']. The new fields that may need to be supported are <code dir=ltr>archiveID</code>, <code dir=ltr>identifier</code>, <code dir=ltr>repository</code>, <code dir=ltr>organization</code>, <code dir=ltr>repositoryLocation</code>, <code dir=ltr>committee</code>, and <code dir=ltr>versionNumber</code>. [https://phabricator.wikimedia.org/T383666] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q15637215|Central Kanuri]] ([[w:knc:|<code>w:knc:</code>]]) [https://phabricator.wikimedia.org/T385181] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[mediawikiwiki:Special:MyLanguage/Help:Extension:Wikisource/Wikimedia OCR|OCR (optical character recognition) tool]] used for Wikisource now supports a new language, Church Slavonic. [https://phabricator.wikimedia.org/T384782] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:09, 4 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28203495 --> == Wikipedia translation of the week: 2025-07 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Assassination of Spencer Perceval]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:PercevalShooting.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> On 11 May 1812, at about 5:15 pm, Spencer Perceval, the prime minister of the United Kingdom of Great Britain and Ireland, was shot dead in the lobby of the House of Commons by John Bellingham, a Liverpool merchant with a grievance against the government. Bellingham was detained; four days after the murder, he was tried, convicted and sentenced to death. He was hanged at Newgate Prison on 18 May, one week after the assassination and one month before the start of the War of 1812. Perceval remains the sole British prime minister to have been assassinated. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 10 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28200320 --> == Tech News: 2025-07 == <section begin="technews-2025-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/07|Translations]] are available. '''Weekly highlight''' * The Product and Technology Advisory Council (PTAC) has published [[m:Special:MyLanguage/Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback|a draft of their recommendations]] for the Wikimedia Foundation's Product and Technology department. They have recommended focusing on [[m:Special:MyLanguage/Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback/Mobile experiences|mobile experiences]], particularly contributions. They request community [[m:Talk:Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback|feedback at the talk page]] by 21 February. '''Updates for editors''' * The "Special pages" portlet link will be moved from the "Toolbox" into the "Navigation" section of the main menu's sidebar by default. This change is because the Toolbox is intended for tools relating to the current page, not tools relating to the site, so the link will be more logically and consistently located. To modify this behavior and update CSS styling, administrators can follow the instructions at [[phab:T385346|T385346]]. [https://phabricator.wikimedia.org/T333211] * As part of this year's work around improving the ways readers discover content on the wikis, the Web team will be running an experiment with a small number of readers that displays some suggestions for related or interesting articles within the search bar. Please check out [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments#Experiment 1: Display article recommendations in more prominent locations, search|the project page]] for more information. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Template editors who use TemplateStyles can now customize output for users with specific accessibility needs by using accessibility related media queries (<code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion prefers-reduced-motion]</code>, <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-transparency prefers-reduced-transparency]</code>, <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-contrast prefers-contrast]</code>, and <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/forced-colors forced-colors]</code>). Thanks to user Bawolff for these improvements. [https://phabricator.wikimedia.org/T384175] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:22}} community-submitted {{PLURAL:22|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the global blocks log will now be shown directly on the {{#special:CentralAuth}} page, similarly to global locks, to simplify the workflows for stewards. [https://phabricator.wikimedia.org/T377024] '''Updates for technical contributors''' * Wikidata [[d:Special:MyLanguage/Help:Default values for labels and aliases|now supports a special language as a "default for all languages"]] for labels and aliases. This is to avoid excessive duplication of the same information across many languages. If your Wikidata queries use labels, you may need to update them as some existing labels are getting removed. [https://phabricator.wikimedia.org/T312511] * The function <code dir="ltr">getDescription</code> was invoked on every Wiki page read and accounts for ~2.5% of a page's total load time. The calculated value will now be cached, reducing load on Wikimedia servers. [https://phabricator.wikimedia.org/T383660] * As part of the RESTBase deprecation [[mw:RESTBase/deprecation|effort]], the <code dir="ltr">/page/related</code> endpoint has been blocked as of February 6, 2025, and will be removed soon. This timeline was chosen to align with the deprecation schedules for older Android and iOS versions. The stable alternative is the "<code dir="ltr">morelike</code>" action API in MediaWiki, and [[gerrit:c/mediawiki/services/mobileapps/+/982154/13/pagelib/src/transform/FooterReadMore.js|a migration example]] is available. The MediaWiki Interfaces team [[phab:T376297|can be contacted]] for any questions. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/GFC2IJO7L4BWO3YTM7C5HF4MCCBE2RJ2/] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/January|Language and Internationalization newsletter]] is available. It includes: Updates about the "Contribute" menu; details on some of the newest language editions of Wikipedia; details on new languages supported by the MediaWiki interface; updates on the Community-defined lists feature; and more. * The latest [[mw:Extension:Chart/Project/Updates#January 2025: Better visibility into charts and tabular data usage|Chart Project newsletter]] is available. It includes updates on the progress towards bringing better visibility into global charts usage and support for categorizing pages in the Data namespace on Commons. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:12, 11 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28231022 --> == Wikipedia translation of the week: 2025-08 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2010 Malagasy constitutional referendum]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A constitutional referendum was held in Madagascar on 17 November 2010, in which voters approved a proposal for the state's fourth Constitution. The Malagasy people were asked to answer "Yes" or "No" to the proposed new constitution, which was considered to help consolidate Andry Rajoelina's grip on power. At the time of the referendum, Rajoelina headed the governing Highest Transitional Authority (HAT), an interim junta established following the military-backed coup d'état against then President Marc Ravalomanana in March 2009. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:21, 17 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28245290 --> == Tech News: 2025-08 == <section begin="technews-2025-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/08|Translations]] are available. '''Weekly highlight''' * Communities using growth tools can now showcase one event on the <code>{{#special:Homepage}}</code> for newcomers. This feature will help newcomers to be informed about editing activities they can participate in. Administrators can create a new event to showcase at <code>{{#special:CommunityConfiguration}}</code>. To learn more about this feature, please read [[diffblog:2025/02/12/community-updates-module-connecting-newcomers-to-your-initiatives/|the Diff post]], have a look [[mw:Special:MyLanguage/Help:Growth/Tools/Community updates module|at the documentation]], or contact [[mw:Talk:Growth|the Growth team]]. '''Updates for editors''' [[File:Page Frame Features on desktop.png|thumb|Highlighted talk pages improvements]] * Starting next week, talk pages at these wikis – {{int:project-localized-name-eswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jawiki/en}} – will get [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|a new design]]. This change was extensively tested as a Beta feature and is the last step of [[mw:Special:MyLanguage/Talk pages project/Feature summary|talk pages improvements]]. [https://phabricator.wikimedia.org/T379102] * You can now navigate to view a redirect page directly from its action pages, such as the history page. Previously, you were forced to first go to the redirect target. This change should help editors who work with redirects a lot. Thanks to user stjn for this improvement. [https://phabricator.wikimedia.org/T5324] * When a Cite reference is reused many times, wikis currently show either numbers like "1.23" or localized alphabetic markers like "a b c" in the reference list. Previously, if there were so many reuses that the alphabetic markers were all used, [[MediaWiki:Cite error references no backlink label|an error message]] was displayed. As part of the work to [[phab:T383036|modernize Cite customization]], these errors will no longer be shown and instead the backlinks will fall back to showing numeric markers like "1.23" once the alphabetic markers are all used. * The log entries for each change to an editor's user-groups are now clearer by specifying exactly what has changed, instead of the plain before and after listings. Translators can [[phab:T369466|help to update the localized versions]]. Thanks to user Msz2001 for these improvements. * A new filter has been added to the [[{{#special:Nuke}}]] tool, which allows administrators to mass delete pages, to enable users to filter for pages in a range of page sizes (in bytes). This allows, for example, deleting pages only of a certain size or below. [https://phabricator.wikimedia.org/T378488] * Non-administrators can now check which pages are able to be deleted using the [[{{#special:Nuke}}]] tool. Thanks to user MolecularPilot for this and the previous improvements. [https://phabricator.wikimedia.org/T376378] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed in the configuration for the AV1 video file format, which enables these files to play again. [https://phabricator.wikimedia.org/T382193] '''Updates for technical contributors''' * Parsoid Read Views is going to be rolling out to most Wiktionaries over the next few weeks, following the successful transition of Wikivoyage to Parsoid Read Views last year. For more information, see the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parsoid/Parser Unification]] project page. [https://phabricator.wikimedia.org/T385923][https://phabricator.wikimedia.org/T371640] * Developers of tools that run on-wiki should note that <code dir=ltr>mw.Uri</code> is deprecated. Tools requiring <code dir=ltr>mw.Uri</code> must explicitly declare <code dir=ltr>mediawiki.Uri</code> as a ResourceLoader dependency, and should migrate to the browser native <code dir=ltr>URL</code> API soon. [https://phabricator.wikimedia.org/T384515] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:17, 17 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28275610 --> == Wikipedia translation of the week: 2025-09 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cooler Heads Coalition]]'''<br /> <small>''([[:de:Cooler Heads Coalition]])&#32;([[:fr:Cooler Heads Coalition]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Cooler Heads Coalition''' is a politically conservative "informal and ad-hoc group" in the United States, financed and operated by the Competitive Enterprise Institute. The group, which rejects the scientific consensus on climate change, made efforts to stop the government from addressing climate change. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 24 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28300238 --> == Tech News: 2025-09 == <section begin="technews-2025-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/09|Translations]] are available. '''Updates for editors''' * Administrators can now customize how the [[m:Special:MyLanguage/User language|Babel feature]] creates categories using [[{{#special:CommunityConfiguration/Babel}}]]. They can rename language categories, choose whether they should be auto-created, and adjust other settings. [https://phabricator.wikimedia.org/T374348] * The <bdi lang="en" dir="ltr">[https://www.wikimedia.org/ wikimedia.org]</bdi> portal has been updated – and is receiving some ongoing improvements – to modernize and improve the accessibility of our portal pages. It now has better support for mobile layouts, updated wording and links, and better language support. Additionally, all of the Wikimedia project portals, such as <bdi lang="en" dir="ltr">[https://wikibooks.org wikibooks.org]</bdi>, now support dark mode when a reader is using that system setting. [https://phabricator.wikimedia.org/T373204][https://phabricator.wikimedia.org/T368221][https://meta.wikimedia.org/wiki/Project_portals] * One new wiki has been created: a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q33965|Santali]] ([[wikt:sat:|<code>wikt:sat:</code>]]) [https://phabricator.wikimedia.org/T386619] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that prevented clicking on search results in the web-interface for some Firefox for Android phone configurations. [https://phabricator.wikimedia.org/T381289] '''Meetings and events''' * The next Language Community Meeting is happening soon, February 28th at [https://zonestamp.toolforge.org/1740751200 14:00 UTC]. This week's meeting will cover: highlights and technical updates on keyboard and tools for the Sámi languages, Translatewiki.net contributions from the Bahasa Lampung community in Indonesia, and technical Q&A. If you'd like to join, simply [[mw:Wikimedia Language and Product Localization/Community meetings#28 February 2025|sign up on the wiki page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:42, 25 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28296129 --> == Wikipedia translation of the week: 2025-10 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:pt:Transmissor de Ondas]]'''<br /> <small>''([[:en:Wave Transmitter]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Esq eletr transm ondas color.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Transmissor de Ondas''' é um equipamento precursor do rádio, desenvolvido por Roberto Landell de Moura na década de 1890, capaz de transmitir áudio via ondas eletromagnéticas, com sua primeira demonstração pública documentada tendo ocorrido no dia 16 de julho de 1899. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:49, 3 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28317097 --> == Tech News: 2025-10 == <section begin="technews-2025-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/10|Translations]] are available. '''Updates for editors''' * All logged-in editors using the mobile view can now edit a full page. The "{{int:Minerva-page-actions-editfull}}" link is accessible from the "{{int:minerva-page-actions-overflow}}" menu in the toolbar. This was previously only available to editors using the [[mw:Special:MyLanguage/Reading/Web/Advanced mobile contributions|Advanced mobile contributions]] setting. [https://phabricator.wikimedia.org/T387180] * Interface administrators can now help to remove the deprecated Cite CSS code matching "<code dir="ltr">mw-ref</code>" from their local <bdi lang="en" dir="ltr">[[MediaWiki:Common.css]]</bdi>. The list of wikis in need of cleanup, and the code to remove, [https://global-search.toolforge.org/?q=mw-ref%5B%5E-a-z%5D&regex=1&namespaces=8&title=.*css can be found with this global search] and in [https://ace.wikipedia.org/w/index.php?title=MediaWiki:Common.css&oldid=145662#L-139--L-144 this example], and you can learn more about how to help on the [[mw:Parsoid/Parser Unification/Cite CSS|CSS migration project page]]. The Cite footnote markers ("<code dir="ltr">[1]</code>") are now rendered by [[mw:Special:MyLanguage/Parsoid|Parsoid]], and the deprecated CSS is no longer needed. The CSS for backlinks ("<code dir="ltr">mw:referencedBy</code>") should remain in place for now. This cleanup is expected to cause no visible changes for readers. Please help to remove this code before March 20, after which the development team will do it for you. * When editors embed a file (e.g. <code><nowiki>[[File:MediaWiki.png]]</nowiki></code>) on a page that is protected with cascading protection, the software will no longer restrict edits to the file description page, only to new file uploads.[https://phabricator.wikimedia.org/T24521] In contrast, transcluding a file description page (e.g. <code><nowiki>{{:File:MediaWiki.png}}</nowiki></code>) will now restrict edits to the page.[https://phabricator.wikimedia.org/T62109] * When editors revert a file to an earlier version it will now require the same permissions as ordinarily uploading a new version of the file. The software now checks for 'reupload' or 'reupload-own' rights,[https://phabricator.wikimedia.org/T304474] and respects cascading protection.[https://phabricator.wikimedia.org/T140010] * When administrators are listing pages for deletion with the Nuke tool, they can now also list associated talk pages and redirects for deletion, alongside pages created by the target, rather than needing to manually delete these pages afterwards. [https://phabricator.wikimedia.org/T95797] * The [[m:Special:MyLanguage/Tech/News/2025/03|previously noted]] update to Single User Login, which will accommodate browser restrictions on cross-domain cookies by moving login and account creation to a central domain, will now roll out to all users during March and April. The team plans to enable it for all new account creation on [[wikitech:Deployments/Train#Tuesday|Group0]] wikis this week. See [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3#Deployment|the SUL3 project page]] for more details and an updated timeline. * Since last week there has been a bug that shows some interface icons as black squares until the page has fully loaded. It will be fixed this week. [https://phabricator.wikimedia.org/T387351] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q2044560|Sylheti]] ([[w:syl:|<code>w:syl:</code>]]) [https://phabricator.wikimedia.org/T386441] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed with loading images in very old versions of the Firefox browser on mobile. [https://phabricator.wikimedia.org/T386400] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.19|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:31, 4 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28334563 --> == Wikipedia translation of the week: 2025-11 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Smoky (mascotte olimpica)]]'''<br /> <small>''([[:en:Smoky (Olympic mascot)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Smoky 1932 Olympic Village Mascot.webp|center|300px]] <div style="text-align:left; padding: .4em;"> '''Smoky''' (Los Angeles, 1931 o 1932 - Los Angeles, aprile 1934), occasionalmente scritto Smokey, è stato un cane che divenne la mascotte del villaggio olimpico estivo del 1932 e, successivamente, dell'evento generale. Pur non essendo oggi riconosciuto dal CIO, è stato, seppur non in modo ufficiale, la prima mascotte olimpica dei Giochi, oltre che a essere attualmente l'unica a essere stata un animale vero. Le successive edizioni non ebbero mascotte, dovendo aspettare i X Giochi olimpici invernali di Grenoble nel 1968 per ritrovarne una ufficialmente riconosciuta, lo sciatore stilizzato Schuss, allora non considerato ufficiale ma successivamente riconosciuto come tale. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:50, 10 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28317097 --> == Tech News: 2025-11 == <section begin="technews-2025-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/11|Translations]] are available. '''Updates for editors''' * Editors who use password managers at multiple wikis may notice changes in the future. The way that our wikis provide information to password managers about reusing passwords across domains has recently been updated, so some password managers might now offer you login credentials that you saved for a different Wikimedia site. Some password managers already did this, and are now doing it for more Wikimedia domains. This is part of the [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3|SUL3 project]] which aims to improve how our unified login works, and to keep it compatible with ongoing changes to the web-browsers we use. [https://phabricator.wikimedia.org/T385520][https://phabricator.wikimedia.org/T384844] * The Wikipedia Apps Team is inviting interested users to help improve Wikipedia’s offline and limited internet use. After discussions in [[m:Afrika Baraza|Afrika Baraza]] and the last [[m:Special:MyLanguage/ESEAP Hub/Meetings|ESEAP call]], key challenges like search, editing, and offline access are being explored, with upcoming focus groups to dive deeper into these topics. All languages are welcome, and interpretation will be available. Want to share your thoughts? [[mw:Special:MyLanguage/Wikimedia Apps/Improving Wikipedia Mobile Apps for Offline & Limited Internet Use|Join the discussion]] or email <bdi lang="en" dir="ltr">aramadan@wikimedia.org</bdi>! * All wikis will be read-only for a few minutes on March 19. This is planned at [https://zonestamp.toolforge.org/1742392800 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.20|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/33|Growth newsletter]] is available. It includes: the launch of the Community Updates module, the most recent changes in Community Configuration, and the upcoming test of in-article suggestions for first-time editors. * An old API that was previously used in the Android Wikipedia app is being removed at the end of March. There are no current software uses, but users of the app with a version that is older than 6 months by the time of removal (2025-03-31), will no longer have access to the Suggested Edits feature, until they update their app. You can [[diffblog:2025/02/24/sunset-of-wikimedia-recommendation-api/|read more details about this change]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:10, 10 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28372257 --> == Wikipedia translation of the week: 2025-12 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Amazonas, o maior rio do mundo]]'''<br /> <small>''([[:pt:Amazonas, o maior rio do mundo]])&#32;([[:es:Amazonas, o maior rio do mundo]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Frame A from Amazonas, o maior rio do mundo.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''''Amazonas, o maior rio do mundo''''' (lit. 'Amazon: The Greatest River in the World') is a 1922 Brazilian silent documentary film produced in 1918 by Silvino Santos. It is a black-and-white film that portrays life in the Amazon rainforest. Completed in 1920, it is considered one of the oldest cinematic records of the Amazon. It was presumed lost in 1931 and only rediscovered in 2023 at the Czech Film Archive. Silvino Santos produced the work over three years using sophisticated cinematic techniques, which led it to be deemed of "immense artistic value" by Le Monde. It has also been described as the "Holy Grail of Brazilian silent cinema" by The Guardian. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 17 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28392163 --> == Tech News: 2025-12 == <section begin="technews-2025-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/12|Translations]] are available. '''Weekly highlight''' * Twice a year, around the equinoxes, the Wikimedia Foundation's Site Reliability Engineering (SRE) team performs [[m:Special:MyLanguage/Tech/Server switch|a datacenter server switchover]], redirecting all traffic from one primary server to its backup. This provides reliability in case of a crisis, as we can always fall back on the other datacenter. [http://listen.hatnote.com/ Thanks to the Listen to Wikipedia] tool, you can hear the switchover take place: Before it begins, you'll hear the steady stream of edits; Then, as the system enters a brief read-only phase, the sound stops for a couple of minutes, before resuming after the switchover. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the background and details of this process on the Diff blog]]. If you want to keep an ear out for the next server switchover, listen to the wikis on [https://zonestamp.toolforge.org/1742392800 March 19 at 14:00 UTC]. '''Updates for editors''' * The [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en&to=es improved Content Translation tool dashboard] is now available in [[phab:T387820|10 Wikipedias]] and will be available for all Wikipedias [[phab:T387821|soon]]. With [[mw:Special:MyLanguage/Content translation#Improved translation experience|the unified dashboard]], desktop users can now: Translate new sections of an article; Discover and access topic-based [https://ig.m.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions&from=en&to=ig&filter-type=automatic&filter-id=previous-edits article suggestion filters] (initially available only for mobile device users); Discover and access the [[mw:Special:MyLanguage/Translation suggestions: Topic-based & Community-defined lists|Community-defined lists]] filter, also known as "Collections", from wiki-projects and campaigns. * On Wikimedia Commons, a [[c:Commons:WMF support for Commons/Upload Wizard Improvements#Improve category selection|new system to select the appropriate file categories]] has been introduced: if a category has one or more subcategories, users will be able to click on an arrow that will open the subcategories directly within the form, and choose the correct one. The parent category name will always be shown on top, and it will always be possible to come back to it. This should decrease the amount of work for volunteers in fixing/creating new categories. The change is also available on mobile. These changes are part of planned improvements to the UploadWizard. * The Community Tech team is seeking wikis to join a pilot for the [[m:Special:MyLanguage/Community Wishlist Survey 2023/Multiblocks|Multiblocks]] feature and a refreshed Special:Block page in late March. Multiblocks enables administrators to impose multiple different types of blocks on the same user at the same time. If you are an admin or steward and would like us to discuss joining the pilot with your community, please leave a message on the [[m:Talk:Community Wishlist Survey 2023/Multiblocks|project talk page]]. * Starting March 25, the Editing team will test a new feature for Edit Check at [[phab:T384372|12 Wikipedias]]: [[mw:Special:MyLanguage/Help:Edit check#Multi-check|Multi-Check]]. Half of the newcomers on these wikis will see all [[mw:Special:MyLanguage/Help:Edit check#ref|Reference Checks]] during their edit session, while the other half will continue seeing only one. The goal of this test is to see if users are confused or discouraged when shown multiple Reference Checks (when relevant) within a single editing session. At these wikis, the tags used on edits that show References Check will be simplified, as multiple tags could be shown within a single edit. Changes to the tags are documented [[phab:T373949|on Phabricator]]. [https://phabricator.wikimedia.org/T379131] * The [[m:Special:MyLanguage/Global reminder bot|Global reminder bot]], which is a service for notifying users that their temporary user-rights are about to expire, now supports using the localized name of the user-rights group in the message heading. Translators can see the [[m:Global reminder bot/Translation|listing of existing translations and documentation]] to check if their language needs updating or creation. * The [[Special:GlobalPreferences|GlobalPreferences]] gender setting, which is used for how the software should refer to you in interface messages, now works as expected by overriding the local defaults. [https://phabricator.wikimedia.org/T386584] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:26}} community-submitted {{PLURAL:26|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Wikipedia App for Android had a bug fixed for when a user is browsing and searching in multiple languages. [https://phabricator.wikimedia.org/T379777] '''Updates for technical contributors''' * Later this week, the way that Codex styles are loaded will be changing. There is a small risk that this may result in unstyled interface message boxes on certain pages. User generated content (e.g. templates) is not impacted. Gadgets may be impacted. If you see any issues [[phab:T388847|please report them]]. See the linked task for details, screenshots, and documentation on how to fix any affected gadgets. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.21|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:48, 17 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28412594 --> == Wikipedia translation of the week: 2025-13 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ali of the Eretnids]]'''<br /> <small>''([[:tr:Alaaddin Ali Bey]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Ala al-Din Ali''' (January 1353 – August 1380) was the third Sultan of the Eretnids ruling from 1366 until his death. He inherited the throne at a very early age and was removed from administrative matters. He was characterized as particularly keen on personal pleasures, which later discredited his authority. During his rule, emirs under the Eretnids enjoyed considerable autonomy, and the state continued to shrink as neighboring powers captured several towns. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 24 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28433698 --> == Tech News: 2025-13 == <section begin="technews-2025-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/13|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation is seeking your feedback on the [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|drafts of the objectives and key results that will shape the Foundation's Product and Technology priorities]] for the next fiscal year (starting in July). The objectives are broad high-level areas, and the key-results are measurable ways to track the success of their objectives. Please share your feedback on the talkpage, in any language, ideally before the end of April. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] will be released to multiple wikis (see [[m:Special:MyLanguage/CampaignEvents/Deployment status#Global Deployment Plan|deployment plan]] for details) in April 2025, and the team has begun the process of engaging communities on the identified wikis. The extension provides tools to organize, manage, and promote collaborative activities (like events, edit-a-thons, and WikiProjects) on the wikis. The extension has three tools: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Special:MyLanguage/Campaigns/Foundation Product Team/Invitation list|Invitation Lists]]. It is currently on 13 Wikipedias, including English Wikipedia, French Wikipedia, and Spanish Wikipedia, as well as Wikidata. Questions or requests can be directed to the [[mw:Help talk:Extension:CampaignEvents|extension talk page]] or in Phabricator (with <bdi lang="en" dir="ltr" style="white-space: nowrap;">#campaigns-product-team</bdi> tag). * Starting the week of March 31st, wikis will be able to set which user groups can view private registrants in [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], as part of the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents]] extension. By default, event organizers and the local wiki admins will be able to see private registrants. This is a change from the current behavior, in which only event organizers can see private registrants. Wikis can change the default setup by [[m:Special:MyLanguage/Requesting wiki configuration changes|requesting a configuration change]] in Phabricator (and adding the <bdi lang="en" dir="ltr" style="white-space: nowrap;">#campaigns-product-team</bdi> tag). Participants of past events can cancel their registration at any time. * Administrators at wikis that have a customized <bdi lang="en" dir="ltr">[[MediaWiki:Sidebar]]</bdi> should check that it contains an entry for the {{int:specialpages}} listing. If it does not, they should add it using <code dir=ltr style="white-space: nowrap;">* specialpages-url|specialpages</code>. Wikis with a default sidebar will see the link moved from the page toolbox into the sidebar menu in April. [https://phabricator.wikimedia.org/T388927] * The Minerva skin (mobile web) combines both Notice and Alert notifications within the bell icon ([[File:OOjs UI icon bell.svg|16px|link=|class=skin-invert]]). There was a long-standing bug where an indication for new notifications was only shown if you had unseen Alerts. This bug is now fixed. In the future, Minerva users will notice a counter atop the bell icon when you have 1 or more unseen Notices and/or Alerts. [https://phabricator.wikimedia.org/T344029] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * VisualEditor has introduced a [[mw:VisualEditor/Hooks|new client-side hook]] for developers to use when integrating with the VisualEditor target lifecycle. This hook should replace the existing lifecycle-related hooks, and be more consistent between different platforms. In addition, the new hook will apply to uses of VisualEditor outside of just full article editing, allowing gadgets to interact with the editor in DiscussionTools as well. The Editing Team intends to deprecate and eventually remove the old lifecycle hooks, so any use cases that this new hook does not cover would be of interest to them and can be [[phab:T355555|shared in the task]]. * Developers who use the <code dir=ltr>mw.Api</code> JavaScript library, can now identify the tool using it with the <code dir=ltr>userAgent</code> parameter: <code dir=ltr>var api = new mw.Api( { userAgent: 'GadgetNameHere/1.0.1' } );</code>. If you maintain a gadget or user script, please set a user agent, because it helps with library and server maintenance and with differentiating between legitimate and illegitimate traffic. [https://phabricator.wikimedia.org/T373874][https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:43, 24 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28443127 --> == Wikipedia translation of the week: 2025-14 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Chilembwe uprising]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Chilembwe supporters being led to be executed (cropped).jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Chilembwe uprising''' was a rebellion against British colonial rule in Nyasaland (modern-day Malawi) which took place in January 1915. It was led by John Chilembwe, an American-educated Baptist minister. Based around his church in the village of Mbombwe in the south-east of the colony, the leaders of the revolt were mainly from an emerging black middle class. They were motivated by grievances against the British colonial system, which included forced labour, racial discrimination and new demands imposed on the African population following the outbreak of World War I. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:52, 31 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-14 == <section begin="technews-2025-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/14|Translations]] are available. '''Updates for editors''' * The Editing team is working on a new [[mw:Special:MyLanguage/Edit Check|Edit check]]: [[mw:Special:MyLanguage/Edit check#26 March 2025|Peacock check]]. This check's goal is to identify non-neutral terms while a user is editing a wikipage, so that they can be informed that their edit should perhaps be changed before they publish it. This project is at the early stages, and the team is looking for communities' input: [[phab:T389445|in this Phabricator task]], they are gathering on-wiki policies, templates used to tag non-neutral articles, and the terms (jargon and keywords) used in edit summaries for the languages they are currently researching. You can participate by editing the table on Phabricator, commenting on the task, or directly messaging [[m:user:Trizek (WMF)|Trizek (WMF)]]. * [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3|Single User Login]] has now been updated on all wikis to move login and account creation to a central domain. This makes user login compatible with browser restrictions on cross-domain cookies, which have prevented users of some browsers from staying logged in. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:35}} community-submitted {{PLURAL:35|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Starting on March 31st, the MediaWiki Interfaces team will begin a limited release of generated OpenAPI specs and a SwaggerUI-based sandbox experience for [[mw:Special:MyLanguage/API:REST API|MediaWiki REST APIs]]. They invite developers from a limited group of non-English Wikipedia communities (Arabic, German, French, Hebrew, Interlingua, Dutch, Chinese) to review the documentation and experiment with the sandbox in their preferred language. In addition to these specific Wikipedia projects, the sandbox and OpenAPI spec will be available on the [[testwiki:Special:RestSandbox|on the test wiki REST Sandbox special page]] for developers with English as their preferred language. During the preview period, the MediaWiki Interfaces Team also invites developers to [[mw:MediaWiki Interfaces Team/Feature Feedback/REST Sandbox|share feedback about your experience]]. The preview will last for approximately 2 weeks, after which the sandbox and OpenAPI specs will be made available across all wiki projects. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.23|MediaWiki]] '''In depth''' * Sometimes a small, [[gerrit:c/operations/cookbooks/+/1129184|one line code change]] can have great significance: in this case, it means that for the first time in years we're able to run all of the stack serving <bdi lang="en" dir="ltr">[http://maps.wikimedia.org/ maps.wikimedia.org]</bdi> - a host dedicated to serving our wikis and their multi-lingual maps needs - from a single core datacenter, something we test every time we perform a [[m:Special:MyLanguage/Tech/Server switch|datacenter switchover]]. This is important because it means that in case one of our datacenters is affected by a catastrophe, we'll still be able to serve the site. This change is the result of [[phab:T216826|extensive work]] by two developers on porting the last component of the maps stack over to [[w:en:Kubernetes|kubernetes]], where we can allocate resources more efficiently than before, thus we're able to withstand more traffic in a single datacenter. This work involved a lot of complicated steps because this software, and the software libraries it uses, required many long overdue upgrades. This type of work makes the Wikimedia infrastructure more sustainable. '''Meetings and events''' * [[mw:Special:MyLanguage/MediaWiki Users and Developers Workshop Spring 2025|MediaWiki Users and Developers Workshop Spring 2025]] is happening in Sandusky, USA, and online, from 14–16 May 2025. The workshop will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. Registration and presentation signup is now available at the workshop's website. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 1 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28473566 --> == Wikipedia translation of the week: 2025-15 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:1930 Bago earthquake]]'''<br /> <small>''([[:my:၁၉၃၀ ပဲခူးငလျင်]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Thiao Mueang Phama (1955, p. 165).jpg|center|300px]] <div style="text-align:left; padding: .4em;"> An earthquake affected Myanmar on 5 May 1930 with a moment magnitude (Mw ) 7.4. The shock occurred 35 km (22 mi) beneath the surface with a maximum Rossi–Forel intensity of IX (Devastating tremor). The earthquake was the result of rupture along a 131 km (81 mi) segment of the Sagaing Fault—a major strike-slip fault that runs through the country. Extensive damage was reported in the southern part of the country, particularly in Bago and Yangon, where buildings collapsed and fires erupted. At least 550, and possibly up to 7,000 people were killed. A moderate tsunami struck the Burmese coast which caused minor damage to ships and a port. It was felt for over 570,000 km2 (220,000 sq mi) and as far as Shan State and Thailand. The mainshock was followed by many aftershocks; several were damaging. The December earthquake was similarly sized which also occurred along the Sagaing Fault. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 7 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-15 == <section begin="technews-2025-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/15|Translations]] are available. '''Updates for editors''' * From now on, [[m:Special:MyLanguage/Interface administrators|interface admins]] and [[m:Special:MyLanguage/Central notice administrators|centralnotice admins]] are technically required to enable [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] before they can use their privileges. In the future this might be expanded to more groups with advanced user-rights. [https://phabricator.wikimedia.org/T150898] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The Design System Team is preparing to release the next major version of Codex (v2.0.0) on April 29. Editors and developers who use CSS from Codex should see the [[mw:Codex/Release Timeline/2.0|2.0 overview documentation]], which includes guidance related to a few of the breaking changes such as <code dir=ltr style="white-space: nowrap;">font-size</code>, <code dir=ltr style="white-space: nowrap;">line-height</code>, and <code dir=ltr style="white-space: nowrap;">size-icon</code>. * The results of the [[mw:Developer Satisfaction Survey/2025|Developer Satisfaction Survey (2025)]]  are now available. Thank you to all participants. These results help the Foundation decide what to work on next and to review what they recently worked on. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.24|MediaWiki]] '''Meetings and events''' * The [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]] will take place in Istanbul, Turkey, between 2–4 May. Registration for attending the in-person event will close on 13 April. Before registering, please note the potential need for a [https://www.mfa.gov.tr/turkish-representations.en.mfa visa] or [https://www.mfa.gov.tr/visa-information-for-foreigners.en.mfa e-visa] to enter the country. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 7 April 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28507470 --> == Wikipedia translation of the week: 2025-16 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Museum of Zoology of the University of São Paulo]]'''<br /> <small>''([[:pt:Museu de Zoologia da Universidade de São Paulo]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Museu de Zoologia da USP 02.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Museum of Zoology of the University of São Paulo''' (Portuguese: Museu de Zoologia da Universidade de São Paulo, abbreviated MZUSP) is a public natural history museum located in the historic Ipiranga district of São Paulo, Brazil. The MZUSP is an educational and research institution that is part of the University of São Paulo. The museum began at the end of the 19th century as part of the Museu Paulista; in 1941, it moved into a dedicated building. In 1969 the museum became a part of the University of São Paulo, receiving its current name. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 14 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-16 == <section begin="technews-2025-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/16|Translations]] are available. '''Weekly highlight''' * Later this week, the default thumbnail size will be increased from 220px to 250px. This changes how pages are shown in all wikis and has been requested by some communities for many years, but wasn't previously possible due to technical limitations. [https://phabricator.wikimedia.org/T355914] * File thumbnails are now stored in discrete sizes. If a page specifies a thumbnail size that's not among the standard sizes (20, 40, 60, 120, 250, 330, 500, 960), then MediaWiki will pick the closest larger thumbnail size but will tell the browser to downscale it to the requested size. In these cases, nothing will change visually but users might load slightly larger images. If it doesn't matter which thumbnail size is used in a page, please pick one of the standard sizes to avoid the extra in-browser down-scaling step. [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Images#Thumbnail_sizes][https://phabricator.wikimedia.org/T355914] '''Updates for editors''' * The Wikimedia Foundation are working on a system called [[m:Edge Uniques|Edge Uniques]] which will enable [[:w:en:A/B testing|A/B testing]], help protect against [[:w:en:Denial-of-service attack|Distributed denial-of-service attacks]] (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is so that they can more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. * To improve security for users, a small percentage of logins will now require that the account owner input a one-time password [[mw:Special:MyLanguage/Help:Extension:EmailAuth|emailed to their account]]. It is recommended that you [[Special:Preferences#mw-prefsection-personal-email|check]] that the email address on your account is set correctly, and that it has been confirmed, and that you have an email set for this purpose. [https://phabricator.wikimedia.org/T390662] * "Are you interested in taking a short survey to improve tools used for reviewing or reverting edits on your Wiki?" This question will be [[phab:T389401|asked at 7 wikis starting next week]], on Recent Changes and Watchlist pages. The [[mw:Special:MyLanguage/Moderator Tools|Moderator Tools team]] wants to know more about activities that involve looking at new edits made to your Wikimedia project, and determining whether they adhere to your project's policies. * On April 15, the full Wikidata graph will no longer be supported on <bdi lang="zxx" dir="ltr">[https://query.wikidata.org/ query.wikidata.org]</bdi>. After this date, scholarly articles will be available through <bdi lang="zxx" dir="ltr" style="white-space:nowrap;">[https://query-scholarly.wikidata.org/ query-scholarly.wikidata.org]</bdi>, while the rest of the data hosted on Wikidata will be available through the <bdi lang="zxx" dir="ltr">[https://query.wikidata.org/ query.wikidata.org]</bdi> endpoint. This is part of the scheduled split of the Wikidata Graph, which was [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/September 2024 scaling update|announced in September 2024]]. More information is [[d:Wikidata:SPARQL query service/WDQS graph split|available on Wikidata]]. * The latest quarterly [[m:Special:MyLanguage/Wikimedia Apps/Newsletter/First quarter of 2025|Wikimedia Apps Newsletter]] is now available. It covers updates, experiments, and improvements made to the Wikipedia mobile apps. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The latest quarterly [[mw:Technical Community Newsletter/2025/April|Technical Community Newsletter]] is now available. This edition includes: an invitation for tool maintainers to attend the Toolforge UI Community Feedback Session on April 15th; recent community metrics; and recent technical blog posts. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.25|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:25, 15 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28540654 --> == Wikipedia translation of the week: 2025-17 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Fear of crime]]'''<br /> <small>''([[:ar:الخوف من الجريمة]])&#32;([[:it:Criminofobia]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Fear of crime''' refers to the fear of being a victim of crime, which is not necessarily reflective of the actual probability of being such a victim. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 21 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28559524 --> == Tech News: 2025-17 == <section begin="technews-2025-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/17|Translations]] are available. '''Updates for editors''' * [[f:Special:MyLanguage/Wikifunctions:Main Page|Wikifunctions]] is now integrated with [[w:dag:Solɔɣu|Dagbani Wikipedia]] since April 15. It is the first project that will be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them in articles. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of [[f:Special:MyLanguage/Wikifunctions:Catalogue|a stable and global function]], rather than via a local template. [https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Status_updates/2025-04-16] * A new type of lint error has been created: [[Special:LintErrors/empty-heading|{{int:linter-category-empty-heading}}]] ([[mw:Special:MyLanguage/Help:Lint errors/empty-heading|documentation]]). The [[mw:Special:MyLanguage/Help:Extension:Linter|Linter extension]]'s purpose is to identify wikitext patterns that must or can be fixed in pages and provide some guidance about what the problems are with those patterns and how to fix them. [https://phabricator.wikimedia.org/T368722] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:37}} community-submitted {{PLURAL:37|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Following its publication on HuggingFace, the "Structured Contents" dataset, developed by Wikimedia Enterprise, is [https://enterprise.wikimedia.com/blog/kaggle-dataset/ now also available on Kaggle]. This Beta initiative is focused on making Wikimedia data more machine-readable for high-volume reusers. They are releasing this beta version in a location that open dataset communities already use, in order to seek feedback, to help improve the product for a future wider release. You can read more about the overall [https://enterprise.wikimedia.com/blog/structured-contents-snapshot-api/#open-datasets Structured Contents project], and about the [https://enterprise.wikimedia.com/blog/structured-contents-wikipedia-infobox/ first release that's freely usable]. * There is no new MediaWiki version this week. '''Meetings and events''' * The Editing and Machine Learning Teams invite interested volunteers to a video meeting to discuss [[mw:Special:MyLanguage/Edit check/Peacock check|Peacock check]], which is the latest [[mw:Special:MyLanguage/Edit check|Edit check]] that will detect "peacock" or "overly-promotional" or "non-neutral" language whilst an editor is typing. Editors who work with newcomers, or help to fix this kind of writing, or are interested in how we use artificial intelligence in our projects are encouraged to attend. The [[mw:Special:MyLanguage/Editing team/Community Conversations#Next Conversation|meeting will be on April 28, 2025]] at [https://zonestamp.toolforge.org/1745863200 18:00–19:00 UTC] and hosted on Zoom. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:01, 21 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28578245 --> == Wikipedia translation of the week: 2025-18 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Heritage preservation in South Korea]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Korean.Dance-03.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The heritage preservation system of South Korea is a multi-level program aiming to preserve and cultivate Korean cultural heritage. The program is administered by the Cultural Heritage Administration (CHA), and the legal framework is provided by the Cultural Heritage Protection Act of 1962, last updated in 2012. The program started in 1962 and has gradually been extended and upgraded since then. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:57, 28 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28583422 --> == Tech News: 2025-18 == <section begin="technews-2025-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/18|Translations]] are available. '''Updates for editors''' * Event organizers who host collaborative activities on [[m:Special:MyLanguage/CampaignEvents/Deployment status#Global Deployment Plan|multiple wikis]], including Bengali, Japanese, and Korean Wikipedias, will have access to the [[mw:Special:MyLanguage/Extension:CampaignEvents|CampaignEvents extension]] this week. Also, admins in the Wikipedia where the extension is enabled will automatically be granted the event organizer right soon. They won't have to manually grant themselves the right before they can manage events as [[phab:T386861|requested by a community]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The release of the next major version of [[mw:Special:MyLanguage/Codex|Codex]], the design system for Wikimedia, is scheduled for 29 April 2025. Technical editors will have access to the release by the week of 5 May 2025. This update will include a number of [[mw:Special:MyLanguage/Codex/Release_Timeline/2.0#Breaking_changes|breaking changes]] and minor [[mw:Special:MyLanguage/Codex/Release_Timeline/2.0#Visual_changes|visual changes]]. Instructions on handling the breaking and visual changes are documented on [[mw:Special:MyLanguage/Codex/Release Timeline/2.0#|this page]]. Pre-release testing is reported in [[phab:T386298|T386298]], with post-release issues tracked in [[phab:T392379|T392379]] and [[phab:T392390|T392390]]. * Users of [[wikitech:Special:MyLanguage/Help:Wiki_Replicas|Wiki Replicas]] will notice that the database views of <code dir="ltr">ipblocks</code>, <code dir="ltr">ipblocks_ipindex</code>, and <code dir="ltr">ipblocks_compat</code> are [[phab:T390767|now deprecated]]. Users can query the <code dir="ltr">[[mw:Special:MyLanguage/Manual:Block_table|block]]</code> and <code dir="ltr">[[mw:Special:MyLanguage/Manual:Block_target_table|block_target]]</code> new views that mirror the new tables in the production database instead. The deprecated views will be removed entirely from Wiki Replicas in June, 2025. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.27|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April|Language and Internationalization Newsletter]] is now available. This edition includes an overview of the improved [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=contributionsmenu&to=es&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en#/ Content Translation Dashboard Tool], [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April#Language Support for New and Existing Languages|support for new languages]], [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April#Wiki Loves Ramadan Articles Made In Content Translation Mobile Workflow|highlights from the Wiki Loves Ramadan campaign]], [[m:Special:MyLanguage/Research:Languages Onboarding Experiment 2024 - Executive Summary|results from the Language Onboarding Experiment]], an analysis of topic diversity in articles, and information on upcoming community meetings and events. '''Meetings and events''' * The [[Special:MyLanguage/Grants:Knowledge_Sharing/Connect/Calendar|Let's Connect Learning Clinic]] will take place on [https://zonestamp.toolforge.org/1745937000 April 29 at 14:30 UTC]. This edition will focus on "Understanding and Navigating Conflict in Wikimedia Projects". You can [[m:Special:MyLanguage/Event:Learning Clinic %E2%80%93 Understanding and Navigating Conflict in Wikimedia Projects (Part_1)|register now]] to attend. * The [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]], which brings the global technical community together to connect, brainstorm, and hack existing projects, will take place from May 2 to 4th, 2025, at Istanbul, Turkey. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:32, 28 April 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28585685 --> == Wikipedia translation of the week: 2025-19 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lhamana]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:We-Wa, a Zuni berdache, weaving - NARA - 523796 (cropped).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lhamana''', in traditional Zuni culture, are biologically male people who take on the social and ceremonial roles usually performed by women in their culture, at least some of the time. They wear a mixture of women's and men's clothing and much of their work is in the areas usually occupied by Zuni women. Some contemporary lhamana participate in the pan-Indian two-spirit community. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 07:28, 5 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28583422 --> == Tech News: 2025-19 == <section begin="technews-2025-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/19|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation has shared the latest draft update to their [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|annual plan]] for next year (July 2025–June 2026). This includes an [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|executive summary]] (also on [[diffblog:2025/04/25/sharing-the-wikimedia-foundations-2025-2026-draft-annual-plan/|Diff]]), details about the three main [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals|goals]] ([[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|Infrastructure]], [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals/Volunteer Support|Volunteer Support]], and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals/Effectiveness|Effectiveness]]), [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Global Trends|global trends]], and the [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Budget Overview|budget]] and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Financial Model|financial model]]. Feedback and questions are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2025-2026|talk page]] until the end of May. '''Updates for editors''' * For wikis that have the [[m:Special:MyLanguage/CampaignEvents/Deployment status|CampaignEvents extension enabled]], two new feature improvements have been released: ** Admins can now choose which namespaces are permitted for [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] via [[mw:Special:MyLanguage/Community Configuration|Community Configuration]] ([[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Permitted namespaces|documentation]]). The default setup is for event registration to be permitted in the Event namespace, but other namespaces (such as the project namespace or WikiProject namespace) can now be added. With this change, communities like WikiProjects can now more easily use Event Registration for their collaborative activities. ** Editors can now [[mw:Special:MyLanguage/Transclusion|transclude]] the Collaboration List on a wiki page ([[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Collaboration list/Transclusion|documentation]]). The Collaboration List is an automated list of events and WikiProjects on the wikis, accessed via {{#special:AllEvents}} ([[w:en:Special:AllEvents|example]]). Now, the Collaboration List can be added to all sorts of wiki pages, such as: a wiki mainpage, a WikiProject page, an affiliate page, an event page, or even a user page. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers who use the <code dir=ltr>moment</code> library in gadgets and user scripts should revise their code to use alternatives like the <code dir=ltr>Intl</code> library or the new <code dir=ltr>mediawiki.DateFormatter</code> library. The <code dir=ltr>moment</code> library has been deprecated and will begin to log messages in the developer console. You can see a global search for current uses, and [[phab:T392532|ask related questions in this Phabricator task]]. * Developers who maintain a tool that queries the Wikidata term store tables (<code dir=ltr style="white-space: nowrap;">wbt_*</code>) need to update their code to connect to a separate database cluster. These tables are being split into a separate database cluster. Tools that query those tables via the wiki replicas must be adapted to connect to the new cluster instead. [[wikitech:News/2025 Wikidata term store database split|Documentation and related links are available]]. [https://phabricator.wikimedia.org/T390954] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.28|MediaWiki]] '''In depth''' * The latest [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|Chart Project newsletter]] is available. It includes updates on preparing to expand the deployment to additional wikis as soon as this week (starting May 6) and scaling up over the following weeks, plus exploring filtering and transforming source data. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:15, 6 May 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28665011 --> == Wikipedia translation of the week: 2025-20 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Gruppo del Sileno]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Parco3.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> '''Sileno ed Egle con Mnasilo e Cromi''', meglio noto come Gruppo del Sileno, è un monumento in marmo di Carrara, realizzato da Jean-Baptiste Boudard nel 1765 per il Giardino Ducale di Parma; sostituito nel 1991 con una copia in polvere di marmo e resina, l'originale si trova provvisoriamente nel chiostro della Fontana del monastero di San Paolo, in attesa della definitiva collocazione prevista all'interno del palazzetto Eucherio Sanvitale nel parco Ducale. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:28, 12 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28709947 --> == Tech News: 2025-20 == <section begin="technews-2025-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/20|Translations]] are available. '''Weekly highlight''' * The [[m:Special:MyLanguage/Wikimedia URL Shortener|"Get shortened URL"]] link on the sidebar now includes a [[phab:T393309|QR code]]. Wikimedia site users can now use it by scanning or downloading it to quickly share and access shared content from Wikimedia sites, conveniently. '''Updates for editors''' * The Wikimedia Foundation is working on a system called [[m:Edge Uniques|Edge Uniques]], which will enable [[w:en:A/B testing|A/B testing]], help protect against [[w:en:Denial-of-service attack|distributed denial-of-service attacks]] (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is to help more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. Tech News has [[m:Special:MyLanguage/Tech/News/2025/16|previously written about this]]. The deployment will be gradual. Some might see the Edge Uniques cookie the week of 19 May. You can discuss this on the [[m:Talk:Edge Uniques|talk page]]. * Starting May 19, 2025, Event organisers in wikis with the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] enabled can use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] in the project namespace (e.g., Wikipedia namespace, Wikidata namespace). With this change, communities don't need admins to use the feature. However, wikis that don't want this change can remove and add the permitted namespaces at [[Special:CommunityConfiguration/CampaignEvents]]. * The Wikipedia project now has a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q36720|Nupe]] ([[w:nup:|<code>w:nup:</code>]]). This is a language primarily spoken in the North Central region of Nigeria. Speakers of this language are invited to contribute to [[w:nup:Tatacin feregi|new Wikipedia]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers can now access pre-parsed Dutch Wikipedia, amongst others (English, German, French, Spanish, Italian, and Portuguese) through the [https://enterprise.wikimedia.com/docs/snapshot/#structured-contents-snapshot-bundle-info-beta Structured Contents snapshots (beta)]. The content includes parsed Wikipedia abstracts, descriptions, main images, infoboxes, article sections, and references. * The <code dir="ltr">/page/data-parsoid</code> REST API endpoint is no longer in use and will be deprecated. It is [[phab:T393557|scheduled to be turned off]] on June 7, 2025. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.1|MediaWiki]] '''In depth''' * The [https://wikitech.wikimedia.org/wiki/News/2025_Cloud_VPS_VXLAN_IPv6_migration IPv6 support] is a newly introduced Cloud virtual network that significantly boosts Wikimedia platforms' scalability, security, and readiness for the future. If you are a technical contributor eager to learn more, check out [https://techblog.wikimedia.org/2025/05/06/wikimedia-cloud-vps-ipv6-support/ this blog post] for an in-depth look at the journey to IPv6. '''Meetings and events''' * The 2nd edition of 2025 of [[m:Special:MyLanguage/Afrika Baraza|Afrika Baraza]], a virtual platform for African Wikimedians to connect, will take place on [https://zonestamp.toolforge.org/1747328400 May 15 at 17:00 UTC]. This edition will focus on discussions regarding [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|Wikimedia Annual planning and progress]]. * The [[m:Special:MyLanguage/MENA Connect Community Call|MENA Connect Community Call]], a virtual meeting for [[w:en:Middle East and North Africa|MENA]] Wikimedians to connect, will take place on [https://zonestamp.toolforge.org/1747501200 May 17 at 17:00 UTC]. You can [[m:Event:MENA Connect (Wiki_Diwan) APP Call|register now]] to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:38, 12 May 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28714188 --> == Wikipedia translation of the week: 2025-21 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lorrin A. Thurston]]'''<br /> <small>''([[:fi:Lorrin Thurston]])&#32;([[:ko:로린 A. 서스턴]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Lorrinandrewsthurston1892.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lorrin Andrews Thurston''' (July 31, 1858 – May 11, 1931) was a Hawaiian citizen lawyer, politician, and businessman. Thurston played a prominent role in the revolution that overthrew the Hawaiian Kingdom to replace Queen Liliʻuokalani with the Republic of Hawaii, with discreet US support for which Congress much later apologized. He published the Pacific Commercial Advertiser (a forerunner of the present-day Honolulu Star-Advertiser), and owned other enterprises. From 1906 to 1916, he and his network lobbied with national politicians to create a national park to preserve the Hawaiian volcanoes. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 19 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28731710 --> == Tech News: 2025-21 == <section begin="technews-2025-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/21|Translations]] are available. '''Weekly highlight''' * The Editing Team and the Machine Learning Team are working on a new check for newcomers: [[mw:Edit check/Peacock check|Peacock check]]. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Peacock language model for the following languages: Arabic, Spanish, Portuguese, English, and Japanese. Users from these wikis interested in reviewing this model are [[mw:Edit check/Peacock check/model test|invited to sign up at MediaWiki.org]]. The deadline to sign up is on May 23, which will be the start date of the test. '''Updates for editors''' * From May 20, 2025, [[m:Special:MyLanguage/Oversight policy|oversighters]] and [[m:Special:MyLanguage/Meta:CheckUsers|checkusers]] will need to have their accounts secured with two-factor authentication (2FA) to be able to use their advanced rights. All users who belong to these two groups and do not have 2FA enabled have been informed. In the future, this requirement may be extended to other users with advanced rights. [[m:Special:MyLanguage/Mandatory two-factor authentication for users with some extended rights|Learn more]]. * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] [[m:Special:MyLanguage/Community Wishlist Survey 2023/Multiblocks|Multiblocks]] will begin mass deployment by the end of the month: all non-Wikipedia projects plus Catalan Wikipedia will adopt Multiblocks in the week of May 26, while all other Wikipedias will adopt it in the week of June 2. Please [[m:Talk:Community Wishlist Survey 2023/Multiblocks|contact the team]] if you have concerns. Administrators can test the new user interface now on your own wiki by browsing to [{{fullurl:Special:Block|usecodex=1}} {{#special:Block}}?usecodex=1], and can test the full multiblocks functionality [[testwiki:Special:Block|on testwiki]]. Multiblocks is the feature that makes it possible for administrators to impose different types of blocks on the same user at the same time. See the [[mw:Special:MyLanguage/Help:Manage blocks|help page]] for more information. [https://phabricator.wikimedia.org/T377121] * Later this week, the [[{{#special:SpecialPages}}]] listing of almost all special pages will be updated with a new design. This page has been [[phab:T219543|redesigned]] to improve the user experience in a few ways, including: The ability to search for names and aliases of the special pages, sorting, more visible marking of restricted special pages, and a more mobile-friendly look. The new version can be [https://meta.wikimedia.beta.wmflabs.org/wiki/Special:SpecialPages previewed] at Beta Cluster now, and feedback shared in the task. [https://phabricator.wikimedia.org/T219543] * The [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] is being enabled on more wikis. For a detailed list of when the extension will be enabled on your wiki, please read the [[mw:Special:MyLanguage/Extension:Chart/Project#Deployment Timeline|deployment timeline]]. * [[f:Special:MyLanguage/Wikifunctions:Main Page|Wikifunctions]] will be deployed on May 27 on five Wiktionaries: [[wikt:ha:|Hausa]], [[wikt:ig:|Igbo]], [[wikt:bn:|Bengali]], [[wikt:ml:|Malayalam]], and [[wikt:dv:|Dhivehi/Maldivian]]. This is the second batch of deployment planned for the project. After deployment, the projects will be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them in their pages. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of [[f:Special:MyLanguage/Wikifunctions:Catalogue|a stable and global function]], rather than via a local template. * Later this week, the Wikimedia Foundation will publish a hub for [[diffblog:2024/07/09/on-the-value-of-experimentation/|experiments]]. This is to showcase and get user feedback on product experiments. The experiments help the Wikimedia movement [[diffblog:2023/07/13/exploring-paths-for-the-future-of-free-knowledge-new-wikipedia-chatgpt-plugin-leveraging-rich-media-social-apps-and-other-experiments/|understand new users]], how they interact with the internet and how it could affect the Wikimedia movement. Some examples are [[m:Special:MyLanguage/Future Audiences/Generated Video|generated video]], the [[m:Special:MyLanguage/Future Audiences/Roblox game|Wikipedia Roblox speedrun game]] and [[m:Special:MyLanguage/Future Audiences/Discord bot|the Discord bot]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a bug with creating an account using the API, which has now been fixed. [https://phabricator.wikimedia.org/T390751] '''Updates for technical contributors''' * Gadgets and user scripts that interact with [[{{#special:Block}}]] may need to be updated to work with the new [[mw:Special:MyLanguage/Help:Manage blocks|manage blocks interface]]. Please review the [[mw:Help:Manage blocks/Developers|developer guide]] for more information. If you need help or are unable to adapt your script to the new interface, please let the team know on the [[mw:Help talk:Manage blocks/Developers|talk page]]. [https://phabricator.wikimedia.org/T377121] * The <code dir=ltr>mw.title</code> object allows you to get information about a specific wiki page in the [[w:en:Wikipedia:Lua|Lua]] programming language. Starting this week, a new property will be added to the object, named <code dir=ltr>isDisambiguationPage</code>. This property allows you to check if a page is a disambiguation page, without the need to write a custom function. [https://phabricator.wikimedia.org/T71441] * [[File:Octicons-tools.svg|15px|link=|class=skin-invert|Advanced item]] User script developers can use a [[toolforge:gitlab-content|new reverse proxy tool]] to load javascript and css from [[gitlab:|gitlab.wikimedia.org]] with <code dir=ltr>mw.loader.load</code>. The tool's author hopes this will enable collaborative development workflows for user scripts including linting, unit tests, code generation, and code review on <bdi lang="zxx" dir="ltr">gitlab.wikimedia.org</bdi> without a separate copy-and-paste step to publish scripts to a Wikimedia wiki for integration and acceptance testing. See [[wikitech:Tool:Gitlab-content|Tool:Gitlab-content on Wikitech]] for more information. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.2|MediaWiki]] '''Meetings and events''' * The 12th edition of [[m:Special:MyLanguage/Wiki Workshop 2025|Wiki Workshop 2025]], a forum that brings together researchers that explore all aspects of Wikimedia projects, will be held virtually on 21-22 May. Researchers can [https://pretix.eu/wikimedia/wikiworkshop2025/ register now]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W21"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:13, 19 May 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28724712 --> == Wikipedia translation of the week: 2025-22 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Lamiera bugnata]]'''<br /> <small>''([[:en:Tread plate]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Diamond Plate.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Una '''lamiera bugnata''' o mandorlata è una lamiera di metallo ottenuta dalla laminazione di una bramma attraverso rulli che, tramite punzonatura o goffratura, imprimono sulla lamina rilievi a forma di rombo o ellisse, detti bugne. Nel caso questi rilievi siano alternati singolarmente nei due assi, si parla di lamiera diamantata, mentre se le forme sono predisposte in maniera parallela per formare piccoli quadranti tra di loro tangenti, questo pattern viene identificato con il nome di mandorlato. We tend to ignore the fact that this type of plate is the only reason we don't slip when we walk on steel and wet or frozen surfaces. The Italian article it's short but quite complete, and has just the right amount of citations, unlike other poor languages' versions. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 06:03, 26 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28751788 --> == Tech News: 2025-22 == <section begin="technews-2025-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/22|Translations]] are available. '''Weekly highlight''' * A community-wide discussion about a very delicate issue for the development of [[m:Special:MyLanguage/Abstract Wikipedia|Abstract Wikipedia]] is now open on Meta: where to store the abstract content that will be developed through functions from Wikifunctions and data from Wikidata. The discussion is open until June 12 at [[m:Special:MyLanguage/Abstract Wikipedia/Location of Abstract Content|Abstract Wikipedia/Location of Abstract Content]], and every opinion is welcomed. The decision will be made and communicated after the consultation period by the Foundation. '''Updates for editors''' * Since last week, on all wikis except [[phab:T388604|the largest 20]], people using the mobile visual editor will have [[phab:T385851|additional tools in the menu bar]], accessed using the new <code>+</code> toolbar button. To start, the new menu will include options to add: citations, hieroglyphs, and code blocks. Deployment to the remaining wikis is [[phab:T388605|scheduled]] to happen in June. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The <code dir=ltr>[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##ifexist|#ifexist]]</code> parser function will no longer register a link to its target page. This will improve the usefulness of [[{{#special:WantedPages}}]], which will eventually only list pages that are the target of an actual red link. This change will happen gradually as the source pages are updated. [https://phabricator.wikimedia.org/T14019] * This week, the Moderator Tools team will launch [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], starting at Indonesian Wikipedia. This new filter highlights edits that are likely to be reverted. The goal is to help Recent Changes patrollers identify potentially problematic edits. Other wikis will benefit from this filter in the future. * Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading. The feature will be available on both desktop and mobile. Readers of Catalan, Hebrew, and Italian Wikipedias and some sister projects will receive the change between May 21 and mid-June. Readers of other wikis will receive the change later. The goal is to encourage users to read the wikis more. [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments/Search Suggestions|Learn more]]. * Some users of the Wikipedia Android app can use a new feature for readers, [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/TrivaGame|WikiGames]], a daily trivia game based on real historical events. The release has started as an A/B test, available to 50% of users in the following languages: English, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. * The [[mw:Special:MyLanguage/Extension:Newsletter|Newsletter extension]] that is available on MediaWiki.org allows the creation of [[mw:Special:Newsletters|various newsletters]] for global users. The extension can now publish new issues as section links on an existing page, instead of requiring a new page for each issue. [https://phabricator.wikimedia.org/T393844] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The previously deprecated <code dir=ltr>[[mw:Special:MyLanguage/Manual:Ipblocks table|ipblocks]]</code> views in [[wikitech:Help:Wiki Replicas|Wiki Replicas]] will be removed in the beginning of June. Users are encouraged to query the new <code dir=ltr>[[mw:Special:MyLanguage/Manual:Block table|block]]</code> and <code dir=ltr>[[mw:Special:MyLanguage/Manual:Block target table|block_target]]</code> views instead. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.3|MediaWiki]] '''Meetings and events''' * [[d:Special:MyLanguage/Event:Wikidata and Sister Projects|Wikidata and Sister Projects]] is a multi-day online event that will focus on how Wikidata is integrated to Wikipedia and the other Wikimedia projects. The event runs from May 29 – June 1. You can [[d:Special:MyLanguage/Event:Wikidata and Sister Projects#Sessions|read the Program schedule]] and [[d:Special:RegisterForEvent/1291|register]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:05, 26 May 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28788673 --> == Wikipedia translation of the week: 2025-23 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Angelo azzurro (cocktail)]]'''<br /> <small>''([[:es:Ángel azul (cóctel)]])&#32;([[:fr:Ange bleu (cocktail)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Angelo Azzurro Cocktail.png|300px|center]] <div style="text-align:left; padding: .4em;"> L''''angelo azzurro''' è un cocktail alcolico italiano. È considerato uno dei cocktail più popolari in Italia negli anni novanta, insieme al B-52 e all'Invisibile. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 05:39, 2 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-23 == <section begin="technews-2025-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/23|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] is now available on all Wikimedia wikis. Editors can use this new extension to create interactive data visualizations like bar, line, area, and pie charts. Charts are designed to replace many of the uses of the legacy [[mw:Special:MyLanguage/Extension:Graph|Graph extension]]. '''Updates for editors''' * It is now easier to configure automatic citations for your wiki within the visual editor's [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|citation generator]]. Administrators can now set a default template by using the <code dir=ltr>_default</code> key in the local <bdi lang="en" dir="ltr">[[MediaWiki:Citoid-template-type-map.json]]</bdi> page ([[mw:Special:Diff/6969653/7646386|example diff]]). Setting this default will also help to future-proof your existing configurations when [[phab:T347823|new item types]] are added in the future. You can still set templates for individual item types as they will be preferred to the default template. [https://phabricator.wikimedia.org/T384709] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Starting the week of June 2, bots logging in using <code dir=ltr>action=login</code> or <code dir=ltr>action=clientlogin</code> will fail more often. This is because of stronger protections against suspicious logins. Bots using [[mw:Special:MyLanguage/Manual:Bot passwords|bot passwords]] or using a loginless authentication method such as [[mw:Special:MyLanguage/OAuth/Owner-only consumers|OAuth]] are not affected. If your bot is not using one of those, you should update it; using <code dir=ltr>action=login</code> without a bot password was deprecated [[listarchive:list/wikitech-l@lists.wikimedia.org/message/3EEMN7VQX5G7WMQI5K2GP5JC2336DPTD/|in 2016]]. For most bots, this only requires changing what password the bot uses. [https://phabricator.wikimedia.org/T395205] * From this week, Wikimedia wikis will allow ES2017 features in JavaScript code for official code, gadgets, and user scripts. The most visible feature of ES2017 is <bdi lang="zxx" dir="ltr"><code>async</code>/<code>await</code></bdi> syntax, allowing for easier-to-read code. Until this week, the platform only allowed up to ES2016, and a few months before that, up to ES2015. [https://phabricator.wikimedia.org/T381537] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.4|MediaWiki]] '''Meetings and events''' * Scholarship applications to participate in the [[m:Special:MyLanguage/GLAM Wiki 2025|GLAM Wiki Conference 2025]] are now open. The conference will take place from 30 October to 1 November, in Lisbon, Portugal. GLAM contributors who lack the means to support their participation can [[m:Special:MyLanguage/GLAM Wiki 2025/Scholarships|apply here]]. Scholarship applications close on June 7th. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:55, 2 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28819186 --> == Wikipedia translation of the week: 2025-24 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fi:Kotiryssä]]'''<br /> <small>''([[:en:Kotiryssä]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A '''kotiryssä''' (jocular Finnish: one’s home Russky or home Russian) was a Soviet or Russian contact person of a Finnish politician, bureaucrat, businessman or other important person. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 9 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-24 == <section begin="technews-2025-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/24|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Trust and Safety Product|Trust and Safety Product team]] is finalizing work needed to roll out [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] on large Wikipedias later this month. The team has worked with stewards and other users with extended rights to predict and address many use cases that may arise on larger wikis, so that community members can continue to effectively moderate and patrol temporary accounts. This will be the second of three phases of deployment – the last one will take place in September at the earliest. For more information about the recent developments on the project, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|see this update]]. If you have any comments or questions, write on the [[mw:Talk:Trust and Safety Product/Temporary Accounts|talk page]], and [[m:Event:CEE Catch up Nr. 10 (June 2025)|join a CEE Catch Up]] this Tuesday. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] The [[mw:Special:MyLanguage/Help:Watchlist expiry|watchlist expiry]] feature allows editors to watch pages for a limited period of time. After that period, the page is automatically removed from your watchlist. Starting this week, you can set a preference for the default period of time to watch pages. The [[Special:Preferences#mw-prefsection-watchlist-pageswatchlist|preferences]] also allow you to set different default watch periods for editing existing pages, pages you create, and when using rollback. [https://phabricator.wikimedia.org/T265716] [[File:Talk pages default look (April 2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages will change at almost all Wikipedias ([[m:Special:MyLanguage/Tech/News/2024/19|some]] have already received this design change, [[phab:T379264|a few]] will get these changes later). You can read details about the changes [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. It is possible to opt out of these changes [[Special:Preferences#mw-prefsection-editing-discussion|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). [https://phabricator.wikimedia.org/T319146][https://phabricator.wikimedia.org/T392121] * Users with specific extended rights (including administrators, bureaucrats, checkusers, oversighters, and stewards) can now have IP addresses of all temporary accounts [[phab:T358853|revealed automatically]] during time-limited periods where they need to combat high-speed account-hopping vandalism. This feature was requested by stewards. [https://phabricator.wikimedia.org/T386492] * This week, the Moderator Tools and Machine Learning teams will continue the rollout of [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], releasing it to several more Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: {{int:project-localized-name-afwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-simplewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}. The rollout will continue in the coming weeks to include [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|the rest of the Wikipedias in this project]]. [https://phabricator.wikimedia.org/T391964] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * AbuseFilter editors active on Meta-Wiki and large Wikipedias are kindly asked to update AbuseFilter to make it compatible with temporary accounts. A link to the instructions and the private lists of filters needing verification are [[phab:T369611|available on Phabricator]]. * Lua modules now have access to the name of a page's associated thumbnail image, and on [https://gerrit.wikimedia.org/g/operations/mediawiki-config/+/2e4ab14aa15bb95568f9c07dd777065901eb2126/wmf-config/InitialiseSettings.php#10849 some wikis] to the WikiProject assessment information. This is possible using two new properties on [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#added-by-extensions|mw.title objects]], named <code dir=ltr>pageImage</code> and <code dir=ltr>pageAssessments</code>. [https://phabricator.wikimedia.org/T131911][https://phabricator.wikimedia.org/T380122] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.5|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:17, 10 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28846858 --> == Wikipedia translation of the week: 2025-25 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Future self]]'''<br /> <small>''([[:pl:Przyszła jaźń]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In the psychology of self, the '''future self''' concerns the processes and consequences associated with thinking about oneself in the future. People think about their future selves similarly to how they think about other people. The extent to which people feel psychologically connected (e.g., similarity, closeness) to their future self influences how well they treat their future self. When people feel connected to their future self, they are more likely to save for retirement, make healthy decisions, and avoid ethical transgressions. Interventions that increase feelings of connectedness with future selves can improve future-oriented decision making across these domains. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 16 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-25 == <section begin="technews-2025-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/25|Translations]] are available. '''Updates for editors''' * You can [https://wikimediafoundation.limesurvey.net/359761?lang=en nominate your favorite tools] for the sixth edition of the [[m:Special:MyLanguage/Coolest Tool Award|Coolest Tool Award]]. Nominations are anonymous and will be open until June 25. You can re-use the survey to nominate multiple tools. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:33}} community-submitted {{PLURAL:33|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.6|MediaWiki]] '''In depth''' * Foundation staff and technical volunteers use Wikimedia APIs to build the tools, applications, features, and integrations that enhance user experiences. Over the coming years, the MediaWiki Interfaces team will be investing in Wikimedia web (HTTP) APIs to better serve technical volunteer needs and protect Wikimedia infrastructure from potential abuse. You can [https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/ read more about their plans to evolve the APIs in this Techblog post]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:39, 16 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28870688 --> == Wikipedia translation of the week: 2025-26 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pictorial map]]'''<br /> <small>''([[:fa:نقشه تصویری]])&#32;([[:ja:絵地図]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Blake Britain Spearhead of Attack.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Pictorial maps''' (also known as illustrated maps, panoramic maps, perspective maps, bird's-eye view maps, and geopictorial maps) depict a given territory with a more artistic rather than technical style. It is a type of map in contrast to road map, atlas, or topographic map. The cartography can be a sophisticated 3-D perspective landscape or a simple map graphic enlivened with illustrations of buildings, people and animals. They can feature all sorts of varied topics like historical events, legendary figures or local agricultural products and cover anything from an entire continent to a college campus. Drawn by specialized artists and illustrators, pictorial maps are a rich, centuries-old tradition and a diverse art form that ranges from cartoon maps on restaurant placemats to treasured art prints in museums. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:18, 23 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-26 == <section begin="technews-2025-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/26|Translations]] are available. '''Weekly highlight''' * This week, the Moderator Tools and Machine Learning teams will continue the rollout of [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], releasing it to the third and last batch of Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: {{int:project-localized-name-azwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-swwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tlwiki/en}}. The rollout will continue in the coming weeks to include [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|the rest of the Wikipedias in this project]]. [https://phabricator.wikimedia.org/T391964] '''Updates for editors''' * Last week, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] were rolled out on Czech, Korean, and Turkish Wikipedias. This and next week, deployments on larger Wikipedias will follow. [[mw:Talk:Trust and Safety Product/Temporary Accounts|Share your thoughts]] about the project. [https://phabricator.wikimedia.org/T340001] * Later this week, the Editing team will release [[mw:Special:MyLanguage/Help:Edit check#Multi check|Multi Check]] to all Wikipedias (except English Wikipedia). This feature shows multiple [[mw:Special:MyLanguage/Help:Edit check#Reference check|Reference checks]] within the editing experience. This encourages users to add citations when they add multiple new paragraphs to a Wikipedia article. This feature was previously available as an A/B test. [https://analytics.wikimedia.org/published/reports/editing/multi_check_ab_test_report_final.html#summary-of-results The test shows] that users who are shown multiple checks are 1.3 times more likely to add a reference to their edit, and their edit is less likely to be reverted (-34.7%). [https://phabricator.wikimedia.org/T395519] * A few pages need to be renamed due to software updates and to match more recent Unicode standards. All of these changes are related to title-casing changes. Approximately 71 pages and 3 files will be renamed, across 15 wikis; the complete list is in [[phab:T396903|the task]]. The developers will rename these pages next week, and they will fix redirects and embedded file links a few minutes later via a system settings update. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that had caused pages to scroll upwards when text near the top was selected. [https://phabricator.wikimedia.org/T364023] '''Updates for technical contributors''' * Editors can now use Lua modules to filter and transform tabular data for use with [[mw:Special:MyLanguage/Extension:Chart|Extension:Chart]]. This can be used for things like selecting a subset of rows or columns from the source data, converting between units, statistical processing, and many other useful transformations. [[mw:Special:MyLanguage/Extension:Chart/Transforms|Information on how to use transforms is available]]. [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Chart/Project/Updates] * The <code dir=ltr>all_links</code> variable in [[Special:AbuseFilter|AbuseFilter]] is now renamed to <code dir=ltr>new_links</code> for consistency with other variables. Old usages will still continue to work. [https://phabricator.wikimedia.org/T391811] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.7|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/34|Growth newsletter]] is available. It includes: the recent updates for the "Add a Link" Task, two new Newcomer Engagement Features, and updates to Community Configuration. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:21, 23 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28870688 --> == Wikipedia translation of the week: 2025-27 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Queen Elizabeth University Hospital]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:QEUH.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Queen Elizabeth University Hospital''' (QEUH) is a 1,677-bed acute hospital located in Govan, in the south-west of Glasgow, Scotland. The hospital is built on the site of the former Southern General Hospital and opened at the end of April 2015. The hospital comprises a 1,109-bed adult hospital, a 256-bed children's hospital and two major Emergency Departments; one for adults and one for children. There is also an Immediate Assessment Unit for local GPs and out-of-hours services, to send patients directly, without having to be processed through the Emergency Department. The retained buildings from the former Southern General Hospital include the Maternity Unit, the Institute of Neurological Sciences, the Langlands Unit for medicine of the elderly and the laboratory. The whole facility is operated by NHS Greater Glasgow and Clyde, and is one of the largest acute hospital campuses in Europe. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 30 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-27 == <section begin="technews-2025-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/27|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] has been enabled on all Wikipedias. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. The extension has three features: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Campaigns/Foundation Product Team/Invitation list|Invitation List]]. To request the extension for your wiki, visit the [[m:Special:MyLanguage/CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|Deployment information page]]. '''Updates for editors''' * AbuseFilter maintainers can now [[mw:Special:MyLanguage/Extension:IPReputation/AbuseFilter variables|match against IP reputation data]] in [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilters]]. IP reputation data is information about the proxies and VPNs associated with the user's IP address. This data is not shown publicly and is not generated for actions performed by registered accounts. [https://phabricator.wikimedia.org/T354599] * Hidden content that is within [[mw:Special:MyLanguage/Manual:Collapsible elements|collapsible parts of wikipages]] will now be revealed when someone searches the page using the web browser's "Find in page" function (Ctrl+F or ⌘F) in supporting browsers. [https://phabricator.wikimedia.org/T327893][https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/hidden#browser_compatibility] * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new feature, called [[mw:Special:MyLanguage/Help:TemplateData/Template discovery|Favourite Templates]], will be deployed later this week on all projects (except English Wikipedia, which will receive the feature next week), following a piloting phase on Polish and Arabic Wikipedia, and Italian and English Wikisource. The feature will provide a better way for new and experienced contributors to recall and discover templates via the template dialog, by allowing users to put templates on a special "favourite list". The feature works with both the visual editor and the wikitext editor. The feature is a [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|community wishlist focus area]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that had caused some Notifications to be sent multiple times. [https://phabricator.wikimedia.org/T397103] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.8|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:41, 30 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28917415 --> == Wikipedia translation of the week: 2025-28 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Non-constituency Member of Parliament]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A '''Non-constituency Member of Parliament''' (NCMP) is a member of an opposition political party in Singapore who, as stipulated in Article 39 of the Constitution and the Parliamentary Elections Act, is declared to have been elected a Member of Parliament (MP) without constituency representation, despite having lost in a general election, by virtue of having been one of the opposition candidates with the highest vote shares among the unelected. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:10, 7 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-28 == <section begin="technews-2025-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/28|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Help:Temporary accounts|Temporary accounts]] have been rolled out on 18 large and medium-sized Wikipedias, including German, Japanese, French, and Chinese. Now, about 1/3 of all logged-out activity across wikis is coming from temporary accounts. Users involved in patrolling may be interested in two new documentation pages: [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Access to IP|Access to IP]], explaining everything related to access to temporary account IP addresses, and [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Repository|Repository]] with a list of new gadgets and user scripts. '''Updates for editors''' * Anyone can play an experimental new game, [[mw:Special:MyLanguage/New Engagement Experiments/WikiRun|WikiRun]], that lets you race through Wikipedia by clicking from one article to another, aiming to reach a target page in as few steps and in as little time as possible. The project's goal is to explore new ways of engaging readers. [https://wikirun-game.toolforge.org/ Try playing the game] and let the team know what you think [[mw:Talk:New Engagement Experiments/WikiRun|on the talk page]]. * Users of the Wikipedia Android app in some languages can now play the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/TrivaGame|trivia game]]. ''Which came first?'' is a simple history game where you guess which of two events happened earlier on today's date. It was previously available as an A/B test. It is now available to all users in English, German, French, Spanish, Portuguese, Russian, Arabic, Turkish, and Chinese. The goal of the feature is to help engage with new generations of readers. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2025/22] * Users of the iOS Wikipedia App in some languages may see a new tabbed browsing feature that enables you to open multiple tabs while reading. This feature makes it easier to explore related topics and switch between articles. The A/B test is currently running in Arabic, English, and Japanese in selected regions. More details are available on the [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Tabbed Browsing (Tabs)|Tabbed Browsing project page]]. * Bureaucrats on Wikimedia wikis can now use [[{{#special:VerifyOATHForUser}}]] to check if users have enabled [[mw:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]]. [https://phabricator.wikimedia.org/T265726] * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new feature related to [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template Recall and Discovery]] will be deployed later this week to all Wikimedia projects: a [[mw:Special:MyLanguage/Help:TemplateData/Template discovery#Template categories|template category browser]] will be introduced to assist users in finding templates to put in their “favourite” list. The browser will allow users to browse a list of templates which have been organised into a given category tree. The feature has been requested by the community [[m:Special:MyLanguage/Community Wishlist/Wishes/Select templates by categories|through the Community Wishlist]]. * It is now possible to access watchlist preferences from the watchlist page. Also the redundant button to edit the watchlist has been removed. [https://www.mediawiki.org/wiki/Moderator_Tools/Watchlist] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * As part of [[mw:MediaWiki_1.44|MediaWiki 1.44]] there is now a unified built-in Notifications system that makes it easier for developers to send, manage, and customize notifications. Check out the updated documentation at [[mw:Manual:Notifications|Manual:Notifications]], information about migration in [[phab:T388663|T388663]] and details on deprecated hooks in [[phab:T389624|T389624]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.9|MediaWiki]] '''Meetings and events''' * [[d:Special:MyLanguage/Event:WikidataCon 2025|WikidataCon 2025]], the conference dedicated to Wikidata is now open for [https://pretalx.com/wikidatacon-2025/cfp session proposals] and for [[d:Special:RegisterForEvent/1340|registration]]. This year's event will be held online from October 31 – November 02 and will explore on the theme of "Connecting People through Linked Open Data". '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 8 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28930584 --> == Wikipedia translation of the week: 2025-29 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Immunolabeling]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Immunolabeling process image.png|300px|center]] <div style="text-align:left; padding: .4em;"> '''Immunolabeling''' is a biochemical process that enables the detection and localization of an antigen to a particular site within a cell, tissue, or organ. Antigens are organic molecules, usually proteins, capable of binding to an antibody. These antigens can be visualized using a combination of antigen-specific antibody as well as a means of detection, called a tag, that is covalently linked to the antibody <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> ---[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:44, 14 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28945528 --> == Tech News: 2025-29 == <section begin="technews-2025-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/29|Translations]] are available. '''Updates for editors''' * [[mw:Special:MyLanguage/Help:TemplateData/Template discovery#Featured templates|Featured templates]], a new feature related to [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template Recall and Discovery]] will be deployed this week to all Wikimedia projects: With this feature, editors will be able to quickly access a list of templates that are likely to be useful. These templates will be displayed in a list, under the "featured" tab of the template discovery interface. Administrators can define the list via the Community Configuration interface. The feature fulfills a request by the community [[m:Special:MyLanguage/Community Wishlist/Wishes/Easy access Templates|through the Community Wishlist]]. [https://phabricator.wikimedia.org/T367428][https://phabricator.wikimedia.org/T392896] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the request to add Malayalam fonts in the [[oldWikisource:Special:MyLanguage/Wikisource:WS Export|Wikisource Book Export Tool]] was resolved and now, the rendering of Malayalam letters in exported Wikisource books are accurate. [https://phabricator.wikimedia.org/T374457] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.10|MediaWiki]] '''In depth''' * Developers, designers, and all Wikimedians are invited to [https://phabricator.wikimedia.org/project/board/7953/ submit a project idea] for the Wikimania Hackathon 2025. Read [https://diff.wikimedia.org/2025/06/30/call-for-projects-wikimania-hackathon-2025-is-coming-to-nairobi/ this Diff blog post] for more details. '''Meetings and events''' * [[m:WikiIndaba conference 2025|WikiIndaba 2025]] scholarship application and program submission is open until 23:59 GMT on July 20. WikiIndaba is a regional conference for African Wikimedians both on the continent and in the diaspora to unite and grow together. Submit [https://docs.google.com/forms/d/e/1FAIpQLSdJTv68R1OPASXXDfpIl8EWiMLTM-TDwh6_5gNVvFuWccFZ2Q/viewform your scholarship application] and [https://ee.kobotoolbox.org/x/BI3omIfH program proposal] now! * [https://br.wikimedia.org/wiki/WikiCon_Brasil_2025 WikiCon Brasil 2025] will take place on July 19-20 in Salvador, Bahia, Brazil. The Brazilian community members are encouraged to register and attend! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:10, 14 July 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28980963 --> == Wikipedia translation of the week: 2025-30 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Vespa analis]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Plumpy hornet on the ground - 1.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Vespa analis''''', the yellow-vented hornet, is a species of common hornet found in Southeast Asia <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:28, 21 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28984647 --> == Tech News: 2025-30 == <section begin="technews-2025-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/30|Translations]] are available. '''Updates for editors''' * The Translation Suggestions feature in the [[mw:Special:MyLanguage/Content translation|Content Translation tool]] now has another level of article filters added to the "[https://en.wikipedia.org/w/index.php?title=Special:ContentTranslation&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en&to=fi#/ ... More]" category. Translators who use the Suggestions feature can now select and receive article suggestions that are customized to geographical locations of their interest using the new "{{int:Cx-sx-suggestions-filters-tab-regions}}" filter. [https://phabricator.wikimedia.org/T113257] * Administrators can now limit "Add a Link" to newcomers. The [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|"Add a Link"]] Structured Task [[mw:Special:MyLanguage/Growth/Constructive activation experimentation#Enwiki A/B test & "Add a Link" Improvements (Wiki Experiences 1.2.11 & 1.2.16)|helps new account holders start editing]], but some communities have requested the ability to restrict it to its intended audience: newcomers. Administrators can configure this setting within the [[Special:CommunityConfiguration/GrowthSuggestedEdits|Community Configuration]] feature. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * For AbuseFilter editors on [[phab:T392144|some wikis]], it is now possible to filter edits based on the RevertRisk score of the edit being attempted. It is only populated if the action being evaluated is an edit. For more information, please see the [[mw:Special:MyLanguage/Extension:ORES/AbuseFilter variables#What variables are available for use|ORES/AbuseFilter variables]] documentation. * The [[mw:Special:MyLanguage/Beta Cluster|Beta Cluster]] wikis have [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/YDABPV75LADRQCXMJAFWUP256N4EQ25B/|been moved]] from <code dir=ltr>beta.wmflabs.org</code> to <code dir=ltr>beta.wmcloud.org</code>. Users may need to update URLs in any tools, or in their password managers. Any related issues can be [[phab:T289318|reported in the task]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.11|MediaWiki]] '''Meetings and events''' * [[m:Special:MyLanguage/WikiCite 2025|WikiCite 2025]] will take place from 29–31 August, both online and in-person in Bern, Switzerland. The event's goals are to reconnect communities, institutions, and individuals working with open citations, bibliographic data, and the Wikidata/Wikibase ecosystem. Registration is open and the call for proposals will be announced soon. [https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/KQZUG3ETKLBWPBYSB2YAWZIRPWHS24TG/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:43, 21 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29005283 --> == Wikipedia translation of the week: 2025-31 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Fernando de Noronha Marine National Park]]'''<br /> <small>''([[:pt:Parque Nacional Marinho de Fernando de Noronha]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Baía dos Porcos - Fernando de Noronha (32811749914).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Fernando de Noronha Marine National Park''' (Portuguese: Parque Nacional Marinho de Fernando de Noronha) is a national park in the state of Pernambuco, Brazil. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:40, 28 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29047614 --> == Tech News: 2025-31 == <section begin="technews-2025-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/31|Translations]] are available. '''Weekly highlight''' * The Community Tech team will be focusing on wishes related to Watchlists and Recent Changes pages, over the next few months. They are looking for feedback. Please [[m:Special:MyLanguage/Community Wishlist/Updates#July 24, 2025: Watchlists and Recent Changes pages|read the latest update]], and if you have ideas, please [[m:Special:MyLanguage/Community Wishlist|submit a wish]] on the topic. '''Updates for editors''' * The Wikimedia Commons community has decided to block [[:mw:Special:MyLanguage/Upload dialog|cross-wiki uploads]] to Wikimedia Commons, for all users without autoconfirmed rights on that wiki, starting on August 16. This is because of [[:c:Commons:Cross-wiki media upload tool/History|widespread problems]] related to files that are uploaded by newcomers. Users who are affected by this will get an error message with a link to the less restrictive UploadWizard on Commons. Please help translating the [[:c:Special:MyLanguage/MediaWiki:Abusefilter-disallowed-cross-wiki-upload|message]] or give feedback on the message text. Please also update your local help pages to explain this restriction. [https://phabricator.wikimedia.org/T370598] * On wikis with temporary accounts enabled and Meta-Wiki, administrators may now set up a footer for the Special:Contributions pages of temporary accounts, similar to those which can be shown on IP and user-account pages. They may do it by creating the page named <code dir=ltr>MediaWiki:Sp-contributions-footer-temp</code>. [https://phabricator.wikimedia.org/T398347] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.12|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2025:Wikimania|Wikimania 2025]] will run from August 6–9. The [https://wikimedia.eventyay.com/talk/wikimania2025/schedule/ program is available] for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please [[wmania:Special:MyLanguage/2025:Registration|register]] for a free virtual ticket. For example, you may be interested in technical sessions such as: ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/KFEFVG/ Temporary Accounts: Enhancing privacy for our unregistered editors] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/TVCVAB/ Building a Sustainable Future for Wikimedia Contributors] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/WTRQCJ/ A dozen visions for wikitext!] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/8YKKP9/ Coordinate Across Stakeholders with the Product and Technology Advisory Council] * The [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2025|MediaWiki Users and Developers Conference, Fall 2025]] will be held 28–30 October 2025 in Hanover, Germany. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:27, 29 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29051727 --> == Wikipedia translation of the week: 2025-32 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Xie Zhiliu]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Xie Zhiliu''' (Chinese: 谢稚柳; 1910–1997) was a leading traditional painter, calligrapher, and art connoisseur of modern China. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:21, 4 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29077280 --> == Tech News: 2025-32 == <section begin="technews-2025-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/32|Translations]] are available. '''Updates for editors''' * Editors can now enable the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/User Info|User Info card]]. This feature adds an icon next to usernames on history pages and similar user-contribution log pages. When you tap or click on the icon, it displays data related to that user account such as the number of edits, reverted edits, blocks, and more. It's part of a broader project to make it easier for moderators to evaluate account trustworthiness. The feature can be enabled in [[testwiki:Special:GlobalPreferences#mw-prefsection-rendering|your global preferences]], and later this week it will be available in local preferences. [https://phabricator.wikimedia.org/T386439] * Everybody is invited to share comments on [[m:Special:MyLanguage/CampaignEvents/Collaborative contributions|Collaborative Contributions]], a project recently launched by the [[m:Special:MyLanguage/Connection Team|Connection team]]. The project aims to create a new way to display the impact of collaborative editing activities (such as edit-a-thons, backlog drives, and WikiProjects) on the wikis. Post your comments on the [[m:Talk:CampaignEvents/Collaborative contributions|project talk page]]. [https://phabricator.wikimedia.org/T378035] * Administrators can now define the default block duration for temporary accounts. To do that, they need to create a page named <code dir=ltr>MediaWiki:Ipb-default-expiry-temporary-account</code> and use a value defined in <code dir=ltr>MediaWiki:Ipboptions</code>. This allows administrators to easily block temporary accounts for 90 days, which is functionally equivalent to an indefinite block. The advantage of this solution is that it does not clutter Special:BlockList. [[mw:Special:MyLanguage/Manual:Block and unblock#Default block duration options|More documentation]] is available. [https://phabricator.wikimedia.org/T398626] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Gadgets can now include <code dir=ltr>.vue</code> files. This makes it easier to develop modern user interfaces using [[mw:Vue.js|Vue.js]], in particular using [[mw:Special:MyLanguage/Codex|Codex]], the official design system of Wikimedia. [[wmdoc:codex/latest/icons/overview.html|Codex icons]] can be loaded through the gadget definition. [[mw:Special:MyLanguage/Extension:Gadgets#Pages|The documentation]] has examples. For user scripts that use Vue.js, an [[mw:API:CodexIcons|API module]] now exists to load Codex icons. [https://phabricator.wikimedia.org/T340460][https://phabricator.wikimedia.org/T311099] * Module developers can now use a [[mw:Help:Extension:Translate/Message Bundles/Lua reference|Lua interface]] to simplify the preparation of Lua modules for translation on Meta-Wiki. This improvement makes it easier for translators to find and edit module strings without dealing with raw Lua code. It helps prevent mistakes that could break the module during translation. Module developers and translators are invited to [[commons:File:Translatable modules video demo July 2025.webm|watch the demo video]], read more about [[mw:Special:MyLanguage/Translatable modules|translatable modules]] to understand how it works, refer to Meta-Wiki's [[m:Module:User Wikimedia project|Module:User Wikimedia project]] for example usage, and [[mw:Talk:Translatable modules|share their feedback]] on how well it addresses the challenges in their workflow. The interface still has some performance issues, so it should not be used in widely used modules yet. [https://phabricator.wikimedia.org/T359918] * Developers of external tools that connect to Wikimedia pages must set a user-agent that complies with [[foundation:Special:MyLanguage/Policy:Wikimedia Foundation User-Agent Policy|the user-agent policy]]. This policy will start to be more strongly enforced in August because of external crawlers that are [[diffblog:2025/04/01/how-crawlers-impact-the-operations-of-the-wikimedia-projects/|overusing]] Wikimedia's resources. Tools that are hosted on Wikimedia's Toolforge or Cloud VPS will not be affected by this for now, but should still set a user-agent. [[phab:T400119|More technical details are available]], and related questions are welcome in that task. * Parsoid Read Views is going to be rolling out to some smaller Wikipedias over the next few weeks, following the successful transition of Wikivoyages and Wiktionaries to Parsoid Read Views. For more information, see the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parsoid/Parser Unification]] project page. [https://phabricator.wikimedia.org/project/profile/7694/] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.13|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2025:Wikimania|Wikimania 2025]] will run from August 6–9. The [https://wikimedia.eventyay.com/talk/wikimania2025/schedule/ program is available] for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please [[wmania:Special:MyLanguage/2025:Registration|register]] for a free virtual ticket. For example, you may be interested in technical sessions such as: ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/GEH9DH/ Wikimedia’s knowledge infrastructure in a changing internet: Establishing sustainable pathways for content reuse] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/7ELN9Q/ Wikifunctions is coming soon to a wiki near you!] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/ZMGVJV/ Shaping the Future of Wikipedia’s Reader Experience] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/KCKTFZ/ Making Wikipedia More Readable: What Comes Next] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:41, 5 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29083927 --> == Wikipedia translation of the week: 2025-33 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lethocerus patruelis]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lethocerus patruelis.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Lethocerus patruelis''''' is a giant water bug in the family Belostomatidae. It is native to southeastern Europe, through Southwest Asia, to Pakistan, India and Burma. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:20, 11 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29085671 --> == Tech News: 2025-33 == <section begin="technews-2025-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/33|Translations]] are available. '''Updates for editors''' * The WikiEditor toolbar now includes [[mw:Special:MyLanguage/Help:Extension:WikiEditor#Keyboard shortcuts|its keyboard shortcuts]] in the tooltips for its buttons. This will help to improve the discoverability of this feature. [https://phabricator.wikimedia.org/T400583] * The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] published a set of [[m:Special:MyLanguage/Product and Technology Advisory Council/August 2025 draft PTAC proposals for feedback|proposed experiments]] the Wikimedia Foundation can try to improve communication with community. Feedback on the proposals are welcomed until August 22 on [[m:Talk:Product and Technology Advisory Council/August 2025 draft PTAC proposals for feedback|this talk page]]. * The search bar on the Minerva skin (mobile) has been updated to use the same type-ahead search component that is used on the Vector 2022 skin. There are no changes in search functionality but there are minor visual changes. Specifically, the close-search button has been changed from an "X" to a back arrow. This helps to distinguish it from the other "X" button that is used to clear any text. [https://phabricator.wikimedia.org/T393944] * Editors on some wikis will see a new toggle for "Group results by page" on watchlist, related changes, and recent changes pages. This is [[mw:Special:MyLanguage/Moderator Tools/Watchlist/Experiment|an A/B experiment]] that is planned to start on August 11, and will run for 3–6 weeks on the Bengali, Chinese, Czech, French, Greek, Portuguese, and Urdu Wikipedias. The experiment will examine how making this feature more discoverable might affect editors' ability to find the edits they are looking for. [https://phabricator.wikimedia.org/T396789] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The multiwiki datasets of [[:wikt:en:Module:Unicode data|Unicode data]] have been moved to [[c:Category:Unicode Module Datasets|Category:Unicode Module Datasets]] on Wikimedia Commons, to follow the idea of "One common data source, multiple local wikis". Most wikis have been updated to use the Commons version. You can ask questions at [[c:Category talk:Unicode Module Datasets|the talkpage]]. [https://en.wiktionary.org/wiki/Module_talk:Unicode_data#Data_from_commons] * Lua code can add warnings when something is wrong, by using the <code dir=ltr>mw.addWarning()</code> function. It is now possible to add more than one warning, instead of new warnings replacing old ones. If you maintain a Lua module that used warnings, you should check it still works as expected. [https://phabricator.wikimedia.org/T398390] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.14|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:30, 11 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29106516 --> == Wikipedia translation of the week: 2025-34 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ikiza]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:CIA map of Burundi and surrounding countries during 1972 killings.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Ikiza''' (variously translated from Kirundi as the Catastrophe, the Great Calamity, and the Scourge), or the Ubwicanyi (Killings), was a series of mass killings—often characterised as a genocide—which were committed in Burundi in 1972 by the Tutsi-dominated army and government, primarily against educated and elite Hutus who lived in the country. Conservative estimates place the death toll of the event between 100,000 and 150,000 killed, while some estimates of the death toll go as high as 300,000. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 18 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29115447 --> == Tech News: 2025-34 == <section begin="technews-2025-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/34|Translations]] are available. '''Updates for editors''' * Later this week, people who are logged-in and have the "[[mw:Special:MyLanguage/Talk pages project/Feature summary|Discussion tools]]" [[Special:Preferences#mw-prefsection-betafeatures|Beta Feature]] enabled will gain the ability to "Thank" individual comments directly from talk pages, rather than needing to navigate to page history. [[mw:Special:MyLanguage/Talk pages project/Feature summary#Comment actions|Learn more about this feature]]. [https://phabricator.wikimedia.org/T400849] * An A/B test comparing two versions of the desktop donate link launched on testwiki on 12 August and on English Wikipedia 14 August for 0.1% of logged out users on the desktop site. The experiment will run for three weeks, ending on 12 September. [https://phabricator.wikimedia.org/T395716] * An A/A test to measure the baseline for reader retention was launched 12 August using [[wikitech:Experimentation Lab|Experimentation Lab]]. This measures the percentage of users who revisit a wiki after their initial visit over a 14-day period. No visual changes are expected. The experiment will run through 31 August. [https://phabricator.wikimedia.org/T399227] * Five new wikis have been created: ** a {{int:project-localized-name-group-wikisource/en}} in [[d:Q34057|Tagalog]] ([[s:tl:|<code>s:tl:</code>]]) [https://phabricator.wikimedia.org/T388639] ** a {{int:project-localized-name-group-wikisource/en}} in [[d:Q36213|Madurese]] ([[s:mad:|<code>s:mad:</code>]]) [https://phabricator.wikimedia.org/T391747] ** a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q3450749|Rakhine]] ([[w:rki:|<code>w:rki:</code>]]) [https://phabricator.wikimedia.org/T392490] ** a {{int:project-localized-name-group-wikibooks/en}} in [[d:Q13324|Minangkabau]] ([[b:min:|<code>b:min:</code>]]) [https://phabricator.wikimedia.org/T395452] ** a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q7598268|Standard Moroccan Amazigh]] ([[wikt:zgh:|<code>wikt:zgh:</code>]]) [https://phabricator.wikimedia.org/T399684] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:46}} community-submitted {{PLURAL:46|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.15|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W34"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:39, 19 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29127690 --> == Wikipedia translation of the week: 2025-35 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Corallite]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Recent azooxanthellate Scleractinia (Cnidaria, Anthozoa) - ZooKeys-227-001-g004.jpeg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''corallite''' is the skeletal cup, formed by an individual stony coral polyp, in which the polyp sits and into which it can retract. The cup is composed of aragonite, a crystalline form of calcium carbonate, and is secreted by the polyp. Corallites vary in size, but in most colonial corals they are less than 3 mm (0.12 in) in diameter. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 25 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29115447 --> == Tech News: 2025-35 == <section begin="technews-2025-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/35|Translations]] are available. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Template authors can now use additional CSS properties, since the CSS sanitizer used by [[mw:Special:MyLanguage/Help:TemplateStyles|TemplateStyles]] was updated. For example: <code>width: fit-content</code>; <code>ruby-align</code>; relative units such as <code>lh</code>; and custom strings in <code>list-style-type</code>. These improvements are a [[m:Special:MyLanguage/Community Wishlist/Wishes/Allow use of modern CSS in templates by updating the TemplateStyles CSS sanitizer|Community Wishlist wish]]. [https://phabricator.wikimedia.org/T271958][https://phabricator.wikimedia.org/T277755][https://phabricator.wikimedia.org/T293633][https://phabricator.wikimedia.org/T295088][https://phabricator.wikimedia.org/T326906][https://phabricator.wikimedia.org/T340057][https://phabricator.wikimedia.org/T360725][https://phabricator.wikimedia.org/T371809][https://phabricator.wikimedia.org/T375344][https://phabricator.wikimedia.org/T394619] * On large wikis, the default time period to display edits from, within the Special:RecentChanges page, has been changed from 7 days to 1 day. This is part of a performance improvement project. This should have no user-facing impact due to the quantity of edits on these wikis. [https://phabricator.wikimedia.org/T399455] * Administrators can now access the [[{{#special:BlockedExternalDomains}}]] page from the [[{{#special:CommunityConfiguration}}]] list page. This makes it easier to find. [https://phabricator.wikimedia.org/T393240] * Wikimedia Commons videos were not shown in the Videos tab in Google Search. The problem was investigated and reported to Google who have now fixed the issue. [https://phabricator.wikimedia.org/T396168][https://meta.wikimedia.org/wiki/Community_Wishlist/Wishes/Do_something_about_Google_%26_DuckDuckGo_search_not_indexing_media_files_and_categories_on_Commons] * One new wiki has been created: a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q33014|Betawi]] ([[wikt:bew:|<code>wikt:bew:</code>]]) [https://phabricator.wikimedia.org/T402130] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:39}} community-submitted {{PLURAL:39|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Two fields of the [[mw:Special:MyLanguage/Manual:Recentchanges table|recentchanges database table]] are being removed. <code>rc_new</code> and <code>rc_type</code> are being removed in favor of <code>rc_source</code>. Queries to these older fields will start to fail starting this week and developers should use <code>rc_source</code> instead. These older fields were deprecated over 10 years ago and should not be in use. This is part of work to improve the performance and stability of queries to the recentchanges table. [https://phabricator.wikimedia.org/T400696] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.16|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/July|Language and Internationalization Newsletter]] is now available. This edition includes: support for new languages in MediaWiki and translatewiki; the start of the Language Onboarding and Development project to help support the growth of new and small wikis; updates on research projects; and more. '''Meetings and events''' * The next [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Community meetings#29 August 2025|Language Community Meeting]] is happening soon, August 29th at [https://zonestamp.toolforge.org/1756479600 15:00 UTC]. This week's meeting will cover: the Avro keyboard developers from Wikimedia Bangladesh, who were recently awarded a national award for their contributions to this keyboard; and other topics. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:13, 26 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29175124 --> == Wikipedia translation of the week: 2025-36 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Diksam Plateau]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Dixam plateau (6407168437).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Diksam Plateau''' or Dixam Plateau (Arabic: دكسم) is a limestone plateau in Socotra, Yemen. The Firmihin forest, located east of the Dirhur canyon within the plateau, has the highest concentration of Dragon's Blood Trees on the entire island. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:40, 1 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29195081 --> == Tech News: 2025-36 == <section begin="technews-2025-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/36|Translations]] are available. '''Weekly highlight''' * The Editing team wants to compile a list of templates, jargon terms, and policies used in edit summaries when a copyright violation is removed. This will help them identify the number of edits reverted due to copyright issues. We invite community members from the following Wikis to list these terms in [[Phab:T402601|T402601]], or to share their list with [[User:Trizek (WMF)|Trizek_(WMF)]]: {{int:project-localized-name-arwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-idwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-plwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ukwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-viwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zhwiki/en}}. This project is open until September 9th 2025. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] has been enabled for all Wikisources. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. The extension has three features: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Special:MyLanguage/Connection Team/Invitation list|Invitation List]]. To request the extension for your wiki, visit the Deployment information page. [https://meta.wikimedia.org/wiki/CampaignEvents/Deployment_status#How_to_Request_the_CampaignEvents_Extension_for_your_wiki] * The lists in the footer of the editing interface, such as "Templates used on this page," will now be organized into columns when there is enough space. This enhancement minimizes scrolling when editing lengthy articles on Wikipedia. [https://phabricator.wikimedia.org/T401066] * On September 3rd, 2025 we will increase the sampling percentages of our [[mw:Special:MyLanguage/Moderator Tools/Watchlist/Experiment#Scope of the experiment|group by toggle experiment]] of the <code>Special:RecentChanges</code>, <code>Special:Watchlist</code>, and <code>Special:RelatedChanges</code> pages on the Chinese, French, and Portuguese Wikipedias to 100 percent, allowing more editors to be part of this experiment. This adjustment is intended to ensure we have sufficient data to make informed decisions when evaluating the experiment results. [https://phabricator.wikimedia.org/T402958][https://phabricator.wikimedia.org/T396789] * Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading on English Wikipedia beginning the week of September 22. The feature will be available on both desktop and mobile. All non-English wikis received this change in June and July. The goal is to make it easier for users to find articles. [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments/Search Suggestions|Learn more]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:37}} community-submitted {{PLURAL:37|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.17|MediaWiki]] '''In depth''' * Wikifunctions now has a new capability called "lightweight enumeration types", an enumeration type is simply a fixed set of values that's in the type's definition. This capability makes it quick and easy to define such a type, and allows for the reuse of values that are already present in Wikidata. Here is [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-07-19|a newsletter]] to learn more. * The latest [[mw:Special:MyLanguage/Readers/Newsletter updates#August 2025: Newsletter #1|Readers Newsletter]] is now available. This edition includes: the formation of two new teams — Reader Growth and Reader Experience; insights into declining pageviews and account creations; highlights from the Wikimania Nairobi panel on improving the reading experience; upcoming experiments to engage new and existing readers; and more. '''Meetings and events''' * Spotlight on some Wikimania 2025 Sessions: ** Identifying AI-generated text by searching for ISBNs whose checksums fail: Mathias Schindler of WMDE [https://www.youtube.com/watch?v=Dw9o8Lsl974&t=15910s shared tools to help communities search for these]. ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/TCHZKH/ La durabilité du mouvement Wikimedia face aux défis actuels et futurs]: This session explored how Wikimedia can stay a trusted source of knowledge in the age of generative AI, information overload, and disinformation. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:51, 1 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29196010 --> == Wikipedia translation of the week: 2025-37 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Ttongsul]]'''<br /> <small>''([[:ja:トンスル]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Ttongsul (imitation).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''ttongsul''' (똥술), o vino di feci, è una tradizionale preparazione medicinale coreana con gradazione alcolica al 9% a base di feci, solitamente umane e preferibilmente di bambino. Nato probabilmente traendo spunto dalla medicina tradizionale cinese, nelle credenze popolari il vino di feci avrebbe proprietà benefiche per molti tipi di malesseri: sarebbe un rimedio per dolori muscolari, ustioni, infiammazioni, epilessia e fratture ossee. Sebbene alcuni media occidentali abbiano in passato riportato che questa bevanda sia diffusa tra la popolazione coreana, al giorno d'oggi un numero molto limitato di persone ne fa uso, dopo aver subito un declino di popolarità nei secoli scorsi, tanto che la maggioranza dei giovani coreani non ne ha mai sentito parlare. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:28, 8 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29195081 --> == Tech News: 2025-37 == <section begin="technews-2025-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/37|Translations]] are available. '''Weekly highlight''' * The Editing team is working on a new check: [[mw:Special:MyLanguage/Paste check|Paste check]]. This check informs newcomers who paste text into Wikipedia that the content might not be accepted. This check is an effort to increase the likelihood that the new content people are adding to Wikipedia is aligned with the Movement's commitment to offering information under a free content license. This check will soon be tested at a few wikis. If your community is interested in this test, please [[phab:T403680|tell us in this task]], or [[mw:Talk:Edit check|contact the team]]. '''Updates for editors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Later this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will be able to use a [[w:en:Lint (software)|linting tool]] to see errors or other potential problems in wikitext in real time. See the [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|help page for more information]]. [https://phabricator.wikimedia.org/T381577] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] When browsing a wiki (like <code dir=ltr>en.wikipedia.org</code>), the software responds in one of two ways: a desktop page, or a redirect to a mobile version on an "m" domain (like <code dir=ltr>en.m.wikipedia.org</code>). Over the next three weeks, MediaWiki will start displaying the mobile version to mobile devices directly on the standard domain, without this redirect. This change does not affect existing m-dot URLs, or the "Desktop view" opt-out. [[mw:Requests for comment/Mobile domain sunsetting/2025 Announcement|Learn more]]. [https://phabricator.wikimedia.org/T214998] * When an edit changes the categories of a page, the changes to the category membership counts are now happening asynchronously. This improves the speed of saving edits, especially when moving many pages to or from the same category, and reduces the risk of site outages, but it means that the counts can show outdated information for a few minutes. [https://phabricator.wikimedia.org/T365303] * Edits on Wikidata to qualifiers (properties and values) and references (properties and values) in a Wikidata item statement will now not add entries to the RecentChanges or Watchlist pages on all other Wikis. This is a temporary change to improve performance while other solutions are created. Wikidata's own pages remain unchanged. [[m:Wikidata For Wikimedia Projects/Reduce change propagation noise#Phase 1: Turn off (temporarily) Qualifiers and References Wikidata edits to the Recent Changes tables|Learn more]]. [https://phabricator.wikimedia.org/T401286][https://phabricator.wikimedia.org/T400698] * Japanese-language wikis have had a major upgrade to the way that search works. The new search should generally give more accurate and more relevant search results. [https://phabricator.wikimedia.org/T318269] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.18|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:15, 9 September 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29238161 --> == Wikipedia translation of the week: 2025-38 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pak Kum-chol]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pak Kum-chol in 1961 (cropped).jpg|center]] <div style="text-align:left; padding: .4em;"> '''Pak Kum-chol''' was a North Korean politician. Having been a guerrilla during the anti-Japanese struggle, he became a high-ranking politician after the liberation of Korea. Pak aligned himself with his former guerrilla brothers in arms from the Kapsan Operation Committee to form a faction within the ruling Workers' Party of Korea (WPK) called the "Kapsan faction". This faction sought to replace Kim Il Sung with Pak. Kim retaliated by purging the faction in 1967 in what is known as the Kapsan faction incident. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 15 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29249252 --> == Tech News: 2025-38 == <section begin="technews-2025-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/38|Translations]] are available. '''Updates for editors''' * References lists that are made using the <code dir=ltr><nowiki><references/></nowiki></code> [[mw:Special:MyLanguage/Help:Cite#references-tag|tag]] will now automatically display with columns in Vector 2022 when readers are using its 'standard' settings for text-size and page-width. [https://phabricator.wikimedia.org/T334941] * Starting in the week of October 6, on [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/small.dblist|small wikis]] and [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/medium.dblist|medium wikis]] that have the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] enabled, all autoconfirmed users will be able to use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] as an organizer. No changes will be made for [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/large.dblist|large wikis]] unless requested in Phabricator. This change is being made to make it easier for more people to use Event Registration, especially on wikis that are less likely to have policies related to the Event Organizer right. [[m:Special:MyLanguage/CampaignEvents/Proposal to grant autoconfirmed users on small and medium wikis the organizer access to the event registration tool|Learn more]]. * Users that search using regular expressions (regex) can now use additional features including: ** for the <code dir=ltr>intitle:</code> keyword: [[mw:Special:MyLanguage/Help:CirrusSearch#Metacharacters|metacharacters]] for start-of-line (<code dir=ltr>^</code>) and end-of-line (<code dir=ltr>$</code>) anchors [https://phabricator.wikimedia.org/T317599] ** for both <code dir=ltr>intitle:</code> and <code dir=ltr>insource:</code> keywords: shorthand [[mw:Special:MyLanguage/Help:CirrusSearch#Character_Classes|character classes]] for digits (<code dir=ltr>\d</code>), whitespace (<code dir=ltr>\s</code>), and word characters (<code dir=ltr>\w</code>); and [[mw:Special:MyLanguage/Help:CirrusSearch#Escape codes|escape codes]] for line feed (<code dir=ltr>\r</code>), newline (<code dir=ltr>\n</code>), tab (<code dir=ltr>\t</code>), and unicode (e.g. <code dir=ltr>\uHHHH</code>). [https://phabricator.wikimedia.org/T403212] * When you search for text that looks like an IP, the system will now show search results. It used to take you to the contributions for that IP instead of showing search results. [https://phabricator.wikimedia.org/T306325] * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on September 24. This is planned at [https://zonestamp.toolforge.org/1758726000 15:00 UTC]. This is for the datacenter server switchover backup tests which happen twice a year. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the background and details of this process on the Diff blog]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that affected users who used the page-tabs to switch from wikitext editing of a section into the visualeditor. [https://phabricator.wikimedia.org/T401043] '''Updates for technical contributors''' * The MediaWiki Interfaces team is redesigning the Wikimedia REST API Sandbox with Codex. If you have feedback on improvements for the API documentation or what makes developer experiences smooth (or frustrating), you’re invited to [https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ2aZzbXeQvjOF7gB1fJXiwAYemQjKf4sXNaRODPA7_obFyNBwkzNkoVCoTF-aeov89kIjXHbCQm join an upcoming discovery interview], or [[mw:MediaWiki Interfaces Team/Developer Feedback/Wikimedia Web APIs|leave feedback onwiki]]. [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/C4FBAOA57PH6G5ORVMAUF5TGYBLZDU5Q/|Learn more]]. * Edits to Wikidata aliases (an alternative name for an item or a property) will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. [[m:Wikidata For Wikimedia Projects/Reduce change propagation noise#Phase 1: More granular Alias tracking|Learn more]]. [https://phabricator.wikimedia.org/T401288] * The new [https://www.unicode.org/versions/Unicode17.0.0/ Unicode 17.0] version has been released. The [[:c:Category:Unicode Module Datasets|datasets on Commons]] for the [[:d:Q39301585|Module:Unicode data]] have been updated. Wikipedias that do not use the Commons datasets should either update their own data or switch to the Commons datasets. * Users of the [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] Structured Contents endpoints can now access [https://enterprise.wikimedia.com/blog/parsed-wikipedia-tables/ Parsed Tables]. The new Parsed Tables feature extracts and represents Wikipedia tables in structured JSON. This improves machine accessibility as part of the [https://enterprise.wikimedia.com/api/structured-contents/ Structured Contents initiative]. Structured Contents output is freely available through the [https://enterprise.wikimedia.com/docs/on-demand/#article-structured-contents-beta On-demand API], or through Wikimedia Cloud Services. * A [https://www.kaggle.com/datasets/wikimedia-foundation/english-wikipedia-people-dataset dataset of English Wikipedia biographical information] from [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] has been published on Kaggle, for evaluation and research. This provides structured data from more than 1.5 million biographies, including birth and death dates, education, affiliations, careers, awards, and more (from a June 2024 snapshot). * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.19|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2026:Scholarships|Scholarship applications]] for Wikimania 2026 in Paris, France, are open until October 31. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:08, 15 September 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29263921 --> == Wikipedia translation of the week: 2025-39 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Federation of Central America (1921–1922)]]'''<br /> <small>''([[:es:Federación de Centro América (1921-1922)]])&#32;([[:ar:اتحاد أمريكا الوسطى (1921-1922)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Central America's Northern Triangle (orthographic projection).png|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Federation of Central America''' (Spanish: Federación de Centro América)[1] was a short-lived federal republic that existed in Central America between 1921 and 1922. The federation consisted of the Central American nations of El Salvador, Guatemala, and Honduras. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:45, 22 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29311347 --> == Tech News: 2025-39 == <section begin="technews-2025-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/39|Translations]] are available. '''Weekly highlight''' * [https://zonestamp.toolforge.org/1758726000 On September 24th at 15:00 UTC], all Wikimedia sites users will experience a brief read-only period due to a scheduled [[m:Special:MyLanguage/Tech/Server switch|datacenter server switchover]]. The Wikimedia Foundation's Site Reliability Engineering (SRE) team will redirect all traffic from one primary server to its backup. You can listen to the switchover using the [http://listen.hatnote.com/ "Listen to Wikipedia"] tool, where you will hear edits stop for a few minutes during the read-only phase, then resume. This twice-yearly datacenter server switchover ensures reliability by testing the backup datacenter, so that our sites can stay online even if the primary datacenter fails. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the process on the Diff blog]]. '''Updates for editors''' * Editors of [[f:Special:Mylanguage/Wikifunctions:Status updates/2025-09-12#Next round of Wiktionaries to receive embedded Wikifunctions calls|60 more Wiktionaries]] will soon be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them into their pages. A function takes one or more inputs and transforms them into a desired output, like adding numbers, converting miles to meters, calculating elapsed time, or declining a word into a case. They will join the other [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-29#Wikifunctions available on 65 Wiktionaries|65 Wiktionary language editions]], which already have access to embedded Wikifunctions calls. Later this year, plans are in place to expand to more Wiktionaries and the Incubator. * A new [[mw:Special:MyLanguage/Help:Magic words#Technical metadata of another page|parser function]] has been added: <code><nowiki>{{#contentmodel}}</nowiki></code>. Template editors and admins can use it to get the localized or canonical name of the [[mw:Special:MyLanguage/Help:ChangeContentModel|content model]] of a specific page. The function makes it easier to create and edit system messages, such as ''MediaWiki:editinginterface'', even when you switch types of pages, like wiki, JavaScript, CSS or JSON page. [https://phabricator.wikimedia.org/T328254] * Adding or editing a <code>DISPLAYTITLE</code> for an article using VisualEditor will no longer be broken. Editors who use VisualEditor mode to modify the <code><nowiki>{{DISPLAYTITLE}}</nowiki></code> would no longer have the literal text "DISPLAYTITLE" or its localized variant added to their articles. A list of pages that may have been affected and might need cleanup is documented in [[phab:P83438|this ticket]]. * Beta users of the Wikipedia Android app can now try the redesigned [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Activity Tab Experiment|Activity tab]], which replaces the Edits tab. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:12}} community-submitted {{PLURAL:12|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.20|MediaWiki]] '''In depth''' * Wikifunctions users can now import many essential facts involving [[f:Special:MyLanguage/Z6011|geo-coordinates]], [[f:Special:MyLanguage/Z6010|quantities]] and [[f:Special:MyLanguage/Z6064|time]] values from Wikidata. This is made possible by the creation of Wikifunctions types for these values, which makes them available for use by functions in Wikifunctions. Learn more about how this works in [[c:File:ImportingWikidataDatatypesIntoWikifunctions.webm|this video]] and Wikifunctions' [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-01#News in Types I: Wikidata quantity|August 1 newsletter]] (for quantities) and [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-22#News in Types: Wikidata geo-coordinate|August 22 newsletter]] (for geo-coordinates). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:56, 22 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29305556 --> == Wikipedia translation of the week: 2025-40 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Palazzo delle Poste (Latina)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Postelittoria2.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''Palazzo delle Poste''', fino al 1945 Ricevitoria Postelegrafonica di Littoria, è un edificio postale di Latina, situato in piazzale dei Bonificatori. Costruito nel 1932 in stile razionalista con influenze futuriste, riscontrabili nell'utilizzo di ampie superfici vetrate e di volumi verticali, oltre che per la presenza di l’utilizzo di materiali e scelte di design molto in voga all'epoca come, come i mattoni a vista, il travertino di Tivoli e l'Anticorodal (una lega di alluminio), ospita l'ufficio postale Latina Centro. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:58, 29 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-40 == <section begin="technews-2025-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/40|Translations]] are available. '''Weekly highlight''' * A major software upgrade has been made to [[phab:|Phabricator]]. The update introduces performance improvements, a refreshed search interface, enhancements to Maniphest task search, updates to user profile pages and project workboards, new Herald automation features, as well as general text input, mobile experience improvements and more. [https://phabricator.wikimedia.org/phame/post/view/321/iterative_improvements_september_2025/] '''Updates for editors''' * The Community Tech team will release the new Community Wishlist extension on October 1, that will improve the way wishes will be submitted. The new extension will allow users to add tags to their wishes to better categorise them, and (in a future iteration) to filter them by status, tags and focus areas. It will also be possible to support individual wishes again, as requested by the community in many instances. The old system will be retired. There will be a brief period of downtime while the extension is deployed and wishes are migrated to the new system. You can read more about this [[:m:Special:MyLanguage/Community Wishlist/Updates|in the latest update]] or you can consult the [[:mw:Special:MyLanguage/Help:Extension:CommunityRequests|current documentation on MediaWiki]]. * As announced [[diffblog:2025/09/02/better-detecting-bots-and-replacing-our-captcha/|on Diff blog]], the production trial of the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/hCaptcha|hCaptcha]] service for bot detection has begun. The trial is currently using hCaptcha to protect account creation on Chinese, Persian, Portuguese, Indonesian, Japanese, and Turkish Wikipedias, where it will replace our existing [[mw:Special:MyLanguage/Extension:ConfirmEdit#FancyCaptcha|CAPTCHA]] (FancyCaptcha). The goal with the trial is to better block bots while also improving usability and accessibility for users who encounter CAPTCHA challenges. * The [[mw:Special:MyLanguage/Extension:CampaignEvents|CampaignEvents]] extension has been [[m:Special:MyLanguage/CampaignEvents/Deployment status|deployed]] to Wikimedia Commons. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. On Commons, anyone who is a registered user can use it as an event participant. To use it as an organizer, someone needs to have the [[c:Special:MyLanguage/Commons:Event organizers|event organizer right]]. * [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new feature to re-use references with different details has been released to German Wikipedia. You can [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#test|test the feature]] on testwiki or [https://en.wikipedia.beta.wmcloud.org/wiki/Sub-referencing on betawiki] as well. Please share your thoughts on [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Templates used in sub-references|using templates in sub-references]] or [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Pilot wikis|volunteer to become a pilot wiki]]. * On wikis using the [[mw:Special:MyLanguage/Help:Growth/Mentorship|Mentorship]] system, communities can now opt experienced editors out of Mentorship through [[{{#special:CommunityConfiguration/Mentorship}}]]. Within this setting, communities may define thresholds, based on edit count and account age, to decide when an editor is considered experienced enough to no longer receive Mentorship. [https://phabricator.wikimedia.org/T403563] * The Editing Team and the Machine Learning Team are working on a new check for newcomers: [[mw:Special:MyLanguage/Edit check/Tone Check|Tone check]]. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Tone language model for the following languages: Arabic, Czech, German, Hebrew, Indonesian, Dutch, Polish, Russian, Turkish, Chinese, Farsi, Italian, Norwegian, Romanian and Latvian. Users from these wikis interested in reviewing this model are [[mw:Special:MyLanguage/Edit_check/Tone_Check/Model_evaluation|invited to sign up at MediaWiki.org]]. The deadline to sign up is on October 3, which will be the start date of the test. * The rollout of [[:mw:Special:MyLanguage/Help:Manage blocks|multiblocks]] had the side effect that non-active block logs may have been shown on {{#special:Contributions}} and on blocked users' user and user_talk pages. This issue will be fully resolved in a few days. As part of the fix, [{{fullurl:Special:Allmessages|prefix=sp-contributions-blocked-notice}} messages prefixed with <code>sp-contributions-blocked-notice</code>] will be removed and replaced with [{{fullurl:Special:Allmessages|prefix=blocked-notice-logextract}} those prefixed with <code>blocked-notice-logextract</code>] in a few weeks. Please help translate the new messages and update any local overrides if needed. * There was a bug with links added using visual editor if they included characters such as <code dir=ltr><nowiki>[ ] |</nowiki></code> after the fragment identifier (<code><nowiki>#</nowiki></code>). They were not encoded properly creating an incorrect link. This has been fixed. [https://phabricator.wikimedia.org/T404823] * One new wiki has been created: a {{int:project-localized-name-group-wikiquote/en}} in [[d:Q9237|Malay]] ([[q:ms:|<code>q:ms:</code>]]) [https://phabricator.wikimedia.org/T404698] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/User Info|User Info Card]] now displays currently active global lock/blocks. [https://phabricator.wikimedia.org/T401128] '''Updates for technical contributors''' * Later this week, editors using Lua modules will be able to use the <code>[[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#mw.title.newBatch|mw.title.newBatch]]</code> function to look up the existence of up to 25 pages at once, in a way that only increases the [[mw:Special:MyLanguage/Manual:Parser functions#Expensive parser functions|expensive function]] count once. * A new [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|Unsupported Tools Working Group]] has been formed as part of ongoing efforts to collectively determine technical work priorities, similar to the [[m:Special:MyLanguage/Product and Technology Advisory Council|Product & Technology Advisory Council]] (PTAC). The working group will help prioritize and review requests for support of unmaintained extensions, gadgets, bots, and tools. For the first cycle, the group will be prioritizing an unsupported Wikimedia Commons tool. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.21|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:54, 29 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29355230 --> == Wikipedia translation of the week: 2025-41 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Majed Abu Maraheel]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Majed Abu Maraheel''' was a Palestinian long-distance runner, football player, security officer, and athletics coach, who was the first Palestinian to compete at the Olympic Games. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:48, 6 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-41 == <section begin="technews-2025-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/41|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Help:Edit check#paste|Paste Check]] is a new Edit Check feature to help avoid and fight copyright violations. When editors paste text into an article, Paste Check prompts them to confirm the origin and licensing of the content. Starting Wednesday, 8 October, [[phab:T403680|22 wikis will test Paste Check]]. Paste Check will help new volunteers understand and follow the policies and guidelines necessary to make constructive contributions to Wikipedia projects. '''Updates for editors''' * Mobile devices will receive mobile articles directly on the standard domain (like <code>en.wikipedia.org</code>), instead of via a redirect to an "m" domain (like <code>en.m.wikipedia.org</code>). This change improves performance. This week it will be enabled on Wikipedias. The existing mobile URLs and the "Desktop view" opt-out remain available. [[mw:Requests for comment/Mobile domain sunsetting/2025 Announcement|Learn more]]. [https://phabricator.wikimedia.org/T214998] * New [[mw:Special:MyLanguage/Help:CirrusSearch#creationdate and lasteditdate|date filters]], <code dir=ltr>creationdate:</code> and <code dir=ltr>lasteditdate:</code>, are now available in the wiki search engine. This allows users to filter search results by a page's first or last revision date. The filters support comparison operators (e.g. <code dir=ltr>>2024</code>) and relative dates (e.g. <code dir=ltr>today-1d</code>), making it easier to find recently updated content or pages within specific age ranges. [https://phabricator.wikimedia.org/T403593] * [[f:|Wikifunctions]] now supports rich text in embedded calls across the 150 wikis where it's enabled. To showcase this, the team created a [[f:Z26333|Latin declination table]] that Wiktionary editors can use to automatically generate noun forms, producing clear, formatted results — see an [[f:Wikifunctions:Embedded function calls/Wiktionary tables demonstration|example output]]. If you need any help or have any feedback, please [[f:Wikifunctions:Project chat|contact the Wikifunctions Team]]. [https://phabricator.wikimedia.org/T397402] * An edit link will now appear inside the categories box on article pages for logged in users, which will directly launch the VisualEditor category dialog. [https://phabricator.wikimedia.org/T291691] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:34}} community-submitted {{PLURAL:34|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a problem downloading pdf files last week and that has been resolved. [https://phabricator.wikimedia.org/T405957] '''Updates for technical contributors''' * The field <code dir=ltr>rev_sha1</code> in the revision database table is being removed in favor of <code dir=ltr>content_sha1</code> in the content database table. See [https://lists.wikimedia.org/hyperkitty/list/cloud@lists.wikimedia.org/thread/2D2M3SP4WHR6BXXKTZ2PBLZQYR3EGQVR/ the announcement] for more information. * The [[mw:Special:MyLanguage/Reading/Web|Reader Experience team]] will roll out [[w:en:Light-on-dark color scheme|Dark Mode]] user interface on all Wikimedia sites on October 29, 2025. All anonymous users of Wikimedia sites will have the option to activate a color scheme that features light-colored text on a dark background. This is designed to provide a more comfortable reading experience, especially in low-light situations. Template authors and technical contributors are encouraged to [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-04|learn how to make pages ready for Dark mode]] and address any compatibility issues found in templates in their wiki before the enablement. Please contact the Web team for questions or any support on [[mw:Talk:Reading/Web/Accessibility for reading#|this talk page]] before the enablement. [https://phabricator.wikimedia.org/T395628] * Starting on Monday, October 6, API endpoints under the <code>rest.php</code> path will be rerouted through a new internal API Gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the [[phab:tag/serviceops/|Service Ops team board]]. [https://phabricator.wikimedia.org/T400130] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:24, 6 October 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29400897 --> == Wikipedia translation of the week: 2025-42 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Abortion in Eritrea]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In Eritrea, abortion is banned except on the grounds of pregnancy from rape or incest, pregnancy of a minor, or risk to physical or mental health. Legal abortions require medical or judicial approval. Prior to Eritrea's independence, it applied Ethiopia's abortion law of the 1950s, which banned abortion unless life-saving. After independence, the 1991 penal code adapted this law to lift punishments on abortions on the grounds of rape, incest, or risk to life or health, but legal abortions did not exist in effect. The penal codes of 2001 and 2015 required physicians to prove health grounds for abortion. Unsafe abortion is common and contributes to maternal mortality in Eritrea. Post-abortion care is unavailable in some regions. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:06, 13 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-42 == <section begin="technews-2025-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/42|Translations]] are available. '''Weekly highlight''' * Last week, improvements to account security and two-factor authentication (2FA) features were enabled across all wikis. These changes include user interface improvements for [https://auth.wikimedia.org/metawiki/wiki/Special:AccountSecurity Special:AccountSecurity], the support of multiple 2FA methods via authenticator apps and portable security keys (previously users could only enable one method), and a new Recovery Codes module which facilitates fewer account lockouts due to lost two-factor apps and devices. As part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project, work is continuing through the rest of 2025 on further user experience improvements, and support for passkeys as an alternate second factor. '''Updates for editors''' * Another part of the Account security project is making 2FA generally available to all users. Along with editors with advanced privileges, such as administrators and bureaucrats, 40% of editors now have access to 2FA. You can check if you have access at [https://auth.wikimedia.org/metawiki/wiki/Special:AccountSecurity Special:AccountSecurity]. Instructions for activation are on the linked page. The plan is to continue increasing availability if it is determined that the user support capabilities are able to support global usage. [https://phabricator.wikimedia.org/T400579] * This week, users at wikis where talk page [[mw:Special:MyLanguage/Talk pages project/Usability|Usability Improvements]] are already available by default (everywhere ''except'' the 12 wikis listed in [[phab:T379264|T379264]]) will gain the ability to Thank a comment directly from the talk page it appears on. Before this change, Thanking could only be done by visiting the revision history of the talk page. You can [[diffblog:2025/10/13/revolutionizing-gratitude-a-new-era-of-thanking-comments/|learn more about this change]]. [https://phabricator.wikimedia.org/T366095] * Users who have not [[Special:Preferences#mw-prefsection-personal-email|verified their email address]] will soon be receiving monthly Notification reminders to do so. This is because users who have verified their email can more easily recover their account. These reminders will not be sent if the user is inactive or removes the unverified email from their account. [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Email_confirmation][https://phabricator.wikimedia.org/T58074] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a fix was made for an occasional error with saving translated paragraphs in the Content Translation tool, and the related error messages are now easier to see. [https://phabricator.wikimedia.org/T376531] '''Updates for technical contributors''' * The Unsupported Tools Working Group has chosen [[c:Special:MyLanguage/Commons:Video2commons|Video2Commons]] as the first tool for its pilot cycle. The group will explore ways to improve and sustain the tool over the coming months. [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|Learn more on Meta]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.23|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:00, 13 October 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29434481 --> == Wikipedia translation of the week: 2025-43 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Liberation of Auschwitz concentration camp]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Auschwitz Liberated January 1945.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> On 27 January 1945, Auschwitz—a Nazi concentration camp and extermination camp in occupied Poland where more than a million people were murdered as part of the Nazis' "Final Solution" to the Jewish question—was liberated by the Soviet Red Army during the Vistula–Oder Offensive. Although most of the prisoners had been forced onto a death march, about 7,000 had been left behind. The Soviet soldiers attempted to help the survivors and were shocked at the scale of Nazi crimes. The date is recognized as International Holocaust Remembrance Day. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 20 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29452019 --> == Tech News: 2025-43 == <section begin="technews-2025-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/43|Translations]] are available. '''Updates for editors''' * To optimize how user data is stored in our databases, the saved preferences of users who haven't logged in for over five years and have fewer than 100 edits will be cleared. When those users return, default settings will apply. [https://phabricator.wikimedia.org/T406724] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a broken link from the GlobalContributions interface message to the XTools GlobalContributions page which has now been fixed. [https://phabricator.wikimedia.org/T406415] '''Updates for technical contributors''' * The work to reroute all traffic to API endpoints under the <code dir=ltr><nowiki>rest.php</nowiki></code> route through a common API gateway is now complete. If any issues are observed, please file a phabricator ticket to the [[phab:tag/serviceops/|Service Ops team board]]. * Edits to Wikidata references or qualifiers will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. [https://phabricator.wikimedia.org/T401290] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.24|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:37, 20 October 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29478670 --> == Wikipedia translation of the week: 2025-44 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Black Diaries]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Black Diaries''' are diaries purported to have been written by the Irish revolutionary Roger Casement, which contained accounts of homosexual liaisons with young men. They cover the years 1903, 1910 and 1911 (two) and were handed in to Scotland Yard after his capture in April 1916. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:51, 27 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29487357 --> == Tech News: 2025-44 == <section begin="technews-2025-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/44|Translations]] are available. '''Updates for editors''' * The Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You can [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Tabbed Browsing (Tabs)/New Tab Experience and Recommendations Experiment|read more on the project page]]. * Autoconfirmed users on [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/small.dblist|small]] and [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/medium.dblist|medium wikis]] with the CampaignEvents extension can now use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed. [https://phabricator.wikimedia.org/T402285] '''Updates for technical contributors''' * The CampaignEvents extension will be deployed to all remaining wikis during the week of 17 November 2025. The extension currently includes three features: Event Registration, Collaboration List, and Invitation List. For this rollout, Invitation List will not be enabled on Wikifunctions and MediaWiki unless requested by those communities. [[m:Special:MyLanguage/CampaignEvents/Deployment status|Visit the deployment page to learn more]]. * The SwaggerUI-based REST sandbox experience is now live on all wiki projects. The sandbox can be accessed through the [[{{#special:RestSandbox}}]] page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on the [[mw:Special:MyLanguage/MediaWiki Interfaces Team/Feature Feedback/REST Sandbox|project launch]] page. [https://phabricator.wikimedia.org/project/board/6931/] * Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using the [https://test.wikipedia.org/w/index.php?api=mw-extra&title=Special%3ARestSandbox REST Sandbox]. See the [[mw:API/Deprecation|MediaWiki REST API Deprecation]] page for more detailed information about the API deprecation policies and procedures. * A dedicated [[mw:API:REST API/Changelog|changelog now exists for the MediaWiki REST API]]. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, please [[mw:API talk:REST API/Changelog|join the discussion]]. * Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked from [[d:Q130635582#sitelinks-wikipedia|Q130635582]]. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited. [https://phabricator.wikimedia.org/T378352] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.25|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:32, 27 October 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29513638 --> |} == Wikipedia translation of the week: 2025-45 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Consolations (Liszt)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Franz Liszt - Consolation No. 3, Lento placido.ogg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Consolations''', S. 171a/172 (German: Tröstungen) are a set of six solo piano works by Franz Liszt. The compositions take the musical style of nocturnes with each having its own distinctive style. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 3 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29558323 --> == Tech News: 2025-45 == <section begin="technews-2025-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/45|Translations]] are available. '''Updates for editors''' * Administrators will now find that [[{{#special:MergeHistory}}]] is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). [https://phabricator.wikimedia.org/T382958] * For users with "{{int:discussiontools-preference-autotopicsub}}" [[Special:Preferences#mw-prefsection-editing|enabled in their preferences]], starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "{{int:Skin-action-addsection}}" or "{{int:Discussiontools-replybutton}}" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time. [https://phabricator.wikimedia.org/T290778] * Scribunto modules can now be used to [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#SVG library|generate SVG images]]. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files. [https://phabricator.wikimedia.org/T405861] * Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. [https://phabricator.wikimedia.org/T395628] * Users with large watchlists have long faced timeouts when editing [[Special:EditWatchlist|Special:EditWatchlist]]. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. A [https://meta.wikimedia.org/wiki/Community_Wishlist/W454 community wish] has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish! [https://phabricator.wikimedia.org/T41510] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query. [https://phabricator.wikimedia.org/T407318] '''Updates for technical contributors''' * Since 2019 the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]] at https://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means <code>/s/</code> URLs will not be advertised under article titles via HTML <code dir=ltr>class="title-shortlink"</code>. The <code>/s/</code> URLs will keep working. [https://phabricator.wikimedia.org/T107188] * On Thursday, October 30, the [[:mw:Special:MyLanguage/MediaWiki Interfaces Team|MediaWiki Interfaces]] and [[:mw:Special:MyLanguage/Wikimedia Site Reliability Engineering|SRE Service Operations]] teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the [https://phabricator.wikimedia.org/tag/serviceops/ Service Ops team] board. * MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/SMWTEAES4SDLDUSK4HMWNBSKNCXZAWYN/] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.26|MediaWiki]] '''In depth''' * In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia in [[diffblog:2025/10/17/new-user-trends-on-wikipedia/|a Diff blog post]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:35, 3 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29552512 --> == Wikipedia translation of the week: 2025-46 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Marine coastal ecosystem]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Vegetation and fauna processes controlling benthic biogeochemical fluxes.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> A '''marine coastal ecosystem''' is a marine ecosystem which occurs where the land meets the ocean. Worldwide there is about 620,000 kilometres (390,000 mi) of coastline. Coastal habitats extend to the margins of the continental shelves, occupying about 7 percent of the ocean surface area. Marine coastal ecosystems include many very different types of marine habitats, each with their own characteristics and species composition. They are characterized by high levels of biodiversity and productivity. For example, estuaries are areas where freshwater rivers meet the saltwater of the ocean, creating an environment that is home to a wide variety of species, including fish, shellfish, and birds. Salt marshes are coastal wetlands which thrive on low-energy shorelines in temperate and high-latitude areas, populated with salt-tolerant plants such as cordgrass and marsh elder that provide important nursery areas for many species of fish and shellfish. Mangrove forests survive in the intertidal zones of tropical or subtropical coasts, populated by salt-tolerant trees that protect habitat for many marine species, including crabs, shrimp, and fish. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 10 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29584005 --> == Tech News: 2025-46 == <section begin="technews-2025-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/46|Translations]] are available. '''Updates for editors''' [[File:Talk pages default look (April 2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * Starting November 12, users will see a change in the [[m:Special:MyLanguage/Talk pages project/Feature summary#Usability improvements|appearance of talk pages]] on [[Phab:T379264|some Wikipedias]]. Almost [[phab:T392121|all wikis]] have received this design change; [[phab:T409297|English Wikipedia]] will get these changes later. You can read more [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. Users can opt out of these changes [[Special:Preferences#mw-prefsection-editing|in their user preferences]] in "{{int:discussiontools-preference-visualenhancements}}". [https://phabricator.wikimedia.org/T379264] * MediaWiki can now display a [[mw:Special:MyLanguage/Help:Protection indicators|page indicator]] automatically while a page is protected. This feature is disabled by default. It can be enabled by [[m:Special:MyLanguage/Requesting wiki configuration changes|community request]]. [https://phabricator.wikimedia.org/T12347] * Using the "{{int:showpreview}}" or "{{int:showdiff}}" buttons in the wikitext editor will now carry over certain URL parameters like '[[mw:Special:MyLanguage/Manual:Parameters to index.php#useskin|useskin]]', '[[mw:Special:MyLanguage/Manual:Parameters to index.php#uselang|uselang]]' and '[[mw:Special:MyLanguage/Help:Section#Editing sections|section]]'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content. [https://phabricator.wikimedia.org/T62744][https://phabricator.wikimedia.org/T24029][https://phabricator.wikimedia.org/T155097] * Wikivoyage wikis can use [[mw:Special:MyLanguage/Help:Extension:Kartographer#Markers and counters|colored map markers in the article text]]. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed. [https://phabricator.wikimedia.org/T369454] * The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. [https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Activity_Tab_Experiment] * The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis. [https://www.mediawiki.org/wiki/Readers/Reader_Growth/WE3.1.3_Image_Browsing] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example the inability to lock accounts on mobile sites has been fixed. [https://phabricator.wikimedia.org/T256185] '''Updates for technical contributors''' * [[wikitech:Help talk:Toolforge/Toolforge standards committee#November 2025 committee nominations|Nominations are open on Wikitech]] for new [[wikitech:Help:Toolforge/Toolforge standards committee|Toolforge standards committee]] members. The committee oversees the Toolforge [[wikitech:Help:Toolforge/Right to fork policy|Right to fork policy]] and [[wikitech:Help:Toolforge/Abandoned tool policy|Abandoned tool policy]] among other duties. Nominations will remain open through 2025-11-28. * The [[w:JSON Web Token#Standard fields|JWT issuer field]] in [[mw:Special:MyLanguage/OAuth/For Developers#OAuth 2|OAuth 2 access tokens]] for [[m:Special:MyLanguage/Help:Unified login|SUL wikis]] has been changed to <code><nowiki>https://meta.wikimedia.org</nowiki></code>. Old access tokens will still work. [https://phabricator.wikimedia.org/T399199] * The [[w:JSON Web Token#Standard fields|JWT subject field]] in [[mw:Special:MyLanguage/OAuth/For Developers#OAuth 2|OAuth 2 access tokens]] will soon change from <code><user id></code> to <code dir=ltr style="white-space:nowrap">mw:<identity type>:<user id></code>, where <code><identity type></code> is typically <code dir=ltr>CentralAuth:</code><!-- not a typo --> (for [[m:Special:MyLanguage/Help:Unified login|SUL wikis]]) or <code dir=ltr style="white-space:nowrap">local:<wiki id></code> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and the <code>sessionJwt</code> cookie more similar. Old access tokens will still work. [https://phabricator.wikimedia.org/T399199] * MediaWiki's block messages ([[MediaWiki:Blockedtext|blockedtext]], [[MediaWiki:Blockedtext-partial|blockedtext-partial]], [[MediaWiki:Autoblockedtext|autoblockedtext]], [[MediaWiki:Systemblockedtext|systemblockedtext]], [[MediaWiki:Blockedtext-tempuser|blockedtext-tempuser]], [[MediaWiki:Autoblockedtext-tempuser|autoblockedtext-tempuser]]) now support additional parameters indicating whether the user is blocked from editing their own user talk page <code><nowiki>$9</nowiki></code> or emailing other users <code><nowiki>$</nowiki><nowiki>10</nowiki></code>. [https://phabricator.wikimedia.org/T285612] * A <code>REL1_45</code> branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/ZUY7TY3Z6XPZWZVAZV63OPO5OW52Q6GE/] * The process for generating CirrusSearch dumps has been updated due to slowing performance. If you encounter any issues migrating to the replacement dumps, please contact the Search Platform Team for support. [https://phabricator.wikimedia.org/T366248][https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/3KQPOR6ACVN6OVLMLZPIBXQSWQKW4E3K/] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.2|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:38, 10 November 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29606150 --> == Wikipedia translation of the week: 2025-47 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Elephant communication]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Three elephant's curly kisses.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Elephants communicate''' via touching, visual displays, vocalisations, seismic vibrations, and semiochemicals. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 17 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29627457 --> == Tech News: 2025-47 == <section begin="technews-2025-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/47|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] is experimenting with [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4_Reading lists|reading lists on mobile web]], allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November. * Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security#Why are you requiring me to enter a code from my email to log in? Can I opt out of this?|Learn more]]. * One new wiki has been created: a {{int:project-localized-name-group-wikisource}} in [[d:Q13324|Minangkabau]] ([[s:min:|<code>s:min:</code>]]) [https://phabricator.wikimedia.org/T408317] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * As part of the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parser Unification]] project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in the [[mw:Special:MyLanguage/Help:Extension:ParserMigration|Extension:ParserMigration]] documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the ''"Report Visual Bug"'' link in the Tools sidebar or create a phab ticket and tag the [[phab:project/view/5846|Content Transform Team in Phabricator]]. * Unsupported Tools: Several issues with [[:c:Special:MyLanguage/Commons:Video2commons|Video2Commons]] have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check the [[phab:tag/video2commons/|Phabricator board]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.3|MediaWiki]] '''Meetings and events''' * Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026. [https://pretix.eu/wikimedia/Hackathon-2026/ Scholarship applications are currently open], and will close on November 28, 2025. If you have any questions, please email <bdi lang="en" dir="ltr">hackathon@wikimedia.org</bdi>. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:27, 17 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29627455 --> == Wikipedia translation of the week: 2025-48 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Animal-made art]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Painting Queen 1024x768.png|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Animal-made art''' consists of works by non-human animals, that have been considered by humans to be artistic, including visual works, music, photography, and videography. Some of these are created naturally by animals, often as courtship displays, while others are created with human involvement. There have been debates about the copyright status of these works, with the United States Copyright Office stating in 2014 that works that lack human authorship cannot have their copyright registered at the US Copyright Office. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 24 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29627457 --> == Tech News: 2025-48 == <section begin="technews-2025-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/48|Translations]] are available. '''Updates for editors''' * Last week, the [[mw:Special:MyLanguage/Wikimedia Search Platform|Wikimedia Search Team]] recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching for ''<span lang="und" dir="ltr">cxfcnmt</span>'' on Russian Wikipedia will now add suggestions for ''<span lang="ru" dir="ltr">счастье</span>'' ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week. [https://phabricator.wikimedia.org/T408734] * Later this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will have syntax highlighting available in [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]]. This requires that the "{{int:discussiontools-preference-sourcemodetoolbar}}" preference be set. [https://phabricator.wikimedia.org/T407918] * [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|Campaign events extension]] – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known as [[m:Special:MyLanguage/CampaignEvents/Collaborative contributions|Collaborative contribution]] to help organizers and participants see the impact of activities has also been added. Join the upcoming [[m:Special:MyLanguage/Event:Connection learning session 3|learning session]] to see the new feature in action and share your feedback. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug which stopped CodeReviewBot from working, has now been fixed. [https://phabricator.wikimedia.org/T410417] '''Updates for technical contributors''' * Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill the [https://wikimediafoundation.limesurvey.net/487662 recruitment survey]. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/IREJRRWTZTGCYWQHDMSNJFTQAEPOOAE3/] * The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for <code dir=ltr>format=xml'''&xlst={stylesheet}'''</code> will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026). [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/5AX7UWAVVUNUSBOIRHMNOKWOZ5EZI3JX/] * The WDQS legacy endpoint ([https://query-legacy-full.wikidata.org/ query-legacy-full.wikidata.org]) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (<span dir=ltr><nowiki>https://query.wikidata.org/</nowiki></span> - Main graph or <span dir=ltr><nowiki>https://query-scholarly.wikidata.org/</nowiki></span> - Scholarly graph). For support with migrating use cases, please review the [[d:Special:MyLanguage/Wikidata:Data_access|Data Access]] and [[d:Wikidata:Request_a_query|Request a Query]] pages for details and assistance on alternative access methods. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.4|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:57, 24 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29702226 --> == Wikipedia translation of the week: 2025-49 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Halachic state]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The term "'''halachic state'''" (Hebrew: מְדִינַת הֲלָכָה‎ Medīnat Hălāḵā) refers to a sovereign state that endorses Judaism in an official capacity and governs by Jewish religious law. It has been a subject of discussion among Orthodox Jews, particularly with regard to modern Israel, which, although a Jewish state, is not classified as a theocracy. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 08:01, 1 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29719355 --> == Tech News: 2025-49 == <section begin="technews-2025-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/49|Translations]] are available. '''Updates for editors''' * The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's [[mw:Special:MyLanguage/Wikimedia Apps/Team/Wikipedia Year in Review/Updates|project page]]. * The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See [[phab:T396155|Phabricator]]. * [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]] will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact [[mw:user:Trizek (WMF)|Trizek (WMF)]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:34}} community-submitted {{PLURAL:34|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [https://phabricator.wikimedia.org/T399476] * Two new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q36846|Toki Pona]] ([[w:tok:|<code>w:tok:</code>]]) [https://phabricator.wikimedia.org/T404457] ** a {{int:project-localized-name-group-wikiquote}} in [[d:Q33655|Nigerian Pidgin]] ([[q:pcm:|<code>q:pcm:</code>]]) [https://phabricator.wikimedia.org/T408318] '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.5|MediaWiki]] '''In depth''' * The Wikimedia Foundation is in the early stages of exploring approaches to '''Article guidance'''. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to [[mw:Special:MyLanguage/Article guidance|learn more]] about the project, and share their thoughts on [[mw:Special:MyLanguage/Talk:Article guidance|the talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:58, 1 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29732328 --> == Wikipedia translation of the week: 2025-50 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ru:Сто лошадей]]'''<br /> <small>''([[:en:One Hundred Horses]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:A_Hundred_Steeds.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''One Hundred Horses''''' (Chinese: 百駿圖) is a Qing dynasty silk and ink painting by Giuseppe Castiglione. It was painted in 1728 for the Yongzheng emperor. The painting depicts a hundred horses in a variety of poses and activities, combining Western realism with traditional Chinese composition and brushwork. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:29, 8 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29719355 --> == Tech News: 2025-50 == <section begin="technews-2025-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/50|Translations]] are available. '''Weekly highlight''' * Anybody who wishes to secure their user account can now use [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] (2FA). This is available to all registered users of all Wikimedia projects. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] initiative. Later, 2FA will be required for all users who can take security- or privacy-sensitive actions. '''Updates for editors''' * Following last week's deployments, the [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]] feature, which allows editors to add suggested links during editing, will be available to an additional [[Phab:T410469|33 Wikipedias]] starting on 9 December. This expansion is possible thanks to the new prediction model that now supports all languages, including those that were previously not covered. While the feature has been available on most Wikipedias for some time, this rollout brings us closer to using the improved model everywhere. If you have any questions or would like more details please contact [[mw:user:Trizek (WMF)|Trizek (WMF)]]. * Last week, the [[mw:Special:MyLanguage/Wikimedia Search Platform|Search Platform team]] added [[w:en:Transliteration|transliterated]] as-you-type search suggestions to Georgian wikis. If there are only a few regular search suggestions, then queries in Latin or Cyrillic script [[phab:T127003|are now rewritten into Georgian script]] to look for more matches. For example, searching for either <bdi lang="ka-Latn" dir="ltr">''bedniereba''</bdi> or <bdi lang="ka-Cyrl" dir="ltr">''бедниереба''</bdi> will now suggest the existing article about <bdi lang="ka" dir="ltr">ბედნიერება</bdi> ("happiness"). You can recommend other languages where transliterated suggestions would be useful [[phab:T375215|on Phabricator]] for future development. * Later this week, a controlled experiment will begin for editors on the 100 largest Wikipedias who are editing a section in the mobile web visual editor. 50% of these editors will notice a new "Edit full page" button that will enable them to expand their editing session to the whole page. This feature is intended to make it easier for people on mobile web to edit any article section, regardless of which section-edit icon they tapped to begin. The experiment will last ~4 weeks. You can find [[phab:T409112|more details]] about the project. * Later this week, the [[mw:Special:MyLanguage/Readers/Reader Growth|Reader Growth team]] will launch a [[mw:Special:MyLanguage/Readers/Reader Growth/WE3.1.14 Expanded Mobile Sections|mobile web experiment]] to expand all article sections by default (currently they are collapsed by default) and pin the section header the user is currently reading to the top of the page. The experiment will affect 10% of users on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias. [https://phabricator.wikimedia.org/T409485] * The [[mw:Special:MyLanguage/Wikimedia Apps/Team/Wikipedia Year in Review/2025 Year in Review|Wikipedia Year in Review 2025]], a feature in the Wikipedia mobile apps (iOS and Android) that provides users with a personalised summary of their engagement with Wikipedia over the year, is now available on the iOS and Android apps. This edition includes expanded personalised insights, improved reading highlights, new donor messaging, and updated designs. Open the app to view your Year in Review and explore your reading journey from 2025. * A recent software bug caused edits made with VisualEditor to make unintended changes to wikitext, including removing whitespace and replacing spaces with underscores in wikilinks inside citations. This was partially fixed last week, and further fixes are in progress. Editors who used VisualEditor between November 28 and December 2 should review their edits for unexpected modifications. [https://phabricator.wikimedia.org/T411238] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the incorrect handling of URLs copied from the address bar of Microsoft Edge users, has been resolved. [https://phabricator.wikimedia.org/T341281] '''Updates for technical contributors''' * Starting this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will have [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror]] as the editor for Lua, JavaScript, CSS, JSON and Vue content models, instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]]. With this, the [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|linters]] will be upgraded. This is part of a larger effort to eventually replace CodeEditor and provide a consistent code editing experience. [https://phabricator.wikimedia.org/T373711] * Developers are encouraged to take the [https://wikimediafoundation.limesurvey.net/552643 2025 Developer Satisfaction Survey], which remains open until 5 January 2026. If you build software for the Wikimedia ecosystem and would like to share your experiences or feedback, your participation is greatly appreciated. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/W4WBKO6Q55UWWCCSFWQATKEXBEHP3QNR/] * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:46, 8 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29738112 --> == Wikipedia translation of the week: 2025-51 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:First Universal Races Congress]]'''<br /> <small>''([[:fr:Premier Congrès universel des races]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Universal Races Congress seated outside the entrance to the Imperial Institute, London, 1911.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''First Universal Races Congress''' met in 1911 for four days at the University of London as an early effort at anti-racism. Speakers from a number of countries discussed race relations and how to improve them. The congress, with 2,100 attendees, was organised by prominent humanists of that era. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 15 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29779168 --> == Tech News: 2025-51 == <section begin="technews-2025-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/51|Translations]] are available. '''Updates for editors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:18}} community-submitted {{PLURAL:18|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, one of the fixes addressed an issue for temporary accounts adding an external URL, which triggered an hCaptcha request in more cases than intended, and did not display the required popup on the first attempt to publish the edit. [https://phabricator.wikimedia.org/T411927] '''Updates for technical contributors''' * To improve database and site performance, external links to Wikimedia projects will no longer be stored in the database. This means they will not be searchable in [[{{#special:LinkSearch}}]], will not be checked by the Spam Blacklist or AbuseFilter as new links, and will not be in the <code dir=ltr>externallinks</code> table on database replicas. In the future this may be extended to other highly-linked trusted websites on a per-wiki basis, such as Creative Commons links on Wikimedia Commons. [https://phabricator.wikimedia.org/T405005] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.7|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:03, 15 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29796010 --> == Wikipedia translation of the week: 2025-52 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pin Malakul]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pin Malakul, January 1922.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pin Malakul''' (24 October 1903 – 5 October 1995) was a Thai professor, educator and writer. His contributions to education in Thailand include the establishment of various institutions of higher education, the introduction of fixed class schedules, and the implementation of teacher-training programmes. In his career he served as Director-General of the Department of General Education, later becoming Permanent Secretary, and Minister, of Education. He was also a member of the executive board of UNESCO. His writings earned him the title of National Artist in 1987, and the 100th anniversary of his birth was celebrated by the UNESCO in 2003 as recognition of his contribution to the advancement of education in Thailand and Southeast Asia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> -[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:26, 22 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29802495 --> == Tech News: 2025-52 == <section begin="technews-2025-W52"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/52|Translations]] are available. '''Updates for editors''' * From January, edit filters [[mw:Special:MyLanguage/Extension:AbuseFilter/Access flags|can be set]] to automatically suppress their details such as rules and list of attempted edits and actions. This will help oversighters use edit filters to prevent doxxing or other suppressible material. [https://phabricator.wikimedia.org/T290324] * The next issue of Tech News will be sent out on 12 January 2026 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:16}} community-submitted {{PLURAL:16|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the crash that occurred when tapping "First Steps" in the Wikipedia Android Year in Review has now been fixed, and the feature opens as expected. [https://phabricator.wikimedia.org/T411546] '''Updates for technical contributors''' * Interface elements such as diffs and categories generated by MediaWiki used to have the attribute <code dir=ltr>data-mw="interface"</code> to distinguish from wiki content. The attribute has been replaced with <code dir=ltr>data-mw-interface=""</code>, to avoid potential conflicts with other <code dir=ltr>data-mw</code> attributes, which are generated by Parsoid. [https://phabricator.wikimedia.org/T409187] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] There is no new MediaWiki version this week or next week. '''Meetings and events''' * The [[mw:Wikimedia Hackathon Northwestern Europe 2026|Wikimedia Hackathon Northwestern Europe 2026]] will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications just opened mid-December and will close in mid-January or earlier if capacity is reached. With space for approximately 100 participants, early application is encouraged. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/52|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W52"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:46, 22 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29831856 --> == Wikipedia translation of the week: 2026-01 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:The Morning of the Magicians]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Le Matin des magiciens, couverture.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''The Morning of the Magicians: Introduction to Fantastic Realism''''' (French: Le Matin des magiciens: Introduction au réalisme fantastique) is a 1960 book by the journalists Louis Pauwels and Jacques Bergier. It covers topics like cryptohistory, ufology, occultism in Nazism, alchemy, spiritual philosophy. The second half of the book is entirely dedicated to the Nazi-Occult connections; the book is widely credited with the proliferation of numerous myths related to occultism in Nazism. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:20, 29 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29802495 --> == Wikipedia translation of the week: 2026-02 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Somaliland War of Independence]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Somaliland, fighters of the Somali National Movement (SNM), 1980s.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Somaliland War of Independence''' was a rebellion waged by the Somali National Movement (SNM) against the ruling military junta in Somalia led by General Siad Barre lasting from its founding on 6 April 1981 and ended on 18 May 1991 when the SNM declared what was then northern Somalia independent as the Republic of Somaliland. The conflict served as the main theater of the larger Somali Rebellion that started in 1978. The conflict was in response to the harsh policies enacted by the Barre regime against the main clan family in Somaliland, the Isaaq, including a declaration of economic warfare on the clan-family. These harsh policies were put into effect shortly after the conclusion of the disastrous Ogaden War in 1978. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:00, 5 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29871911 --> == Wikipedia translation of the week: 2026-03 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Pietro Lauro]]'''<br /> <small>''([[:en:Pietro Lauro]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Master I.A.V.F., Pietro Lauro, born 1508, Modenese Poet and Scholar (obverse), 1555, NGA 45072.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pietro Lauro''', conosciuto anche come Pietro Lauro Modonese o Pietro Lauro da Modona (Modena o dintorni, 1510 circa – Venezia, 1568 circa) è stato un traduttore, scrittore e divulgatore scientifico italiano. Nonostante non si conosca gran parte della sua biografia, fu uno dei poligrafi italiani più conosciuti del Cinquecento. La sua produzione raccoglie traduzioni dal latino, dal greco e dallo spagnolo e riguardano opere di autori classici, stranieri e protestanti. Lauro si dimostrò abile nel trattare testi con temi molto diversi, come la filosofia, l'architettura, la medicina, il giardinaggio, l'agronomia, le scienze biologiche, la storia, la teologia e l'astronomia. Si cimentò anche nella scrittura di un poema cavalleresco sullo stile di quelli spagnoli, il Polendo, sua magnum opus in questo senso. Aderente alla Riforma protestante, sebbene le sue trasposizioni siano state oggetto di critiche già degli autori a lui contemporanei, che le giudicarono troppo letterali, rozze e imparziali, a Lauro si deve il merito di aver ultimato la traduzione in lingua volgare di numerosi testi sia classici, sia scientifici, sia epistolari. I suoi lavori ebbero una notevole diffusione, non solo tra i letterati veneziani della sua epoca, ma in tutta Italia, tanto che alcune sue traduzioni vengono ancora oggi ristampate in nuove edizioni. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:45, 12 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29894468 --> == Tech News: 2026-03 == <section begin="technews-2026-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/03|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2026-2027/Product & Technology OKRs|Meta]] and ''[[diffblog:2025/12/10/shaping-wikimedia-foundations-2026-2027-annual-goals-key-questions-for-the-wikimedia-movement/|Diff]]''. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. '''Updates for editors''' * As part of the current work of Community Tech team on the [[m:Special:MyLanguage/Community Wishlist/W372|Multiple watchlists]] project, the display of [[Special:EditWatchlist|EditWatchlist]] will be updated as a first step towards multiple watchlists. Additionally, the pagination on [[Special:Search|Search]] will be updated too, as a part of the work on the [[m:Special:MyLanguage/Community Wishlist/W186|Revamp pagination / page navigation]] wish. [https://phabricator.wikimedia.org/T411596] * [[m:Special:GlobalWatchlist|The Global Watchlist]] is a MediaWiki [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] that lets you see your watchlists from different wikis on the same page. It was recently updated to look more like the regular [[Special:Watchlist|Watchlist]], such as preparing it for temporary accounts in IP masking (including rerouting user links to contributions pages), making page titles bold, and opening links in edit summaries and tags in new browser tabs. [https://phabricator.wikimedia.org/T398361][https://phabricator.wikimedia.org/T298919][https://phabricator.wikimedia.org/T273526][https://phabricator.wikimedia.org/T286309] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where global blocks did not have the option to disable sending emails, has now been fixed, and will be available for use in the week of January 13. [https://phabricator.wikimedia.org/T401293] '''Updates for technical contributors''' * The [[mw:Special:MyLanguage/VisualEditor/Citation tool|VisualEditor citation tool]] and [[mw:Special:MyLanguage/Help:Reference Previews|Reference Previews]] now support "map" as a reference type. [https://phabricator.wikimedia.org/T411083] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.10|MediaWiki]]/[[mw:MediaWiki 1.46/wmf.11|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:34, 12 January 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29907192 --> == Wikipedia translation of the week: 2026-04 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Volto di Palazzo Vecchio]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Piazza della signoria angolo via della ninna, palazzo vecchio, cantonata con testa scolpita 02.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''volto di Palazzo Vecchio''' (conosciuto anche come L'importuno o L'inopportuno) è un incisione su pietraforte attibuita a Michelangelo Buonarroti, scolpita in una delle pietre di Palazzo Vecchio a Firenze. Secondo le varie leggende, il profilo sarebbe stato realizzato come graffito dall'artista toscano, con soggetto un suo importunatore, un debitore, un condannato a morte o se stesso. Nel 2020, gli studiosi hanno ipotizzato possa invece trattarsi di un ritratto di Francesco Granacci, pittore amico di Michelangelo. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:14, 19 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-04 == <section begin="technews-2026-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/04|Translations]] are available. '''Updates for editors''' * The tray shown on [[Special:Diff|Special:Diff]] in mobile view has been redesigned. It is now collapsed by default, and incorporates a link to undo the edit being viewed, making it easier for mobile editors and reviewers to take action while keeping the interface uncluttered. [https://phabricator.wikimedia.org/T402297] * [[m:Special:GlobalWatchlist|The Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] continues to improve — it now automatically determines the text direction (ensuring correct display of sites with unusual domain names) and shows detailed descriptions for log actions. Later this week, a new permanent link for page creations and CSS classes for each entry element will be added. [https://phabricator.wikimedia.org/T412505][https://phabricator.wikimedia.org/T287929][https://phabricator.wikimedia.org/T262768][https://phabricator.wikimedia.org/T414135] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the previously observed issue in Vector 2022, where anchor link targets were obscured by the sticky header, has now been addressed. [https://phabricator.wikimedia.org/T406114] '''Updates for technical contributors''' * As mentioned in the [[m:Special:MyLanguage/Tech/News/2025/44|October 2025 deprecation announcement]], MediaWiki Interfaces team will begin sunsetting all transform endpoints containing a trailing slash from the MediaWiki REST API the week of January 26. Changes are expected to roll out to all wikis on or before January 30th. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found, compared, and tested using the [https://test.wikipedia.org/wiki/Special:RestSandbox REST Sandbox]. If you have questions or encounter any problems, please file a ticket in Phabricator to the [https://phabricator.wikimedia.org/project/view/6931/ #MW-Interfaces-Team board]. * Interactive reference documentation for the [[mw:Special:MyLanguage/Wikimedia REST API|Wikimedia REST API]] has moved. Requests to API docs previously hosted through [[mw:Special:MyLanguage/RESTBase|RESTBase]] (e.g.: <code dir=ltr>https://en.wikipedia.org/api/rest_v1/</code>) are now redirected to the [[w:en:Special:RestSandbox|REST Sandbox]]. * The [[mw:Special:MyLanguage/Wikidata Platform|WMF Wikidata Platform team]] (WDP) has published its [[d:Special:MyLanguage/Wikidata:Wikidata Platform team/Newsletter|January 2026 newsletter]]. It includes updates on the legacy full-graph endpoint decommissioning, the User-Agent policy change, the monthly Blazegraph migration office hours, and efforts to reduce regressions caused by the legacy endpoint shutdown. As a reminder, you can [[m:Special:MyLanguage/Global message delivery/Targets/WDP team updates|subscribe to the WDP newsletter]]! * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.12|MediaWiki]] '''Meetings and events''' * The [[mw:Wikimedia Hackathon Northwestern Europe 2026|Wikimedia Hackathon Northwestern Europe 2026]] will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications opened mid-December and will close soon or when capacity is reached. It's a two-day, technically oriented hackathon bringing together Wikimedians from the region. Hope to see you there! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:30, 19 January 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29943403 --> == Wikipedia translation of the week: 2026-05 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Raffaello Kobayashi]]'''<br /> <small>''([[:en:Raffaello Kobayashi]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Raffaello Kobayashi''', nato Raffaele Sanzio (Bari, 14 gennaio 1917 – Yokohama, 1 aprile 2011), è stato un militare italiano naturalizzato giapponese. Sommergibilista durante la Seconda guerra mondiale, prestò servizio per tutte e tre le principali Potenze dell'Asse: Regno d'Italia, Germania nazista e Impero giapponese. Alla fine della guerra si nascose in Giappone per evitare di subire l'internamento in un campo di prigionia, divenendo poi cittadino nipponico e cambiando il proprio nome. Prese parte all'affondamento della HMS Calypso nel 1940, primo successo italiano in campo navale nel corso del conflitto mondiale. Con l'abbattimento di un bombardiere statunitense il 22 agosto 1945, otto giorni dopo il discorso di resa del Giappone alle potenze alleate della seconda guerra mondiale, a bordo del Comandante Cappellini, sarebbe stata l'ultima persona in assoluto a mettere fuori combattimento un velivolo degli Alleati nella stessa guerra. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 26 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-05 == <section begin="technews-2026-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/05|Translations]] are available. '''Updates for editors''' * Wikimedia Foundation invites comments on [[m:Special:MyLanguage/Product and Technology Advisory Council/Year1 Reflections and Proposed Way Forward 2026 Update|proposed future]] of the [[:m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] until 28 February. * All users with registered accounts can now use passkeys for [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] (2FA). Passkeys are a simple way to log in without using a second device. They verify the user's identity using a fingerprint, face scan, or a PIN code. To set up a passkey, first set up a regular 2FA method. Currently, to log in with a passkey, users must also use a password. Later this quarter, passwordless login will allow users to log in with a single click and a passkey. Users with advanced rights will also be required to have 2FA enabled. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project. * Unregistered contributors on blocked IPs or blocked IP ranges can now interact on-wiki to appeal a block by creating a temporary account to appeal a block on the user talk page, unless the "prevent this user from editing their own talk page" is enabled. This solves the problem of logged-out users unable to use the default unblock process via user talk page. [https://phabricator.wikimedia.org/T398673] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Two-Factor Authentication (2FA) methods description on the management page has been updated. It is now clearer and easier for users to understand and make use of. [https://phabricator.wikimedia.org/T332385] '''Updates for technical contributors''' * A new AbuseFilter variable, <code>account_type</code>, has been added to provide a reliable way to determine the account type being created in the <code>createaccount</code> and <code>autocreateaccount</code> actions. As part of this change, the variable <code>accountname</code> has been renamed to <code>account_name</code>, and <code>accountname</code> is now deprecated. Edit filter managers should update any filters that use hardcoded account type checks or the deprecated variable. [https://phabricator.wikimedia.org/T414049] * Image thumbnails that are requested in non-standard sizes, and using non-standard methods such as direct requests to <code dir=ltr><nowiki>upload.wikimedia.org/…</nowiki></code> will stop working in the near future. This change is to prevent ongoing external abuse by web-scrapers and bots. Some users with custom CSS/JS, Interface Admins who can fix gadgets and local skins, and Tool-authors, will need to update their code to use standard thumbnail sizes. [[phab:T414805|Details, search-links, and examples of how to fix them, are available in the task]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.13|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:18, 26 January 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29969530 --> == Wikipedia translation of the week: 2026-06 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Censorship in the Czech Republic]]'''<br /> <small>''([[:cs:Cenzura v Česku]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Censorship in the Czech Republic''' had been highly active until 17 November 1989 and the fall of Communism in the former Czechoslovakia. Czech Republic was ranked as the 13th most free country in the World Press Freedom Index in 2014. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:32, 2 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-06 == <section begin="technews-2026-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/06|Translations]] are available. '''Updates for editors''' * The "{{int:pageinfo-toolboxlink}}" feature, which gives validating information about a page ([{{fullurl:{{FULLPAGENAME}}|action=info}} example]), now automatically includes a table of contents. If there is a local [[{{ns:8}}:Pageinfo-header]] page created by individual users, it can now be removed. [https://phabricator.wikimedia.org/T363726] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, VisualEditor previously added bold or italic formatting inside link descriptions, making the wikicode complex. This has now been fixed. [https://phabricator.wikimedia.org/T409669] '''Updates for technical contributors''' * There was no XML dump on 20 January. Additionally, from now on, dumps will be generated once per month only. [https://phabricator.wikimedia.org/T414389] * The MediaWiki Interfaces team removed support for all transform endpoints containing a trailing slash from the [https://www.mediawiki.org/wiki/Special:MyLanguage/API:REST%20API MediaWiki REST API]. All API users currently calling those endpoints are encouraged to transition to the non-trailing slash versions. If you have questions or encounter any problems, please file a ticket in phabricator to the [https://phabricator.wikimedia.org/project/view/6931/ #MW-Interfaces-Team board]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.14|MediaWiki]] '''Weekly highlight''' * Users are reminded that the Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2026-2027/Product & Technology OKRs|Meta]] and ''[[diffblog:2025/12/10/shaping-wikimedia-foundations-2026-2027-annual-goals-key-questions-for-the-wikimedia-movement/|Diff]]''. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:44, 2 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30000986 --> == Wikipedia translation of the week: 2026-07 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Petites Heures of Jean de France, Duc de Berry]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Jacquemart de Hesdin 002.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Petites Heures of Jean de France, Duc de Berry''' is an illuminated book of hours commissioned by John, Duke of Berry between 1375 and 1385–90. It is known for its ornate miniature leaves and border decorations. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:59, 9 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-07 == <section begin="technews-2026-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/07|Translations]] are available. '''Updates for editors''' * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] Logged-in contributors who manage large or complex watchlists can now organise and filter watched pages in ways that improve their workflows with the new [[mw:Special:MyLanguage/Help:Watchlist labels|Watchlist labels]] feature. By adding custom labels (for example: pages you created, pages being monitored for vandalism, or discussion pages) users can more quickly identify what needs attention, reduce cognitive load, and respond more efficiently. This improves watchlist usability, especially for highly active editors. * A new feature available on [[Special:Contributions|Special:Contributions]] shows [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] that are likely operated by the same person, and so makes patrolling less time-consuming. Upon checking contributions of a temporary account, users with access to temporary account IP addresses can now see a view of contributions from the related temporary accounts. The feature looks up all the IPs associated with a given temporary account within the data retention period and shows all the contributions of all temporary accounts that have used these IPs. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts#February 2026: Improvements to the patroller tooling|Learn more]]. [https://phabricator.wikimedia.org/T415674] * When editors preview a wikitext edit, the reminder box that they are only seeing a preview (which is shown at the top), now has a grey/neutral background instead of a yellow/warning background. This makes it easier to distinguish preview notes from actual warnings (for example, edit conflicts or problematic redirect targets), which will now be shown in separate warning or error boxes. [https://phabricator.wikimedia.org/T414742] * The [[m:Special:GlobalWatchlist|Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] continues to improve — it now properly supports more than one Wikibase site, for example both [[d:|Wikidata]] and [[testwikidata:|testwikidata]]. In addition, issues regarding text direction have been fixed for users who prefer Wikidata or other Wikibase sites in right-to-left (RTL) languages. [https://phabricator.wikimedia.org/T415440][https://phabricator.wikimedia.org/T415458] * The automatic "magic links" for ISBN, RFC, and PMID numbers have been [[mw:Special:MyLanguage/Help:Magic links|deprecated in wikitext since 2021]] due to inflexibility and difficulties with localization. Several wikis have successfully replaced RFC and PMID magic links with equivalent external links, but a template was often required to replace the functionality of the ISBN magic link. There is now a new [[mw:Special:MyLanguage/Help:Magic words#isbn|built-in parser function]] <code dir=ltr><nowiki>{{#isbn}}</nowiki></code> available to replace the basic functionality of the ISBN magic link. This makes it easier for wikis who wish to migrate off of the deprecated magic link functionality to do so. [https://phabricator.wikimedia.org/T145604] * Two new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35401|Jju]] ([[w:kaj:|<code>w:kaj:</code>]]) [https://phabricator.wikimedia.org/T413283] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q1186896|Nawat]] ([[w:ppl:|<code>w:ppl:</code>]]) [https://phabricator.wikimedia.org/T413273] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * A new global user group has been created: [[{{int:grouppage-local-bot}}|{{int:group-local-bot}}]]. It will be used internally by the software to allow community bots to bypass rate limits that are applied to abusive [[w:en:Web scraping|web scrapers]]. Accounts that are approved as bots on at least one Wikimedia wiki will be automatically added to this group. It will not change what user permissions the bot has. [https://phabricator.wikimedia.org/T415588] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.15|MediaWiki]] '''Meetings and events''' * The [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Spring 2026|MediaWiki Users and Developers Conference, Spring 2026]] will be held March 25–27 in Salt Lake City, USA. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/AZBWVI46SDEB65PGR5J6E4TYOQQEZXM7/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:31, 9 February 2026 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30026671 --> == Wikipedia translation of the week: 2026-08 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lysmata grabhami]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lysmata grabhami1.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Lysmata grabhami''''' is a species of saltwater shrimp in the family Hippolytidae. It was first described by Gordon in 1935. It occurs in the tropical and subtropical Atlantic Ocean and is a cleaner shrimp, operating a cleaning station to which fish come to have parasites removed. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:45, 16 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-08 == <section begin="technews-2026-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/08|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Wikimedia Site Reliability Engineering|SRE Team]] will be performing a cleanup of Wikimedia's [[m:Special:MyLanguage/Etherpad|Etherpad]] instance, the web-based editor for real-time collaborative document editing. All pads will be permanently deleted after 30 April, 2026 – if there are still migration projects in progress at that point the team can revisit the date on a case by case basis. Please create local backups of any content you wish to keep, as deleted data cannot be recovered. This cleanup helps reduce database size and minimize infrastructure footprint. Etherpad will continue to support real-time collaboration, but long-term storage should not be expected. Additional cleanups may occur in the future without prior notice. [https://phabricator.wikimedia.org/T415237] '''Updates for editors''' * The Information Retrieval team will be launching an [[mw:Special:MyLanguage/Readers/Information Retrieval/Phase 1|Android mobile app experiment]] that tests hybrid search capabilities which can handle both semantic and keyword queries. The improvement of on-platform search will enable readers to find what they’re looking for directly on Wikipedia more easily. The experiment will first be launched on Greek Wikipedia in late February, followed by English, French, and Portuguese in March. [https://diff.wikimedia.org/2026/01/08/semantic-search-making-it-easier-to-find-the-information-readers-want/ Read more] on Diff blog. [https://www.mediawiki.org/wiki/Readers/Information_Retrieval] * The Reader Growth team will run [[mw:Special:MyLanguage/Readers/Reader Growth/WE3.10.2 Mobile Table of Contents|an experiment]] for mobile web users, that adds a table of contents and automatically expands all article sections, to learn more about navigation issues they face. The test will be available on Arabic, Chinese, English, French, Indonesian, and Vietnamese Wikipedias. * Previously, site notices ([[{{ns:8}}:Sitenotice]] and [[{{ns:8}}:Anonnotice]]) would only render on the desktop site. Now, they will render on all platforms. Users on mobile web will now see these notices and be informed. Site administrators should be prepared to test and fix notices on mobile devices to avoid interference with articles. To opt out, interface admins can add <code dir="ltr">#siteNotice { display: none; }</code> to [[{{ns:8}}:Minerva.css]]. [https://phabricator.wikimedia.org/T138572][https://phabricator.wikimedia.org/T416644] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue on [[Special:RecentChanges|Special:RecentChanges]] has been fixed. Previously, clicking hide in the active filters caused the "view new changes since…" button to disappear, though it should have remained visible. The button now behaves as expected. [https://phabricator.wikimedia.org/T406339] '''Updates for technical contributors''' * New documentation is now available to help editors debug on-site search features. It supports troubleshooting when pages do not appear in results, when ranking seems unexpected, and when you need to inspect what content is being indexed, helping make search behavior easier to understand and analyze. [[mw:Help:CirrusSearch/Debug|Learn more]]. [https://phabricator.wikimedia.org/T411169] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.16|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:17, 16 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30086330 --> == Wikipedia translation of the week: 2026-09 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Elefante di Cremona]]'''<br /> <small>''([[:de:Elefant von Cremona]])&#32;([[:eo:Elefanto de Cremona]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Matthew Paris Elephant from Parker MS 16 fol 151v.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> L''''elefante di Cremona''' (Asia, prima del 1228 - Parma, gennaio 1248) fu un esemplare di elefante donato nel 1228 a Federico II di Svevia da parte del sultano ayyubide al-Malik al-Kamil durante gli incontri che porteranno alla Pace di Giaffa. Usato principalmente per le manifestazioni trionfali del sovrano, l'elefante è citato da numerosi cronachisti e testimoni dell'epoca ed è noto per aver trainato il Carroccio dopo la grande vittoria delle armate di Federico II nella battaglia di Cortenuova del 1237. Rimasto a lungo nell'immaginario popolare collettivo, l'animale venne ucciso durante alcuni scontri occorsi nelle settimane immediatamente precedenti alla battaglia di Parma. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 11:43, 23 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-09 == <section begin="technews-2026-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/09|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Edit check/Reference Check|Reference Check]] has been deployed to English Wikipedia, completing its rollout across all Wikipedias. The feature prompts newcomers to add a citation before publishing new content, helping reduce common citation-related reverts and improve verifiability. In A/B testing, the impact was substantial: newcomers shown Reference Check were approximately 2.2 times more likely to include a reference on desktop and about 17.5 times more likely on mobile web. [https://analytics.wikimedia.org/published/reports/editing/reference_check_ab_test_report_final_2025.html] '''Updates for editors''' * The [[mw:Special:MyLanguage/Extension:InterwikiSorting|InterwikiSorting extension]], which allowed for the [[m:Special:MyLanguage/Interwiki sorting order|sorting of interwiki links]], has been undeployed from Wikipedia. As a result, editors who had enabled interwiki link sorting in non-compact mode (full list format) will now see links reordered. The links moving forward will be listed in the alphabetical order of language code. [https://phabricator.wikimedia.org/T253764] * Later this week, people who are editing a page-section using the mobile visual editor, will notice a new "Edit full page" button. When tapped, you will be able to edit the entire article. This helps when the change you want to make is outside the section you initially opened. [https://phabricator.wikimedia.org/T387175][https://phabricator.wikimedia.org/T409112] * [[mw:Special:MyLanguage/Readers/Reader Experience|The Reader Experience team]] is inviting editors to assess whether dark mode should still be considered "beta" on their wiki, based on their experience of how well it functions on desktop and mobile. If the feature is deemed mature, editors can update the interface messages in <code dir=ltr>MediaWiki:skin-theme-description</code> and <code dir=ltr>MediaWiki:Vector-night-mode-beta-tag</code> to indicate that dark mode is ready and no longer considered beta. * The improved [[mw:Wikimedia_Apps/Team/iOS/Activity_Tab|Activity tab]] which displays user-insights is now available to all users of the Wikipedia iOS app (version 7.9.0 and later). Following earlier A/B testing that showed higher account creation among users with access to the feature, it has been rolled out to 100% of users along with some updates. The Activity tab now shows your edited articles in the timeline, offers editing impact insights like contribution counts and article view trends, and customization options to improve in-app experience for users. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug that prevented [[mw:Special:MyLanguage/Extension:DiscussionTools|DiscussionTools]] from working on mobile has now been fixed, restoring full functionality. [https://phabricator.wikimedia.org/T415303] '''Updates for technical contributors''' * The [[m:Special:GlobalWatchlist|Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] that makes this possible continues to improve. The latest upgrade is the inclusion of a [[mw:Extension:GlobalWatchlist#hook|new hook]], <code dir=ltr>ext.globalwatchlist.rebuild</code>, which fires after each watchlist rebuild. This allows you to run gadgets and user scripts for the Special page. [https://phabricator.wikimedia.org/T275159] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.17|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:04, 23 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30119102 --> == Wikipedia translation of the week: 2026-10 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Treaty of the Danish West Indies]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:The Virgin islands of the United States of America; historical and descriptive, commercial and industrial facts, figures, and resources (1918) (14596880870).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Treaty of the Danish West Indies''' (Danish: Vestindiens traktat), officially the Convention between the United States and Denmark for cession of the Danish West Indies (Danish: Konventionen mellem USA og Danmark), was a 1916 treaty transferring sovereignty of the Danish West Indies from Denmark to the United States in exchange for a sum of US$25,000,000 in gold ($722 million in 2024) and a declaration from the United States that it would "not object to the Danish Government extending their political and economic interests to the whole of Greenland". It is one of the most recent permanent expansions of United States territory. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 2 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-10 == <section begin="technews-2026-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/10|Translations]] are available. '''Weekly highlight''' * Wikipedia 25 [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments|Birthday mode]] is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments/article configuration|~2,500 articles]], waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments#Community Configuration Demo|community configuration]] on the local wiki. '''Updates for editors''' * [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new feature to re-use references with different details has been released to Swedish Wikipedia, Polish Wikipedia and [[:phab:T418209|a couple of other wikis]]. You can [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#test|try the feature]] on these projects or on testwiki and [https://en.wikipedia.beta.wmcloud.org/wiki/Sub-referencing betawiki]. Learnings from the first pilot wiki German Wikipedia have been [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing/Learnings|published in a report]]. Reach out to the Wikimedia Deutschland team if you are [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Pilot wikis|interested in becoming a pilot wiki]]. * [[mw:Special:MyLanguage/Help:Edit check#Paste check|Paste Check]] will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check [[mw:Special:MyLanguage/Edit check/Tags|tags]] all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via [[{{#special:EditChecks}}]]. [[mw:Special:MyLanguage/Edit check/Paste Check#A/B Experiment|Research]] across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can [https://translatewiki.net/w/i.php?title=Special%3ATranslate&group=ext-visualeditor-ve-mw-editcheck&filter=&optional=1&action=translate help to localize] this and related features. * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface. [https://phabricator.wikimedia.org/T413912] * Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one. [https://phabricator.wikimedia.org/T410807] * Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon. [https://phabricator.wikimedia.org/T383948] * The [[m:Special:GlobalWatchlist|Global Watchlist]] which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] now allows activating the [[mw:Special:MyLanguage/Manual:Language#Fallback languages|language fallback system]] for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no <code dir=ltr>uselang=</code> URL parameter is provided. [https://phabricator.wikimedia.org/T373686][https://phabricator.wikimedia.org/T416111] * The Wikipedia Android team has started a beta test of [[mw:Special:MyLanguage/Readers/Information Retrieval/Phase 1|hybrid search]] on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily. * For security reasons, members of certain user groups are [[m:Special:MyLanguage/Mandatory two-factor authentication for users with some extended rights|required to have two-factor authentication]] (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will [[phab:T418580|gradually change in March]]. Members of these groups will be unable to disable last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule. [https://phabricator.wikimedia.org/T418580] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue preventing users from creating an instance in [https://www.wikibase.cloud/ Wikibase.cloud] has now been fixed. [https://phabricator.wikimedia.org/T416807] '''Updates for technical contributors''' * To help ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]], over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]]. * The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts. [https://phabricator.wikimedia.org/T415696] * The new Parsoid parser [[mw:Special:MyLanguage/Parsoid/Parser Unification/Updates|continues to be deployed to additional wikis]], improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views. * The process and criteria for [[Special:MyLanguage/Wikimedia Enterprise#Access|requesting exceptional access]] to the high volume feed of the ''Wikimedia Enterprise'' APIs (at no cost for mission-aligned usecases), [[m:Talk:Wikimedia Enterprise#Exceptional access criteria|have now been published]]. This is to provide more thorough and clearer documentation for users. * [https://techblog.wikimedia.org/ Tech Blog], the blog dedicated to the Wikimedia technical community [https://techblog.wikimedia.org/2026/02/24/a-tech-blog-diff/ will be migrating] to [[diffblog:|Diff]], the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at https://diff.wikimedia.org/techblog. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.18|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:52, 2 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30137798 --> == Wikipedia translation of the week: 2026-11 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Steens Mountain]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Steens Mountain near Andrews, Oregon.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Steens Mountain''' is a large fault-block mountain in the northwest United States, located in Harney County, Oregon. Stretching some fifty miles (80 km) north to south, on its east side it rises from the Alvord Desert at an elevation of about 4,200 feet (1,280 m) to 9,738 feet (2,968 m) at the summit. Steens Mountain is not part of a mountain range but is properly a single mountain, the largest of Oregon's fault-block mountains. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 07:30, 9 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-11 == <section begin="technews-2026-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/11|Translations]] are available. '''Weekly highlight''' * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 25 March 2026 at [https://zonestamp.toolforge.org/1774450800 15:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. * Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the [[m:Steward's noticeboard#Statement on Meta about today's user script security incident|post on the Stewards' noticeboard]] ([[m:Special:MyLanguage/Wikimedia Foundation/Product and Technology/Product Safety and Integrity/March 2026 User Script Incident|translations]]). '''Updates for editors''' * Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as [[Special:MyLanguage/Apple iCloud Private Relay|iCloud Private Relay]]) will receive clearer guidance on what they need to do to start editing again. [https://phabricator.wikimedia.org/T357118] * Later this week, [[mw:Special:MyLanguage/VisualEditor/Suggestion Mode|Suggestion Mode]] will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at [[Special:EditChecks]] and there are [[mw:Special:MyLanguage/Help:Suggestion mode#For administrators %E2%80%93 local customization|instructions for how administrators can customize]] the links to point to local guidelines. The feature is connected to [[mw:Special:MyLanguage/Help:Edit check|Edit check]] which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment. [https://phabricator.wikimedia.org/T404600] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools. [https://phabricator.wikimedia.org/T418793] '''Updates for technical contributors''' * API rate limiting update: To help ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]], global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]]. * The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and [[d:Wikidata:Wikibase GraphQL#Feedback and development|give feedback]]. You can also [https://greatquestion.co/wikimediadeutschland/GraphQLAPI/apply sign up for usability tests]. * The [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|PTAC Unsupported Tools Working Group]] continued improvements to [[commons:Special:MyLanguage/Commons:Video2commons#|Video2Commons]] in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group#February 2026|this update]] to learn more. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.19|MediaWiki]] '''In depth''' * The Article Guidance team invites experienced Wikipedia editors from selected [[mw:Special:MyLanguage/Article guidance/Pilot wikis and collaborators#Collaborators|pilot wikis]] and interested contributors from other Wikipedias to fill out this questionnaire which is available in [https://docs.google.com/forms/d/e/1FAIpQLSfmLeVWnxmsCbPoI_UF2jyRcn73WRGWCVPHzerXb4Cz97X_Ag/viewform English], [https://docs.google.com/forms/d/e/1FAIpQLSd6rzr4XXQw8r4024fE3geTPFe13M_6w7Mitj-YJi0sOlWTAw/viewform?usp=header Arabic], [https://docs.google.com/forms/d/e/1FAIpQLSdok3-RfB18lcugYTUMGkpwmqG_8p760Wv4dCXitOXOszjUDw/viewform?usp=header Bengali], [https://docs.google.com/forms/d/e/1FAIpQLSfjTfYp4jEo0akA4B1e-Nfg3QZPCudUjhJzHzzDi6AHyAaMGA/viewform?usp=header Japanese], [https://docs.google.com/forms/d/e/1FAIpQLScteVoI29Aue4xc72dekk-6RYtvmMgQxzMI900UOawrFrSTWg/viewform?usp=header Portuguese], [https://docs.google.com/forms/d/e/1FAIpQLSetdxnYwL3ub2vqA7awCg5hJZPMIYcDPaiTe12rY9h0GYnVlw/viewform?usp=header Persian], and [https://docs.google.com/forms/d/e/1FAIpQLScNvfJF-Ot-4pzA4qAN771_0QDJ4Li19YcUsaTgSKW8Nc7U_Q/viewform?usp=header Turkish]. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more [[mw:Special:MyLanguage/Article guidance|on the project page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 9 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30213008 --> == Wikipedia translation of the week: 2026-12 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Casque (anatomy)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Great hornbill (Buceros bicornis) Photograph by Shantanu Kuveskar.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''casque''' is an anatomical feature found in some species of birds, reptiles, and amphibians. In birds, it is an enlargement of the bones of the upper mandible or the skull, either on the front of the face, the top of the head, or both. The casque has been hypothesized to serve as a visual cue to a bird's sex, state of maturity, or social status; as reinforcement to the beak's structure; or as a resonance chamber, enhancing calls. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 16 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30245038 --> == Tech News: 2026-12 == <section begin="technews-2026-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/12|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature, also known as [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror 6]], has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Features|features]] to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror|please share]]. [https://phabricator.wikimedia.org/T259059] * Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks. [https://phabricator.wikimedia.org/T6055] * On wikis using [[m:Special:MyLanguage/Flagged Revisions|Flagged Revisions]], the number of pending changes shown on [[{{#Special:PendingChanges}}]] previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself. [https://phabricator.wikimedia.org/T413016] * Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about [[f:Special:MyLanguage/Wikifunctions:Status updates/2026-03-11|the changes]]. * Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'. [https://phabricator.wikimedia.org/T403775] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed. [https://phabricator.wikimedia.org/T419263] '''Updates for technical contributors''' * A new special page, [[{{#special:LintTemplateErrors}}]], has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example: [[{{#special:LintTemplateErrors}}/night-mode-unaware-background-color]]. [https://phabricator.wikimedia.org/T170874] * Users of the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature have been using [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror|Feedback or concerns are welcome]]. [https://phabricator.wikimedia.org/T419332] * The [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the <code dir=ltr>ext.CodeMirror</code> or <code dir=ltr>ext.CodeMirror.lib</code> modules from gadgets and user scripts was deprecated in July 2025. The use of the <code dir=ltr>ext.CodeMirror.switch</code> hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the [[mw:Special:MyLanguage/Extension:CodeMirror#Gadgets and user scripts|migration guide]] for more information. [https://phabricator.wikimedia.org/T373720] * The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include [[mw:Special:MyLanguage/API:REST API/Extensions|extension APIs]]. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for [https://phabricator.wikimedia.org/T414470 GrowthExperiments] and [https://phabricator.wikimedia.org/T419053 Wikifunctions] APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the [https://test.wikipedia.org/wiki/Special:RestSandbox REST Sandbox] (i.e., [[{{#Special:RestSandbox}}]], available on all wiki projects). * The [[mw:Special:MyLanguage/Extension:Scribunto|Scribunto]] extension provides different pieces of information about the wiki where the module is being used via the [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual|mw.site]] library. Starting last week, the library also provides a [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#mw.site.wikiId|way]] of accessing the [[mw:Special:MyLanguage/Manual:Wiki ID|wiki ID]] that can be used to facilitate cross-wiki module maintenance. [https://phabricator.wikimedia.org/T146616] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.20|MediaWiki]] '''In depth''' * The [[m:Special:MyLanguage/Coolest Tool Award|2026 Coolest Tool Award]] celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the [https://wikimediafoundation.limesurvey.net/435684?lang=en nomination survey] form by 23 March 2026. For more information on privacy and data handling, please see the [[foundation:Special:MyLanguage/Legal:Coolest_Tool_Award_2026_Survey_Privacy_Statement|survey privacy statement]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:36, 16 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30260505 --> == Wikipedia translation of the week: 2026-13 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Etruscan sculpture]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Frontone A del grande tempio di luni con concilio degli dei, 175-150 ac. ca. 01.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> '''Etruscan sculpture''' was one of the most important artistic expressions of the Etruscan people, who inhabited the regions of Northern Italy and Central Italy between about the 9th century BC and the 1st century BC. Etruscan art was largely a derivation of Greek art, although developed with many characteristics of its own. Given the almost total lack of Etruscan written documents, a problem compounded by the paucity of information on their language—still largely undeciphered—it is in their art that the keys to the reconstruction of their history are to be found, although Greek and Roman chronicles are also of great help. Like its culture in general, Etruscan sculpture has many obscure aspects for scholars, being the subject of controversy and forcing them to propose their interpretations always tentatively, but the consensus is that it was part of the most important and original legacy of Italian art and even contributed significantly to the initial formation of the artistic traditions of ancient Rome. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:07, 23 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30245038 --> == Tech News: 2026-13 == <section begin="technews-2026-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/13|Translations]] are available. '''Weekly highlight''' * Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional [[phab:T417120|"Log in with passkey" button]] will soon be available for users who have already registered a passkey. This update will improve security and user experience. The [[c:File:Passwordless_login_screencast.webm|screen recording]] demonstrates the passwordless login process step by step. * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 25 March 2026 at [https://zonestamp.toolforge.org/1774450800 15:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. '''Updates for editors''' * Wikimedia site users can now export their notifications older than 5 years using a [[toolforge:echo-chamber|new Toolforge tool]]. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced. [https://phabricator.wikimedia.org/T383948] * Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an [[mw:Special:MyLanguage/Moderator Tools/Dashboard|early version of an experience]] that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project. [https://phabricator.wikimedia.org/T402647] * The [[Special:Block]] now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: [[MediaWiki:Ipbreason-indef-dropdown]]. [https://phabricator.wikimedia.org/T401823] * Mobile editors [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#Logged-out|at several wikis]] can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance [[mw:Special:MyLanguage/Contributors/Account Creation Experiments|account creation experience on mobile]] and then increase participation. [https://phabricator.wikimedia.org/T408484] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:36}} community-submitted {{PLURAL:36|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia. '''Updates for technical contributors''' * Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent [https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/EMYTA32EV2V5SQ2JIEOD2CL66YFIZEKV/ cloud-announce email] and update your build configuration as necessary to ensure your tools are compatible. [https://wikitech.wikimedia.org/w/index.php?title=Help:Toolforge/Building_container_images&oldid=2392097#Buildpack_environment_upgrade_process][https://phabricator.wikimedia.org/T380127] * The [https://api.wikimedia.org/wiki/Main_Page API Portal] documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to [[mw:Wikimedia APIs|mediawiki.org]]. Learn more on the [[wikitech:API Portal/Deprecation|project page]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.21|MediaWiki]] '''In depth''' * [[m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]] is considering improvements to [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names|automatically generated reference names in VisualEditor]]. Please check out the [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names#Proposed solutions|proposed solutions]] and participate in the [[m:Talk:WMDE Technical Wishes/References/VisualEditor automatic reference names#Request for comment|request for comment]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:51, 23 March 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30268305 --> == Wikipedia translation of the week: 2026-14 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pulse (nightclub)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Orlando FL Pulse Nightclub01.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pulse''' was a gay bar, dance club, and nightclub in Orlando, Florida, founded in 2004 by Barbara Poma and Ron Legler. On June 12, 2016, the club was the scene of the second-deadliest mass shooting by a single gunman in U.S. history, and the second-deadliest terrorist attack on U.S. soil since the September 11 attacks. Forty-nine people were killed and 58 other people were injured. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:37, 30 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-14 == <section begin="technews-2026-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/14|Translations]] are available. '''Weekly highlight''' * The Beta version of [[abstract:|Abstract Wikipedia]] a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-03-26|Read more]]. '''Updates for editors''' * The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#2. Improve logged-out warning message (T415160)|Read more]]. * The Wikimedia Apps team is inviting feedback on [[mw:Special:MyLanguage/Wikimedia Apps/Team/Future of Editing on the Mobile Apps|how editing should work on the Wikipedia mobile apps]]. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:45}} community-submitted {{PLURAL:45|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where citation fetching from the large newspaper archive [https://www.newspapers.com Newspapers.com] was no longer working, due to a block in [[mw:Special:MyLanguage/Citoid|Citoid]] requests, has now been fixed. [https://phabricator.wikimedia.org/T419903] '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:26, 30 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30329462 --> == Wikipedia translation of the week: 2026-15 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Tofana di Rozes]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Tofana di Rozes 04.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Tofana di Rozes''' (3,225 metres (10,581 ft)) is a mountain of the Dolomites in the Province of Belluno, Veneto, Italy. Located west of the resort of Cortina d'Ampezzo, the mountain's giant three-edged pyramid shape and its vertical south face, above the Falzarego Pass, makes it the most popular peak in the Tofane group, and one of the most popular in the Dolomites. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:27, 6 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-15 == <section begin="technews-2026-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/15|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in [[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Collaborative contributions#Goal setting|the documentation]]. * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] The new [[mw:Special:MyLanguage/Help:Watchlist labels|watchlist labels]] feature (announced in [[m:Special:MyLanguage/Tech/News/2026/07|Tech News 2026-07]]) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via [[Special:EditWatchlist|EditWatchlist]]. In all three places it is a new field following the expiry field. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed. [https://phabricator.wikimedia.org/T419171] '''Updates for technical contributors''' * The [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|sub-referencing feature]], which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to [[phab:T414094|more wikis]] later this year. Wikis using the [[mw:Special:MyLanguage/Reference Tooltips|Reference Tooltips]] gadget are encouraged to update their version (typically at [[m:MediaWiki:Gadget-ReferenceTooltips.js|MediaWiki:Gadget-ReferenceTooltips.js]] as shown [https://en.wikipedia.org/w/index.php?diff=1344408362 here]) to ensure compatibility. Other reference-related gadgets may also be affected. [https://phabricator.wikimedia.org/T416304] * All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. [[m:Wikimedia Foundation Board noticeboard#Board of Trustees Approves Closure of Wikinews|Read more]]. * The [[:mw:Special:MyLanguage/API:Action API|Action API]] has had several formats for requested output. One of them, <bdi lang="zxx" dir="ltr"><code><nowiki>format=php</nowiki></code></bdi>, is being removed soon. Please ensure your scripts or bots use the [[mw:Special:MyLanguage/API:Data formats#Output|JSON format]]. This removal should affect very few scripts and bots. [https://phabricator.wikimedia.org/T118538] * The [[Special:NamespaceInfo|Special:NamespaceInfo]] page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia. [https://phabricator.wikimedia.org/T381455] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.23|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:19, 6 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30362761 --> == Wikipedia translation of the week: 2026-16 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Very-low-calorie diet]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Green smoothie (8222465502).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''very-low-calorie diet''' (VLCD), also known as semistarvation diet and crash diet, is a type of diet with very or extremely low daily food energy consumption. VLCDs are defined as a diet of 800 kilocalories (3,300 kJ) per day or less. Modern medically supervised VLCDs use total meal replacements, with regulated formulations in Europe and Canada which contain the recommended daily requirements for vitamins, minerals, trace elements, fatty acids, protein and electrolyte balance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:56, 13 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-16 == <section begin="technews-2026-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/16|Translations]] are available. '''Weekly highlight''' * Experienced editors are invited to [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Main_Page test] the [[mw:Special:MyLanguage/Article guidance|Article guidance]] feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are [[mw:Special:MyLanguage/Article guidance/Test feature guide|available]]. Also, after reviewing [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Category:Pages_using_article_guidance the outlines], please provide feedback on the [[mw:Talk:Article guidance|project talk page]]. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out [[c:File:Article Guidance workflow demo - April 2026.webm|the video]] explaining the feature. '''Updates for editors''' * On most wikis, all autoconfirmed users can now use [[Special:ChangeContentModel|Special:ChangeContentModel]] page to [[mw:Special:MyLanguage/Help:ChangeContentModel|create new pages with custom content models]], such as mass message lists, making custom page formats more accessible. Check [[Special:ListGroupRights|Special:ListGroupRights]] for the status of your wiki. [https://phabricator.wikimedia.org/T248294] * The Growth team has launched an [[mw:Special:MyLanguage/Contributors/Account_Creation_Experiments|account creation experiment]] to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed. [https://phabricator.wikimedia.org/T382856] '''Updates for technical contributors''' * Starting later this week, {{int:group-abusefilter}} who have the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature enabled will have [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] as the editor at [[Special:AbuseFilter|Special:AbuseFilter]]. This is part of the broader effort to make the user experience more consistent across all editors. [https://phabricator.wikimedia.org/T399673][https://phabricator.wikimedia.org/T419332] * Tools and bots that access the [[mw:Special:MyLanguage/Notifications/API|Notifications API]] (<bdi lang="zxx" dir="ltr"><code><nowiki>action=query&meta=notifications</nowiki></code></bdi>) will need to update their OAuth or BotPassword grants to also include access to private notifications. [https://phabricator.wikimedia.org/T421991] * Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia). [https://phabricator.wikimedia.org/T422544] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.24|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:19, 13 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30380527 --> == Wikipedia translation of the week: 2026-17 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Chromodoris willani]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Babosa de mar (Chromodoris willani), Anilao, Filipinas, 2023-08-24, DD 34.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Chromodoris willani''''', commonly known as Willan's chromodoris, is a species of sea slug, a dorid nudibranch, a shell-less marine gastropod mollusk in the family Chromodorididae. The species is named for the renowned nudibranch taxonomist Dr. Richard C. Willan. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:34, 20 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30430366 --> == Tech News: 2026-17 == <section begin="technews-2026-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/17|Translations]] are available. '''Weekly highlight''' * After two years of development, [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]], also known as [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror 6]], is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other [[mw:Special:MyLanguage/Help:Extension:CodeMirror|benefits]] to all users of the standard syntax highlighter. A huge thank you to volunteer [https://phabricator.wikimedia.org/p/Bhsd/ Bhsd] who developed many of the new features, including [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Code folding|code folding]], [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Autocompletion|autocompletion]], and [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|linting]]. [https://phabricator.wikimedia.org/T259059] * A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design. [https://apps.apple.com/us/app/wikipedia/id324715238 Download the latest version] and explore the update. '''Updates for editors''' * [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|Reading lists]] is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias. * An experiment which explores extending [[mw:Special:MyLanguage/Readers/Reader Growth/Mobile page previews|Page Previews to mobile web]] will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps. [[m:Special:MyLanguage/List of experiments in Product and Technology#Template|Read more about this experiment and others]]. * On several wikis, logged-in editors who haven't [[mw:Special:MyLanguage/Help:Email confirmation|confirmed their email addresses]] can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it. [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security#Encouraging users to confirm their email addresses|Learn more]]. [https://phabricator.wikimedia.org/T421366] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:15}} community-submitted {{PLURAL:15|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed. [https://phabricator.wikimedia.org/T184857] '''Updates for technical contributors''' * As part of the promotion of [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror]] from a beta feature, all users will use [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages. [https://phabricator.wikimedia.org/T419332] * The <code>mirrors.wikimedia.org</code> service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/LJYRIS4WB66HIRCAO4GIDTXCMDVZRBMA/ You can read more]. [https://phabricator.wikimedia.org/T416707] * The <bdi lang="zxx" dir="ltr"><code><nowiki>image</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>oldimage</nowiki></code></bdi> table will be removed from [[wikitech:Help:Wiki Replicas|wikireplicas]]. If your tools or queries access <bdi lang="zxx" dir="ltr"><code><nowiki>image</nowiki></code></bdi> or <bdi lang="zxx" dir="ltr"><code><nowiki>oldimage</nowiki></code></bdi> directly, please update them to use the <bdi lang="zxx" dir="ltr"><code><nowiki>file</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>filerevision</nowiki></code></bdi> table before 28 May. [https://phabricator.wikimedia.org/T28741] * Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]] by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]] and [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits/FAQ|Frequently Asked Questions]]. * The [[mw:Special:MyLanguage/Attribution API|Attribution API]] is now available as a [[mw:Special:MyLanguage/Wikimedia APIs/Stability policy|beta]]. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the [https://en.wikipedia.org/w/index.php?api=attribution.v0-beta&title=Special%3ARestSandbox REST sandbox on English Wikipedia]). Share your feedback on the [[mw:Talk:Attribution API|project talk page]]. * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:01, 20 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30432763 --> == Wikipedia translation of the week: 2026-18 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Platypus venom]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Platypus spur.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> The platypus is one of the few living mammals to produce venom. The venom is made in venom glands that are connected to hollow spurs on their hind legs; it is primarily made during the mating season.[1] While the venom's effects are described as extremely painful, it is not lethal to humans. Many archaic mammal groups possess similar tarsal spurs, so it is thought that, rather than having developed this characteristic uniquely, the platypus simply inherited this characteristic from its ancestors. Rather than being a unique outlier, the platypus is the last demonstration of what was once a common mammalian characteristic, and it can be used as a model for non-therian mammals and their venom delivery and properties. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 27 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30449041 --> == Tech News: 2026-18 == <section begin="technews-2026-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/18|Translations]] are available. '''Updates for editors''' * There is a change in how new users are autoconfirmed that will improve anti-vandalism protection. Currently, users who have had an account for a few days and made a few edits are automatically added to the [[{{int:grouppage-autoconfirmed/{{CONTENTLANGUAGE}}}}|{{int:group-autoconfirmed}}]] group. This configuration tends to be exploited by some vandals, who create accounts and start to use them only after some time. To mitigate this, the configuration will be updated next week so that – for the purpose of becoming autoconfirmed – the account age will be counted from their first edit, instead of registration date. The numeric value of the age threshold will remain the same. This change will be deployed only to wikis which require at least one edit as part of the autoconfirmation conditions. [https://phabricator.wikimedia.org/T418484] * All Wikipedia users with new accounts and those who activated the "automatically enable most beta features" option in their preference can now use the [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|reading lists]] beta feature to save articles for later reading. This helps organize reading interests in one place for convenient access. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where infobox images have huge padding in Firefox, has been fixed. [https://phabricator.wikimedia.org/T423676] '''Updates for technical contributors''' * As a reminder, the global API rate limits will be applied this week to identified API traffic. This is to help ensure [[mw:MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]]. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, including the actual rate limits, see [[mw:Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]] and [[mw:Wikimedia APIs/Rate limits/FAQ|Frequently Asked Questions]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.26|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:06, 27 April 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30458046 --> == Wikipedia translation of the week: 2026-19 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kuwait National Assembly Building]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Kuwait City Arabian Gulf Street 10.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Kuwait National Assembly Building''' is the building that housed the National Assembly of Kuwait. Designed by Danish architect Jørn Utzon in 1972, it was completed in 1982 under the direction of his son Jan. The structural design was by Max Walt. The building was seriously damaged in February 1991 when retreating Iraqi troops set it on fire but has since been restored. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:16, 4 May 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30464799 --> 7yoxtczu4i67ngf3q92m84uxjdyauzc 4634189 4634061 2026-05-04T20:44:03Z MediaWiki message delivery 1188004 /* Tech News: 2026-19 */ new section 4634189 wikitext text/x-wiki <noinclude> {{User:Xeverything11/tabs}} {{User:Xeverything11/header|Welcome to|Xeverything11's|updates talk page!|archives= * [[User talk:Xeverything11/archives/2022|2022]] * [[User talk:Xeverything11/archives/2023|2023]] }} </noinclude> __NOTOC__ {{User:MiszaBot/config |archive = User talk:Xeverything11/archives/%(year)d |algo = old(60d) |counter = 1 |minthreadsleft = 1 |minthreadstoarchive = 1 }} == Tech News: 2023-03 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/03|Translations]] are available. '''Problems''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] The URLs in "{{int:last}}" links on page history now contain <bdi lang="zxx" dir="ltr"><code><nowiki>diff=prev&oldid=[revision ID]</nowiki></code></bdi> in place of <bdi lang="zxx" dir="ltr"><code><nowiki>diff=[revision ID]&oldid=[revision ID]</nowiki></code></bdi>. This is to fix a problem with links pointing to incorrect diffs when history was filtered by a tag. Some user scripts may break as a result of this change. [https://phabricator.wikimedia.org/T243569] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-17|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-01-18|en}}. It will be on all wikis from {{#time:j xg|2023-01-19|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Some [[mw:Special:MyLanguage/Talk pages project/Usability|changes to the appearance of talk pages]] have only been available on <code>{{ns:1}}:</code> and <code>{{ns:3}}:</code> namespaces. These will be extended to other talk namespaces, such as <code>{{ns:5}}:</code>. They will continue to be unavailable in non-talk namespaces, including <code>{{ns:4}}:</code> pages (e.g., at the Village Pump). You can [[Special:Preferences#mw-prefsection-editing-discussion|change your preferences]] ([[Special:Preferences#mw-prefsection-betafeatures|beta feature]]). [https://phabricator.wikimedia.org/T325417] *On Wikisources, when an image is zoomed or panned in the Page: namespace, the same zoom and pan settings will be remembered for all Page: namespace pages that are linked to a particular Index: namespace page. [https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ProofreadPage/+/868841] * The Vector 2022 skin will become the default for the English Wikipedia desktop users. The change will take place on January 18 at 15:00 UTC. [[:en:w:Wikipedia:Vector 2022|Learn more]]. '''Future changes''' * The 2023 edition of the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey]], which invites contributors to make technical proposals and vote for tools and improvements, starts next week on 23 January 2023 at 18:00 UTC. You can start drafting your proposals in [[m:Community Wishlist Survey/Sandbox|the CWS sandbox]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:11, 17 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24381020 --> == Tech News: 2023-04 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/04|Translations]] are available. '''Problems''' * Last week, for ~15 minutes, all wikis were unreachable for logged-in users and non-cached pages. This was caused by a timing issue. [https://wikitech.wikimedia.org/wiki/Incidents/2023-01-17_MediaWiki] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-24|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-01-25|en}}. It will be on all wikis from {{#time:j xg|2023-01-26|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * If you have the Beta Feature for [[mw:Special:MyLanguage/Talk pages project|DiscussionTools]] enabled, the appearance of talk pages will add more information about discussion activity. [https://www.mediawiki.org/wiki/Special:MyLanguage/Talk_pages_project/Usability#Status][https://phabricator.wikimedia.org/T317907] * The 2023 edition of the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey]] (CWS), which invites contributors to make technical proposals and vote for tools and improvements, starts on Monday 23 January 2023 at [https://zonestamp.toolforge.org/1674496814 18:00 UTC]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:46, 23 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24418874 --> == Tech News: 2023-05 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/05|Translations]] are available. '''Problems''' * Last week, for ~15 minutes, some users were unable to log in or edit pages. This was caused by a problem with session storage. [https://wikitech.wikimedia.org/wiki/Incidents/2023-01-24_sessionstore_quorum_issues] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.21|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-31|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-01|en}}. It will be on all wikis from {{#time:j xg|2023-02-02|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] Wikis that use localized numbering schemes for references need to add new CSS. This will help to show citation numbers the same way in all reading and editing modes. If your wiki would prefer to do it yourselves, please see the [[mw:Special:MyLanguage/Parsoid/Parser Unification/Cite CSS|details and example CSS to copy from]], and also add your wiki to the list. Otherwise, the developers will directly help out starting the week of February 5. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 31 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24455949 --> == Wikipedia translation of the week: 2023-06 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sweden Finns' Day]] '''<br /> <small>''([[:fi:Ruotsinsuomalaisten päivä]]) ([[:sv:Sverigefinnarnas dag]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sverigefinskaflaggan.svg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Sweden Finns' Day''' (Finnish: Ruotsinsuomalaisten päivä, Swedish: Sverigefinnarnas dag) is an anniversary celebrated in Sweden on 24 February. The anniversary of the calendar was approved by the Swedish Academy in 2010 and was celebrated for the first time in 2011. February 24 was chosen as the birthday of Carl Axel Gottlund, a collector of folk poetry and a defender of the status of the Finnish language. The purpose of the day is to celebrate the Sweden Finns and to recognize their history, language and culture as a prominent part of Sweden's cultural heritage. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:04, 6 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24491747 --> == Tech News: 2023-06 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/06|Translations]] are available. '''Recent changes''' * In the [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements|Vector 2022 skin]], logged-out users using the full-width toggle will be able to see the setting of their choice even after refreshing pages or opening new ones. This only applies to wikis where Vector 2022 is the default. [https://phabricator.wikimedia.org/T321498] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-08|en}}. It will be on all wikis from {{#time:j xg|2023-02-09|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Previously, we announced when some wikis would be in read-only for a few minutes because of a switch of their main database. These switches will not be announced any more, as the read-only time has become non-significant. Switches will continue to happen at 7AM UTC on Tuesdays and Thursdays. [https://phabricator.wikimedia.org/T292543#8568433] * Across all the wikis, in the Vector 2022 skin, logged-in users will see the page-related links such as "What links here" in a [[mw:Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Page_tools|new side menu]]. It will be displayed on the other side of the screen. This change had previously been made on Czech, English, and Vietnamese Wikipedias. [https://phabricator.wikimedia.org/T328692] *[[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey 2023]] will stop receiving new proposals on [https://zonestamp.toolforge.org/1675706431 Monday, 6 February 2023, at 18:00 UTC]. Proposers should complete any edits by then, to give time for [[m:Special:MyLanguage/Community_Wishlist_Survey/Help_us|translations]] and review. Voting will begin on Friday, 10 February. '''Future changes''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] Gadgets and user scripts will be changing to load on desktop and mobile sites. Previously they would only load on the desktop site. It is recommended that wiki administrators audit the [[MediaWiki:Gadgets-definition|gadget definitions]] prior to this change, and add <bdi lang="zxx" dir="ltr"><code>skins=…</code></bdi> for any gadgets which should not load on mobile. [https://phabricator.wikimedia.org/T328610 More details are available]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 10:21, 6 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24491749 --> == Wikipedia translation of the week: 2023-07 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Delivery robot]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Woman Takes Groceries from Dax Delivery Robot.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> A '''delivery robot''' is an autonomous robot that provides "last mile" delivery services. An operator may monitor and take control of the robot remotely in certain situations that the robot cannot resolve by itself such as when it is stuck in an obstacle. Delivery robots can be used in different settings such as food delivery, package delivery, hospital delivery, and room service. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:26, 13 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24515453 --> == Tech News: 2023-07 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/07|Translations]] are available. '''Problems''' * On wikis where patrolled edits are enabled, changes made to the [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|mentor list]] by autopatrolled mentors are not correctly marked as patrolled. It will be fixed later this week. [https://phabricator.wikimedia.org/T328444] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-15|en}}. It will be on all wikis from {{#time:j xg|2023-02-16|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * The Reply tool and other parts of [[mw:Special:MyLanguage/Help:DiscussionTools#Mobile|DiscussionTools]] will be deployed for all editors using the mobile site. You can [[mw:Special:MyLanguage/Talk_pages_project/Mobile#Status_Updates|read more about this decision]]. [https://phabricator.wikimedia.org/T298060] '''Future changes''' * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T328287][https://phabricator.wikimedia.org/T327920][https://wikitech.wikimedia.org/wiki/Deployments] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:49, 14 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24540832 --> == Wikipedia translation of the week: 2023-08 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Buddha Dhatu Jadi]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Swarno Mandir.JPG|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Buddha Dhatu Jadi''' (Bengali: বুদ্ধ ধাতু জাদি; Burmese: ဗုဒ္ဓဓာတုစေတီ also known as the Bandarban Golden Temple) is located close to Balaghata town, in Bandarban City, in Bangladesh. Dhatu are the material remains of a holy person, and in this temple the relics belong to Buddha. It is the largest Theravada Buddhist temple in Bangladesh and has the second-largest Buddha statue in the country. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:18, 20 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24581813 --> == Tech News: 2023-08 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/08|Translations]] are available. '''Problems''' * Last week, during planned maintenance of Cloud Services, unforeseen complications forced the team to turn off all tools for 2–3 hours to prevent data corruption. Work is ongoing to prevent similar problems in the future. [https://phabricator.wikimedia.org/T329535] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-22|en}}. It will be on all wikis from {{#time:j xg|2023-02-23|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). *The voting phase for the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey 2023]] ends on [https://zonestamp.toolforge.org/1677261621 24 February at 18:00 UTC]. The results of the survey will be announced on 28 February. '''Future changes''' * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T328287][https://phabricator.wikimedia.org/T327920][https://wikitech.wikimedia.org/wiki/Deployments] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:58, 21 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24570514 --> == Wikipedia translation of the week: 2023-09 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Alina Scholtz]] '''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Alina Scholtz''' (24 September 1908 – 25 February 1996) was a Polish landscape architect, known as one of country's pioneers in developing the field. Throughout her career she worked on various public and private projects for cemeteries, parks and green spaces. Some of her most noted works include the grounds of a villa on Kielecka Street in Warsaw for which she won a Silver Medal at the 1937 World Exhibition in Paris, the memorial cemetery to the victims of the Palmiry massacre, and landscaping projects along the East-West traffic route of Warsaw. In addition to her design work, she served as one of the founding members of the International Federation of Landscape Architects. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:04, 27 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24617511 --> == Tech News: 2023-09 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/09|Translations]] are available. '''Problems''' * Last week, in some areas of the world, there were problems with loading pages for 20 minutes and saving edits for 55 minutes. These issues were caused by a problem with our caching servers due to unforseen events during a routine maintenance task. [https://wikitech.wikimedia.org/wiki/Incidents/2023-02-22_wiki_outage][https://wikitech.wikimedia.org/wiki/Incidents/2023-02-22_read_only] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-01|en}}. It will be on all wikis from {{#time:j xg|2023-03-02|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:47, 27 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24634242 --> == Wikipedia translation of the week: 2023-10 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Mary Nzimiro]] '''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Mary Nzimiro''', birthname Mary Nwametu Onumonu, MBE (1898–1993) was a pioneering Nigerian businesswoman, politician and women's activist. In 1948, she was appointed principal representative of the United Africa Company (UAC) for Eastern Nigeria, while maintaining textile and cosmetics retail outlets of her own in Port Harcourt, Aba and Owerri. By the early 1950s, she was among the richest individuals in West Africa, becoming a resident of the exclusive Bernard Carr Street in Port Harcourt. On the political front, she was a member of the influential National Council of Nigeria and the Cameroons, becoming a member of its executive committee in 1957 and vice-president of the NCNC Estern Women's Association in 1962. During the Nigerian Civil War (1967–1970), she organized Igbo women in support of the Biafrans. As a result she lost most of her property in Port Harcourt and returned to her native Oguta where she died in 1993. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:47, 6 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24636259 --> == Tech News: 2023-10 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/10|Translations]] are available. '''Recent changes''' * The Community Wishlist Survey 2023 edition has been concluded. Community Tech has [[m:Special:MyLanguage/Community Wishlist Survey 2023/Results|published the results]] of the survey and will provide an update on what is next in April 2023. * On wikis which use [[mw:Special:MyLanguage/Writing_systems|LanguageConverter]] to handle multiple writing systems, articles which used custom conversion rules in the wikitext (primarily on Chinese Wikipedia) would have these rules applied inconsistently in the table of contents, especially in the Vector 2022 skin. This has now been fixed. [https://phabricator.wikimedia.org/T306862] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-08|en}}. It will be on all wikis from {{#time:j xg|2023-03-09|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * A search system has been added to the [[Special:Preferences|Preferences screen]]. This will let you find different options more easily. Making it work on mobile devices will happen soon. [https://phabricator.wikimedia.org/T313804] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:50, 6 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24676916 --> == Wikipedia translation of the week: 2023-11 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Elizabeth Langdon Williams]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Elizabeth Langdon Williams.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Elizabeth Langdon Williams''' (February 8, 1879 in Putnam, Connecticut – 1981 in Enfield, New Hampshire) was an American human computer and astronomer whose work helped lead to the discovery of Pluto, or Planet X. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:21, 13 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24700408 --> == Tech News: 2023-11 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/11|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.27|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-15|en}}. It will be on all wikis from {{#time:j xg|2023-03-16|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-cbk_zamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cdowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cebwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ckbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-csbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T304542][https://phabricator.wikimedia.org/T304550] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:20, 13 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24700189 --> == Wikipedia translation of the week: 2023-12 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:I Didn't Raise My Boy to Be a Soldier]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Peerless Quartet - I Didn't Raise my Boy to be a Soldier.ogg|300px|center]] <div style="text-align:left; padding: .4em;"> an American anti-war song that was influential within the pacifist movement that existed in the United States before it entered World War I. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:31, 20 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24720571 --> == Tech News: 2023-12 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/12|Translations]] are available. '''Problems''' * Last week, some users experienced issues loading image thumbnails. This was due to incorrectly cached images. [https://phabricator.wikimedia.org/T331820] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-22|en}}. It will be on all wikis from {{#time:j xg|2023-03-23|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] A link to the user's [[{{#special:CentralAuth}}]] page will appear on [[{{#special:Contributions}}]] — some user scripts which previously added this link may cause conflicts. This feature request was [[:m:Community Wishlist Survey 2023/Admins and patrollers/Add link to CentralAuth on Special:Contributions|voted #17 in the 2023 Community Wishlist Survey]]. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The [[{{#special:AbuseFilter}}]] edit window will be resizable and larger by default. This feature request was [[:m:Community Wishlist Survey 2023/Anti-harassment/Make the AbuseFilter edit window resizable and larger by default|voted #80 in the 2023 Community Wishlist Survey]]. * There will be a new option for Administrators when they are unblocking a user, to add the unblocked user’s user page to their watchlist. This will work both via [[{{#special:Unblock}}]] and via the API. [https://phabricator.wikimedia.org/T257662] '''Meetings''' * You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on [https://zonestamp.toolforge.org/1679677204 24 March at 17:00 (UTC)]. See [[mw:Special:MyLanguage/Wikimedia Apps/Office Hours|details and how to join]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:26, 21 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24732558 --> == Wikipedia translation of the week: 2023-13 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:es:Diana Aguavil]]'''<br /> <small>''([[:en:Diana Aguavil]]) ([[:pt:Diana Aguavil]]) ''</small> </div> Please be bold and help translate this article! ---- [[File:Diana Aguavil.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Diana Alexandra Aguavil Calazacón''' (born 7 August 1983) is an Ecuadorian indigenous leader, since 25 August 2018, the first female governor of the Tsáchila nationality after 104 years of male administrations and winning the 2018 Tsáchila election. She was also the second woman to become a candidate. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:39, 27 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24758626 --> == Tech News: 2023-13 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/13|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]] condition limit was increased from 1000 to 2000. [https://phabricator.wikimedia.org/T309609] * [[:m:Special:MyLanguage/Global AbuseFilter#Locally disabled actions|Some Global AbuseFilter]] actions will no longer apply to local projects. [https://phabricator.wikimedia.org/T332521] * Desktop users are now able to subscribe to talk pages by clicking on the {{int:discussiontools-newtopicssubscription-button-subscribe-label}} link in the {{int:toolbox}} menu. If you subscribe to a talk page, you receive [[mw:Special:MyLanguage/Notifications|notifications]] when new topics are started on that talk page. This is separate from putting the page on your watchlist or subscribing to a single discussion. [https://phabricator.wikimedia.org/T263821] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-29|en}}. It will be on all wikis from {{#time:j xg|2023-03-30|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). '''Future changes''' * You will be able to choose [[mw:Special:MyLanguage/VisualEditor/Diffs|visual diffs]] on all [[m:Special:MyLanguage/Help:Page history|history pages]] at the Wiktionaries and Wikipedias. [https://phabricator.wikimedia.org/T314588] * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] The legacy [[mw:Mobile Content Service|Mobile Content Service]] is going away in July 2023. Developers are encouraged to switch to Parsoid or another API before then to ensure service continuity. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/4MVQQTONJT7FJAXNVOFV3WWVVMCHRINE/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:14, 28 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24780854 --> == Tech News: 2023-14 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/14|Translations]] are available. '''Recent changes''' * The system for automatically creating categories for the [[mw:Special:MyLanguage/Extension:Babel|Babel]] extension has had several important changes and fixes. One of them allows you to insert templates for automatic category descriptions on creation, allowing you to categorize the new categories. [https://phabricator.wikimedia.org/T211665][https://phabricator.wikimedia.org/T64714][https://phabricator.wikimedia.org/T170654][https://phabricator.wikimedia.org/T184941][https://phabricator.wikimedia.org/T33074] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-05|en}}. It will be on all wikis from {{#time:j xg|2023-04-06|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Some older [[w:en:Web browser|Web browsers]] will stop being able to use [[w:en:JavaScript|JavaScript]] on Wikimedia wikis from this week. This mainly affects users of Internet Explorer 11. If you have an old web browser on your computer you can try to upgrade to a newer version. [https://phabricator.wikimedia.org/T178356] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The deprecated <bdi lang="zxx" dir="ltr"><code>jquery.hoverIntent</code></bdi> module has been removed. This module could be used by gadgets and user scripts, to create an artificial delay in how JavaScript responds to a hover event. Gadgets and user scripts should now use jQuery <bdi lang="zxx" dir="ltr"><code>hover()</code></bdi> or <bdi lang="zxx" dir="ltr"><code>on()</code></bdi> instead. Examples can be found in the [[mw:Special:MyLanguage/ResourceLoader/Migration_guide_(users)#jquery.hoverIntent|migration guide]]. [https://phabricator.wikimedia.org/T311194] * Some of the links in [[{{#special:SpecialPages}}]] will be re-arranged. There will be a clearer separation between links that relate to all users, and links related to your own user account. [https://phabricator.wikimedia.org/T333242] * You will be able to hide the [[mw:Special:MyLanguage/Talk pages project/Replying|Reply button]] in archived discussion pages with a new <bdi lang="zxx" dir="ltr"><code><nowiki>__ARCHIVEDTALK__</nowiki></code></bdi> magic word. There will also be a new <bdi lang="zxx" dir="ltr"><code>.mw-archivedtalk</code></bdi> CSS class for hiding the Reply button in individual sections on a page. [https://phabricator.wikimedia.org/T249293][https://phabricator.wikimedia.org/T295553][https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DiscussionTools/+/738221] '''Future changes''' * The Vega software that creates data visualizations in pages, such as graphs, will be upgraded to the newest version in the future. Graphs that still use the very old version 1.5 syntax may stop working properly. Most existing uses have been found and updated, but you can help to check, and to update any local documentation. [[phab:T260542|Examples of how to find and fix these graphs are available]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:40, 3 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24820268 --> == Tech News: 2023-15 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/15|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] In the visual editor, it is now possible to edit captions of images in galleries without opening the gallery dialog. This feature request was [[:m:Community Wishlist Survey 2023/Editing/Editable gallery captions in Visual Editor|voted #61 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T190224] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] You can now receive notifications when another user edits your user page. See the "{{int:Echo-category-title-edit-user-page}}" option in [[Special:Preferences#mw-prefsection-echo|your Preferences]]. This feature request was [[:m:Community Wishlist Survey 2023/Anti-harassment/Notifications for user page edits|voted #3 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T3876] '''Problems''' * There was a problem with all types of CentralNotice banners still being shown to logged-in users even if they had [[Special:Preferences#mw-prefsection-centralnotice-banners|turned off]] specific banner types. This has now been fixed. [https://phabricator.wikimedia.org/T331671] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-12|en}}. It will be on all wikis from {{#time:j xg|2023-04-13|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-arywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dinwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dsbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-elwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-emlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-etwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-euwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-extwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tumwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ffwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiu_vrowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fjwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frpwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-furwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gcrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-glwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-glkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gomwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gotwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-guwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gvwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T304551][https://phabricator.wikimedia.org/T308133] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:05, 10 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24851886 --> == Wikipedia translation of the week: 2023-16 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Lucy Salani]]'''<br /> <small>''([[:en:Lucy Salani]]) ([[:fr:Lucy Salani]]) ''</small> </div> Please be bold and help translate this article! ---- [[File:Lucy Salani.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lucy Salani''' was an Italian activist and is considered the only Italian transgender person to have survived the Nazi concentration camps. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:06, 17 April 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-16 == <section begin="technews-2023-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/16|Translations]] are available. '''Recent changes''' * You can now see [[mw:Special:MyLanguage/Help:Extension:Kartographer#Show_nearby_articles|nearby articles on a Kartographer map]] with the button for the new feature "{{int:Kartographer-sidebar-nearbybutton}}". Six wikis have been testing this feature since October. [https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Geoinformation/Nearby_articles#Implementation][https://phabricator.wikimedia.org/T334079] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The [[m:Special:GlobalWatchlist|Special:GlobalWatchlist]] page now has links for "{{int:globalwatchlist-markpageseen}}" for each entry. This feature request was [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Button to mark a single change as read in the global watch list|voted #161 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334246] '''Problems''' * At Wikimedia Commons, some thumbnails have not been getting replaced correctly after a new version of the image is uploaded. This should be fixed later this week. [https://phabricator.wikimedia.org/T331138][https://phabricator.wikimedia.org/T333042] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] For the last few weeks, some external tools had inconsistent problems with logging-in with OAuth. This has now been fixed. [https://phabricator.wikimedia.org/T332650] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-19|en}}. It will be on all wikis from {{#time:j xg|2023-04-20|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:55, 18 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24881071 --> == Wikipedia translation of the week: 2023-17 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ca:María Fernanda Castro Maya]]'''<br /> <small>''([[:pt:María Fernanda Castro Maya]]) ([[:eu:María Fernanda Castro Maya]]) ''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''María Fernanda Castro Maya''' is a Mexican self-advocate disability rights activist. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:55, 24 April 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-17 == <section begin="technews-2023-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/17|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The date-selection menu on pages such as [[{{#special:Contributions}}]] will now show year-ranges that are in the current and past decade, instead of the current and future decade. This feature request was [[m:Community Wishlist Survey 2023/Miscellaneous/Change year range shown in date selection popup|voted #145 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334316] '''Problems''' * Due to security issues with the [[mw:Special:MyLanguage/Extension:Graph|Graph extension]], graphs have been disabled in all Wikimedia projects. Wikimedia Foundation teams are working to respond to these vulnerabilities. [https://phabricator.wikimedia.org/T334940] * For a few days, it was not possible to save some kinds of edits on the mobile version of a wiki. This has been fixed. [https://phabricator.wikimedia.org/T334797][https://phabricator.wikimedia.org/T334799][https://phabricator.wikimedia.org/T334794] '''Changes later this week''' * All wikis will be read-only for a few minutes on April 26. This is planned for [https://zonestamp.toolforge.org/1682517653 14:00 UTC]. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.6|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-26|en}}. It will be on all wikis from {{#time:j xg|2023-04-27|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * The Editing team plans an A/B test for [[mw:Special:MyLanguage/Talk pages project/Usability|a usability analysis of the Talk page project]]. The [[mw:Special:MyLanguage/Talk pages project/Usability/Analysis|planned measurements are available]]. Your wiki [[phab:T332946|may be invited to participate]]. Please suggest improvements to the measurement plan at [[mw:Talk:Talk pages project/Usability|the discussion page]]. * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2023-2024|The Wikimedia Foundation annual plan 2023-2024 draft is open for comment and input]] until May 19. The final plan will be published in July 2023 on Meta-wiki. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:04, 24 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24933592 --> == Wikipedia translation of the week: 2023-18 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sonia Orbuch]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Sonia Shainwald Orbuch''' (born Sarah Shainwald, May 24, 1925 – September 30, 2018) was an American Holocaust educator. During the Second World War she was a Jewish resistance fighter in eastern Poland. Orbuch hid in the forests of Poland with her family during the Second World War. She joined a group of Soviet partisans, being renamed Sonia in case she was captured, and helped fight against the Germans. After the war, she returned home, where she met her future husband. After having a daughter in a refugee camp in Germany, the family eventually emigrated to the United States. She spent the rest of life in public engagement, speaking about her experiences and in 2009, published her autobiography, Here, There Are No Sarahs: A Woman's Courageous Fight Against the Nazis and Her Bittersweet Fulfillment of the American Dream. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 06:24, 1 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-18 == <section begin="technews-2023-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/18|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The content attribution tools [[mw:Special:MyLanguage/Who Wrote That?|Who Wrote That?]], [[xtools:authorship|XTools Authorship]], and [[xtools:blame|XTools Blame]] now support the French and Italian Wikipedias. More languages will be added in the near future. This is part of the [[m:Community Wishlist Survey 2023/Reading/Extend "Who Wrote That?" tool to more wikis|#7 wish in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T243711][https://phabricator.wikimedia.org/T270490][https://phabricator.wikimedia.org/T334891] * The [[:commons:Special:MyLanguage/Commons:Video2commons|Video2commons]] tool has been updated. This fixed several bugs related to YouTube uploads. [https://github.com/toolforge/video2commons/pull/162/commits] * The [[{{#special:Preferences}}]] page has been redesigned on mobile web. The new design makes it easier to browse the different categories and settings at low screen widths. You can also now access the page via a link in the Settings menu in the mobile web sidebar. [https://www.mediawiki.org/wiki/Moderator_Tools/Content_moderation_on_mobile_web/Preferences] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-02|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-03|en}}. It will be on all wikis from {{#time:j xg|2023-05-04|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:45, 2 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24966974 --> == Wikipedia translation of the week: 2023-19 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Nadia Ghulam]]'''<br /><small>''([[:fr:Nadia Ghulam]]) ([[:es:Nadia Ghulam]]) ([[:ca:Nadia Ghulam]])''</small> </div> Please be bold and help translate this article! ---- [[File:Nadia Ghulam (cropped).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Nadia Ghulam Dastgir''' is an Afghan woman who spent ten years posing as her dead brother to evade the Taliban's strictures against women. Her book about her experiences, written with Agnès Rotger and published in 2010, El secret del meu turbant (The Secret of My Turban), won the Prudenci Bertrana Prize for fiction. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:37, 8 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24966177 --> == Tech News: 2023-19 == <section begin="technews-2023-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/19|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] Last week, Community Tech released the first update for providing [[m:Special:MyLanguage/Community Wishlist Survey 2022/Better diff handling of paragraph splits|better diffs]], the #1 request in the 2022 Community Wishlist Survey. [[phab:T324759|This update]] adds legends and tooltips to inline diffs so that users unfamiliar with the blue and yellow highlights can better understand the type of edits made. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] When you close an image that is displayed via MediaViewer, it will now return to the wiki page instead of going back in your browser history. This feature request was [[m:Community Wishlist Survey 2023/Reading/Return to the article when closing the MediaViewer|voted #65 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T236591] * The [[mw:Special:MyLanguage/Extension:SyntaxHighlight|SyntaxHighlight]] extension now supports <bdi lang="en" dir="ltr"><code>wikitext</code></bdi> as a selected language. Old alternatives that were used to highlight wikitext, such as <bdi lang="en" dir="ltr"><code>html5</code></bdi>, <bdi lang="en" dir="ltr"><code>moin</code></bdi>, and <bdi lang="en" dir="ltr"><code>html+handlebars</code></bdi>, can now be replaced. [https://phabricator.wikimedia.org/T29828] * [[mw:Special:MyLanguage/Manual:Creating pages with preloaded text|Preloading text to new pages/sections]] now supports preloading from localized MediaWiki interface messages. [https://cs.wikipedia.org/wiki/User_talk:Martin_Urbanec_(WMF)?action=edit&section=new&preload=MediaWiki:July Here is an example] at the {{int:project-localized-name-cswiki/en}} that uses <bdi lang="zxx" dir="ltr"><code><nowiki>preload=MediaWiki:July</nowiki></code></bdi>. [https://phabricator.wikimedia.org/T330337] '''Problems''' * Graph Extension update: Foundation developers have completed upgrading the visualization software to Vega5. Existing community graphs based on Vega2 are no longer compatible. Communities need to update local graphs and templates, and shared lua modules like <bdi lang="de" dir="ltr">[[:de:Modul:Graph]]</bdi>. The [https://vega.github.io/vega/docs/porting-guide/ Vega Porting guide] provides the most comprehensive detail on migration from Vega2 and [https://www.mediawiki.org/w/index.php?title=Template:Graph:PageViews&action=history here is an example migration]. Vega5 has currently just been enabled on mediawiki.org to provide a test environment for communities. [https://phabricator.wikimedia.org/T334940#8813922] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.8|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-10|en}}. It will be on all wikis from {{#time:j xg|2023-05-11|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Until now, all new OAuth apps went through manual review. Starting this week, apps using identification-only or basic authorizations will not require review. [https://phabricator.wikimedia.org/T67750] '''Future changes''' * During the next year, MediaWiki will stop using IP addresses to identify logged-out users, and will start automatically assigning unique temporary usernames. Read more at [[m:Special:MyLanguage/IP Editing: Privacy Enhancement and Abuse Mitigation/Updates|IP Editing: Privacy Enhancement and Abuse Mitigation/Updates]]. You can [[m:Talk:IP Editing: Privacy Enhancement and Abuse Mitigation#What should it look like?|join the discussion]] about the [[m:Special:MyLanguage/IP Editing: Privacy Enhancement and Abuse Mitigation/Updates#What will temporary usernames look like?|format of the temporary usernames]]. [https://phabricator.wikimedia.org/T332805] * There will be an [[:w:en:A/B testing|A/B test]] on 10 Wikipedias where the Vector 2022 skin is the default skin. Half of logged-in desktop users will see an interface where the different parts of the page are more clearly separated. You can [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Updates/2023-05 Zebra9 A/B test|read more]]. [https://phabricator.wikimedia.org/T333180][https://phabricator.wikimedia.org/T335972] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] <code>jquery.tipsy</code> will be removed from the MediaWiki core. This will affect some user scripts. Many lines with <code>.tipsy(</code> can be commented out. <code>OO.ui.PopupWidget</code> can be used to keep things working like they are now. You can [[phab:T336019|read more]] and [[:mw:Help:Locating broken scripts|read about how to find broken scripts]]. [https://phabricator.wikimedia.org/T336019] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:36, 9 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24998636 --> == Wikipedia translation of the week: 2023-20 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Purple Day]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Epilepsy Warrior Brooch May 2018 Purple Day.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Purple Day''' is a global grassroots event that was formed with the intention to increase worldwide awareness of epilepsy, and to dispel common myths and fears of this neurological disorder. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:17, 15 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25000361 --> == Tech News: 2023-20 == <section begin="technews-2023-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/20|Translations]] are available. '''Problems''' * Citations that are automatically generated based on [[d:Q33057|ISBN]] are currently broken. This affects citations made with the [[mw:Special:MyLanguage/Help:VisualEditor/User_guide/Citations-Full#Automatic|VisualEditor Automatic tab]], and the use of the citoid API in gadgets and user scripts. Work is ongoing to restore this feature. [https://phabricator.wikimedia.org/T336298] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-17|en}}. It will be on all wikis from {{#time:j xg|2023-05-18|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-gorwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hakwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hifwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hsbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-htwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-igwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ilowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-inhwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jvwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308134] '''Future changes''' * There is a recently formed team at the Wikimedia Foundation which will be focusing on experimenting with new tools. Currently they are building [[m:Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI|a prototype ChatGPT plugin that allows information generated by ChatGPT to be properly attributed]] to the Wikimedia projects. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadget and userscript developers should replace <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> with <bdi lang="zxx" dir="ltr"><code>mediawiki.cookie</code></bdi>. The <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> library will be removed in ~1 month, and staff developers will run a script to replace any remaining uses at that time. [https://phabricator.wikimedia.org/T336018] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:45, 15 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25011501 --> == Tech News: 2023-21 == <section begin="technews-2023-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/21|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The "recent edits" time period for page watchers is now 30 days. It used to be 180 days. This was a [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Change information about the number of watchers on a page|Community Wishlist Survey proposal]]. [https://phabricator.wikimedia.org/T336250] '''Changes later this week''' * An [[mw:special:MyLanguage/Growth/Positive reinforcement#Impact|improved impact module]] will be available at Wikipedias. The impact module is a feature available to newcomers [[mw:Special:MyLanguage/Growth/Feature summary#Newcomer homepage|at their personal homepage]]. It will show their number of edits, how many readers their edited pages have, how many thanks they have received and similar things. It is also accessible by accessing Special:Impact. [https://phabricator.wikimedia.org/T336203] * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-24|en}}. It will be on all wikis from {{#time:j xg|2023-05-25|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W21"/> 16:55, 22 May 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25028325 --> == Wikipedia translation of the week: 2023-22 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Valencian Art Nouveau]]'''<br /> <small>''([[:es:Modernismo valenciano]])''</small> </div> Please be bold and help translate this article! ---- [[File:Santuario Novelda.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Valencian Art Nouveau''' (Spanish: modernismo valenciano, Valencian: modernisme valencià), is the historiographic denomination given to an art and literature movement associated with the Art Nouveau in the Valencian Community, in Spain. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:46, 29 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25074014 --> == Tech News: 2023-22 == <section begin="technews-2023-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/22|Translations]] are available. '''Recent changes''' * Citations can once again be added automatically from ISBNs, thanks to Zotero's ISBN searches. The current data sources are the Library of Congress (United States), the Bibliothèque nationale de France (French National Library), and K10plus ISBN (German repository). Additional data source searches can be [[mw:Citoid/Creating Zotero translators|proposed to Zotero]]. The ISBN labels in the [[mw:Special:MyLanguage/Help:VisualEditor/User_guide/Citations-Full#Automatic|VisualEditor Automatic tab]] will reappear later this week. [https://phabricator.wikimedia.org/T336298#8859917] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The page [[{{#special:EditWatchlist}}]] now has "{{int:watchlistedit-normal-check-all}}" options to select all the pages within a namespace. This feature request was [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Watchlist edit - "check all" checkbox|voted #161 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334252] '''Problems''' * For a few days earlier this month, the "Add interlanguage link" item in the Tools menu did not work properly. This has now been fixed. [https://phabricator.wikimedia.org/T337081] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.11|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-31|en}}. It will be on all wikis from {{#time:j xg|2023-06-01|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * VisualEditor will be switched to a new backend on [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/small.dblist small] and [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/medium.dblist medium] wikis this week. Large wikis will follow in the coming weeks. This is part of the effort to move Parsoid into MediaWiki core. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [https://phabricator.wikimedia.org/T320529] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:04, 29 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25079963 --> == Wikipedia translation of the week: 2023-23 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:pt:Alessandra Korap]]'''<br /> <small>''([[:en:Alessandra Korap]]) ''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Alessandra Korap''' is an indigenous leader and Brazilian environmental activist from the Munduruku ethnic group. Her main work is defending the demarcation of indigenous territory and denouncing the illegal exploitation and activities of the mining and logging industries. Alessandra is internationally recognized for her work. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:33, 5 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25111481 --> == Tech News: 2023-23 == <section begin="technews-2023-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/23|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Help:Extension:RealMe|RealMe]] extension allows you to mark URLs on your user page as verified for Mastodon and similar software. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] Citation and footnote editing can now be started from the reference list when using the visual editor. This feature request was [[m:Community Wishlist Survey 2023/Citations/Allow citations to be edited in the references section with VisualEditor|voted #2 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T54750] * Previously, clicking on someone else's link to Recent Changes with filters applied within the URL could unintentionally change your preference for "{{int:Rcfilters-group-results-by-page}}". This has now been fixed. [https://phabricator.wikimedia.org/T202916#8874081] '''Problems''' * For a few days last week, some tools and bots returned outdated information due to database replication problems, and may have been down entirely while it was being fixed. These issues have now been fixed. [https://phabricator.wikimedia.org/T337446] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.12|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-06|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-07|en}}. It will be on all wikis from {{#time:j xg|2023-06-08|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Bots will no longer be prevented from making edits because of URLs that match the [[mw:Special:MyLanguage/Extension:SpamBlacklist|spam blacklist]]. [https://phabricator.wikimedia.org/T313107] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:52, 5 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25114640 --> == Wikipedia translation of the week: 2023-24 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cassinga Day]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Cassinga Day''' is a national public holiday in Namibia remembering the Cassinga Massacre. Commemorated annually on 4 May, the date "remembers those (approximately 600) killed in 1978 when the South African Defence Force attacked a SWAPO base at Cassinga in southern Angola". <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:07, 12 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25111481 --> == Tech News: 2023-24 == <section begin="technews-2023-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/24|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The content attribution tools [[mw:Special:MyLanguage/Who Wrote That?|Who Wrote That?]], [[xtools:authorship|XTools Authorship]], and [[xtools:blame|XTools Blame]] now support the Dutch, German, Hungarian, Indonesian, Japanese, Polish and Portuguese Wikipedias. This was the [[m:Community Wishlist Survey 2023/Reading/Extend "Who Wrote That?" tool to more wikis|#7 wish in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334891] * The [[mw:Special:MyLanguage/Structured Data Across Wikimedia/Search Improvements#Search Preview panel|Search Preview panel]] has been deployed on four Wikipedias (Catalan, Dutch, Hungarian and Norwegian). The panel will show an image related to the article (if existing), the top sections of the article, related images (coming from MediaSearch on Commons), and eventually the sister projects associated with the article. [https://phabricator.wikimedia.org/T306341] * The [[:mw:Special:MyLanguage/Help:Extension:RealMe#Verifying_a_link_on_non-user_pages|RealMe]] extension now allows administrators to verify URLs for any page, for Mastodon and similar software. [https://phabricator.wikimedia.org/T324937] * The default project license [https://lists.wikimedia.org/hyperkitty/list/wikimediaannounce-l@lists.wikimedia.org/thread/7G6XPWZPQFLZ2JANN3ZX6RT4DVUI3HZQ/ has been officially upgraded] to CC BY-SA 4.0. The software interface messages have been updated. Communities should feel free to start updating any mentions of the old CC BY-SA 3.0 licensing within policies and related documentation pages. [https://phabricator.wikimedia.org/T319064] '''Problems''' * For three days last month, some Wikipedia pages edited with VisualEditor or DiscussionTools had an unintended <code><nowiki>__TOC__</nowiki></code> (or its localized form) added during an edit. There is [[mw:Parsoid/Deployments/T336101_followup|a listing of affected pages sorted by wiki]], that may still need to be fixed. [https://phabricator.wikimedia.org/T336101] * Currently, the "{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}" feature in VisualEditor is broken. Existing <code><nowiki>{{DEFAULTSORT:...}}</nowiki></code> keywords incorrectly appear as missing templates in VisualEditor. Developers are exploring how to fix this. In the meantime, those wishing to edit the default sortkey of a page are advised to switch to source editing. [https://phabricator.wikimedia.org/T337398] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Last week, an update to the delete form may have broken some gadgets or user scripts. If you need to manipulate (empty) the reason field, replace <bdi lang="zxx" dir="ltr"><code>#wpReason</code></bdi> with <bdi lang="zxx" dir="ltr" style="white-space: nowrap;"><code>#wpReason > input</code></bdi>. See [https://cs.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-CleanDeleteReasons.js&diff=22859956&oldid=12794189 an example fix]. [https://phabricator.wikimedia.org/T337809] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.13|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-13|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-14|en}}. It will be on all wikis from {{#time:j xg|2023-06-15|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * VisualEditor will be switched to a new backend on English Wikipedia on Monday, and all other [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/large.dblist large] wikis on Thursday. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [https://phabricator.wikimedia.org/T320529] '''Future changes''' * From 5 June to 17 July, the Foundation's [[:mw:Wikimedia Security Team|Security team]] is holding a consultation with contributors regarding a draft policy to govern the use of third-party resources in volunteer-developed gadgets and scripts. Feedback and suggestions are warmly welcome at [[m:Special:MyLanguage/Third-party resources policy|Third-party resources policy]] on meta-wiki. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:52, 12 June 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25133779 --> == Tech News: 2023-25 == <section begin="technews-2023-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/25|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Flame graphs are now available in WikimediaDebug. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/JXNQD3EHG5V5QW5UXFDPSHQG4MJ3FWJQ/][https://techblog.wikimedia.org/2023/06/08/flame-graphs-arrive-in-wikimediadebug/] '''Changes later this week''' * There is no new MediaWiki version this week. * There is now a toolbar search popup in the visual editor. You can trigger it by typing <code>\</code> or pressing <code>ctrl + shift + p</code>. It can help you quickly access most tools in the editor. [https://commons.wikimedia.org/wiki/File:Visual_editor_toolbar_search_feature.png][https://phabricator.wikimedia.org/T66905] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:09, 19 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25159510 --> == Wikipedia translation of the week: 2023-26 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Rawon]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Rawon Setan.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Rawon''' (Javanese: ꦫꦮꦺꦴꦤ꧀) is an Indonesian beef soup. Originating from East Java, rawon utilizes the black keluak nut as the main seasoning, which gives a dark color and nutty flavor to the soup. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:18, 26 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25177056 --> == Tech News: 2023-26 == <section begin="technews-2023-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/26|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Action API modules and Special:LinkSearch will now add a trailing <bdi lang="zxx" dir="ltr"><code>/</code></bdi> to all <bdi lang="zxx" dir="ltr"><code>prop=extlinks</code></bdi> responses for bare domains. This is part of the work to remove duplication in the <code>externallinks</code> database table. [https://phabricator.wikimedia.org/T337994] '''Problems''' * Last week, search was broken on Commons and Wikidata for 23 hours. [https://phabricator.wikimedia.org/T339810][https://wikitech.wikimedia.org/wiki/Incidents/2023-06-18_search_broken_on_wikidata_and_commons] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.15|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-27|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-28|en}}. It will be on all wikis from {{#time:j xg|2023-06-29|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Minerva skin now applies more predefined styles to the <bdi lang="zxx" dir="ltr"><code>.mbox-text</code></bdi> CSS class. This enables support for mbox templates that use divs instead of tables. Please make sure that the new styles won't affect other templates in your wiki. [https://gerrit.wikimedia.org/r/c/mediawiki/skins/MinervaNeue/+/930901/][https://phabricator.wikimedia.org/T339040] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadgets will now load on both desktop and mobile by default. Previously, gadgets loaded only on desktop by default. Changing this default using the <bdi lang="zxx" dir="ltr"><code>|targets=</code></bdi> parameter is also deprecated and should not be used. You should make gadgets work on mobile or disable them based on the skin (with the <bdi lang="zxx" dir="ltr"><code>|skins=</code></bdi> parameter in <bdi lang="en" dir="ltr">MediaWiki:Gadgets-definition</bdi>) rather than whether the user uses the mobile or the desktop website. Popular gadgets that create errors on mobile will be disabled by developers on the Minerva skin as a temporary solution. [https://phabricator.wikimedia.org/T127268] * All namespace tabs now have the same browser [[m:Special:MyLanguage/Help:Keyboard_shortcuts|access key]] by default. Previously, custom and extension-defined namespaces would have to have their access keys set manually on-wiki, but that is no longer necessary. [https://phabricator.wikimedia.org/T22126] * The review form of the Flagged Revisions extension now uses the standardized [[mw:Special:MyLanguage/Codex|user interface components]]. [https://phabricator.wikimedia.org/T191156] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] How media is structured in the parser's HTML output will change in the coming weeks at [[:wikitech:Deployments/Train#Thursday|group2 wikis]]. This change improves the accessibility of content. You may need to update your site-CSS, or userscripts and gadgets. There are [[mw:Special:MyLanguage/Parsoid/Parser_Unification/Media_structure/FAQ|details on what code to check, how to update the code, and where to report any related problems]]. [https://phabricator.wikimedia.org/T314318] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:19, 26 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25202311 --> == Wikipedia translation of the week: 2023-27 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hook echo]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Tornadic classic supercell radar.gif|center|300px]] <div style="text-align:left; padding: .4em;"> A '''hook echo''' is a pendant or hook-shaped weather radar signature as part of some supercell thunderstorms. It is found in the lower portions of a storm as air and precipitation flow into a mesocyclone, resulting in a curved feature of reflectivity. The echo is produced by rain, hail, or even debris being wrapped around the supercell <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:18, 3 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25241057 --> == Tech News: 2023-27 == <section begin="technews-2023-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/27|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the rolling out of the [[m:Community Wishlist Survey 2022/Multimedia and Commons/Audio links that play on click|audio links that play on click]] wishlist proposal, [https://noc.wikimedia.org/conf/highlight.php?file=dblists/small.dblist small wikis] will now be able to use the [[mw:Special:MyLanguage/Help:Extension:Phonos#Inline audio player mode|inline audio player]] that is implemented by the [[mw:Extension:Phonos|Phonos]] extension. [https://phabricator.wikimedia.org/T336763] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] From this week all gadgets automatically load on mobile and desktop sites. If you see any problems with gadgets on your wikis, please adjust the [[mw:Special:MyLanguage/Extension:Gadgets#Options|gadget options]] in your gadget definitions file. [https://phabricator.wikimedia.org/T328610] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.16|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-05|en}}. It will be on all wikis from {{#time:j xg|2023-07-06|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:51, 3 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25231546 --> == Tech News: 2023-28 == <section begin="technews-2023-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/28|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Structured Data Across Wikimedia/Section-level Image Suggestions|Section-level Image Suggestions feature]] has been deployed on seven Wikipedias (Portuguese, Russian, Indonesian, Catalan, Hungarian, Finnish and Norwegian Bokmål). The feature recommends images for articles on contributors' watchlists that are a good match for individual sections of those articles. * [[:m:Special:MyLanguage/Global AbuseFilter|Global abuse filters]] have been enabled on all Wikimedia projects, except English and Japanese Wikipedias (who opted out). This change was made following a [[:m:Requests for comment/Make global abuse filters opt-out|global request for comments]]. [https://phabricator.wikimedia.org/T341159] * [[{{#special:BlockedExternalDomains}}]] is a new tool for administrators to help fight spam. It provides a clearer interface for blocking plain domains (and their subdomains), is more easily searchable, and is faster for the software to process for each edit on the wiki. It does not support regex (for complex cases), nor URL path-matching, nor the [[MediaWiki:Spam-whitelist|MediaWiki:Spam-whitelist]], but otherwise it replaces most of the functionalities of the existing [[MediaWiki:Spam-blacklist|MediaWiki:Spam-blacklist]]. There is a Python script to help migrate all simple domains into this tool, and more feature details, within [[mw:Special:MyLanguage/Manual:BlockedExternalDomains|the tool's documentation]]. It is available at all wikis except for Meta-wiki, Commons, and Wikidata. [https://phabricator.wikimedia.org/T337431] * The WikiEditor extension was updated. It includes some of the most frequently used features of wikitext editing. In the past, many of its messages could only be translated by administrators, but now all regular translators on translatewiki can translate them. Please check [https://translatewiki.net/wiki/Special:MessageGroupStats?group=ext-wikieditor&messages=&x=D#sortable:0=asc the state of WikiEditor localization into your language], and if the "Completion" for your language shows anything less than 100%, please complete the translation. See [https://lists.wikimedia.org/hyperkitty/list/wikitech-ambassadors@lists.wikimedia.org/thread/D4YELU2DXMZ75PGELUOKXXMFF3FH45XA/ a more detailed explanation]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.17|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-12|en}}. It will be on all wikis from {{#time:j xg|2023-07-13|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * The default protocol of [[{{#special:LinkSearch}}]] and API counterparts has changed from http to both http and https. [https://phabricator.wikimedia.org/T14810] * [[{{#special:LinkSearch}}]] and its API counterparts will now search for all of the URL provided in the query. It used to be only the first 60 characters. This feature was requested fifteen years ago. [https://phabricator.wikimedia.org/T17218] '''Future changes''' * There is an experiment with a [[:w:en:ChatGPT|ChatGPT]] plugin. This is to show users where the information is coming from when they read information from Wikipedia. It has been tested by Wikimedia Foundation staff and other Wikimedians. Soon all ChatGPT plugin users can use the Wikipedia plugin. This is the same plugin which was mentioned in [[m:Special:MyLanguage/Tech/News/2023/20|Tech News 2023/20]]. [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI] * There is an ongoing discussion on a [[m:Special:MyLanguage/Third-party resources policy|proposed Third-party resources policy]]. The proposal will impact the use of third-party resources in gadgets and userscripts. Based on the ideas received so far, policy includes some of the risks related to user scripts and gadgets loading third-party resources, some best practices and exemption requirements such as code transparency and inspectability. Your feedback and suggestions are warmly welcome until July 17, 2023 on [[m:Talk:Third-party resources policy|on the policy talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:54, 10 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25278797 --> == Wikipedia translation of the week: 2023-29 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Esther Cooper Jackson]]'''<br /> <small>''([[:fr:Esther Cooper Jackson]]) ([[:simple:Esther Cooper Jackson]])''</small> </div> Please be bold and help translate this article! ---- [[File:Esther Cooper Jackson, 1968, Great Barrington.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Esther Victoria Cooper Jackson''' was an American civil rights activist and social worker. She was one of the founding editors of the magazine Freedomways. She also was an organizational and executive secretary at the Southern Negro Youth Congress. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:14, 17 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25266525 --> == Tech News: 2023-29 == <section begin="technews-2023-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/29|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] We are now serving 1% of all global user traffic from [[w:en:Kubernetes|Kubernetes]] (you can [[wikitech:MediaWiki On Kubernetes|read more technical details]]). We are planning to increment this percentage regularly. You can [[phab:T290536|follow the progress of this work]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.18|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-19|en}}. It will be on all wikis from {{#time:j xg|2023-07-20|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki [[mw:Special:MyLanguage/Help:System_message|system messages]] will now look for available local fallbacks, instead of always using the default fallback defined by software. This means wikis no longer need to override each language on the [[mw:Special:MyLanguage/Manual:Language#Fallback_languages|fallback chain]] separately. For example, English Wikipedia doesn't have to create <bdi lang="zxx" dir="ltr"><code>en-ca</code></bdi> and <bdi lang="zxx" dir="ltr"><code>en-gb</code></bdi> subpages with a transclusion of the base pages anymore. This makes it easier to maintain local overrides. [https://phabricator.wikimedia.org/T229992] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The <bdi lang="zxx" dir="ltr"><code>action=growthsetmentorstatus</code></bdi> API will be deprecated with the new MediaWiki version. Bots or scripts calling that API should use the <bdi lang="zxx" dir="ltr"><code>action=growthmanagementorlist</code></bdi> API now. [https://phabricator.wikimedia.org/T321503] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:08, 17 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25289122 --> == Wikipedia translation of the week: 2023-30 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cut of pork]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:American Pork Cuts.svg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''cuts of pork''' are the different parts of the pig which are consumed as food by humans. The terminology and extent of each cut varies from country to country. There are between four and six primal cuts, which are the large parts in which the pig is first cut: the shoulder (blade and picnic), loin, belly (spare ribs and side) and leg <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:21, 24 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25318972 --> == Tech News: 2023-30 == <section begin="technews-2023-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/30|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] On July 18, the Wikimedia Foundation launched a survey about the [[:mw:Technical_decision_making|technical decision making process]] for people who do technical work that relies on software that is maintained by the Foundation or affiliates. If this applies to you, [https://wikimediafoundation.limesurvey.net/885471 please take part in the survey]. The survey will be open for three weeks, until August 7. You can find more information in [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/Q7DUCFA75DXG3G2KHTO7CEWMLCYTSDB2/|the announcement e-mail on wikitech-l]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-26|en}}. It will be on all wikis from {{#time:j xg|2023-07-27|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:20, 25 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25332248 --> == Wikipedia translation of the week: 2023-31 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Gunhild Cross]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Gunhildkorset.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Gunhild Cross''' (Danish: Gunhildkorset), named for its first owner, Gunhild, a daughter of Svend III of Denmark, is a mid-12th-century crucifix carved in walrus tusk and with both Latin and Runic inscriptions. It is now in the collection of the National Museum of Denmark. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:48, 31 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25380210 --> == Tech News: 2023-31 == <section begin="technews-2023-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/31|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Synchronizer|Synchronizer]] tool is now available to keep Lua modules synced across Wikimedia wikis, along with [[mw:Multilingual Templates and Modules|updated documentation]] to develop global Lua modules and templates. * The tag filter on [[{{#special:NewPages}}]] and revision history pages can now be inverted. For example, you can hide edits that were made using an automated tool. [https://phabricator.wikimedia.org/T334337][https://phabricator.wikimedia.org/T334338] * The Wikipedia [[:w:en:ChatGPT|ChatGPT]] plugin experiment can now be used by ChatGPT users who can use plugins. You can participate in a [[:m:Talk:Wikimedia Foundation Annual Plan/2023-2024/Draft/Future Audiences#Announcing monthly Future Audiences open "office hours"|video call]] if you want to talk about this experiment or similar work. [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI] '''Problems''' * It was not possible to generate a PDF for pages with non-Latin characters in the title, for the last two weeks. This has now been fixed. [https://phabricator.wikimedia.org/T342442] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-01|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-02|en}}. It will be on all wikis from {{#time:j xg|2023-08-03|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Tuesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-kawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kaawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kabwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kbdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kbpwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-knwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kshwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kwwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308135] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:54, 31 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25362228 --> == Wikipedia translation of the week: 2023-32 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Polyura athamas]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Close wing mud-puddling position of Charaxes bharata (C.& R. Felder,1867) - Indian Nawab.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''''Polyura athamas''''', the common nawab, is a species of fast-flying canopy butterfly found in tropical Asia. It belongs to the Charaxinae (rajahs and nawabs) in the brush-footed butterfly family (Nymphalidae). <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 03:14, 7 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25410866 --> == Tech News: 2023-32 == <section begin="technews-2023-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/32|Translations]] are available. '''Recent changes''' * Mobile Web editors can now [[mw:Special:MyLanguage/Reading/Web/Advanced_mobile_contributions#August_1,_2023_-_Full-page_editing_added_on_mobile|edit a whole page at once]]. To use this feature, turn on "{{int:Mobile-frontend-mobile-option-amc}}" in your settings and use the "{{int:Minerva-page-actions-editfull}}" button in the "{{int:Minerva-page-actions-overflow}}" menu. [https://phabricator.wikimedia.org/T203151] '''Changes later this week''' * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:21, 7 August 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25420038 --> == Wikipedia translation of the week: 2023-33 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Women's page]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:"Doings in Pittsburg Society" The Pittsburg Press February 1, 1920.png|center|300px]] <div style="text-align:left; padding: .4em;"> The '''women's page''' (sometimes called home page or women's section) of a newspaper was a section devoted to covering news assumed to be of interest to women. Women's pages started out in the 19th century as society pages and eventually morphed into features sections in the 1970s. Although denigrated during much of that period, they had a significant impact on journalism and in their communities. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:51, 14 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-33 == <section begin="technews-2023-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/33|Translations]] are available. '''Recent changes''' * The Content translation system is no longer using Youdao's [[mw:Special:MyLanguage/Help:Content_translation/Translating/Initial_machine_translation|machine translation service]]. The service was in place for several years, but due to no usage, and availability of alternatives, it was deprecated to reduce maintenance overheads. Other services which cover the same languages are still available. [https://phabricator.wikimedia.org/T329137] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-15|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-16|en}}. It will be on all wikis from {{#time:j xg|2023-08-17|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-lawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ladwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lbewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lezwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lfnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-liwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lijwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lmowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ltgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-maiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-map_bmswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mdfwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kywiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308136] <!-- TODO replace wiki codes --> '''Future changes''' * A few gadgets/user scripts which add icons to the Minerva skin need to have their CSS updated. There are more details available including a [[phab:T344067|search for all existing instances and how to update them]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 06:00, 15 August 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25428668 --> == Wikipedia translation of the week: 2023-34 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Insect toxin]]'''<br /> <small>''([[:de:Insektengift]])''</small> </div> Please be bold and help translate this article! ---- [[File:PDB 1lmr EBI.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Insect toxins''' are various protein toxins produced by insect species. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:32, 21 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-34 == <section begin="technews-2023-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/34|Translations]] are available. '''Recent changes''' * The [https://gdrive-to-commons.toolforge.org/ GDrive to Commons Uploader] tool is now available. It enables [[m:Special:MyLanguage/GDrive to Commons Uploader|securely selecting and uploading files]] from your Google Drive directly to Wikimedia Commons. [https://phabricator.wikimedia.org/T267868] * From now on, we will announce new Wikimedia wikis in Tech News, so you can update any tools or pages. ** Since the last edition, two new wikis have been created: *** a Wiktionary in [[d:Q7121294|Pa'O]] ([[wikt:blk:|<code>wikt:blk:</code>]]) [https://phabricator.wikimedia.org/T343540] *** a Wikisource in [[d:Q34002|Sundanese]] ([[s:su:|<code>s:su:</code>]]) [https://phabricator.wikimedia.org/T343539] ** To catch up, the next most recent six wikis are: *** Wikifunctions ([[f:|<code>f:</code>]]) [https://phabricator.wikimedia.org/T275945] *** a Wiktionary in [[d:Q2891049|Mandailing]] ([[wikt:btm:|<code>wikt:btm:</code>]]) [https://phabricator.wikimedia.org/T335216] *** a Wikipedia in [[d:Q5555465|Ghanaian Pidgin]] ([[w:gpe:|<code>w:gpe:</code>]]) [https://phabricator.wikimedia.org/T335969] *** a Wikinews in [[d:Q3111668|Gungbe]] ([[n:guw:|<code>n:guw:</code>]]) [https://phabricator.wikimedia.org/T334394] *** a Wiktionary in [[d:Q33522|Kabardian]] ([[wikt:kbd:|<code>wikt:kbd:</code>]]) [https://phabricator.wikimedia.org/T333266] *** a Wikipedia in [[d:Q35570|Fante]] ([[w:fat:|<code>w:fat:</code>]]) [https://phabricator.wikimedia.org/T335016] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-22|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-23|en}}. It will be on all wikis from {{#time:j xg|2023-08-24|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] There is an existing [[mw:Stable interface policy|stable interface policy]] for MediaWiki backend code. There is a [[mw:User:Jdlrobson/Stable interface policy/frontend|proposed stable interface policy for frontend code]]. This is relevant for anyone who works on gadgets or Wikimedia frontend code. You can read it, discuss it, and let the proposer know if there are any problems. [https://phabricator.wikimedia.org/T344079] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W34"/> 15:25, 21 August 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25497111 --> == Wikipedia translation of the week: 2023-35 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Manchester Blitz]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Air Raid Damage in Britain- Manchester HU49833.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Manchester Blitz''' (also known as the Christmas Blitz) was the heavy bombing of the city of Manchester and its surrounding areas in North West England during the Second World War by the German Luftwaffe. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:16, 28 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-35 == <section begin="technews-2023-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/35|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Community Wishlist Survey 2022/Better diff handling of paragraph splits|better diff handling of paragraph splits]], improved detection of splits is being rolled out. Over the last two weeks, we deployed this support to [[wikitech:Deployments/Train#Groups|group0]] and group1 wikis. This week it will be deployed to group2 wikis. [https://phabricator.wikimedia.org/T341754] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] All [[{{#special:Contributions}}]] pages now show the user's local edit count and the account's creation date. [https://phabricator.wikimedia.org/T324166] * Wikisource users can now use the <bdi lang="zxx" dir="ltr"><code>prpbengalicurrency</code></bdi> label to denote Bengali currency characters as page numbers inside the <bdi lang="zxx" dir="ltr"><code><nowiki><pagelist></nowiki></code></bdi> tag. [https://phabricator.wikimedia.org/T268932] * Two preferences have been relocated. The preference "{{int:visualeditor-preference-visualeditor}}" is now shown on the [[Special:Preferences#mw-prefsection-editing|"{{int:prefs-editing}}" tab]] at all wikis. Previously it was shown on the "{{int:prefs-betafeatures}}" tab at some wikis. The preference "{{int:visualeditor-preference-newwikitexteditor-enable}}" is now also shown on the "{{int:prefs-editing}}" tab at all wikis, instead of the "{{int:prefs-betafeatures}}" tab. [https://phabricator.wikimedia.org/T335056][https://phabricator.wikimedia.org/T344158] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.24|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-29|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-30|en}}. It will be on all wikis from {{#time:j xg|2023-08-31|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] New signups for a Wikimedia developer account will start being pushed towards <bdi lang="en" dir="ltr">[https://idm.wikimedia.org/ idm.wikimedia.org]</bdi>, rather than going via Wikitech. [[wikitech:IDM|Further information about the new system is available]]. * All right-to-left language wikis, plus Korean, Armenian, Ukrainian, Russian, and Bulgarian Wikipedias, will have a link in the sidebar that provides a short URL of that page, using the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]]. This feature will come to more wikis in future weeks. [https://phabricator.wikimedia.org/T267921] '''Future changes''' * The removal of the [[mw:Special:MyLanguage/Extension:DoubleWiki|DoubleWiki extension]] is being discussed. This extension currently allows Wikisource users to view articles from multiple language versions side by side when the <bdi lang="zxx" dir="ltr"><code><=></code></bdi> symbol next to a specific language edition is selected. Comments on this are welcomed at [[phab:T344544|the phabricator task]]. * A proposal has been made to merge the second hidden-categories list (which appears below the wikitext editing form) with the main list of categories (which is further down the page). [[phab:T340606|More information is available on Phabricator]]; feedback is welcome! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:00, 28 August 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25510866 --> == Wikipedia translation of the week: 2023-36 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ghana Independence Act 1957]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> The '''Ghana Independence Act 1957''' is an Act of the Parliament of the United Kingdom that granted the Gold Coast fully responsible government within the British Commonwealth of Nations under the name of Ghana <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:18, 4 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-36 == <section begin="technews-2023-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/36|Translations]] are available. '''Recent changes''' * [[m:Wikisource_EditInSequence|EditInSequence]], a feature that allows users to edit pages faster on Wikisource has been moved to a Beta Feature based on community feedback. To enable it, you can navigate to the [[Special:Preferences#mw-prefsection-betafeatures|beta features tab in Preferences]]. [https://phabricator.wikimedia.org/T308098] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Special:MyLanguage/Community Wishlist Survey 2022/Generate Audio for IPA|Generate Audio for IPA]] and [[m:Community Wishlist Survey 2022/Multimedia and Commons/Audio links that play on click|Audio links that play on click]] wishlist proposals, the [[mw:Special:MyLanguage/Help:Extension:Phonos#Inline_audio_player_mode|inline audio player mode]] of [[mw:Extension:Phonos|Phonos]] has been deployed to all projects. [https://phabricator.wikimedia.org/T336763] * There is a new option for Administrators when they are changing the usergroups for a user, to add the user’s user page to their watchlist. This works both via [[{{#special:UserRights}}]] and via the API. [https://phabricator.wikimedia.org/T272294] * One new wiki has been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q34318|Talysh]] ([[w:tly:|<code>w:tly:</code>]]) [https://phabricator.wikimedia.org/T345166] '''Problems''' * The [[mw:Special:MyLanguage/Extension:LoginNotify|LoginNotify extension]] was not sending notifications since January. It has now been fixed, so going forward, you may see notifications for failed login attempts, and successful login attempts from a new device. [https://phabricator.wikimedia.org/T344785] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-05|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-06|en}}. It will be on all wikis from {{#time:j xg|2023-09-07|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-mhrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-miwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-minwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrjwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mtwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mwlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-myvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mznwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nahwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-napwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ndswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nds_nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-novwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nqowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nrmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nsowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ocwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-olowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-omwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-orwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-oswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pagwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-papwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pcdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pdcwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pflwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pihwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pmswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pnbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pntwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pswiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308137][https://phabricator.wikimedia.org/T308138] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:34, 4 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25566983 --> == Wikipedia translation of the week: 2023-37 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Betrayal trauma]]'''<br /> <small>''([[:sv:Svektrauma]]) ([[:ar:صدمة الخيانة]]) ([[:ko:배신 트라우마]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Betrayal trauma''' is defined as a trauma perpetrated by someone with whom the victim is close to and reliant upon for support and survival. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:49, 11 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-37 == <section begin="technews-2023-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/37|Translations]] are available. '''Recent changes''' * [[mw:Special:MyLanguage/ORES|ORES]], the revision evaluation service, is now using a new open-source infrastructure on all wikis except for English Wikipedia and Wikidata. These two will follow this week. If you notice any unusual results from the Recent Changes filters that are related to ORES (for example, "{{int:ores-rcfilters-damaging-title}}" and "{{int:ores-rcfilters-goodfaith-title}}"), please [[mw:Talk:Machine Learning|report them]]. [https://phabricator.wikimedia.org/T342115] * When you are logged in on one Wikimedia wiki and visit a different Wikimedia wiki, the system tries to log you in there automatically. This has been unreliable for a long time. You can now visit the login page to make the system try extra hard. If you feel that made logging in better or worse than it used to be, your feedback is appreciated. [https://phabricator.wikimedia.org/T326281] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-13|en}}. It will be on all wikis from {{#time:j xg|2023-09-14|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Special:MyLanguage/Technical decision making|Technical Decision-Making Forum Retrospective]] team invites anyone involved in the technical field of Wikimedia projects to signup to and join [[mw:Technical decision making/Listening Sessions|one of their listening sessions]] on 13 September. Another date will be scheduled later. The goal is to improve the technical decision-making processes. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Special:MyLanguage/Community Wishlist Survey 2022/Better diff handling of paragraph splits|Better diff handling of paragraph splits]] wishlist proposal, the inline switch widget in diff pages is being rolled out this week to all wikis. The inline switch will allow viewers to toggle between a unified inline or two-column diff wikitext format. [https://phabricator.wikimedia.org/T336716] '''Future changes''' * All wikis will be read-only for a few minutes on 20 September. [[m:Special:MyLanguage/Tech/Server switch|This is planned at 14:00 UTC.]] More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T345263] * The Enterprise API is launching a new feature called "[http://breakingnews-beta.enterprise.wikimedia.com/ breaking news]". Currently in BETA, this attempts to identify likely "newsworthy" topics as they are currently being written about in any Wikipedia. Your help is requested to improve the accuracy of its detection model, especially on smaller language editions, by recommending templates or identifiable editing patterns. See more information at [[mw:Special:MyLanguage/Wikimedia Enterprise/Breaking news|the documentation page]] on MediaWiki or [[m:Special:MyLanguage/Wikimedia Enterprise/FAQ#What is Breaking News|the FAQ]] on Meta. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:08, 11 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25589064 --> == Wikipedia translation of the week: 2023-38 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:es:Genocidio del Putumayo]]'''<br /> <small>''([[:en:Putumayo genocide]]) ([[:ca:Genocidi del Putumayo]])''</small></div> Please be bold and help translate this article! ---- [[File:The Putumayo - the devil's paradise, travels in the Peruvian Amazon Region and an account of the atrocities committed upon the Indians therein (1913) (14782203995).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Putumayo genocide''' is the term which is used in reference to the enslavement, massacres and ethnocide of the indigenous population of the Amazon at the hands of the Peruvian Amazon Company, specifically in the area between the Putumayo River and the Caquetá River during the Amazon rubber boom period from 1879 to 1912. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 03:38, 18 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25599361 --> == Tech News: 2023-38 == <section begin="technews-2023-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/38|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki now has a [[mw:Stable interface policy/frontend|stable interface policy for frontend code]] that more clearly defines how we deprecate MediaWiki code and wiki-based code (e.g. gadgets and user scripts). Thank you to everyone who contributed to the content and discussions. [https://phabricator.wikimedia.org/T346467][https://phabricator.wikimedia.org/T344079] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.27|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-20|en}}. It will be on all wikis from {{#time:j xg|2023-09-21|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * All wikis will be read-only for a few minutes on September 20. [[m:Special:MyLanguage/Tech/Server switch|This is planned at 14:00 UTC.]] [https://phabricator.wikimedia.org/T345263] * All wikis will have a link in the sidebar that provides a short URL of that page, using the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]]. [https://phabricator.wikimedia.org/T267921] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The team investigating the Graph Extension posted [[mw:Extension:Graph/Plans#Proposal|a proposal for reenabling it]] and they need your input. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:20, 18 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25623533 --> == Tech News: 2023-39 == <section begin="technews-2023-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/39|Translations]] are available. '''Recent changes''' * The Vector 2022 skin will now remember the pinned/unpinned status for the Table of Contents for all logged-out users. [https://phabricator.wikimedia.org/T316060] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.28|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-26|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-27|en}}. It will be on all wikis from {{#time:j xg|2023-09-28|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The ResourceLoader <bdi lang="zxx" dir="ltr"><code><nowiki>mediawiki.ui</nowiki></code></bdi> modules are now deprecated as part of the move to Vue.js and Codex. There is a [[mw:Codex/Migrating_from_MediaWiki_UI|guide for migrating from MediaWiki UI to Codex]] for any tools that use it. More [[phab:T346468|details are available in the task]] and your questions are welcome there. * Gadget definitions will have a [[mw:Special:MyLanguage/Extension:Gadgets#Options|new "namespaces" option]]. The option takes a list of namespace IDs. Gadgets that use this option will only load on pages in the given namespaces. '''Future changes''' * New variables will be added to [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]]: <code><bdi lang="zxx" dir="ltr">global_account_groups</bdi></code> and <code><bdi lang="zxx" dir="ltr">global_account_editcount</bdi></code>. They are available only when an account is being created. You can use them to prevent blocking automatic creation of accounts when users with many edits elsewhere visit your wiki for the first time. [https://phabricator.wikimedia.org/T345632][https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:AbuseFilter/Rules_format] '''Meetings''' * You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on [https://zonestamp.toolforge.org/1698426015 27 October at 17:00 (UTC)]. See [[mw:Special:MyLanguage/Wikimedia_Apps/Office_Hours#October_2023|details and how to join]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:51, 26 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25655264 --> == Tech News: 2023-40 == <section begin="technews-2023-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/40|Translations]] are available. '''Recent changes''' * There is a new [[Special:Preferences#mw-prefsection-rendering-advancedrendering|user preference]] for "{{int:tog-forcesafemode}}". This setting will make pages load without including any on-wiki JavaScript or on-wiki stylesheet pages. It can be useful for debugging broken JavaScript gadgets. [https://phabricator.wikimedia.org/T342347] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadget definitions now have a [[mw:Special:MyLanguage/Extension:Gadgets#Options|new "<var>contentModels</var>" option]]. The option takes a list of page content models, like <code><bdi lang="zxx" dir="ltr">wikitext</bdi></code> or <code><bdi lang="zxx" dir="ltr">css</bdi></code>. Gadgets that use this option will only load on pages with the given content models. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.29|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-03|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-04|en}}. It will be on all wikis from {{#time:j xg|2023-10-05|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Vector 2022 skin will no longer use the custom styles and scripts of Vector legacy (2010). The change will be made later this year or in early 2024. See [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Loading Vector 2010 scripts|how to adjust the CSS and JS pages on your wiki]]. [https://phabricator.wikimedia.org/T331679] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:27, 3 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25686930 --> == Tech News: 2023-41 == <section begin="technews-2023-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/41|Translations]] are available. '''Recent changes''' * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q33291|Fon]] ([[w:fon:|<code>w:fon:</code>]]) [https://phabricator.wikimedia.org/T347935] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.30|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-10|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-11|en}}. It will be on all wikis from {{#time:j xg|2023-10-12|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-swwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-wawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-warwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-wowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xalwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xhwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xmfwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-yiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-yowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zeawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zh_min_nanwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zuwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308139] * At some wikis, newcomers are suggested images from Commons to add to articles without any images. Starting on Tuesday, newcomers at these wikis will be able to add images to unillustrated article sections. The specific wikis are listed under "Images recommendations" [[mw:Special:MyLanguage/Growth/Deployment table|at the Growth team deployment table]]. You can [[mw:Special:MyLanguage/Help:Growth/Tools/Add an image|learn more about this feature.]] [https://phabricator.wikimedia.org/T345940] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] In the mobile web skin (Minerva) the CSS ID <bdi lang="zxx" dir="ltr"><code><nowiki>#page-actions</nowiki></code></bdi> will be replaced with <bdi lang="zxx" dir="ltr"><code><nowiki>#p-views</nowiki></code></bdi>. This change is to make it consistent with other skins and to improve support for gadgets and extensions in the mobile skin. A few gadgets may need to be updated; there are [https://phabricator.wikimedia.org/T348267 details and search-links in the task]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:39, 9 October 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25712895 --> == Wikipedia translation of the week: 2023-42 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Athyma nefte]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:VB 019 Color Sergeant UP.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''''Athyma nefte''''', the colour sergeant, is a species of brush-footed butterfly found in tropical South and Southeast Asia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:58, 16 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25693965 --> == Tech News: 2023-42 == <section begin="technews-2023-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/42|Translations]] are available. '''Recent changes''' * The [[m:Special:MyLanguage/Help:Unified login|Unified login]] system's edge login should now be fixed for some browsers (Chrome, Edge, Opera). This means that if you visit a new sister project wiki, you should be logged in automatically without the need to click "Log in" or reload the page. Feedback on whether it's working for you is welcome. [https://phabricator.wikimedia.org/T347889] * [[mw:Special:MyLanguage/Manual:Interface/Edit_notice|Edit notices]] are now available within the MobileFrontend/Minerva skin. This feature was inspired by [[w:en:Wikipedia:EditNoticesOnMobile|the gadget on English Wikipedia]]. See more details in [[phab:T316178|T316178]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-17|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-18|en}}. It will be on all wikis from {{#time:j xg|2023-10-19|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * In 3 weeks, in the Vector 2022 skin, code related to <bdi lang="zxx" dir="ltr"><code><nowiki>addPortletLink</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>#p-namespaces</nowiki></code></bdi> that was deprecated one year ago will be removed. If you notice tools that should appear next to the "Discussion" tab are then missing, please tell the gadget's maintainers to see [[phab:T347907|instructions in the Phabricator task]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:47, 16 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25745824 --> == Wikipedia translation of the week: 2023-43 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Typhoon Rusa]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Rusa 2002-08-27 0350Z.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Typhoon Rusa''' was the most powerful typhoon to strike South Korea in 43 years. It was the 21st JTWC tropical depression, the 15th named storm, and the 10th typhoon of the 2002 Pacific typhoon season. It developed on August 22 from the monsoon trough in the northwestern Pacific Ocean, well to the southeast of Japan. For several days, Rusa moved to the northwest, eventually intensifying into a powerful typhoon. On August 26, the storm moved across the Amami Islands of Japan, where Rusa left 20,000 people without power and caused two fatalities. Across Japan, the typhoon dropped torrential rainfall peaking at 902 mm (35.5 in) in Tokushima Prefecture. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:50, 23 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25693965 --> == Tech News: 2023-43 == <section begin="technews-2023-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/43|Translations]] are available. '''Recent changes''' * There is a new [[mw:Special:MyLanguage/Wikimedia Language engineering/Newsletter/2023/October|Language and internationalization newsletter]], written quarterly. It contains updates on new feature development, improvements in various language-related technical projects, and related support work. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Source map support has been enabled on all wikis. When you open the debugger in your browser's developer tools, you should be able to see the unminified JavaScript source code. [https://phabricator.wikimedia.org/T47514] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-24|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-25|en}}. It will be on all wikis from {{#time:j xg|2023-10-26|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:17, 23 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25782286 --> == Wikipedia translation of the week: 2023-44 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hein Eersel]]'''<br /> <small>''([[:nl:Hein Eersel]]) ([[:it:Hein Eersel]])''</small> </div> Please be bold and help translate this article! ---- [[File:HeinEersel.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Christiaan Hendrik "Hein" Eersel''' was a Surinamese linguist and cultural researcher. He served as Minister of Education and Population Development in the cabinet of acting Prime Minister Arthur Johan May. He was also the first chancellor of the University of Suriname. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:09, 30 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-44 == <section begin="technews-2023-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/44|Translations]] are available. '''Recent changes''' * The Structured Content team, as part of its project of [[:commons:Commons:WMF support for Commons/Upload Wizard Improvements|improving UploadWizard on Commons]], made some UX improvements to the upload step of choosing own vs not own work ([[phab:T347590|T347590]]), as well as to the licensing step for own work ([[phab:T347756|T347756]]). * The Design Systems team has released version 1.0.0 of [[wmdoc:codex/latest/|Codex]], the new design system for Wikimedia. See the [[mw:Special:MyLanguage/Design_Systems_Team/Announcing_Codex_1.0|full announcement about the release of Codex 1.0.0]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-31|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-01|en}}. It will be on all wikis from {{#time:j xg|2023-11-02|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). * Listings on category pages are sorted on each wiki for that language using a [[:w:en:International Components for Unicode|library]]. For a brief period on 2 November, changes to categories will not be sorted correctly for many languages. This is because the developers are upgrading to a new version of the library. They will then use a script to fix the existing categories. This will take a few hours or a few days depending on how big the wiki is. You can [[mw:Special:MyLanguage/Wikimedia Technical Operations/ICU announcement|read more]]. [https://phabricator.wikimedia.org/T345561][https://phabricator.wikimedia.org/T267145] * Starting November 1, the impact module (Special:Impact) will be upgraded by the Growth team. The new impact module shows newcomers more data regarding their impact on the wiki. It was tested by a few wikis during the last few months. [https://phabricator.wikimedia.org/T336203] '''Future changes''' * There is [[mw:Special:MyLanguage/Extension:Graph/Plans#Roadmap|a proposed plan]] for re-enabling the Graph Extension. You can help by reviewing this proposal and [[mw:Extension_talk:Graph/Plans#c-PPelberg_(WMF)-20231020221600-Update:_20_October|sharing what you think about it]]. * The WMF is working on making it possible for administrators to [[mw:Special:MyLanguage/Community_configuration_2.0|edit MediaWiki configuration directly]]. This is similar to previous work on Special:EditGrowthConfig. [[phab:T349757|A technical RfC is running until November 08, where you can provide feedback.]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:21, 30 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25801989 --> == Tech News: 2023-45 == <section begin="technews-2023-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/45|Translations]] are available. '''Recent changes''' * In the Vector 2022 skin, the default font-size of a number of navigational elements (tagline, tools menu, navigational links, and more) has been increased slightly to match the font size used in page content. [https://phabricator.wikimedia.org/T346062] '''Problems''' * Last week, there was a problem displaying some recent edits on [https://noc.wikimedia.org/conf/highlight.php?file=dblists/s5.dblist a few wikis], for 1-6 hours. The edits were saved but not immediately shown. This was due to a database problem. [https://phabricator.wikimedia.org/T350443] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-08|en}}. It will be on all wikis from {{#time:j xg|2023-11-09|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). * The Growth team will reassign newcomers from former mentors to [[mw:Special:MyLanguage/Growth/Structured mentor list|the currently active mentors]]. They have also changed the notification language to be more user-friendly. [https://phabricator.wikimedia.org/T330071][https://phabricator.wikimedia.org/T327493] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:06, 6 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25838105 --> == Wikipedia translation of the week: 2023-45 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Reclaim the Night]]'''<br /> <small>''([[:de:Reclaim the Night]])''</small> </div> Please be bold and help translate this article! ---- [[File:Reclaim the Night 2014.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Reclaim the Night''' is a movement started in Leeds in 1977 as part of the Women's Liberation Movement. Marches demanding that women be able to move throughout public spaces at night took place across England until the 1990s. Later, the organisation was revived and sponsors annual and national marches against rape and violence against women. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:40, 8 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Wikipedia translation of the week: 2023-46 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ishe Komborera Africa]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Ishe Komborera Africa.mp3|center|300px|]] <div style="text-align:left; padding: .4em;"> "'''Ishe Komborera Africa'''" (Shona for: God Bless Africa), also called "Ishe Komborera Zimbabwe" (Shona for: God Bless Zimbabwe), was the Zimbabwean national anthem from 1980 to 1994. It was the country's first national anthem after gaining independence in 1980. It is a translation of 19th-century South African schoolteacher Enoch Sontonga's popular African hymn "Nkosi Sikelel' iAfrika" into Zimbabwe's native Shona and Ndebele languages. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:38, 13 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-46 == <section begin="technews-2023-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/46|Translations]] are available. '''Recent changes''' * Four new wikis have been created: ** a Wikipedia in [[d:Q7598268|Moroccan Amazigh]] ([[w:zgh:|<code>w:zgh:</code>]]) [https://phabricator.wikimedia.org/T350216] ** a Wikipedia in [[d:Q35159|Dagaare]] ([[w:dga:|<code>w:dga:</code>]]) [https://phabricator.wikimedia.org/T350218] ** a Wikipedia in [[d:Q33017|Toba Batak]] ([[w:bbc:|<code>w:bbc:</code>]]) [https://phabricator.wikimedia.org/T350320] ** a Wikiquote in [[d:Q33151|Banjar]] ([[q:bjn:|<code>q:bjn:</code>]]) [https://phabricator.wikimedia.org/T350217] '''Problems''' * Last week, users who previously visited Meta-Wiki or Wikimedia Commons and then became logged out on those wikis could not log in again. The problem is now resolved. [https://phabricator.wikimedia.org/T350695] * Last week, some pop-up dialogs and menus were shown with the wrong font size. The problem is now resolved. [https://phabricator.wikimedia.org/T350544] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-15|en}}. It will be on all wikis from {{#time:j xg|2023-11-16|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). '''Future changes''' * Reference Previews are coming to many wikis as a default feature. They are popups for references, similar to the [[mw:Special:MyLanguage/Page Previews|PagePreviews feature]]. [[m:WMDE Technical Wishes/ReferencePreviews#Opt-out feature|You can opt out]] of seeing them. If you are [[Special:Preferences#mw-prefsection-gadgets|using the gadgets]] Reference Tooltips or Navigation Popups, you won’t see Reference Previews. [[phab:T282999|Deployment]] is planned for November 22, 2023. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Canary (also known as heartbeat) events will be produced into [https://stream.wikimedia.org/?doc#/streams Wikimedia event streams] from December 11. Streams users are advised to filter out these events, by discarding all events where <bdi lang="zxx" dir="ltr"><code><nowiki>meta.domain == "canary"</nowiki></code></bdi>. Updates to [[mw:Special:MyLanguage/Manual:Pywikibot|Pywikibot]] or [https://github.com/ChlodAlejandro/wikimedia-streams wikimedia-streams] will discard these events by default. [https://phabricator.wikimedia.org/T266798] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:52, 13 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25859263 --> == Wikipedia translation of the week: 2023-47 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Bhagavata Mela]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Bhagavata Mela''' is a classical Indian dance that is performed in Tamil Nadu, particularly the Thanjavur area. It is choreographed as an annual Vaishnavism tradition in Melattur and nearby regions, and celebrated as a dance-drama performance art. The dance art has roots in a historic migration of practitioners of Kuchipudi, another Indian classical dance art, from Andhra Pradesh to the kingdom of Tanjavur. The term Bhagavata, state Brandon and Banham, refers to the Hindu text Bhagavata Purana. Mela is a Sanskrit word that means "gathering, meeting of a group" and connotes a folk festival. The traditional Bhagavata Mela performance acts out the legends of Hinduism, set to the Carnatic style music. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:38, 04:07, 20 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-47 == <section begin="technews-2023-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/47|Translations]] are available. '''Changes later this week''' * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-quwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rmywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-roa_rupwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-roa_tarawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ruewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rwwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sahwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-satwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-shwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-siwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-skwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-slwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-smwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sqwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-srwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-srnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-stwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-stqwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-suwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-szlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tcywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tetwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-thwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-towiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tpiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ttwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-twwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tyvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-udmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ugwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-uzwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vecwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vepwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vlswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vowiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308141][https://phabricator.wikimedia.org/T308142][https://phabricator.wikimedia.org/T308143] * The Vector 2022 skin will have some minor visual changes to drop-down menus, column widths, and more. These changes were added to four Wikipedias last week. If no issues are found, these changes will proceed to all wikis this week. These changes will make it possible to add new menus for readability and dark mode. [[mw:Special:MyLanguage/Reading/Web/Desktop_Improvements/Updates#November_2023:_Visual_changes,_more_deployments,_and_shifting_focus|Learn more]]. [https://phabricator.wikimedia.org/T347711] '''Future changes''' * There is [[mw:Extension talk:Graph/Plans#Update: 15 November|an update on re-enabling the Graph Extension]]. To speed up the process, Vega 2 will not be supported and only [https://phabricator.wikimedia.org/T335325 some protocols] will be available at launch. You can help by sharing what you think about the plan. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:55, 21 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25884616 --> == Wikipedia translation of the week: 2023-48 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fr:Zanskari]]'''<br /> <small>''([[:en:Zaniskari]])''</small> </div> Please be bold and help translate this article! ---- [[File:Zaniskari Horse in Ladakh, India.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Zaniskari''' or '''Zanskari''' is a breed of small mountain horse or pony from Ladakh, in northern India. It is named for the Zanskar valley or region in Kargil district. It is similar to the Spiti breed of Himachal Pradesh, but is better adapted to work at high altitude. Like the Spiti, it shows similarities to the Tibetan breeds of neighbouring Tibet. It is of medium size, and is often grey in colour. The breed is considered endangered, as there are only a few hundred alive today, and a conservation programme has been started at Padum, Zanskar, in the Kargil district of Ladakh. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:44, 27 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-48 == <section begin="technews-2023-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/48|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-29|en}}. It will be on all wikis from {{#time:j xg|2023-11-30|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). There is no new MediaWiki version next week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki's JavaScript system will now allow <bdi lang="zxx" dir="ltr"><code>async</code>/<code>await</code></bdi> syntax in gadgets and user scripts. Gadget authors should remember that users' browsers may not support it, so it should be used appropriately. [https://phabricator.wikimedia.org/T343499] * The deployment of "[[mw:Special:MyLanguage/Help:Growth/Tools/Add_a_link|Add a link]]" announced [[m:Special:MyLanguage/Tech/News/2023/47|last week]] was postponed. It will resume this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:09, 27 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25906379 --> == Wikipedia translation of the week: 2023-49 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sheikh Hussein]]'''<br /> <small>''([[:fr:Sheikh Hussein]]) ([[:it:Scec Hussèn]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sheikh Hussein.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Sheikh Hussein''' is a town in south-eastern Ethiopia. The site has been recorded in the tentative list for UNESCO World Heritage List since 2011 as a religious, cultural and historical site. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:34, 4 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25921616 --> == Tech News: 2023-49 == <section begin="technews-2023-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/49|Translations]] are available. '''Recent changes''' * The spacing between paragraphs on Vector 2022 has been changed from 7px to 14px to match the size of the text. This will make it easier to distinguish paragraphs from sentences. [https://phabricator.wikimedia.org/T351754] * The "{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}" feature in VisualEditor is working again. You no longer need to switch to source editing to edit <bdi lang="zxx" dir="ltr"><code><nowiki>{{DEFAULTSORT:...}}</nowiki></code></bdi> keywords. [https://phabricator.wikimedia.org/T337398] '''Changes later this week''' * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * On 6 December, people who have the enabled the preference for "{{int:Discussiontools-preference-visualenhancements}}" will notice the [[mw:Special:MyLanguage/Talk pages project/Usability|talk page usability improvements]] appear on pages that include the <bdi lang="zxx" dir="ltr"><code><nowiki>__NEWSECTIONLINK__</nowiki></code></bdi> magic word. If you notice any issues, please [[phab:T352232|share them with the team on Phabricator]]. '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Toolforge [[wikitech:News/Toolforge Grid Engine deprecation|Grid Engine shutdown process]] will start on December 14. Maintainers of [[toolforge:grid-deprecation|tools that still use this old system]] should plan to migrate to Kubernetes, or tell the team your plans on Phabricator in the task about your tool, before that date. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/VIWWQKMSQO2ED3TVUR7KPPWRTOBYBVOA/] * Communities using [[mw:Special:MyLanguage/Structured_Discussions|Structured Discussions]] are being contacted regarding [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|the upcoming deprecation of Structured Discussions]]. You can read more about this project, and share your comments, [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|on the project's page]]. '''Events''' * Registration & Scholarship applications are now open for the [[mw:Special:MyLanguage/Wikimedia Hackathon 2024|Wikimedia Hackathon 2024]] that will take place from 3–5 May in Tallinn, Estonia. Scholarship applications are open until 5 January 2024. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:50, 4 December 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25914435 --> == Wikipedia translation of the week: 2023-50 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fr:Applaudissements aux fenêtres pendant la pandémie de Covid-19]]'''<br /> <small>''([[:es:Aplauso por los trabajadores de la salud]]) ([[:gl:Aplauso ao persoal sanitario]])''</small> </div> Please be bold and help translate this article! ---- [[File:Koronabirus konfinamendua Lasarten 2020-03-29.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> During the COVID-19 pandemic, applauding daily at a scheduled hour was a gesture of acclamation, recognition and gratitude towards health professionals in tribute to their work at the time. This habit emerged in January 2020 in Wuhan, where the pandemic originated, and then spread to several cities around the world during the quarantines and sanitary cordons ordered as preventive measures, Italy being the first one. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:26, 11 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25925561 --> == Tech News: 2023-50 == <section begin="technews-2023-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/50|Translations]] are available. '''Recent changes''' * On Wikimedia Commons, there are some minor user-interface improvements for the "choosing own vs not own work" step in the UploadWizard. This is part of the Structured Content team's project of [[:commons:Commons:WMF support for Commons/Upload Wizard Improvements|improving UploadWizard on Commons]]. [https://phabricator.wikimedia.org/T352707][https://phabricator.wikimedia.org/T352709] '''Problems''' * There was a problem showing the [[mw:Special:MyLanguage/Growth/Personalized first day/Newcomer homepage|Newcomer homepage]] feature with the "impact module" and their page-view graphs, for a few days in early December. This has now been fixed. [https://phabricator.wikimedia.org/T352352][https://phabricator.wikimedia.org/T352349] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-12-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-12-13|en}}. It will be on all wikis from {{#time:j xg|2023-12-14|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * [[File:Octicons-tools.svg|15px|link=]] The [https://wikimediafoundation.limesurvey.net/796964 2023 Developer Satisfaction Survey] is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 5 January 2024, and has an associated [[foundation:Legal:December_2023_Developer_Satisfaction_Survey|privacy statement]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:13, 12 December 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25945501 --> == Wikipedia translation of the week: 2023-51 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Jamaica Bay Wildlife Refuge]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Aerial view of Subway Island, July 2019.JPG|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Jamaica Bay Wildlife Refuge''' is a wildlife refuge in New York City managed by the National Park Service as part of Gateway National Recreation Area. It is composed of the open water and intertidal salt marshes of Jamaica Bay. It lies entirely within the boundaries of New York City, divided between the boroughs of Brooklyn to the west and Queens to the east. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:05, 18 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25951007 --> == Tech News: 2023-51 == <section begin="technews-2023-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/51|Translations]] are available. '''Tech News''' * The next issue of Tech News will be sent out on 8 January 2024 because of [[w:en:Christmas and holiday season|the holidays]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-12-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-12-20|en}}. It will be on all wikis from {{#time:j xg|2023-12-21|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). There is no new MediaWiki version next week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting December 18, it won't be possible to activate Structured Discussions on a user's own talk page using the Beta feature. The Beta feature option remains available for users who want to deactivate Structured Discussions. This is part of [[mw:Structured Discussions/Deprecation|Structured Discussions' deprecation work]]. [https://phabricator.wikimedia.org/T248309] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] There will be full support for redirects in the Module namespace. The "Move Page" feature will leave an appropriate redirect behind, and such redirects will be appropriately recognized by the software (e.g. hidden from [[{{#special:UnconnectedPages}}]]). There will also be support for [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#Renaming or moving modules|manual redirects]]. [https://phabricator.wikimedia.org/T120794] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The MediaWiki JavaScript documentation is moving to a new format. During the move, you can read the old docs using [https://doc.wikimedia.org/mediawiki-core/REL1_41/js/ version 1.41]. Feedback about [https://doc.wikimedia.org/mediawiki-core/master/js/ the new site] is welcome on the [[mw:Talk:JSDoc_WMF_theme|project talk page]]. * The Wishathon is a new initiative that encourages collaboration across the Wikimedia community to develop solutions for wishes collected through the [[m:Special:MyLanguage/Community Wishlist Survey|Community Wishlist Survey]]. The first community Wishathon will take place from 15–17 March. If you are interested in a project proposal as a user, developer, designer, or product lead, you can [[m:Special:MyLanguage/Event:WishathonMarch2024|register for the event and read more]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:18, 18 December 2023 (UTC) <!-- Message sent by User:Johan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25959059 --> == Wikipedia translation of the week: 2023-52 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Plant blindness]]'''<br /> <small>''([[:fr:Cécité botanique]]) ([[:de:Pflanzenblindheit]])''</small> </div> Please be bold and help translate this article! ---- [[File:Plant blindness 0323.png|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Plant blindness''' is an informally-proposed form of cognitive bias, which in its broadest meaning, is a human tendency to ignore plant species. This includes such phenomena as not noticing plants in the surrounding environment, not recognizing the importance of plant life to the whole biosphere and to human affairs, a philosophical view of plants as an inferior form of life to animals and/or the inability to appreciate the unique features or aesthetics of plants. Related terms include plant‐neglect, zoo-centrism, and zoo‐chauvinism. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:58, 25 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25971304 --> == Wikipedia translation of the week: 2024-02 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pax airship disaster]]'''<br /> <small>''([[:pt:Catástrofe do dirigível Pax]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sim new-mcclures-magazine 1902-09 19 5 (page 75 crop).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''''Pax''''' '''airship disaster''' was the explosion of the ''Pax'' airship on May 12, 1902, in Paris, which killed the Brazilian inventor Augusto Severo and the French mechanic Georges Saché. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 12:14, 8 January 2024 (UTC)'' </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26033876 --> == Tech News: 2024-02 == <section begin="technews-2024-W02"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/02|Translations]] are available. '''Recent changes''' * [https://mediawiki2latex.wmflabs.org/ mediawiki2latex] is a tool that converts wiki content into the formats of LaTeX, PDF, ODT, and EPUB. The code now runs many times faster due to recent improvements. There is also an optional Docker container you can [[b:de:Benutzer:Dirk_Hünniger/wb2pdf/install#Using_Docker|install]] on your local machine. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The way that Random pages are selected has been updated. This will slowly reduce the problem of some pages having a lower chance of appearing. [https://phabricator.wikimedia.org/T309477] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.13|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-10|en}}. It will be on all wikis from {{#time:j xg|2024-01-11|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/02|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W02"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:20, 9 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26026251 --> == Wikipedia translation of the week: 2024-03 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Conversion to Islam]]'''<br /> <small>''([[:fr:Conversion à l'islam]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sahadah-Topkapi-Palace.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Conversion to Islam''' is accepting Islam as a religion or faith and rejecting any other religion or irreligion. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:11, 15 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26044632 --> == Tech News: 2024-03 == <section begin="technews-2024-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/03|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Pages that use the JSON [[mw:Special:MyLanguage/Manual:ContentHandler|contentmodel]] will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. [https://phabricator.wikimedia.org/T326065] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] and personal user scripts may now use JavaScript syntax introduced in ES6 (also known as "ES2015") and ES7 ("ES2016"). MediaWiki validates the source code to protect other site functionality from syntax errors, and to ensure scripts are valid in all [[mw:Special:MyLanguage/Compatibility#Browsers|supported browsers]]. Previously, Gadgets could use the <bdi lang="zxx" dir="ltr"><code><nowiki>requiresES6</nowiki></code></bdi> option. This option is no longer needed and will be removed in the future. [https://phabricator.wikimedia.org/T75714] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Manual:Bot passwords|Bot passwords]] and [[mw:Special:MyLanguage/OAuth/Owner-only consumers|owner-only OAuth consumers]] can now be restricted to allow editing only specific pages. [https://phabricator.wikimedia.org/T349957] * You can now [[mw:Special:MyLanguage/Extension:Thanks|thank]] edits made by bots. [https://phabricator.wikimedia.org/T341388] * An update on the status of the Community Wishlist Survey for 2024 [[m:Special:MyLanguage/Community Wishlist Survey/Future Of The Wishlist/January 4, 2024 Update|has been published]]. Please read and give your feedback. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.14|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-17|en}}. It will be on all wikis from {{#time:j xg|2024-01-18|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting on January 17, it will not be possible to login to Wikimedia wikis from some specific old versions of the Chrome browser (versions 51–66, released between 2016 and 2018). Additionally, users of iOS 12, or Safari on Mac OS 10.14, may need to login to each wiki separately. [https://phabricator.wikimedia.org/T344791] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> module was deprecated and replaced with the <bdi lang="zxx" dir="ltr"><code>mediawiki.cookie</code></bdi> module last year. A script has now been run to replace any remaining uses, and this week the temporary alias will be removed. [https://phabricator.wikimedia.org/T354966] '''Future changes''' * Wikimedia Deutschland is working to [[m:WMDE Technical Wishes/Reusing references|make reusing references easier]]. They are looking for people who are interested in participating in [https://wikimedia.sslsurvey.de/User-research-into-Reusing-References-Sign-up-Form-2024/en/ individual video calls for user research in January and February]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:13, 16 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26074460 --> == Wikipedia translation of the week: 2024-04 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kinder der Landstrasse]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Kinderdlandstrasse plakat.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Kinder der Landstrasse''' (literally: Children of the Country Road) was a project implemented by the Swiss foundation Pro Juventute from 1926 to 1973. The project aimed to assimilate the itinerant Yenish people in Switzerland by forcibly removing their children from their parents and placing them in orphanages or foster homes. Approximately 590 children were affected by this program. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:02, 22 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26044632 --> == Tech News: 2024-04 == <section begin="technews-2024-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/04|Translations]] are available. '''Problems''' * A bug in UploadWizard prevented linking to the userpage of the uploader when uploading. It has now been fixed. [https://phabricator.wikimedia.org/T354529] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.15|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-24|en}}. It will be on all wikis from {{#time:j xg|2024-01-25|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:04, 23 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26096197 --> == Wikipedia translation of the week: 2024-05 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Qurm Nature Reserve]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Al-Qurm Wetlands.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Qurm Nature Reserve''' is a national nature reserve in Muscat Governorate, Oman. Located on the Gulf of Oman coast, the reserve protects a mangrove forest and the surrounding wetland in a small estuary within the urban area of Qurm. Established in 1975, the reserve has been designated as an Important Bird Area since 1994, and as a protected Ramsar site since 2013. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:03, 29 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26149847 --> == Tech News: 2024-05 == <section begin="technews-2024-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/05|Translations]] are available. '''Recent changes''' * Starting Monday January 29, all talk pages messages' timestamps will become a link. This link is a permanent link to the comment. It allows users to find the comment they are looking for, even if this comment was moved elsewhere. This will affect all wikis except for the English Wikipedia. You can read more about this change [https://diff.wikimedia.org/2024/01/29/talk-page-permalinks-dont-lose-your-threads/ on Diff] or [[mw:Special:MyLanguage/Help:DiscussionTools#Talk_pages_permalinking|on Mediawiki.org]].<!-- The Diff post will be published on Monday morning UTC--> [https://phabricator.wikimedia.org/T302011] * There are some improvements to the CAPTCHA to make it harder for spam bots and scripts to bypass it. If you have feedback on this change, please comment on [[phab:T141490|the task]]. Staff are monitoring metrics related to the CAPTCHA, as well as secondary metrics such as account creations and edit counts. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.16|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-31|en}}. It will be on all wikis from {{#time:j xg|2024-02-01|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] On February 1, a link will be added to the "Tools" menu to download a [[w:en:QR code|QR code]] that links to the page you are viewing. There will also be a new [[{{#special:QrCode}}]] page to create QR codes for any Wikimedia URL. This addresses the [[m:Community Wishlist Survey 2023/Mobile and apps/Add ability to share QR code for a page in any Wikimedia project|#19 most-voted wish]] from the [[m:Community Wishlist Survey 2023/Results|2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T329973] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] which only work in some skins have sometimes used the <bdi lang="zxx" dir="ltr"><code>targets</code></bdi> option to limit where you can use them. This will stop working this week. You should use the <bdi lang="zxx" dir="ltr"><code>skins</code></bdi> option instead. [https://phabricator.wikimedia.org/T328497] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:31, 29 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26137870 --> == Wikipedia translation of the week: 2024-06 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Timurid architecture]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Gur-e-Amir Mausolueum - Samarkand - Uzbekistan (7488414078).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Timurid architecture''' was an important stage in the architectural history of Iran and Central Asia during the late 14th and 15th centuries. The Timurid Empire (1370–1507), founded by Timur (d. 1405) and conquering most of this region, oversaw a cultural renaissance. In architecture, the Timurid dynasty patronized the construction of palaces, mausoleums, and religious monuments across the region. Their architecture is distinguished by its grand scale, luxurious decoration in tilework, and sophisticated geometric vaulting. This architectural style, along with other aspects of Timurid art, spread across the empire and subsequently influenced the architecture of other empires from the Middle East to the Indian subcontinent. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 5 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26169542 --> == Tech News: 2024-06 == <section begin="technews-2024-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/06|Translations]] are available. '''Recent changes''' *The mobile site history pages now use the same HTML as the desktop history pages. If you hear of any problems relating to mobile history usage please point them to [[phab:T353388|the phabricator task]]. *On most wikis, admins can now block users from making specific actions. These actions are: uploading files, creating new pages, moving (renaming) pages, and sending thanks. The goal of this feature is to allow admins to apply blocks that are adequate to the blocked users' activity. [[m:Special:MyLanguage/Community health initiative/Partial blocks#action-blocks|Learn more about "action blocks"]]. [https://phabricator.wikimedia.org/T242541][https://phabricator.wikimedia.org/T280531] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.17|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-06|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-07|en}}. It will be on all wikis from {{#time:j xg|2024-02-08|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Talk pages permalinks that included diacritics and non-Latin script were malfunctioning. This issue is fixed. [https://phabricator.wikimedia.org/T356199] '''Future changes''' * [[m:WMDE Technical Wishes/ReferencePreviews#24WPs|24 Wikipedias]] with [[mw:Special:MyLanguage/Reference_Tooltips|Reference Tooltips]] as a default gadget are encouraged to remove that default flag. This would make [[mw:Special:MyLanguage/Help:Reference_Previews|Reference Previews]] the new default for reference popups, leading to a more consistent experience across wikis. For [[m:WMDE Technical Wishes/ReferencePreviews#46WPs|46 Wikipedias]] with less than 4 interface admins, the change is already scheduled for mid-February, [[m:Talk:WMDE Technical Wishes/ReferencePreviews#Reference Previews to become the default for previewing references on more wikis.|unless there are concerns]]. The older Reference Tooltips gadget will still remain usable and will override this feature, if it is available on your wiki and you have enabled it in your settings. [https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews#Reference_Previews_to_become_the_default_for_previewing_references_on_more_wikis][https://phabricator.wikimedia.org/T355312] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:22, 5 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26180971 --> == Wikipedia translation of the week: 2024-07 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Adoration of the Magi (Fra Angelico and Filippo Lippi)]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Fra Angelico, Fra Filippo Lippi, The Adoration of the Magi.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''''Adoration of the Magi''''' is a tondo, or circular painting, of the Adoration of the Magi assumed to be that recorded in 1492 in the Palazzo Medici Riccardi in Florence as by Fra Angelico. It dates from the mid-15th century and is now in the National Gallery of Art in Washington D.C. Most art historians think that Filippo Lippi painted more of the original work, and that it was added to some years after by other artists, as well as including work by assistants in the workshops of both the original masters. It has been known as the Washington Tondo and Cook Tondo after Herbert Cook, and this latter name in particular continues to be used over 50 years after the painting left the Cook collection. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 07:00, 12 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26187446 --> == Tech News: 2024-07 == <section begin="technews-2024-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/07|Translations]] are available. '''Recent changes''' * The [[d:Wikidata:SPARQL query service/WDQS graph split|WDQS Graph Split experiment]] is working and loaded onto 3 test servers. The team in charge is testing the split's impact and requires feedback from WDQS users through the UI or programmatically in different channels. [https://www.wikidata.org/wiki/Wikidata_talk:SPARQL_query_service/WDQS_graph_split][https://phabricator.wikimedia.org/T356773][https://www.wikidata.org/wiki/User:Sannita_(WMF)] Users' feedback will validate the impact of various use cases and workflows around the Wikidata Query service. [https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/October_2023_scaling_update][https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Federation] '''Problems''' *There was a bug that affected the appearance of visited links when using mobile device to access wiki sites. It made the links appear black; [[phab:T356928|this issue]] is fixed. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.18|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-13|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-14|en}}. It will be on all wikis from {{#time:j xg|2024-02-15|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] As work continues on the grid engine deprecation,[https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation] tools on the grid engine will be stopped starting on February 14th, 2024. If you have tools actively migrating you can ask for an extension so they are not stopped. [https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Communication_and_support] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 05:49, 13 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26223994 --> == Wikipedia translation of the week: 2024-08 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:nl:Graf met de handjes]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Weg langs het kerkhof tegenover 1, Roermond.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The monument '''Van Gorkum-Van Aefferden''', more well known as the "'''grave with the little hands'''" is a monumental Tombstone in the Dutch city of Roermond. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:24, 19 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26260848 --> == Tech News: 2024-08 == <section begin="technews-2024-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/08|Translations]] are available. '''Recent changes''' * If you have the "{{int:Tog-enotifwatchlistpages}}" option enabled, edits by bot accounts no longer trigger notification emails. Previously, only minor edits would not trigger the notification emails. [https://phabricator.wikimedia.org/T356984] * There are changes to how user and site scripts load for [[mw:Special:MyLanguage/Skin:Vector/2022| Vector 2022]] on specific wikis. The changes impacted the following Wikis: all projects with [[mw:Special:MyLanguage/Skin:Vector|Vector legacy]] as the default skin, Wikivoyage, and Wikibooks. Other wikis will be affected over the course of the next three months. Gadgets are not impacted. If you have been affected or want to minimize the impact on your project, see [[Phab:T357580| this ticket]]. Please coordinate and take action proactively. *Newly auto-created accounts (the accounts you get when you visit a new wiki) now have the same local notification preferences as users who freshly register on that wiki. It is effected in four notification types listed in the [[phab:T353225|task's description]]. *The maximum file size when using [[c:Special:MyLanguage/Commons:Upload_Wizard|Upload Wizard]] is now 5 GiB. [https://phabricator.wikimedia.org/T191804] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-20|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-21|en}}. It will be on all wikis from {{#time:j xg|2024-02-22|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Selected tools on the grid engine have been [[wikitech:News/Toolforge_Grid_Engine_deprecation|stopped]] as we prepare to shut down the grid on March 14th, 2024. The tool's code and data have not been deleted. If you are a maintainer and you want your tool re-enabled reach out to the [[wikitech:Portal:Toolforge/About_Toolforge#Communication_and_support|team]]. Only tools that have asked for extension are still running on the grid. * The CSS <bdi lang="zxx" dir="ltr"><code>[https://developer.mozilla.org/en-US/docs/Web/CSS/filter filter]</code></bdi> property can now be used in HTML <bdi lang="zxx" dir="ltr"><code>style</code></bdi> attributes in wikitext. [https://phabricator.wikimedia.org/T308160] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:37, 19 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26254282 --> == Wikipedia translation of the week: 2024-09 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Doorway effect]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> The '''doorway effect''' is a known psychological event where a person's short-term memory declines when passing through a doorway moving from one location to another when it would not if they had remained in the same place. People experience this effect by forgetting what they were going to do, thinking about, or planning upon entering a different room. This is thought to be due to the change in one's physical environment, which is used to distinguish boundaries between remembered events: memories of events encountered in the present environment are more accessible than those beyond it. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:30, 26 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26260848 --> == Tech News: 2024-09 == <section begin="technews-2024-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/09|Translations]] are available. '''Recent changes''' * The [[mw:Special:MyLanguage/VisualEditor_on_mobile|mobile visual editor]] is now the default editor for users who never edited before, at a small group of wikis. [[mw:Special:MyLanguage/VisualEditor_on_mobile/VE_mobile_default#A/B_test_results| Research ]] shows that users using this editor are slightly more successful publishing the edits they started, and slightly less successful publishing non-reverted edits. Users who defined the wikitext editor as their default on desktop will get the wikitext editor on mobile for their first edit on mobile as well. [https://phabricator.wikimedia.org/T352127] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Special:MyLanguage/ResourceLoader/Core modules#mw.config|mw.config]] value <code>wgGlobalGroups</code> now only contains groups that are active in the wiki. Scripts no longer have to check whether the group is active on the wiki via an API request. A code example of the above is: <bdi lang="zxx" dir="ltr"><code>if (/globalgroupname/.test(mw.config.get("wgGlobalGroups")))</code></bdi>. [https://phabricator.wikimedia.org/T356008] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-27|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-28|en}}. It will be on all wikis from {{#time:j xg|2024-02-29|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * The right to change [[mw:Special:MyLanguage/Manual:Tags|edit tags]] (<bdi lang="zxx" dir="ltr"><code>changetags</code></bdi>) will be removed from users in Wikimedia sites, keeping it by default for admins and bots only. Your community can ask to retain the old configuration on your wiki before this change happens. Please indicate in [[phab:T355639|this ticket]] to keep it for your community before the end of March 2024. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:23, 26 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26294125 --> == Wikipedia translation of the week: 2024-10 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sissieretta Jones]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:1899 poster of Mme. M. Sissieretta Jones.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Matilda Sissieretta Joyner Jones''' (January 5, 1868, or 1869 – June 24, 1933) was an American soprano. She sometimes was called "The Black Patti" in reference to Italian opera singer Adelina Patti. Jones' repertoire included grand opera, light opera, and popular music <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 4 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26313143 --> == Tech News: 2024-10 == <section begin="technews-2024-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/10|Translations]] are available. '''Recent changes''' * The <bdi lang="zxx" dir="ltr"><code>Special:Book</code></bdi> page (as well as the associated "Create a book" functionality) provided by the old [[mw:Special:MyLanguage/Extension:Collection|Collection extension]] has been removed from all Wikisource wikis, as it was broken. This does not affect the ability to download normal books, which is provided by the [[mw:Special:MyLanguage/Extension:Wikisource|Wikisource extension]]. [https://phabricator.wikimedia.org/T358437] * [[m:Wikitech|Wikitech]] now uses the next-generation [[mw:Special:MyLanguage/Parsoid|Parsoid]] wikitext parser by default to generate all pages in the Talk namespace. Report any problems on the [[mw:Talk:Parsoid/Parser_Unification/Known_Issues|Known Issues discussion page]]. You can use the [[mw:Special:MyLanguage/Extension:ParserMigration|ParserMigration]] extension to control the use of Parsoid; see the [[mw:Special:MyLanguage/Help:Extension:ParserMigration|ParserMigration help documentation]] for more details. * Maintenance on [https://etherpad.wikimedia.org etherpad] is completed. If you encounter any issues, please indicate in [[phab:T316421|this ticket]]. * [[File:Octicons-tools.svg|12px|link=|alt=| Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] allow interface admins to create custom features with CSS and JavaScript. The <bdi lang="zxx" dir="ltr"><code>Gadget</code></bdi> and <bdi lang="zxx" dir="ltr"><code>Gadget_definition</code></bdi> namespaces and <bdi lang="zxx" dir="ltr"><code>gadgets-definition-edit</code></bdi> user right were reserved for an experiment in 2015, but were never used. These were visible on Special:Search and Special:ListGroupRights. The unused namespaces and user rights are now removed. No pages are moved, and no changes need to be made. [https://phabricator.wikimedia.org/T31272] * A usability improvement to the "Add a citation" in Wikipedia workflow has been made, the insert button was moved to the popup header. [https://phabricator.wikimedia.org/T354847] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.21|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-05|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-06|en}}. It will be on all wikis from {{#time:j xg|2024-03-07|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * All wikis will be read-only for a few minutes on March 20. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T358233] * The HTML markup of headings and section edit links will be changed later this year to improve accessibility. See [[mw:Special:MyLanguage/Heading_HTML_changes|Heading HTML changes]] for details. The new markup will be the same as in the new Parsoid wikitext parser. You can test your gadget or stylesheet with the new markup if you add <bdi lang="zxx" dir="ltr"><code>?useparsoid=1</code></bdi> to your URL ([[mw:Special:MyLanguage/Help:Extension:ParserMigration#Selecting_a_parser_using_a_URL_query_string|more info]]) or turn on Parsoid read views in your user options ([[mw:Special:MyLanguage/Help:Extension:ParserMigration#Enabling_via_user_preference|more info]]). * '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:47, 4 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26329807 --> == Wikipedia translation of the week: 2024-11 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Preventative Coup of November 11]]'''<br /> <small>''([[:es:Golpe de Estado en Brasil de 1955]])''</small> </div> Please be bold and help translate this article! ---- [[File:Exército na casa de Café Filho.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Preventative Coup of November 11''' sometimes called the '''1955 Brazilian coup d'état''' or referred to as an "anti-coup" or a "counter-coup" (Portuguese: ''Novembrada, Movimento de 11 de Novembro, Contragolpe, Golpe Preventivo do Marechal Lott'') was a series of military and political events led by Henrique Teixeira Lott that resulted in Nereu Ramos assuming the presidency of Brazil until being peacefully succeeded by Juscelino Kubitschek a few months later. The bloodless coup removed Carlos Luz from the presidency because he was suspected of plotting to prevent Kubitschek from taking office. As a result of the tensions, Brazil had three presidents in the span of a single week. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 11 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26366849 --> == Tech News: 2024-11 == <section begin="technews-2024-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/11|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-13|en}}. It will be on all wikis from {{#time:j xg|2024-03-14|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * After consulting with various communities, the line height of the text on the [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva skin]] will be increased to its previous value of 1.65. Different options for typography can also be set using the options in the menu, as needed. [https://phabricator.wikimedia.org/T358498] *The active link color in [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva]] will be changed to provide more consistency with our other platforms and best practices. [https://phabricator.wikimedia.org/T358516] * [[c:Special:MyLanguage/Commons:Structured data|Structured data on Commons]] will no longer ask whether you want to leave the page without saving. This will prevent the “information you’ve entered may not be saved” popups from appearing when no information have been entered. It will also make file pages on Commons load faster in certain cases. However, the popups will be hidden even if information has indeed been entered. If you accidentally close the page before saving the structured data you entered, that data will be lost. [https://phabricator.wikimedia.org/T312315] '''Future changes''' * All wikis will be read-only for a few minutes on March 20. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T358233][https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:04, 11 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26374013 --> == Wikipedia translation of the week: 2024-12 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hojang Taret]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Hojang Taret''' is a classical Meitei language play based on Euripides's ancient Greek tragedy The Phoenician Women. It is directed by Oasis Sougaijam and produced by The Umbilical Theatre in Imphal, Kangleipak. It depicts the moral ambiguities of conflict between brothers resulting to the ruination of the ancient city of Thebes. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 18 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26366849 --> == Tech News: 2024-12 == <section begin="technews-2024-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/12|Translations]] are available. '''Recent changes''' * The notice "Language links are at the top of the page" that appears in the [[mw:Special:MyLanguage/Skin:Vector/2022|Vector 2022 skin]] main menu has been removed now that users have learned the new location of the Language switcher. [https://phabricator.wikimedia.org/T353619] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[m:Special:MyLanguage/IP_Editing:_Privacy_Enhancement_and_Abuse_Mitigation/IP_Info_feature|IP info feature]] displays data from Spur, an IP addresses database. Previously, the only data source for this feature was MaxMind. Now, IP info is more useful for patrollers. [https://phabricator.wikimedia.org/T341395] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Toolforge Grid Engine services have been shut down after the final migration process from Grid Engine to Kubernetes. [https://wikitech.wikimedia.org/wiki/Obsolete:Toolforge/Grid][https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation][https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/] * Communities can now customize the default reasons for undeleting a page by creating [[MediaWiki:Undelete-comment-dropdown]]. [https://phabricator.wikimedia.org/T326746] '''Problems''' * [[m:Special:MyLanguage/WMDE_Technical_Wishes/RevisionSlider|RevisionSlider]] is an interface to interactively browse a page's history. Users in [[mw:Special:MyLanguage/Extension:RevisionSlider/Developing_a_RTL-accessible_feature_in_MediaWiki_-_what_we%27ve_learned_while_creating_the_RevisionSlider|right-to-left]] languages reported RevisionSlider reacting wrong to mouse clicks. This should be fixed now. [https://phabricator.wikimedia.org/T352169] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-20|en}}. It will be on all wikis from {{#time:j xg|2024-03-21|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * All wikis will be read-only for a few minutes on March 20. This is planned at [https://zonestamp.toolforge.org/1710943200 14:00 UTC]. [https://phabricator.wikimedia.org/T358233][https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:40, 18 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26410165 --> == Wikipedia translation of the week: 2024-13 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Magna Lykseth-Skogman]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Magna Lykseth in Tristan och Isolde at Kungliga Operan 1909 - SMV - GL164.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Magna Elvine Lykseth-Skogman''' (6 February 1874 – 13 November 1949), also known as Magna Lykseth-Schjerven, was a Norwegian-born Swedish operatic soprano. After making her début at the Royal Swedish Opera in 1901 as Santuzza in Cavalleria rusticana, she was engaged there until 1918 becoming the company's prima donna. She performed leading roles in a wide range of operas but is remembered in particular for her Wagnerian interpretations, creating Brünnhilde in the Swedish premières of Siegfried and Götterdämmerung, and Isolde in 1909. Considered to be one of the most outstanding Swedish opera singers of her generation, she was awarded the Litteris et Artibus medal in 1907 and became a member of the Royal Swedish Academy of Music in 1912 <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:00, 25 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26447450 --> == Tech News: 2024-13 == <section begin="technews-2024-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/13|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] An update was made on March 18th 2024 to how various projects load site, user JavaScript and CSS in [[mw:Special:MyLanguage/Skin:Vector/2022|Vector 2022 skin]]. A [[phab:T360384|checklist]] is provided for site admins to follow. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.24|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-26|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-27|en}}. It will be on all wikis from {{#time:j xg|2024-03-28|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:57, 25 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26446209 --> == Wikipedia translation of the week: 2024-14 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lidder Valley]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Pahalgam Valley.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Lidder Valley''' or Liddar Valley is a Himalayan sub-valley that forms the southeastern corner of Anantnag district in Indian-administered Kashmir. The Lidder River flows down the valley. The entrance to the valley lies 7 km northeast from Anantnag town and 62 km southeast from Srinagar, the summer capital of Jammu and Kashmir. It is a 40-km-long gorge valley with an average width of 3 km. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:15, 1 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26509189 --> == Tech News: 2024-14 == <section begin="technews-2024-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/14|Translations]] are available. '''Recent changes''' * Users of the [[mw:Special:MyLanguage/Reading/Web/Accessibility_for_reading|reading accessibility]] beta feature will notice that the default line height for the standard and large text options has changed. [https://phabricator.wikimedia.org/T359030] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-02|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-03|en}}. It will be on all wikis from {{#time:j xg|2024-04-04|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * The Wikimedia Foundation has an annual plan. The annual plan decides what the Wikimedia Foundation will work on. You can now read [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2024-2025/Product & Technology OKRs#Draft Key Results|the draft key results]] for the Product and Technology department. They are suggestions for what results the Foundation wants from big technical changes from July 2024 to June 2025. You can [[m:Talk:Wikimedia Foundation Annual Plan/2024-2025/Product & Technology OKRs|comment on the talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:36, 2 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26462933 --> == Wikipedia translation of the week: 2024-15 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Operation Kraai]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Overzicht van het vliegveld te Djokja vanuit de 'Control Tower', Bestanddeelnr 5128.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Operation Kraai''' (Operation Crow) was a Dutch military offensive against the de facto Republic of Indonesia in December 1948 after negotiations failed. With the advantage of surprise the Dutch managed to capture the Indonesian Republic's temporary capital, Yogyakarta, and seized Indonesian leaders such as de facto Republican President Sukarno. This apparent military success was however followed by guerrilla warfare, while the violation of the Renville Agreement ceasefire diplomatically isolated the Dutch, leading to the Dutch–Indonesian Round Table Conference and recognition of the United States of Indonesia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:47, 8 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26550154 --> == Tech News: 2024-15 == <section begin="technews-2024-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/15|Translations]] are available. '''Recent changes''' * Web browsers can use tools called [[:w:en:Browser extension|extensions]]. There is now a Chrome extension called [[m:Future Audiences/Experiment:Citation Needed|Citation Needed]] which you can use to see if an online statement is supported by a Wikipedia article. This is a small experiment to see if Wikipedia can be used this way. Because it is a small experiment, it can only be used in Chrome in English. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] A new [[mw:Special:MyLanguage/Help:Edit Recovery|Edit Recovery]] feature has been added to all wikis, available as a [[Special:Preferences#mw-prefsection-editing|user preference]]. Once you enable it, your in-progress edits will be stored in your web browser, and if you accidentally close an editing window or your browser or computer crashes, you will be prompted to recover the unpublished text. Please leave any feedback on the [[m:Special:MyLanguage/Talk:Community Wishlist Survey 2023/Edit-recovery feature|project talk page]]. This was the #8 wish in the 2023 Community Wishlist Survey. * Initial results of [[mw:Special:MyLanguage/Edit check|Edit check]] experiments [[mw:Special:MyLanguage/Edit_check#4_April_2024|have been published]]. Edit Check is now deployed as a default feature at [[phab:T342930#9538364|the wikis that tested it]]. [[mw:Talk:Edit check|Let us know]] if you want your wiki to be part of the next deployment of Edit check. [https://phabricator.wikimedia.org/T342930][https://phabricator.wikimedia.org/T361727] * Readers using the [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva skin]] on mobile will notice there has been an improvement in the line height across all typography settings. [https://phabricator.wikimedia.org/T359029] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-10|en}}. It will be on all wikis from {{#time:j xg|2024-04-11|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * New accounts and logged-out users will get the [[mw:Special:MyLanguage/VisualEditor|visual editor]] as their default editor on mobile. This deployment is made at all wikis except for the English Wikipedia. [https://phabricator.wikimedia.org/T361134] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:38, 8 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26564838 --> == Wikipedia translation of the week: 2024-16 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ru:Павильон Росси]]'''<br /> <small>''([[:en:Rossi Pavilion]])&#32;([[:fr:Pavillon Rossi]])''</small> </div> Please be bold and help translate this article! ---- [[File:Rossi's Pavilion in Mikhailovsky Garden. Saint-Petersburg. 1825..jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Rossi Pavilion''' (Russian: Павильон Росси) is a pavilion on the bank of the Moyka River in the Mikhailovsky Garden in Saint Petersburg. It was designed by architect Carlo Rossi in the early 1820s and built in 1825 during his redevelopment of the garden. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:53, 15 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26565118 --> == Tech News: 2024-16 == <section begin="technews-2024-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/16|Translations]] are available. '''Problems''' * Between 2 April and 8 April, on wikis using [[mw:Special:MyLanguage/Extension:FlaggedRevs|Flagged Revisions]], the "{{Int:tag-mw-reverted}}" tag was not applied to undone edits. In addition, page moves, protections and imports were not autoreviewed. This problem is now fixed. [https://phabricator.wikimedia.org/T361918][https://phabricator.wikimedia.org/T361940] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-17|en}}. It will be on all wikis from {{#time:j xg|2024-04-18|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[mw:Special:MyLanguage/Help:Magic words#DEFAULTSORT|Default category sort keys]] will now affect categories added by templates placed in [[mw:Special:MyLanguage/Help:Cite|footnotes]]. Previously footnotes used the page title as the default sort key even if a different default sort key was specified (category-specific sort keys already worked). [https://phabricator.wikimedia.org/T40435] * A new variable <bdi lang="zxx" dir="ltr"><code>page_last_edit_age</code></bdi> will be added to [[Special:AbuseFilter|abuse filters]]. It tells how many seconds ago the last edit to a page was made. [https://phabricator.wikimedia.org/T269769] '''Future changes''' * Volunteer developers are kindly asked to update the code of their tools and features to handle [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]]. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers/2024-04 CTA|Learn more]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Four database fields will be removed from database replicas (including [[quarry:|Quarry]]). This affects only the <bdi lang="zxx" dir="ltr"><code>abuse_filter</code></bdi> and <bdi lang="zxx" dir="ltr"><code>abuse_filter_history</code></bdi> tables. Some queries might need to be updated. [https://phabricator.wikimedia.org/T361996] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:29, 15 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26564838 --> == Wikipedia translation of the week: 2024-17 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Devorà Ascarelli]]'''<br /> <small>''([[:it:Debora Ascarelli]])&#32;([[:es:Devorà Ascarelli]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Devorà Ascarelli''' was a 16th-century Italian poet living in Rome, Italy. Ascarelli may have been the first Jewish woman to have a book of her own work published. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:35, 22 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-17 == <section begin="technews-2024-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/17|Translations]] are available. '''Recent changes''' * Starting this week, newcomers editing Wikipedia [[mw:Special:MyLanguage/Growth/Positive reinforcement#Leveling up 3|will be encouraged]] to try structured tasks. [[mw:Special:MyLanguage/Growth/Feature summary#Newcomer tasks|Structured tasks]] have been shown to [[mw:Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add a link/Experiment analysis, December 2021|improve newcomer activation and retention]]. [https://phabricator.wikimedia.org/T348086] * You can [[m:Special:MyLanguage/Coolest Tool Award|nominate your favorite tools]] for the fifth edition of the Coolest Tool Award. Nominations will be open until May 10. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-24|en}}. It will be on all wikis from {{#time:j xg|2024-04-25|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * This is the last warning that by the end of May 2024 the Vector 2022 skin will no longer share site and user scripts/styles with old Vector. For user-scripts that you want to keep using on Vector 2022, copy the contents of [[{{#special:MyPage}}/vector.js]] to [[{{#special:MyPage}}/vector-2022.js]]. There are [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Loading Vector 2010 scripts|more technical details]] available. Interface administrators who foresee this leading to lots of technical support questions may wish to send a mass message to your community, as was done on French Wikipedia. [https://phabricator.wikimedia.org/T362701] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:28, 22 April 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26647188 --> == Wikipedia translation of the week: 2024-18 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:1989 Serbian general election]]'''<br /> <small>''([[:sr:Председнички избори у Србији 1989.]])&#32;([[:vi:Tổng tuyển cử Serbia 1989]])''</small></div> Please be bold and help translate this article! ---- [[File:Parliament of SR Serbia (1989–1991).svg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''General elections were held in Serbia''', a constituent federal unit of SFR Yugoslavia, on 12 November 1989 to elect the president of the presidency of the Socialist Republic of Serbia and delegates of the Assembly of SR Serbia. Voting for delegates also took place on 10 and 30 November 1989. In addition to the general elections, local elections were held simultaneously. These were the first direct elections conducted after the adoption of the 1974 Yugoslav Constitution and the delegate electoral system, and the last elections conducted under a one-party system. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:32, 29 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-18 == <section begin="technews-2024-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/18|Translations]] are available. '''Recent changes''' [[File:Talk_pages_default_look_(April_2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages changed for the following wikis: {{int:project-localized-name-azwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-idwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-thwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ukwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-viwiki/en}}. These wikis participated to a test, where 50% of users got the new design, for one year. As this test [[Mw:Special:MyLanguage/Talk pages project/Usability/Analysis|gave positive results]], the new design is deployed on these wikis as the default design. It is possible to opt-out these changes [[Special:Preferences#mw-prefsection-editing|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). The deployment will happen at all wikis in the coming weeks. [https://phabricator.wikimedia.org/T341491] * Seven new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q33014|Betawi]] ([[w:bew:|<code>w:bew:</code>]]) [https://phabricator.wikimedia.org/T357866] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35708|Kusaal]] ([[w:kus:|<code>w:kus:</code>]]) [https://phabricator.wikimedia.org/T359757] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35513|Igala]] ([[w:igl:|<code>w:igl:</code>]]) [https://phabricator.wikimedia.org/T361644] ** a {{int:project-localized-name-group-wiktionary}} in [[d:Q33541|Karakalpak]] ([[wikt:kaa:|<code>wikt:kaa:</code>]]) [https://phabricator.wikimedia.org/T362135] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q9228|Burmese]] ([[s:my:|<code>s:my:</code>]]) [https://phabricator.wikimedia.org/T361085] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q9237|Malay]] ([[s:ms:|<code>s:ms:</code>]]) [https://phabricator.wikimedia.org/T363039] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q8108|Georgian]] ([[s:ka:|<code>s:ka:</code>]]) [https://phabricator.wikimedia.org/T363085] * You can now [https://translatewiki.net/wiki/Support#Early_access:_Watch_Message_Groups_on_Translatewiki.net watch message groups/projects] on [[m:Special:MyLanguage/translatewiki.net|Translatewiki.net]]. Initially, this feature will notify you of added or deleted messages in these groups. [https://phabricator.wikimedia.org/T348501] * Dark mode is now available on all wikis, on mobile web for logged-in users who opt into the [[Special:MobileOptions|advanced mode]]. This is the early release of the feature. Technical editors are invited to [https://night-mode-checker.wmcloud.org/ check for accessibility issues on wikis]. See [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-04|more detailed guidelines]]. '''Problems''' * [[mw:Special:MyLanguage/Help:Extension:Kartographer|Kartographer]] maps can use an alternative visual style without labels, by using <bdi lang="zxx" dir="ltr"><code><nowiki>mapstyle="osm"</nowiki></code></bdi>. This wasn't working in previews, creating the wrong impression that it wasn't supported. This has now been fixed. [https://phabricator.wikimedia.org/T362531] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-01|en}}. It will be on all wikis from {{#time:j xg|2024-05-02|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:34, 30 April 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26689057 --> == Wikipedia translation of the week: 2024-19 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Heinrich Bünting]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Heinrich Bünting''' (1545 – 1606) was a Protestant pastor and theologian. He is best known for his book of woodcut maps titled Itinerarium Sacrae Scripturae (Travel book through Holy Scripture) first published in 1581. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 6 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-19 == <section begin="technews-2024-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/19|Translations]] are available. '''Recent changes''' [[File:Talk_pages_default_look_(April_2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages changed for all wikis, except for Commons, Wikidata and most Wikipedias ([[m:Special:MyLanguage/Tech/News/2024/18|a few]] have already received this design change). You can read the detail of the changes [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. It is possible to opt-out these changes [[Special:Preferences#mw-prefsection-editing|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). The deployment will happen at remaining wikis in the coming weeks. [https://phabricator.wikimedia.org/T352087][https://phabricator.wikimedia.org/T319146] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Interface admins now have greater control over the styling of article components on mobile with the introduction of the <code>SiteAdminHelper</code>. More information on how styles can be disabled can be found [[mw:Special:MyLanguage/Extension:WikimediaMessages#Site_admin_helper|at the extension's page]]. [https://phabricator.wikimedia.org/T363932] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] has added article body sections in JSON format and a curated short description field to the existing parsed Infobox. This expansion to the API is also available via Wikimedia Cloud Services. [https://enterprise.wikimedia.com/blog/article-sections-and-description/] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-08|en}}. It will be on all wikis from {{#time:j xg|2024-05-09|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * When you look at the Special:Log page, the first view is labelled "All public logs", but it only shows some logs. This label will now say "Main public logs". [https://phabricator.wikimedia.org/T237729] '''Future changes''' * A new service will be built to replace [[mw:Special:MyLanguage/Extension:Graph|Extension:Graph]]. Details can be found in [[mw:Special:MyLanguage/Extension:Graph/Plans|the latest update]] regarding this extension. * Starting May 21, English Wikipedia and German Wikipedia will get the possibility to activate "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]". This is part of the [[phab:T304110|progressive deployment of this tool to all Wikipedias]]. These communities can [[mw:Special:MyLanguage/Growth/Community configuration|activate and configure the feature locally]]. [https://phabricator.wikimedia.org/T308144] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:45, 6 May 2024 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26729363 --> == Wikipedia translation of the week: 2024-20 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:var(--background-color-backdrop-dark, #DDDDDD); border:1px solid #BBBBBB; color:var(--color-inverted, #000000); padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ruyan (district)]]'''<br /> <small>''([[:fa:رویان (طبرستان)]])''</small> </div> Please be bold and help translate this article! ---- [[File:Northern Iran and its surroundings during the Iranian intermezzo.svg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Ruyan''' (Persian: رویان), later known as Rustamdar (رستمدار), was the name of a mountainous district that encompassed the western part of Tabaristan/Mazandaran, a region on the Caspian coast of northern Iran. In Iranian mythology, Ruyan appears as one of the places that the legendary archer Arash shot his arrow from, reaching the edge of Khorasan to mark the border between Iran and Turan. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:39, 13 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26755244 --> == Tech News: 2024-20 == <section begin="technews-2024-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/20|Translations]] are available. '''Recent changes''' * On Wikisource there is a special page listing pages of works without corresponding scan images. Now you can use the new magic word <bdi lang="zxx" dir="ltr"><code>__EXPECTWITHOUTSCANS__</code></bdi> to exclude certain pages (list of editions or translations of works) from that list. [https://phabricator.wikimedia.org/T344214] * If you use the [[Special:Preferences#mw-prefsection-editing|user-preference]] "{{int:tog-uselivepreview}}", then the template-page feature "{{int:Templatesandbox-editform-legend}}" will now also work without reloading the page. [https://phabricator.wikimedia.org/T136907] * [[mw:Special:Mylanguage/Extension:Kartographer|Kartographer]] maps can now specify an alternative text via the <bdi lang="zxx" dir="ltr"><code><nowiki>alt=</nowiki></code></bdi> attribute. This is identical in usage to the <bdi lang="zxx" dir="ltr"><code><nowiki>alt=</nowiki></code></bdi> attribute in the [[mw:Special:MyLanguage/Help:Images#Syntax|image and gallery syntax]]. An exception for this feature is wikis like Wikivoyage where the miniature maps are interactive. [https://phabricator.wikimedia.org/T328137] * The old [[mw:Special:MyLanguage/Extension:GuidedTour|Guided Tour]] for the "[[mw:Special:MyLanguage/Edit Review Improvements/New filters for edit review|New Filters for Edit Review]]" feature has been removed. It was created in 2017 to show people with older accounts how the interface had changed, and has now been seen by most of the intended people. [https://phabricator.wikimedia.org/T217451] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-15|en}}. It will be on all wikis from {{#time:j xg|2024-05-16|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[{{#special:search}}]] results page will now use CSS flex attributes, for better accessibility, instead of a table. If you have a gadget or script that adjusts search results, you should update your script to the new HTML structure. [https://phabricator.wikimedia.org/T320295] '''Future changes''' * In the Vector 2022 skin, main pages will be displayed at full width (like special pages). The goal is to keep the number of characters per line large enough. This is related to the coming changes to typography in Vector 2022. [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates|Learn more]]. [https://phabricator.wikimedia.org/T357706] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Two columns of the <bdi lang="zxx" dir="ltr"><code>[[mw:Special:MyLanguage/Manual:pagelinks table|pagelinks]]</code></bdi> database table (<bdi lang="zxx" dir="ltr"><code>pl_namespace</code></bdi> and <bdi lang="zxx" dir="ltr"><code>pl_title</code></bdi>) are being dropped soon. Users must use two columns of the new <bdi lang="zxx" dir="ltr"><code>[[mw:special:MyLanguage/Manual:linktarget table|linktarget]]</code></bdi> table instead (<bdi lang="zxx" dir="ltr"><code>lt_namespace</code></bdi> and <bdi lang="zxx" dir="ltr"><code>lt_title</code></bdi>). In your existing SQL queries: *# Replace <bdi lang="zxx" dir="ltr"><code>JOIN pagelinks</code></bdi> with <bdi lang="zxx" dir="ltr"><code>JOIN linktarget</code></bdi> and <bdi lang="zxx" dir="ltr"><code>pl_</code></bdi> with <bdi lang="zxx" dir="ltr"><code>lt_</code></bdi> in the <bdi lang="zxx" dir="ltr"><code>ON</code></bdi> statement *# Below that add <bdi lang="zxx" dir="ltr"><code>JOIN pagelinks ON lt_id = pl_target_id</code></bdi> ** See <bdi lang="en" dir="ltr">[[phab:T222224]]</bdi> for technical reasoning. [https://phabricator.wikimedia.org/T222224][https://phabricator.wikimedia.org/T299947] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:59, 13 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26762074 --> == Wikipedia translation of the week: 2024-21 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Turlough (lake)]]'''<br /> <small>''([[:de:Turlough]])&#32;([[:no:Turlough]])''</small> </div> Please be bold and help translate this article! ---- [[File:Carran Turlough.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''turlough''' is a seasonal or periodic water body found mostly in limestone karst areas of Ireland, west of the River Shannon. [...] The water bodies fill and empty with the changes in the level of the water table, usually being very low or empty during summer and autumn and full in the winter. As groundwater levels drop the water drains away underground through cracks in the karstic limestone. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:31, 20 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26789673 --> == Tech News: 2024-21 == <section begin="technews-2024-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/21|Translations]] are available. '''Recent changes''' * The [[mw:Special:MyLanguage/Extension:Nuke|Nuke]] feature, which enables administrators to mass delete pages, will now correctly delete pages which were moved to another title. [https://phabricator.wikimedia.org/T43351] * New changes have been made to the UploadWizard in Wikimedia Commons: the overall layout has been improved, by following new styling and spacing for the form and its fields; the headers and helper text for each of the fields was changed; the Caption field is now a required field, and there is an option for users to copy their caption into the media description. [https://commons.wikimedia.org/wiki/Commons:WMF_support_for_Commons/Upload_Wizard_Improvements#Changes_to_%22Describe%22_workflow][https://phabricator.wikimedia.org/T361049] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.6|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-22|en}}. It will be on all wikis from {{#time:j xg|2024-05-23|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML used to render all headings [[mw:Heading_HTML_changes|is being changed to improve accessibility]]. It will change on 22 May in some skins (Timeless, Modern, CologneBlue, Nostalgia, and Monobook). Please test gadgets on your wiki on these skins and [[phab:T13555|report any related problems]] so that they can be resolved before this change is made in all other skins. The developers are also considering the introduction of a [[phab:T337286|Gadget API for adding buttons to section titles]] if that would be helpful to tool creators, and would appreciate any input you have on that. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W21"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:04, 20 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26786311 --> == Wikipedia translation of the week: 2024-22 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Geiranger Church]]'''<br /> <small>''([[:no:Geiranger kirke]])''</small> </div> Please be bold and help translate this article! ---- [[File:Iglesia parroquial, Geiranger, Noruega, 2019-09-07, DD 84-97 PAN.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Geiranger Church''' (Norwegian: Geiranger kyrkje) is a parish church of the Church of Norway in Stranda Municipality in Møre og Romsdal county, Norway. It is located in the village of Geiranger, and the end of the famous Geirangerfjorden. It is the church for the Geiranger parish which is part of the Nordre Sunnmøre prosti (deanery) in the Diocese of Møre. The white, wooden church was built in an octagonal design in 1842 using plans drawn up by the architect Hans Klipe. The church seats about 165 people. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:48, 27 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26828106 --> == Tech News: 2024-22 == <section begin="technews-2024-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/22|Translations]] are available. '''Recent changes''' * Several bugs related to the latest updates to the UploadWizard on Wikimedia Commons have been fixed. For more information, see [[:phab:T365107|T365107]] and [[:phab:T365119|T365119]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] In March 2024 a new [[mw:ResourceLoader/Core_modules#addPortlet|addPortlet]] API was added to allow gadgets to create new portlets (menus) in the skin. In certain skins this can be used to create dropdowns. Gadget developers are invited to try it and [[phab:T361661|give feedback]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Some CSS in the Minerva skin has been removed to enable easier community configuration. Interface editors should check the rendering on mobile devices for aspects related to the classes: <bdi lang="zxx" dir="ltr"><code>.collapsible</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.multicol</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.reflist</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.coordinates</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.topicon</code></bdi>. [[phab:T361659|Further details are available on replacement CSS]] if it is needed. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-29|en}}. It will be on all wikis from {{#time:j xg|2024-05-30|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * When you visit a wiki where you don't yet have a local account, local rules such as edit filters can sometimes prevent your account from being created. Starting this week, MediaWiki takes your global rights into account when evaluating whether you can override such local rules. [https://phabricator.wikimedia.org/T316303] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:15, 28 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26832205 --> == Wikipedia translation of the week: 2024-23 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Guillermo Larrazábal]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Guillermo Larrazábal Arzubide''' (10 February 1907 – 1983) was a Spanish stained glass artist who was active in Ecuador. He is considered Ecuador's most important stained glass artist. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:14, 3 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26828106 --> == Tech News: 2024-23 == <section begin="technews-2024-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/23|Translations]] are available. '''Recent changes''' * It is now possible for local administrators to add new links to the bottom of the site Tools menu without JavaScript. [[mw:Manual:Interface/Sidebar#Add or remove toolbox sections|Documentation is available]]. [https://phabricator.wikimedia.org/T6086] * The message name for the definition of the tracking category of WikiHiero has changed from "<bdi lang="zxx" dir="ltr"><code>MediaWiki:Wikhiero-usage-tracking-category</code></bdi>" to "<bdi lang="zxx" dir="ltr"><code>MediaWiki:Wikihiero-usage-tracking-category</code></bdi>". [https://gerrit.wikimedia.org/r/c/mediawiki/extensions/wikihiero/+/1035855] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q5317225|Kadazandusun]] ([[w:dtp:|<code>w:dtp:</code>]]) [https://phabricator.wikimedia.org/T365220] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.8|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-05|en}}. It will be on all wikis from {{#time:j xg|2024-06-06|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * Next week, on wikis with the Vector 2022 skin as the default, logged-out desktop users will be able to choose between different font sizes. The default font size will also be increased for them. This is to make Wikimedia projects easier to read. [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-06 deployments|Learn more]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:35, 3 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26844397 --> == Tech News: 2024-24 == <section begin="technews-2024-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/24|Translations]] are available. '''Recent changes''' * The software used to render SVG files has been updated to a new version, fixing many longstanding bugs in SVG rendering. [https://phabricator.wikimedia.org/T265549] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML used to render all headings [[mw:Heading HTML changes|is being changed to improve accessibility]]. It was changed last week in some skins (Vector legacy and Minerva). Please test gadgets on your wiki on these skins and [[phab:T13555|report any related problems]] so that they can be resolved before this change is made in Vector-2022. The developers are still considering the introduction of a [[phab:T337286|Gadget API for adding buttons to section titles]] if that would be helpful to tool creators, and would appreciate any input you have on that. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML markup used for citations by [[mw:Special:MyLanguage/Parsoid|Parsoid]] changed last week. In places where Parsoid previously added the <bdi lang="zxx" dir="ltr"><code>mw-reference-text</code></bdi> class, Parsoid now also adds the <bdi lang="zxx" dir="ltr"><code>reference-text</code></bdi> class for better compatibility with the legacy parser. [[mw:Specs/HTML/2.8.0/Extensions/Cite/Announcement|More details are available]]. [https://gerrit.wikimedia.org/r/1036705] '''Problems''' * There was a bug with the Content Translation interface that caused the tools menus to appear in the wrong location. This has now been fixed. [https://phabricator.wikimedia.org/T366374] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-12|en}}. It will be on all wikis from {{#time:j xg|2024-06-13|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The new version of MediaWiki includes another change to the HTML markup used for citations: [[mw:Special:MyLanguage/Parsoid|Parsoid]] will now generate a <bdi lang="zxx" dir="ltr"><code><nowiki><span class="mw-cite-backlink"></nowiki></code></bdi> wrapper for both named and unnamed references for better compatibility with the legacy parser. Interface administrators should verify that gadgets that interact with citations are compatible with the new markup. [[mw:Specs/HTML/2.8.0/Extensions/Cite/Announcement|More details are available]]. [https://gerrit.wikimedia.org/r/1035809] * On multilingual wikis that use the <bdi lang="zxx" dir="ltr"><code><nowiki><translate></nowiki></code></bdi> system, there is a feature that shows potentially-outdated translations with a pink background until they are updated or confirmed. From this week, confirming translations will be logged, and there is a new user-right that can be required for confirming translations if the community [[m:Special:MyLanguage/Requesting wiki configuration changes|requests it]]. [https://phabricator.wikimedia.org/T49177] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:20, 10 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26893898 --> == Wikipedia translation of the week: 2024-25 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:de:Magdalena Zeger]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Magdalena Zeger''' ([mak.da.ˈleː.na ˈt͡seː.gɐ], * 1491; † 16. January 1568 in Kolding) was a calendar maker, astronomer and astrologist. Her Hamburg almanacs and forecasts from 1561 and 1563 have been preserved. Zeger's calendars are the first independent publications by a woman in the field of astronomy. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:29, 17 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26940351 --> == Tech News: 2024-25 == <section begin="technews-2024-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/25|Translations]] are available. '''Recent changes''' * People who attempt to add an external link in the visual editor will now receive immediate feedback if they attempt to link to a domain that a project has decided to block. Please see [[mw:Special:MyLanguage/Edit_check#11_June_2024|Edit check]] for more details. [https://phabricator.wikimedia.org/T366751] * The new [[mw:Special:MyLanguage/Extension:CommunityConfiguration|Community Configuration extension]] is available [[testwiki:Special:CommunityConfiguration|on Test Wikipedia]]. This extension allows communities to customize specific features to meet their local needs. Currently only Growth features are configurable, but the extension will support other [[mw:Special:MyLanguage/Community_configuration#Use_cases|Community Configuration use cases]] in the future. [https://phabricator.wikimedia.org/T323811][https://phabricator.wikimedia.org/T360954] * The dark mode [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] is now available on category and help pages, as well as more special pages. There may be contrast issues. Please report bugs on the [[mw:Talk:Reading/Web/Accessibility_for_reading|project talk page]]. [https://phabricator.wikimedia.org/T366370] '''Problems''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Cloud Services tools were not available for 25 minutes last week. This was caused by a faulty hardware cable in the data center. [https://wikitech.wikimedia.org/wiki/Incidents/2024-06-11_WMCS_Ceph] * Last week, styling updates were made to the Vector 2022 skin. This caused unforeseen issues with templates, hatnotes, and images. Changes to templates and hatnotes were reverted. Most issues with images were fixed. If you still see any, [[phab:T367463|report them here]]. [https://phabricator.wikimedia.org/T367480] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-19|en}}. It will be on all wikis from {{#time:j xg|2024-06-20|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting June 18, the [[mw:Special:MyLanguage/Help:Edit check#ref|Reference Edit Check]] will be deployed to [[phab:T361843|a new set of Wikipedias]]. This feature is intended to help newcomers and to assist edit-patrollers by inviting people who are adding new content to a Wikipedia article to add a citation when they do not do so themselves. During [[mw:Special:MyLanguage/Edit_check#Reference_Check_A/B_Test|a test at 11 wikis]], the number of citations added [https://diff.wikimedia.org/?p=127553 more than doubled] when Reference Check was shown to people. Reference Check is [[mw:Special:MyLanguage/Edit check/Configuration|community configurable]]. [https://phabricator.wikimedia.org/T361843]<!-- NOTE: THE DIFF BLOG WILL BE PUBLISHED ON MONDAY --> * [[m:Special:MyLanguage/Mailing_lists|Mailing lists]] will be unavailable for roughly two hours on Tuesday 10:00–12:00 UTC. This is to enable migration to a new server and upgrade its software. [https://phabricator.wikimedia.org/T367521] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:49, 17 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26911987 --> == Wikipedia translation of the week: 2024-26 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Koreans in Micronesia]]'''<br /> <small>''([[:zh:朝鮮裔密克羅尼西亞人]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Koreans in Micronesia''' used to form a significant population before World War II, when most of the region was ruled as the South Seas Mandate of the Empire of Japan; for example, they formed 7.3% of the population of Palau in 1943. However, after the area came under the control of the United States as the Trust Territory of the Pacific Islands, most Koreans returned to their homeland. As of 2013, about seven thousand South Korean expatriates & immigrants and Korean Americans reside in the Marianas (Guam and the Commonwealth of the Northern Mariana Islands), which have remained under U.S. control, while only around two hundred South Korean expatriates reside in the independent countries of Micronesia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 04:03, 24 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26940351 --> == Tech News: 2024-26 == <section begin="technews-2024-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/26|Translations]] are available. '''Recent changes''' * Editors will notice that there have been some changes to the background color of text in the diff view, and the color of the byte-change numbers, last week. These changes are intended to make text more readable in both light mode and dark mode, and are part of a larger effort to increase accessibility. You can share your comments or questions [[mw:Talk:Reading/Web/Accessibility for reading|on the project talkpage]]. [https://phabricator.wikimedia.org/T361717] * The text colors that are used for visited-links, hovered-links, and active-links, were also slightly changed last week to improve their accessibility in both light mode and dark mode. [https://phabricator.wikimedia.org/T366515] '''Problems''' * You can [[mw:Special:MyLanguage/Help:DiscussionTools#Talk pages permalinking|copy permanent links to talk page comments]] by clicking on a comment's timestamp. [[mw:Talk pages project/Permalinks|This feature]] did not always work when the topic title was very long and the link was used as a wikitext link. This has been fixed. Thanks to Lofhi for submitting the bug. [https://phabricator.wikimedia.org/T356196] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.11|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-26|en}}. It will be on all wikis from {{#time:j xg|2024-06-27|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting 26 June, all talk pages messages' timestamps will become a link at English Wikipedia, making this feature available for you to use at all wikis. This link is a permanent link to the comment. It allows users to find the comment they were linked to, even if this comment has since been moved elsewhere. You can read more about this feature [[DiffBlog:/2024/01/29/talk-page-permalinks-dont-lose-your-threads/|on Diff]] or [[mw:Special:MyLanguage/Help:DiscussionTools#Talk pages permalinking|on Mediawiki.org]]. [https://phabricator.wikimedia.org/T365974] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:33, 24 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26989424 --> == Wikipedia translation of the week: 2024-27 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Roller printing on textiles]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Silverstudio.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Roller printing''' on fabrics is a textile printing process patented by Thomas Bell of Scotland in 1783 in an attempt to reduce the cost of the earlier copperplate printing. This method was used in Lancashire fabric mills to produce cotton dress fabrics from the 1790s, most often reproducing small monochrome patterns characterized by striped motifs and tiny dotted patterns called "machine grounds". Improvements in the technology resulted in more elaborate roller prints in bright, rich colours from the 1820s; Turkey red and chrome yellow were particularly popular. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:44, 1 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-27 == <section begin="technews-2024-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/27|Translations]] are available. '''Recent changes''' * Over the next three weeks, dark mode will become available for all users, both logged-in and logged-out, starting with the mobile web version. This fulfils one of the [[m:Special:MyLanguage/Community_Wishlist_Survey_2023/Reading/Dark_mode|top-requested community wishes]], and improves low-contrast reading and usage in low-light settings. As part of these changes, dark mode will also work on User-pages and Portals. There is more information in [[mw:Special:MyLanguage/Reading/Web/Accessibility_for_reading/Updates#June_2024:_Typography_and_dark_mode_deployments,_new_global_preferences|the latest Web team update]]. [https://phabricator.wikimedia.org/T366364] * Logged-in users can now set [[m:Special:GlobalPreferences#mw-prefsection-rendering-skin-skin-prefs|global preferences for the text-size and dark-mode]], thanks to a combined effort across Foundation teams. This allows Wikimedians using multiple wikis to set up a consistent reading experience easily, for example by switching between light and dark mode only once for all wikis. [https://phabricator.wikimedia.org/T341278] * If you use a very old web browser some features might not work on the Wikimedia wikis. This affects Internet Explorer 11 and versions of Chrome, Firefox and Safari older than 2016. This change makes it possible to use new [[d:Q46441|CSS]] features and to send less code to all readers. [https://phabricator.wikimedia.org/T288287][https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:How_to_make_a_MediaWiki_skin#Using_CSS_variables_for_supporting_different_themes_e.g._dark_mode] * Wikipedia Admins can customize local wiki configuration options easily using [[mw:Special:MyLanguage/Community Configuration|Community Configuration]]. Community Configuration was created to allow communities to customize how some features work, because each language wiki has unique needs. At the moment, admins can configure [[mw:Special:MyLanguage/Growth/Feature_summary|Growth features]] on their home wikis, in order to better recruit and retain new editors. More options will be provided in the coming months. [https://phabricator.wikimedia.org/T366458] * Editors interested in language issues that are related to [[w:en:Unicode|Unicode standards]], can now discuss those topics at [[mw:Talk:WMF membership with Unicode Consortium|a new conversation space in MediaWiki.org]]. The Wikimedia Foundation is now a [[mw:Special:MyLanguage/WMF membership with Unicode Consortium|member of the Unicode Consortium]], and the coordination group can collaboratively review the issues discussed and, where appropriate, bring them to the attention of the Unicode Consortium. * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q2891049|Mandailing]] ([[w:btm:|<code>w:btm:</code>]]) [https://phabricator.wikimedia.org/T368038] '''Problems''' * Editors can once again click on links within the visual editor's citation-preview, thanks to a bug fix by the Editing Team. [https://phabricator.wikimedia.org/T368119] '''Future changes''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 2 weeks. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:59, 1 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27038456 --> == Wikipedia translation of the week: 2024-28 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:simple:India naming dispute]]'''<br /> <small>''([[:ur:انڈیا نام کا تنازعہ]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''India naming dispute''' in 1947 refers to the argument over the use of the name India during and after the partition of British Raj, between the countries of Pakistan and the Republic of India. This dispute involved key figures such as Lord Mountbatten, the last Viceroy of British Raj, and Muhammad Ali Jinnah, the leader of the Muslim League and a founder of Pakistan. By 1947, the British Raj was going to be divided into two new nation states – Hindustan and Pakistan. Jinnah was initially convinced that Hindustan would not use the term India, since it lacked indigenous pedigree, etymologically and historically India meant the Indus Valley (modern-Pakistan). He also opposed the use of the name India as it would cause confusion regarding history. The disagreement had significant implications for national identity and international recognition. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 8 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-28 == <section begin="technews-2024-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/28|Translations]] are available. '''Recent changes''' * At the Wikimedia Foundation a new task force was formed to replace the disabled Graph with [[mw:Special:MyLanguage/Extension:Chart/Project|more secure, easy to use, and extensible Chart]]. You can [[mw:Special:MyLanguage/Newsletter:Chart Project|subscribe to the newsletter]] to get notified about new project updates and other news about Chart. * The [[m:Special:MyLanguage/CampaignEvents|CampaignEvents]] extension is now available on Meta-wiki, Igbo Wikipedia, and Swahili Wikipedia, and can be requested on your wiki. This extension helps in managing and making events more visible, giving Event organizers the ability to use tools like the Event registration tool. To learn more about the deployment status and how to request this extension for your wiki, visit the [[m:Special:MyLanguage/CampaignEvents/Deployment_status|CampaignEvents page on Meta-wiki]]. * Editors using the iOS Wikipedia app who have more than 50 edits can now use the [[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits#Add an image|Add an Image]] feature. This feature presents opportunities for small but useful contributions to Wikipedia. * Thank you to [[mw:MediaWiki Product Insights/Contributor retention and growth/Celebration|all of the authors]] who have contributed to MediaWiki Core. As a result of these contributions, the [[mw:MediaWiki Product Insights/Contributor retention and growth|percentage of authors contributing more than 5 patches has increased by 25% since last year]], which helps ensure the sustainability of the platform for the Wikimedia projects. '''Problems''' * A problem with the color of the talkpage tabs always showing as blue, even for non-existent pages which should have been red, affecting the Vector 2022 skin, [[phab:T367982|has been fixed]]. '''Future changes''' * The Trust and Safety Product team wants to introduce [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] with as little disruption to tools and workflows as possible. Volunteer developers, including gadget and user-script maintainers, are kindly asked to update the code of their tools and features to handle temporary accounts. The team has [[mw:Trust and Safety Product/Temporary Accounts/For developers|created documentation]] explaining how to do the update. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers/2024-04 CTA|Learn more]]. '''Tech News survey''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 1 more week. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:32, 8 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27080357 --> == Wikipedia translation of the week: 2024-29 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Adumu]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Maasai 2012 05 31 2782 (7522645058).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Adumu''', is a type of dance that the Maasai people of Kenya and Tanzania practice. Young Maasai warriors generally perform the energetic and acrobatic dance at ceremonial occasions including weddings, religious rites, and other significant cultural events. The Adumu dance is characterized by a sequence of jumps performed by the dancers, who stand in a circle and alternately jump while keeping their bodies as straight and upright as possible. In addition to wearing vividly colored shúkàs (clothes) and beaded jewelry, the dancers are typically clad in traditional Maasai costume. Traditional Maasai songs and chants are also performed during the dance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:15, 15 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-29 == <section begin="technews-2024-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/29|Translations]] are available. '''Tech News survey''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 3 more days. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia developers can now officially continue to use both [[mw:Special:MyLanguage/Gerrit|Gerrit]] and [[mw:Special:MyLanguage/GitLab|GitLab]], due to a June 24 decision by the Wikimedia Foundation to support software development on both platforms. Gerrit and GitLab are both code repositories used by developers to write, review, and deploy the software code that supports the MediaWiki software that the wiki projects are built on, as well as the tools used by editors to create and improve content. This decision will safeguard the productivity of our developers and prevent problems in code review from affecting our users. More details are available in the [[mw:GitLab/Migration status|Migration status]] page. * The Wikimedia Foundation seeks applicants for the [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal|Product and Technology Advisory Council]] (PTAC). This group will bring technical contributors and Wikimedia Foundation together to co-define a more resilient, future-proof technological platform. Council members will evaluate and consult on the movement's product and technical activities, so that we develop multi-generational projects. We are looking for a range of technical contributors across the globe, from a variety of Wikimedia projects. [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal#Joining the PTAC as a technical volunteer|Please apply here by August 10]]. * Editors with rollback user-rights who use the Wikipedia App for Android can use the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Anti Vandalism|Edit Patrol]] features. These features include a new feed of Recent Changes, related links such as Undo and Rollback, and the ability to create and save a personal library of user talk messages to use while patrolling. If your wiki wants to make these features available to users who do not have rollback rights but have reached a certain edit threshold, [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android#Contact us|you can contact the team]]. You can [[diffblog:2024/07/10/ِaddressing-vandalism-with-a-tap-the-journey-of-introducing-the-patrolling-feature-in-the-mobile-app/|read more about this project on Diff blog]]. * Editors who have access to [[m:Special:MyLanguage/The_Wikipedia_Library|The Wikipedia Library]] can once again use non-open access content in SpringerLinks, after the Foundation [[phab:T368865|contacted]] them to restore access. You can read more about [[m:Tech/News/Recently_resolved_community_tasks|this and 21 other community-submitted tasks that were completed last week]]. '''Changes later this week''' * This week, [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-07 deployments|dark mode will be available on a number of Wikipedias]], both desktop and mobile, for logged-in and logged-out users. Interface admins and user script maintainers are encouraged to check gadgets and user scripts in the dark mode, to find any hard-coded colors and fix them. There are some [[mw:Special:MyLanguage/Recommendations for night mode compatibility on Wikimedia wikis|recommendations for dark mode compatibility]] to help. '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Next week, functionaries, volunteers maintaining tools, and software development teams are invited to test the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] feature on testwiki. Temporary accounts is a feature that will help improve privacy on the wikis. No further temporary account deployments are scheduled yet. Please [[mw:Talk:Trust and Safety Product/Temporary Accounts|share your opinions and questions on the project talk page]]. [https://phabricator.wikimedia.org/T348895] * Editors who upload files cross-wiki, or teach other people how to do so, may wish to join a Wikimedia Commons discussion. The Commons community is discussing limiting who can upload files through the cross-wiki upload/Upload dialog feature to users auto-confirmed on Wikimedia Commons. This is due to the large amount of copyright violations uploaded this way. There is a short summary at [[c:Special:MyLanguage/Commons:Cross-wiki upload|Commons:Cross-wiki upload]] and [[c:Commons:Village pump/Proposals#Deactivate cross-wiki uploads for new users|discussion at Commons:Village Pump]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' You can also get other news from the [[m:Special:MyLanguage/Wikimedia Foundation Bulletin|Wikimedia Foundation Bulletin]]. </div><section end="technews-2024-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:31, 16 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27124561 --> == Wikipedia translation of the week: 2024-30 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Rathaus-Glockenspiel]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:2019-11-16, Glockenspiel, Neues Münchner Rathaus, IMG 7463 edit Christoph Braun.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Rathaus-Glockenspiel''' is a large mechanical clock located in Marienplatz Square, in the heart of Munich, Germany. Famous for its life-size characters, the clock twice daily re-enacts scenes from Munich's history. First is the story of the marriage of Duke Wilhelm V to Renata of Lorraine in 1568, followed by the story of the Schäfflerstanz, also known as the coopers' dance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 22 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-30 == <section begin="technews-2024-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/30|Translations]] are available. '''Feature News''' * Stewards can now [[:m:Special:MyLanguage/Global_blocks|globally block]] accounts. Before [[phab:T17294|the change]] only IP addresses and IP ranges could be blocked globally. Global account blocks are useful when the blocked user should not be logged out. [[:m:Special:MyLanguage/Global_locks|Global locks]] (a similar tool logging the user out of their account) are unaffected by this change. The new global account block feature is related to the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] project, which is a new type of user account that replaces IP addresses of unregistered editors that are no longer made public. * Later this week, Wikimedia site users will notice that the Interface of [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs]] (also known as "Pending Changes") is improved and consistent with the rest of the MediaWiki interface and [[mw:Special:MyLanguage/Codex|Wikimedia's design system]]. The FlaggedRevs interface experience on mobile and [[mw:Special:MyLanguage/Skin:MinervaNeue|Minerva skin]] was inconsistent before it was fixed and ported to [[mw:Special:MyLanguage/Codex|Codex]] by the WMF Growth team and some volunteers. [https://phabricator.wikimedia.org/T191156] * Wikimedia site users can now submit account vanishing requests via [[m:Special:GlobalVanishRequest|GlobalVanishRequest]]. This feature is used when a contributor wishes to stop editing forever. It helps you hide your past association and edit to protect your privacy. Once processed, the account will be locked and renamed. [https://phabricator.wikimedia.org/T367329] * Have you tried monitoring and addressing vandalism in Wikipedia using your phone? [https://diff.wikimedia.org/2024/07/10/%d9%90addressing-vandalism-with-a-tap-the-journey-of-introducing-the-patrolling-feature-in-the-mobile-app/ A Diff blog post on Patrolling features in the Mobile App] highlights some of the new capabilities of the feature, including swiping through a feed of recent changes and a personal library of user talk messages for use when patrolling from your phone. * Wikimedia contributors and GLAM (galleries, libraries, archives, and museums) organisations can now learn and measure the impact Wikimedia Commons is having towards creating quality encyclopedic content using the [https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/reference/commons.html Commons Impact Metrics] analytics dashboard. The dashboard offers organizations analytics on things like monthly edits in a category, the most viewed files, and which Wikimedia articles are using Commons images. As a result of these new data dumps, GLAM organisation can more reliably measure their return on investment for programs bringing content into the digital Commons. [https://diff.wikimedia.org/2024/07/19/commons-impact-metrics-now-available-via-data-dumps-and-api/] '''Project Updates''' * Come share your ideas for improving the wikis on the newly reopened [[m:Special:MyLanguage/Community Wishlist|Community Wishlist]]. The Community Wishlist is Wikimedia’s forum for volunteers to share ideas (called wishes) to improve how the wikis work. The new version of the wishlist is always open, works with both wikitext and Visual Editor, and allows wishes in any language. '''Learn more''' * Have you ever wondered how Wikimedia software works across over 300 languages? This is 253 languages more than the Google Chrome interface, and it's no accident. The Language and Product Localization Team at the Wikimedia Foundation supports your work by adapting all the tools and interfaces in the MediaWiki software so that contributors in our movement who translate pages and strings can translate them and have the sites in all languages. Read more about the team and their upcoming work on [https://diff.wikimedia.org/2024/07/17/building-towards-a-robust-multilingual-knowledge-ecosystem-for-the-wikimedia-movement/ Diff]. * How can Wikimedia build innovative and experimental products while maintaining such heavily used websites? A recent [https://diff.wikimedia.org/2024/07/09/on-the-value-of-experimentation/ blog post] by WMF staff Johan Jönsson highlights the work of the [[m:Future Audiences#Objectives and Key Results|WMF Future Audience initiative]], where the goal is not to build polished products but test out new ideas, such as a [[m:Future_Audiences/Experiments: conversational/generative AI|ChatGPT plugin]] and [[m:Future_Audiences/Experiment:Add a Fact|Add a Fact]], to help take Wikimedia into the future. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' You can also get other news from the [[m:Special:MyLanguage/Wikimedia Foundation Bulletin|Wikimedia Foundation Bulletin]]. </div><section end="technews-2024-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:05, 23 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27142915 --> == Wikipedia translation of the week: 2024-31 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Nederlandsche Cocaïnefabriek]]'''<br /> <small>''([[:es:Nederlandsche Cocaïnefabriek]])&#32;([[:nl:Nederlandsche Cocaïnefabriek]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Nederlandsche Cocainefabriek Schinkelstraat Amsterdam architect HH Baanders 1902.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Nederlandsche Cocaïnefabriek''' (Dutch pronunciation: [ˈneːdərlɑntsə koːkaːˈinəfaːˌbrik]; English: Dutch Cocaine Factory) or NCF was an Amsterdam-based company producing cocaine for medical purposes in the 20th century. It imported its raw materials mainly from the Dutch East Indies and sold its products across Europe, making good profits especially in the early years of World War I. The NCF produced morphine, heroin and ephedrine as well. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:44, 29 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27150339 --> == Tech News: 2024-31 == <section begin="technews-2024-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/31|Translations]] are available. '''Feature news''' * Editors using the Visual Editor in languages that use non-Latin characters for numbers, such as Hindi, Manipuri and Eastern Arabic, may notice some changes in the formatting of reference numbers. This is a side effect of preparing a new sub-referencing feature, and will also allow fixing some general numbering issues in Visual Editor. If you notice any related problems on your wiki, please share details at the [[m:Talk:WMDE Technical Wishes/Sub-referencing|project talkpage]]. '''Bugs status''' * Some logged-in editors were briefly unable to edit or load pages last week. [[phab:T370304|These errors]] were mainly due to the addition of new [[mw:Special:MyLanguage/Help:Extension:Linter|linter]] rules which led to caching problems. Fixes have been applied and investigations are continuing. * Editors can use the [[mw:Special:MyLanguage/Trust and Safety Product/IP Info|IP Information tool]] to get information about IP addresses. This tool is available as a Beta Feature in your preferences. The tool was not available for a few days last week, but is now working again. Thank you to Shizhao for filing the bug report. You can read about that, and [[m:Tech/News/Recently resolved community tasks#2024-07-25|28 other community-submitted tasks]] that were resolved last week. '''Project updates''' * There are new features and improvements to Phabricator from the Release Engineering and Collaboration Services teams, and some volunteers, including: the search systems, the new task creation system, the login systems, the translation setup which has resulted in support for more languages (thanks to Pppery), and fixes for many edge-case errors. You can [[phab:phame/post/view/316/iterative_improvements/|read details about these and other improvements in this summary]]. * There is an [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|update on the Charts project]]. The team has decided which visualization library to use, which chart types to start focusing on, and where to store chart definitions. * One new wiki has been created: a {{int:project-localized-name-group-wikivoyage}} in [[d:Q9056|Czech]] ([[voy:cs:|<code>voy:cs:</code>]]) [https://phabricator.wikimedia.org/T370905] '''Learn more''' * There is a [[diffblog:2024/07/26/the-journey-to-open-our-first-data-center-in-south-america/|new Wikimedia Foundation data center]] in São Paulo, Brazil which helps to reduce load times. * There is new [[diffblog:2024/07/22/the-perplexing-process-of-uploading-images-to-wikipedia/|user research]] on problems with the process of uploading images. * Commons Impact Metrics are [[diffblog:2024/07/19/commons-impact-metrics-now-available-via-data-dumps-and-api/|now available]] via data dumps and API. * The latest quarterly [[mw:Technical Community Newsletter/2024/July|Technical Community Newsletter]] is now available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:11, 29 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27164109 --> == Wikipedia translation of the week: 2024-32 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Suffrage drama]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pamphlet from NAWSA for women's suffrage plays, page 1.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Suffrage drama''' (also known as suffrage plays or suffrage theatre) is a form of dramatic literature that emerged during the British women's suffrage movement in the early twentieth century. Suffrage performances lasted approximately from 1907-1914. Many suffrage plays called for a predominant or all female cast. Suffrage plays served to reveal issues behind the suffrage movement. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 5 August 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27150339 --> == Tech News: 2024-32 == <section begin="technews-2024-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/32|Translations]] are available. '''Feature news''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Two new parser functions will be available this week: <code><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic_words#dir|#dir]]<nowiki>}}</nowiki></code> and <code><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic_words#bcp47|#bcp47]]<nowiki>}}</nowiki></code>. These will reduce the need for <code>Template:Dir</code> and <code>Template:BCP47</code> on Commons and allow us to [[phab:T343131|drop 100 million rows]] from the "what links here" database. Editors at any wiki that use these templates, can help by replacing the templates with these new functions. The templates at Commons will be updated during the Hackathon at Wikimania. [https://phabricator.wikimedia.org/T359761][https://phabricator.wikimedia.org/T366623] * Communities can request the activation of the visual editor on entire namespaces where discussions sometimes happen (for instance ''Wikipedia:'' or ''Wikisource:'' namespaces) if they understand the [[mw:Special:MyLanguage/Help:VisualEditor/FAQ#WPNS|known limitations]]. For discussions, users can already use [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]] in these namespaces. * The tracking category "Pages using Timeline" has been renamed to "Pages using the EasyTimeline extension" [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ATimeline-tracking-category&namespace=8 in TranslateWiki]. Wikis that have created the category locally should rename their local creation to match. '''Project updates''' * Editors who help to organize WikiProjects and similar on-wiki collaborations, are invited to share ideas and examples of successful collaborations with the Campaigns and Programs teams. You can fill out [[m:Special:MyLanguage/Campaigns/WikiProjects|a brief survey]] or share your thoughts [[m:Talk:Campaigns/WikiProjects|on the talkpage]]. The teams are particularly looking for details about successful collaborations on non-English wikis. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The new parser is being rolled out on {{int:project-localized-name-group-wikivoyage}} wikis over the next few months. The {{int:project-localized-name-enwikivoyage}} and {{int:project-localized-name-hewikivoyage}} were [[phab:T365367|switched]] to Parsoid last week. For more information, see [[mw:Parsoid/Parser_Unification|Parsoid/Parser Unification]]. '''Learn more''' * There will be more than 200 sessions at Wikimania this week. Here is a summary of some of the [[diffblog:2024/08/05/interested-in-product-and-tech-here-are-some-wikimania-sessions-you-dont-want-to-miss/|key sessions related to the product and technology area]]. * The latest [[m:Special:MyLanguage/Wikimedia Foundation Bulletin/2024/07-02|Wikimedia Foundation Bulletin]] is available. * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2024/July|Language and Internationalization newsletter]] is available. It includes: New design previews for Translatable pages; Updates about MinT for Wiki Readers; the release of Translation dumps; and more. * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/31|Growth newsletter]] is available. * The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/July 2024|MediaWiki Product Insights newsletter]] is available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:44, 5 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27233905 --> == Wikipedia translation of the week: 2024-33 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Karatgurk]]'''<br /> <small>''([[:it:Karatgurk]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In the Australian Aboriginal mythology of the Aboriginal people of south-eastern Australian state of Victoria, the '''Karatgurk''' were seven sisters who represented the constellation known in western astronomy as the Pleiades. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 12 August 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27264174 --> == Tech News: 2024-33 == <section begin="technews-2024-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/33|Translations]] are available. '''Feature news''' * [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]] editors and maintainers can now [[mw:Special:MyLanguage/Extension:AbuseFilter/Actions#Show a CAPTCHA|make a CAPTCHA show if a filter matches an edit]]. This allows communities to quickly respond to spamming by automated bots. [https://phabricator.wikimedia.org/T20110] * [[m:Special:MyLanguage/Stewards|Stewards]] can now specify if global blocks should prevent account creation. Before [[phab:T17273|this change]] by the [[mw:Special:MyLanguage/Trust and Safety Product|Trust and Safety Product]] Team, all global blocks would prevent account creation. This will allow stewards to reduce the unintended side-effects of global blocks on IP addresses. '''Project updates''' * [[wikitech:Help talk:Toolforge/Toolforge standards committee#August_2024_committee_nominations|Nominations are open on Wikitech]] for new members to refresh the [[wikitech:Help:Toolforge/Toolforge standards committee|Toolforge standards committee]]. The committee oversees the Toolforge [[wikitech:Help:Toolforge/Right to fork policy|Right to fork policy]] and [[wikitech:Help:Toolforge/Abandoned tool policy|Abandoned tool policy]] among other duties. Nominations will remain open until at least 2024-08-26. * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q2880037|West Coast Bajau]] ([[w:bdr:|<code>w:bdr:</code>]]) [https://phabricator.wikimedia.org/T371757] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:22, 12 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27253654 --> == Wikipedia translation of the week: 2024-34 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:B1 (classification)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''B1''' is a medical-based Paralympic classification for blind sport. Athletes in this classification are totally or almost totally blind. It is used by a number of blind sports including blind tennis, para-alpine skiing, para-Nordic skiing, blind cricket, blind golf, five-a-side football, goalball and judo. Some other sports, including adaptive rowing, athletics and swimming, have equivalents to this class. The B1 classification was first created by the IBSA in the 1970s, and has largely remained unchanged since despite an effort by the International Paralympic Committee (IPC) to move towards a more functional and evidence-based classification system. Classification is often handled on the international level by the International Blind Sports Federation (IBSA) but it sometimes handled by national sport federations. There are exceptions for sports like athletics and cycling, where classification is handled by their own governing bodies. Equipment utilized by competitors in this class may differ from sport to sport, and may include sighted guides, guide rails, beeping balls and clapsticks. There may be some modifications related to equipment and rules to specifically address needs of competitors in this class to allow them to compete in specific sports. Some sports specifically do not allow a guide, whereas cycling and skiing require one. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 19 August 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27278917 --> == Tech News: 2024-34 == <section begin="technews-2024-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/34|Translations]] are available. '''Feature news''' * Editors who want to re-use references but with different details such as page numbers, will be able to do so by the end of 2024, using a new [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#Sub-referencing in a nutshell|sub-referencing]] feature. You can read more [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|about the project]] and [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#Test|how to test the prototype]]. * Editors using tracking categories to identify which pages use specific extensions may notice that six of the categories have been renamed to make them more easily understood and consistent. These categories are automatically added to pages that use specialized MediaWiki extensions. The affected names are for: [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Aintersection-category&namespace=8 DynamicPageList], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Akartographer-tracking-category&namespace=8 Kartographer], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Aphonos-tracking-category&namespace=8 Phonos], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Arss-tracking-category&namespace=8 RSS], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Ascore-use-category&namespace=8 Score], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Awikihiero-usage-tracking-category&namespace=8 WikiHiero]. Wikis that have created the category locally should rename their local creation to match. Thanks to Pppery for these improvements. [https://phabricator.wikimedia.org/T347324] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Technical volunteers who edit modules and want to get a list of the categories used on a page, can now do so using the <code><bdi lang="zxx" dir="ltr">categories</bdi></code> property of <code><bdi lang="zxx" dir="ltr">[[mediawikiwiki:Special:MyLanguage/Extension:Scribunto/Lua reference manual#Title objects|mw.title objects]]</bdi></code>. This enables wikis to configure workflows such as category-specific edit notices. Thanks to SD001 for these improvements. [https://phabricator.wikimedia.org/T50175][https://phabricator.wikimedia.org/T85372] '''Bugs status''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Your help is needed to check if any pages need to be moved or deleted. A maintenance script was run to clean up unreachable pages (due to Unicode issues or introduction of new namespaces/namespace aliases). The script tried to find appropriate names for the pages (e.g. by following the Unicode changes or by moving pages whose titles on Wikipedia start with <code>Talk:WP:</code> so that their titles start with <code>Wikipedia talk:</code>), but it may have failed for some pages, and moved them to <bdi lang="zxx" dir="ltr">[[Special:PrefixIndex/T195546/]]</bdi> instead. Your community should check if any pages are listed there, and move them to the correct titles, or delete them if they are no longer needed. A full log (including pages for which appropriate names could be found) is available in [[phab:P67388]]. * Editors who volunteer as [[mw:Special:MyLanguage/Help:Growth/Mentorship|mentors]] to newcomers on their wiki are once again able to access lists of potential mentees who they can connect with to offer help and guidance. This functionality was restored thanks to [[phab:T372164|a bug fix]]. Thank you to Mbch331 for filing the bug report. You can read about that, and 18 other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Project updates''' * The application deadline for the [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal|Product & Technology Advisory Council]] (PTAC) has been extended to September 16. Members will help by providing advice to Foundation Product and Technology leadership on short and long term plans, on complex strategic problems, and help to get feedback from more contributors and technical communities. Selected members should expect to spend roughly 5 hours per month for the Council, during the one year pilot. Please consider applying, and spread the word to volunteers you think would make a positive contribution to the committee. '''Learn more''' * The [[m:Special:MyLanguage/Coolest Tool Award#2024 Winners|2024 Coolest Tool Awards]] were awarded at Wikimania, in seven categories. For example, one award went to the ISA Tool, used for adding structured data to files on Commons, which was recently improved during the [[m:Event:Wiki Mentor Africa ISA Hackathon 2024|Wiki Mentor Africa Hackathon]]. You can see video demonstrations of each tool at the awards page. Congratulations to this year's recipients, and thank you to all tool creators and maintainers. * The latest [[m:Special:MyLanguage/Wikimedia Foundation Bulletin/2024/08-01|Wikimedia Foundation Bulletin]] is available, and includes some highlights from Wikimania, an upcoming Language community meeting, and other news from the movement. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W34"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:54, 20 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27307284 --> == Wikipedia translation of the week: 2024-35 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Erzi (village)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Caucasus, Ingushetia, Ингушские боевые и смотровые башни, горы Кавказа.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Erzi''' (Russian: Эрзи; Ingush: Аьрзи, romanized: Ärzi, lit. 'Eagle') is a medieval village (aul) in the Dzheyrakhsky District of Ingushetia. It is part of the rural settlement (administrative center) of Olgeti. The entire territory of the settlement is included in the Dzheyrakh-Assa State Historical-Architectural and Natural Museum-Reserve and is under state protection. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:19, 26 August 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27345183 --> == Tech News: 2024-35 == <section begin="technews-2024-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/35|Translations]] are available. '''Feature news''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Administrators can now test the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] feature on test2wiki. This was done to allow cross-wiki testing of temporary accounts, for when temporary accounts switch between projects. The feature was enabled on testwiki a few weeks ago. No further temporary account deployments are scheduled yet. Temporary Accounts is a project to create a new type of user account that replaces IP addresses of unregistered editors which are no longer made public. Please [[mw:Talk:Trust and Safety Product/Temporary Accounts|share your opinions and questions on the project talk page]]. * Later this week, editors at wikis that use [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs]] (also known as "Pending Changes") may notice that the indicators at the top of articles have changed. This change makes the system more consistent with the rest of the MediaWiki interface. [https://phabricator.wikimedia.org/T191156] '''Bugs status''' * Editors who use the 2010 wikitext editor, and use the Character Insert buttons, will [[phab:T361465|no longer]] experience problems with the buttons adding content into the edit-summary instead of the edit-window. You can read more about that, and 26 other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Project updates''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Please review and vote on [[m:Special:MyLanguage/Community Wishlist/Focus areas|Focus Areas]], which are groups of wishes that share a problem. Focus Areas were created for the newly reopened Community Wishlist, which is now open year-round for submissions. The first batch of focus areas are specific to moderator workflows, around welcoming newcomers, minimizing repetitive tasks, and prioritizing tasks. Once volunteers have reviewed and voted on focus areas, the Foundation will then review and select focus areas for prioritization. * Do you have a project and are willing to provide a three (3) month mentorship for an intern? [[mw:Special:MyLanguage/Outreachy|Outreachy]] is a twice a year program for people to participate in a paid internship that will start in December 2024 and end in early March 2025, and they need mentors and projects to work on. Projects can be focused on coding or non-coding (design, documentation, translation, research). See the Outreachy page for more details, and a list of past projects since 2013. '''Learn more''' * If you're curious about the product and technology improvements made by the Wikimedia Foundation last year, read [[diffblog:2024/08/21/wikimedia-foundation-product-technology-improving-the-user-experience/|this recent highlights summary on Diff]]. * To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Ohrid - Day 2 - Community Configuration - Shaping On-Wiki Functionality Together.webm|Community Configuration - Shaping On-Wiki Functionality Together]] (55 mins) - about the [[mw:Special:MyLanguage/Community Configuration|Community Configuration]] project. ** [[c:File:Wikimania 2024 - Belgrade - Day 1 - Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views.webm|Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views]] (30 mins) - an overview for both technical and non technical audiences, covering some of the challenges and open questions, related to the [[mw:MediaWiki Product Insights|platform evolution, stewardship and developer experiences]] research. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:34, 26 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27341211 --> == Tech News: 2024-36 == <section begin="technews-2024-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/36|Translations]] are available. '''Weekly highlight''' * Editors and volunteer developers interested in data visualisation can now test the new software for charts. Its early version is available on beta Commons and beta Wikipedia. This is an important milestone before making charts available on regular wikis. You can [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|read more about this project update]] and help to test the charts. '''Feature news''' * Editors who use the [[{{#special:Unusedtemplates}}]] page can now filter out pages which are expected to be there permanently, such as sandboxes, test-cases, and templates that are always substituted. Editors can add the new magic word [[mw:Special:MyLanguage/Help:Magic words#EXPECTUNUSEDTEMPLATE|<code dir="ltr"><nowiki>__EXPECTUNUSEDTEMPLATE__</nowiki></code>]] to a template page to hide it from the listing. Thanks to Sophivorus and DannyS712 for these improvements. [https://phabricator.wikimedia.org/T184633] * Editors who use the New Topic tool on discussion pages, will [[phab:T334163|now be reminded]] to add a section header, which should help reduce the quantity of newcomers who add sections without a header. You can read more about that, and {{formatnum:28}} other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. * Last week, some Toolforge tools had occasional connection problems. The cause is still being investigated, but the problems have been resolved for now. [https://phabricator.wikimedia.org/T373243] * Translation administrators at multilingual wikis, when editing multiple translation units, can now easily mark which changes require updates to the translation. This is possible with the [[phab:T298852#10087288|new dropdown menu]]. '''Project updates''' * A new draft text of a policy discussing the use of Wikimedia's APIs [[m:Special:MyLanguage/API Policy Update 2024|has been published on Meta-Wiki]]. The draft text does not reflect a change in policy around the APIs; instead, it is an attempt to codify existing API rules. Comments, questions, and suggestions are welcome on [[m:Talk:API Policy Update 2024|the proposed update’s talk page]] until September 13 or until those discussions have concluded. '''Learn more''' * To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Ohrid - Day 2 - Charts, the successor of Graphs - A secure and extensible tool for data visualization.webm|Charts, the successor of Graphs - A secure and extensible tool for data visualization]] (25 mins) – about the above-mentioned Charts project. ** [[c:File:Wikimania 2024 - Ohrid - Day 3 - State of Language Technology and Onboarding at Wikimedia.webm|State of Language Technology and Onboarding at Wikimedia]] (90 mins) – about some of the language tools that support Wikimedia sites, such as [[mw:Special:MyLanguage/Content translation|Content]]/[[mw:Special:MyLanguage/Content translation/Section translation|Section Translation]], [[mw:Special:MyLanguage/MinT|MinT]], and LanguageConverter; also the current state and future of languages onboarding. [https://phabricator.wikimedia.org/T368772] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:08, 3 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27390268 --> == Wikipedia translation of the week: 2024-37 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cappadocian calendar]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Cappadocian calendar''' was a solar calendar that was derived from the Persian Zoroastrian calendar. It is named after the historic region Cappadocia in present-day Turkey, where it was used. The calendar, which had 12 months of 30 days each and five epagomenal days, originated between 550 and 330 BC, when Cappadocia was part of the Persian Achaemenid Empire. The Cappadocian calendar was identical to the Zoroastrian calendar; this can be seen in its structure, in the Avestan names and in the order of the months. The Cappadocian calendar reflects the Iranian cultural influence in the region. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:42, 9 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27357319 --> == Tech News: 2024-37 == <section begin="technews-2024-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/37|Translations]] are available. '''Feature news''' * Starting this week, the standard [[mw:Special:MyLanguage/Extension:CodeMirror|syntax highlighter]] will receive new colors that make them compatible in dark mode. This is the first of many changes to come as part of a major upgrade to syntax highlighting. You can learn more about what's to come on the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|help page]]. [https://phabricator.wikimedia.org/T365311][https://phabricator.wikimedia.org/T259059] * Editors of wikis using Wikidata will now be notified of only relevant Wikidata changes in their watchlist. This is because the Lua functions <bdi lang="zxx" dir="ltr"><code>entity:getSitelink()</code></bdi> and <bdi lang="zxx" dir="ltr"><code>mw.wikibase.getSitelink(qid)</code></bdi> will have their logic unified for tracking different aspects of sitelinks to reduce junk notifications from [[m:Wikidata For Wikimedia Projects/Projects/Watchlist Wikidata Sitelinks Tracking|inconsistent sitelinks tracking]]. [https://phabricator.wikimedia.org/T295356] '''Project updates''' * Users of all Wikis will have access to Wikimedia sites as read-only for a few minutes on September 25, starting at 15:00 UTC. This is a planned datacenter switchover for maintenance purposes. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T370962] * Contributors of [[phab:T363538#10123348|11 Wikipedias]], including English will have a new <bdi lang="zxx" dir="ltr"><code>MOS</code></bdi> namespace added to their Wikipedias. This improvement ensures that links beginning with <bdi lang="zxx" dir="ltr"><code>MOS:</code></bdi> (usually shortcuts to the [[w:en:Wikipedia:Manual of Style|Manual of Style]]) are not broken by [[w:en:Mooré|Mooré]] Wikipedia (language code <bdi lang="zxx" dir="ltr"><code>mos</code></bdi>). [https://phabricator.wikimedia.org/T363538] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 9 September 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27424457 --> == Tech News: 2024-38 == <section begin="technews-2024-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/38|Translations]] are available. '''Improvements and Maintenance''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Editors interested in templates can help by reading the latest Wishlist focus area, [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template recall and discovery]], and share your feedback on the talkpage. This input helps the Community Tech team to decide the right technical approach to build. Everyone is also encouraged to continue adding [[m:Special:MyLanguage/Community Wishlist|new wishes]]. * The new automated [[{{#special:NamespaceInfo}}]] page helps editors understand which [[mw:Special:MyLanguage/Help:Namespaces|namespaces]] exist on each wiki, and some details about how they are configured. Thanks to DannyS712 for these improvements. [https://phabricator.wikimedia.org/T263513] * [[mw:Special:MyLanguage/Help:Edit check#Reference check|References Check]] is a feature that encourages editors to add a citation when they add a new paragraph to a Wikipedia article. For a short time, the corresponding tag "Edit Check (references) activated" was erroneously being applied to some edits outside of the main namespace. This has been fixed. [https://phabricator.wikimedia.org/T373692] * It is now possible for a wiki community to change the order in which a page’s categories are displayed on their wiki. By default, categories are displayed in the order they appear in the wikitext. Now, wikis with a consensus to do so can [[m:Special:MyLanguage/Requesting wiki configuration changes|request]] a configuration change to display them in alphabetical order. [https://phabricator.wikimedia.org/T373480] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Tool authors can now access ToolsDB's [[wikitech:Portal:Data Services#ToolsDB|public databases]] from both [[m:Special:MyLanguage/Research:Quarry|Quarry]] and [[wikitech:Superset|Superset]]. Those databases have always been accessible to every [[wikitech:Portal:Toolforge|Toolforge]] user, but they are now more broadly accessible, as Quarry can be accessed by anyone with a Wikimedia account. In addition, Quarry's internal database can now be [[m:Special:MyLanguage/Research:Quarry#Querying Quarry's own database|queried from Quarry itself]]. This database contains information about all queries that are being run and starred by users in Quarry. This information was already public through the web interface, but you can now query it using SQL. You can read more about that, and {{formatnum:20}} other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. * Any pages or tools that still use the very old CSS classes <bdi lang="zxx" dir="ltr"><code>mw-message-box</code></bdi> need to be updated. These old classes will be removed next week or soon afterwards. Editors can use a [https://global-search.toolforge.org/?q=mw-message-box&regex=1&namespaces=&title= global-search] to determine what needs to be changed. It is possible to use the newer <bdi lang="zxx" dir="ltr"><code>cdx-message</code></bdi> group of classes as a replacement (see [https://doc.wikimedia.org/codex/latest/components/demos/message.html#css-only-version the relevant Codex documentation], and [https://meta.wikimedia.org/w/index.php?title=Tech/Header&diff=prev&oldid=27449042 an example update]), but using locally defined onwiki classes would be best. [https://phabricator.wikimedia.org/T374499] '''Technical project updates''' * Next week, all Wikimedia wikis will be read-only for a few minutes. This will start on September 25 at [https://zonestamp.toolforge.org/1727276400 15:00 UTC]. This is a planned datacenter switchover for maintenance purposes. [[m:Special:MyLanguage/Tech/Server switch|This maintenance process also targets other services.]] The previous switchover took 3 minutes, and the Site Reliability Engineering teams use many tools to make sure that this essential maintenance work happens as quickly as possible. [https://phabricator.wikimedia.org/T370962] '''Tech in depth''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/August 2024|MediaWiki Product Insights newsletter]] is available. This edition includes details about: research about [[mw:Special:MyLanguage/Manual:Hooks|hook]] handlers to help simplify development, research about performance improvements, work to improve the REST API for end-users, and more. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Auditorium Kyiv - Day 4 - Hackathon Showcase.webm|Hackathon Showcase]] (45 mins) - 19 short presentations by some of the Hackathon participants, describing some of the projects they worked on, such as automated testing of maintenance scripts, a video-cutting command line tool, and interface improvements for various tools. There are [[phab:T369234|more details and links available]] in the Phabricator task. ** [[c:File:Co-Creating a Sustainable Future for the Toolforge Ecosystem.webm|Co-Creating a Sustainable Future for the Toolforge Ecosystem]] (40 mins) - a roundtable discussion for tool-maintainers, users, and supporters of Toolforge about how to make the platform sustainable and how to evaluate the tools available there. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:03, 17 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27460876 --> == Wikipedia translation of the week: 2024-39 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Independence Day (Albania)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Independence Day''' (Albanian: Dita e Pavarësisë) is a public holiday in Albania observed on 28 November. It commemorates the Albanian Declaration of Independence (from the Ottoman Empire), which was ratified by the All-Albanian Congress on 28 November 1912, establishing the state of Albania. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:29, 23 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27456350 --> == Tech News: 2024-39 == <section begin="technews-2024-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/39|Translations]] are available. '''Weekly highlight''' * All wikis will be [[m:Special:MyLanguage/Tech/Server switch|read-only]] for a few minutes on Wednesday September 25 at [https://zonestamp.toolforge.org/1727276400 15:00 UTC]. Reading the wikis will not be interrupted, but editing will be paused. These twice-yearly processes allow WMF's site reliability engineering teams to remain prepared to keep the wikis functioning even in the event of a major interruption to one of our data centers. '''Updates for editors''' [[File:Add alt text from a halfsheet, with the article behind.png|thumb|A screenshot of the interface for the Alt Text suggested-edit feature]] * Editors who use the iOS Wikipedia app in Spanish, Portuguese, French, or Chinese, may see the [[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits project/Alt Text Experiment|Alt Text suggested-edit experiment]] after editing an article, or completing a suggested edit using "[[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits project#Hypothesis 2 Add an Image Suggested Edit|Add an image]]". Alt-text helps people with visual impairments to read Wikipedia articles. The team aims to learn if adding alt-text to images is a task that editors can be successful with. Please share any feedback on [[mw:Talk:Wikimedia Apps/iOS Suggested edits project/Alt Text Experiment|the discussion page]]. * The Codex color palette has been updated with new and revised colors for the MediaWiki user interfaces. The [[mw:Special:MyLanguage/Design System Team/Color/Design documentation#Updates|most noticeable changes]] for editors include updates for: dark mode colors for Links and for quiet Buttons (progressive and destructive), visited Link colors for both light and dark modes, and background colors for system-messages in both light and dark modes. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] It is now possible to include clickable wikilinks and external links inside code blocks. This includes links that are used within <code><nowiki><syntaxhighlight></nowiki></code> tags and on code pages (JavaScript, CSS, Scribunto and Sanitized CSS). Uses of template syntax <code><nowiki>{{…}}</nowiki></code> are also linked to the template page. Thanks to SD0001 for these improvements. [https://phabricator.wikimedia.org/T368166] * Two bugs were fixed in the [[m:Special:MyLanguage/Account vanishing|GlobalVanishRequest]] system by improving the logging and by removing an incorrect placeholder message. [https://phabricator.wikimedia.org/T370595][https://phabricator.wikimedia.org/T372223] * View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] From [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]]: ** The API now enables 5,000 on-demand API requests per month and twice-monthly HTML snapshots freely (gratis and libre). More information on the updates and also improvements to the software development kits (SDK) are explained on [https://enterprise.wikimedia.com/blog/enhanced-free-api/ the project's blog post]. While Wikimedia Enterprise APIs are designed for high-volume commercial reusers, this change enables many more community use-cases to be built on the service too. ** The Snapshot API (html dumps) have added beta Structured Contents endpoints ([https://enterprise.wikimedia.com/blog/structured-contents-snapshot-api/ blog post on that]) as well as released two beta datasets (English and French Wikipedia) from that endpoint to Hugging Face for public use and feedback ([https://enterprise.wikimedia.com/blog/hugging-face-dataset/ blog post on that]). These pre-parsed data sets enable new options for researchers, developers, and data scientists to use and study the content. '''In depth''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The Wikidata Query Service (WDQS) is used to get answers to questions using the Wikidata data set. As Wikidata grows, we had to make a major architectural change so that WDQS could remain performant. As part of the [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS graph split|WDQS Graph Split project]], we have new SPARQL endpoints available for serving the "[https://query-scholarly.wikidata.org scholarly]" and "[https://query-main.wikidata.org main]" subgraphs of Wikidata. The [http://query.wikidata.org query.wikidata.org endpoint] will continue to serve the full Wikidata graph until March 2025. After this date, it will only serve the main graph. For more information, please see [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/September 2024 scaling update|the announcement on Wikidata]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:37, 23 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27493779 --> == Wikipedia translation of the week: 2024-40 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Wildlife of Bahrain]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Birds in Al-Areen Wildlife Park.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The wildlife of the archipelago of Bahrain, is more varied than might be expected of this small group of islands in the Persian Gulf. Apart from a strip of the north and west of the main island, where crops are grown with irrigation, the land is arid. With a very hot dry summer, a mild winter, and brackish groundwater, the plants need adaptations in order to survive. Nevertheless, 196 species of higher plant have been recorded here, as well as about seventeen species of terrestrial mammals, many birds and reptiles, and many migratory birds visit the islands in autumn and spring. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 30 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27456350 --> == Tech News: 2024-40 == <section begin="technews-2024-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/40|Translations]] are available. '''Updates for editors''' * Readers of [[phab:T375401|42 more wikis]] can now use Dark Mode. If the option is not yet available for logged-out users of your wiki, this is likely because many templates do not yet display well in Dark Mode. Please use the [https://night-mode-checker.wmcloud.org/ night-mode-checker tool] if you are interested in helping to reduce the number of issues. The [[mw:Special:MyLanguage/Recommendations for night mode compatibility on Wikimedia wikis|recommendations page]] provides guidance on this. Dark Mode is enabled on additional wikis once per month. * Editors using the 2010 wikitext editor as their default can access features from the 2017 wikitext editor by adding <code dir=ltr>?veaction=editsource</code> to the URL. If you would like to enable the 2017 wikitext editor as your default, it can be set in [[Special:Preferences#mw-input-wpvisualeditor-newwikitext|your preferences]]. [https://phabricator.wikimedia.org/T239796] * For logged-out readers using the Vector 2022 skin, the "donate" link has been moved from a collapsible menu next to the content area into a more prominent top menu, next to "Create an account". This restores the link to the level of prominence it had in the Vector 2010 skin. [[mw:Readers/2024 Reader and Donor Experiences#Donor Experiences (Key Result WE 3.2 and the related hypotheses)|Learn more]] about the changes related to donor experiences. [https://phabricator.wikimedia.org/T373585] * The CampaignEvents extension provides tools for organizers to more easily manage events, communicate with participants, and promote their events on the wikis. The extension has been [[m:Special:MyLanguage/CampaignEvents/Deployment status|enabled]] on Arabic Wikipedia, Igbo Wikipedia, Swahili Wikipedia, and Meta-Wiki. [[w:zh:Wikipedia:互助客栈/其他#引進CampaignEvents擴充功能|Chinese Wikipedia has decided]] to enable the extension, and discussions on the extension are in progress [[w:es:Wikipedia:Votaciones/2024/Sobre la política de Organizadores de Eventos|on Spanish Wikipedia]] and [[d:Wikidata:Project chat#Enabling the CampaignEvents Extention on Wikidata|on Wikidata]]. To learn how to enable the extension on your wiki, you can visit [[m:Special:MyLanguage/CampaignEvents|the CampaignEvents page on Meta-Wiki]]. * View all {{formatnum:22}} community-submitted {{PLURAL:22|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers with an account on Wikitech-wiki should [[wikitech:Wikitech/SUL-migration|check if any action is required]] for their accounts. The wiki is being changed to use the single-user-login (SUL) system, and other configuration changes. This change will help reduce the overall complexity for the weekly software updates across all our wikis. '''In depth''' * The [[m:Special:MyLanguage/Tech/Server switch|server switch]] was completed successfully last week with a read-only time of [[wikitech:Switch Datacenter#Past Switches|only 2 minutes 46 seconds]]. This periodic process makes sure that engineers can switch data centers and keep all of the wikis available for readers, even if there are major technical issues. It also gives engineers a chance to do maintenance and upgrades on systems that normally run 24 hours a day, and often helps to reveal weaknesses in the infrastructure. The process involves dozens of software services and hundreds of hardware servers, and requires multiple teams working together. Work over the past few years has reduced the time from 17 minutes down to 2–3 minutes. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/66ZW7B2MG63AESQVTXDIFQBDBS766JGW/] '''Meetings and events''' * October 4–6: [[m:Special:MyLanguage/WikiIndaba conference 2024|WikiIndaba Conference's Hackathon]] in Johannesburg, South Africa * November 4–6: [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2024|MediaWiki Users and Developers Conference Fall 2024]] in Vienna, Austria '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:21, 30 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27530062 --> == Tech News: 2024-41 == <section begin="technews-2024-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/41|Translations]] are available. '''Weekly highlight''' * Communities can now request installation of [[mw:Special:MyLanguage/Moderator Tools/Automoderator|Automoderator]] on their wiki. Automoderator is an automated anti-vandalism tool that reverts bad edits based on scores from the new "Revert Risk" machine learning model. You can [[mw:Special:MyLanguage/Extension:AutoModerator/Deploying|read details about the necessary steps]] for installation and configuration. [https://phabricator.wikimedia.org/T336934] '''Updates for editors''' * Translators in wikis where [[mw:Special:MyLanguage/Content translation/Section translation#Try the tool|the mobile experience of Content Translation is available]], can now customize their articles suggestion list from 41 filtering options when using the tool. This topic-based article suggestion feature makes it easy for translators to self-discover relevant articles based on their area of interest and translate them. You can [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions try it with your mobile device]. [https://phabricator.wikimedia.org/T368422] * View all {{formatnum:12}} community-submitted {{PLURAL:12|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * It is now possible for <bdi lang="zxx" dir="ltr"><code><nowiki><syntaxhighlight></nowiki></code></bdi> code blocks to offer readers a "Copy" button if the <bdi lang="zxx" dir="ltr"><code><nowiki>copy=1</nowiki></code></bdi> attribute is [[mw:Special:MyLanguage/Extension:SyntaxHighlight#copy|set on the tag]]. Thanks to SD0001 for these improvements. [https://phabricator.wikimedia.org/T40932] * Customized copyright footer messages on all wikis will be updated. The new versions will use wikitext markup instead of requiring editing raw HTML. [https://phabricator.wikimedia.org/T375789] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Later this month, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] will be rolled out on several pilot wikis. The final list of the wikis will be published in the second half of the month. If you maintain any tools, bots, or gadgets on [[phab:T376499|these 11 wikis]], and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|Guidance on how to update the code is available]]. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Rate limiting has been enabled for the code review tools [[Wikitech:Gerrit|Gerrit]] and [[Wikitech:GitLab|GitLab]] to address ongoing issues caused by malicious traffic and scraping. Clients that open too many concurrent connections will be restricted for a few minutes. This rate limiting is managed through [[Wikitech:nftables|nftables]] firewall rules. For more details, see Wikitech's pages on [[Wikitech:Firewall#Throttling with nftables|Firewall]], [[Wikitech:GitLab/Abuse and rate limiting|GitLab limits]] and [[Wikitech:Gerrit/Operations#Throttling IPs|Gerrit operations]]. * Five new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q49224|Komering]] ([[w:kge:|<code>w:kge:</code>]]) [https://phabricator.wikimedia.org/T374813] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q36096|Mooré]] ([[m:mos:|<code>m:mos:</code>]]) [https://phabricator.wikimedia.org/T374641] ** a {{int:project-localized-name-group-wiktionary}} in [[d:Q36213|Madurese]] ([[wikt:mad:|<code>wikt:mad:</code>]]) [https://phabricator.wikimedia.org/T374968] ** a {{int:project-localized-name-group-wikiquote}} in [[d:Q2501174|Gorontalo]] ([[q:gor:|<code>q:gor:</code>]]) [https://phabricator.wikimedia.org/T375088] ** a {{int:project-localized-name-group-wikinews}} in [[d:Q56482|Shan]] ([[n:shn:|<code>n:shn:</code>]]) [https://phabricator.wikimedia.org/T375430] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:43, 7 October 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27557422 --> == Wikipedia translation of the week: 2024-42 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Little Danes experiment]]'''<br /> <small>''([[:fa:آزمایش دانمارکی‌های کوچک]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Children play at a Danish Red Cross-run orphanage in Greenland.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''little Danes experiment''' was a 1951 Danish operation where 22 Greenlandic Inuit children were sent to Danish foster families in an attempt to re-educate them as "little Danes". While the children were all supposed to be orphans, most were not. Six children were adopted while in Denmark, and sixteen returned to Greenland, only to be placed in Danish-speaking orphanages and never live with their families again. Half of the children experienced mental health disturbances, and half of them died in young adulthood. The government of Denmark officially apologised in 2020, after several years of demands from Greenlandic officials. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:16, 14 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27572997 --> == Tech News: 2024-42 == <section begin="technews-2024-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/42|Translations]] are available. '''Updates for editors''' * The Structured Discussion extension (also known as Flow) is starting to be removed. This extension is unmaintained and causes issues. It will be replaced by [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]], which is used on any regular talk page. [[mw:Special:MyLanguage/Structured Discussions/Deprecation#Deprecation timeline|A first set of wikis]] are being contacted. These wikis are invited to stop using Flow, and to move all Flow boards to sub-pages, as archives. At these wikis, a script will move all Flow pages that aren't a sub-page to a sub-page automatically, starting on 22 October 2024. On 28 October 2024, all Flow boards at these wikis will be set in read-only mode. [https://www.mediawiki.org/wiki/Structured_Discussions/Deprecation][https://phabricator.wikimedia.org/T370722] * WMF's Search Platform team is working on making it easier for readers to perform text searches in their language. A [[phab:T332342|change last week]] on over 30 languages makes it easier to find words with accents and other diacritics. This applies to both full-text search and to types of advanced search such as the <bdi lang="en" dir="ltr">''hastemplate''</bdi> and <bdi lang="en" dir="ltr">''incategory''</bdi> keywords. More technical details (including a few other minor search upgrades) are available. [https://www.mediawiki.org/wiki/User:TJones_%28WMF%29/Notes/Language_Analyzer_Harmonization_Notes#ASCII-folding/ICU-folding_%28T332342%29] * View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[mw:Special:MyLanguage/Help:Edit check|EditCheck]] was installed at Russian Wikipedia, and fixes were made for some missing user interface styles. '''Updates for technical contributors''' * Editors who use the Toolforge tool [[toolforge:copyvios|Earwig's Copyright Violation Detector]] will now be required to log in with their Wikimedia account before running checks using the "search engine" option. This change is needed to help prevent external bots from misusing the system. Thanks to Chlod for these improvements. [https://en.wikipedia.org/wiki/Wikipedia_talk:New_pages_patrol/Reviewers#Authentication_is_now_required_for_search_engine_checks_on_Earwig's_Copyvio_Tool] * [[m:Special:MyLanguage/Phabricator|Phabricator]] users can create tickets and add comments on existing tickets via Email again. [[mw:Special:MyLanguage/Phabricator/Help#Using email|Sending email to Phabricator]] has been fixed. [https://phabricator.wikimedia.org/T356077] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Some HTML elements in the interface are now wrapped with a <code><nowiki><bdi></nowiki></code> element, to make our HTML output more aligned with Web standards. More changes like this will be coming in future weeks. This change might break some tools that rely on the previous HTML structure of the interface. Note that relying on the HTML structure of the interface is [[mw:Special:MyLanguage/Stable interface policy/Frontend#What is not stable?|not recommended]] and might break at any time. [https://phabricator.wikimedia.org/T375975] '''In depth''' * The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/September 2024|MediaWiki Product Insights newsletter]] is available. This edition includes: updates on Wikimedia's authentication system, research to simplify feature development in the MediaWiki platform, updates on Parser Unification and MathML rollout, and more. * The latest quarterly [[mw:Technical Community Newsletter/2024/October|Technical Community Newsletter]] is now available. This edition include: research about improving topic suggestions related to countries, improvements to PHPUnit tests, and more. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:22, 14 October 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27597254 --> == Wikipedia translation of the week: 2024-43 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kharayeb]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Muharram 1Oth-Ashouraa 2007 in Kharayeb - panoramio.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Kharayeb''' (Arabic: الخرايب) is a historic town in the Sidon District in the South Governorate, Lebanon. The town is 77 km (48 mi) south of Beirut, and stands at an average altitude of 190 m (620 ft) above sea level. The town boasts a rich historical legacy, with archaeological excavations revealing a complex settlement history spanning from Prehistory to the Ottoman period. Notably, Kharayeb's origins can be traced back to the Persian period (539–330 BC), when it played a pivotal role in the region's agricultural and economic landscape, culminating in the construction of its Phoenician temple around the 6th century BC. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:38, 21 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27572997 --> == Tech News: 2024-43 == <section begin="technews-2024-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/43|Translations]] are available. '''Weekly highlight''' * The Mobile Apps team has released an [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Navigation Refresh#Phase 1: Creating a user Profile Menu (T373714)|update]] to the iOS app's navigation, and it is now available in the latest App store version. The team added a new Profile menu that allows for easy access to editor features like Notifications and Watchlist from the Article view, and brings the "Donate" button into a more accessible place for users who are reading an article. This is the first phase of a larger planned [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Navigation Refresh|navigation refresh]] to help the iOS app transition from a primarily reader-focused app, to an app that fully supports reading and editing. The Wikimedia Foundation has added more editing features and support for on-wiki communication based on volunteer requests in recent years. [[File:IOS App Navigation refresh first phase 05.png|thumb|iOS Wikipedia App's profile menu and contents]] '''Updates for editors''' * Wikipedia readers can now download a browser extension to experiment with some early ideas on potential features that recommend articles for further reading, automatically summarize articles, and improve search functionality. For more details and to stay updated, check out the Web team's [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments|Content Discovery Experiments page]] and [[mw:Special:MyLanguage/Newsletter:Web team's projects|subscribe to their newsletter]]. * Later this month, logged-out editors of [[phab:T376499|these 12 wikis]] will start to have [[mw:Special:Mylanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] created. The list may slightly change - some wikis may be removed but none will be added. Temporary account is a new [[mw:Special:MyLanguage/User account types|type of user account]]. It enhances the logged-out editors' privacy and makes it easier for community members to communicate with them. If you maintain any tools, bots, or gadgets on these 12 wikis, and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|Guidance on how to update the code is available]]. Read more about the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|deployment plan across all wikis]]. * View all {{formatnum:33}} community-submitted {{PLURAL:33|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[w:nr:Main Page|South Ndebele]], [[w:rsk:Главни бок|Pannonian Rusyn]], [[w:ann:Uwu|Obolo]], [[w:iba:Lambar Keterubah|Iban]] and [[w:tdd:ᥞᥨᥝᥴ ᥘᥣᥲ ᥖᥥᥰ|Tai Nüa]] Wikipedia languages were created last week. [https://www.wikidata.org/wiki/Q36785][https://www.wikidata.org/wiki/Q35660][https://www.wikidata.org/wiki/Q36614][https://www.wikidata.org/wiki/Q33424][https://www.wikidata.org/wiki/Q36556] * It is now possible to create functions on Wikifunctions using Wikidata lexemes, through the new [[f:Z6005|Wikidata lexeme type]] launched last week. When you go to one of these functions, the user interface provides a lexeme selector that helps you pick a lexeme from Wikidata that matches the word you type. After hitting run, your selected lexeme is retrieved from Wikidata, transformed into a Wikidata lexeme type, and passed into the selected function. Read more about this in [[f:Special:MyLanguage/Wikifunctions:Status updates/2024-10-17#Function of the Week: select representation from lexeme|the latest Wikifunctions newsletter]]. '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Users of the Wikimedia sites can now format dates more easily in different languages with the new <code dir="ltr">{{[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##timef|#timef]]:…}}</code> parser function. For example, <code dir="ltr"><nowiki>{{#timef:now|date|en}}</nowiki></code> will show as "<bdi lang="en" dir="ltr">{{#timef:now|date|en}}</bdi>". Previously, <code dir="ltr"><nowiki>{{#time:…}}</nowiki></code> could be used to format dates, but this required knowledge of the order of the time and date components and their intervening punctuation. <code dir="ltr">#timef</code> (or <code dir="ltr">#timefl</code> for local time) provides access to the standard date formats that MediaWiki uses in its user interface. This may help to simplify some templates on multi-lingual wikis like Commons and Meta. [https://phabricator.wikimedia.org/T223772][https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:ParserFunctions##timef] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Commons and Meta users can now efficiently [[mw:Special:MyLanguage/Help:Magic words#Localization|retrieve the user's language]] using <code dir="ltr"><nowiki>{{USERLANGUAGE}}</nowiki></code> instead of using <code dir="ltr"><nowiki>{{int:lang}}</nowiki></code>. [https://phabricator.wikimedia.org/T4085] * The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Tech Advisory Council]] (PTAC) now has its pilot members with representation across Africa, Asia, Europe, North America and South America. They will work to address the [[Special:MyLanguage/Movement Strategy/Initiatives/Technology Council|Movement Strategy's Technology Council]] initiative of having a co-defined and more resilient technological platform. [https://meta.wikimedia.org/wiki/Movement_Strategy/Initiatives/Technology_Council] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/32|Growth newsletter]] is available. It includes: an upcoming Newcomer Homepage Community Updates module, new Community Configuration options, and details on new projects. * The Wikimedia Foundation is [[mw:Special:MyLanguage/Wikimedia Security Team#CNA Partnership|now an official partner of the CVE program]], which is an international effort to catalog publicly disclosed cybersecurity vulnerabilities. This partnership will allow the Security Team to instantly publish [[w:en:Common Vulnerabilities and Exposures|common vulnerabilities and exposures]] (CVE) records that are affecting MediaWiki core, extensions, and skins, along with any other code the Foundation is a steward of. * The [[m:Special:MyLanguage/Community Wishlist|Community Wishlist]] is now [[m:Community Wishlist/Updates#October 16, 2024: Conversations Made Easier: Machine-Translated Wishes Are Here!|testing machine translations]] for Wishlist content. Volunteers can now read machine-translated versions of wishes and dive into discussions even before translators arrive to translate content. '''Meetings and events''' * 24 October - Wiki Education Speaker Series Webinar - [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/N4XTB4G55BUY3M3PNGUAKQWJ7A4UOPAK/ Open Source Tech: Building the Wiki Education Dashboard], featuring Wikimedia interns and a Web developer in the panel. * 20–22 December 2024 - [[m:Special:MyLanguage/Indic Wikimedia Hackathon Bhubaneswar 2024|Indic Wikimedia Hackathon Bhubaneswar 2024]] in Odisha, India. A hackathon for community members, including developers, designers and content editors, to build technical solutions that improve contributors' experiences. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:53, 21 October 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27634672 --> == Wikipedia translation of the week: 2024-44 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Christmas horror]]'''<br /> <small>''([[:es:Terror navideño]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Christmascarol1843 -- 169.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Christmas horror''' is a fiction genre and film genre that incorporates horror elements into a seasonal setting. It is popular in multiple countries. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 28 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27647428 --> == Tech News: 2024-44 == <section begin="technews-2024-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/44|Translations]] are available. '''Updates for editors''' * Later in November, the Charts extension will be deployed to the test wikis in order to help identify and fix any issue. A security review is underway to then enable deployment to pilot wikis for broader testing. You can read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates#October 2024: Working towards production deployment|the October project update]] and see the [https://en.wikipedia.beta.wmflabs.org/wiki/Charts latest documentation and examples on Beta Wikipedia]. * View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[w:en:PediaPress|Pediapress.com]], an external service that creates books from Wikipedia, can now use [[mw:Special:MyLanguage/Wikimedia Maps|Wikimedia Maps]] to include existing pre-rendered infobox map images in their printed books on Wikipedia. [https://phabricator.wikimedia.org/T375761] '''Updates for technical contributors''' * Wikis can use [[:mw:Special:MyLanguage/Extension:GuidedTour|the Guided Tour extension]] to help newcomers understand how to edit. The Guided Tours extension now works with [[mw:Special:MyLanguage/Manual:Dark mode|dark mode]]. Guided Tour maintainers can check their tours to see that nothing looks odd. They can also set <code>emitTransitionOnStep</code> to <code>true</code> to fix an old bug. They can use the new flag <code>allowAutomaticBack</code> to avoid back-buttons they don't want. [https://phabricator.wikimedia.org/T73927#10241528] * Administrators in the Wikimedia projects who use the [[mw:Special:MyLanguage/Help:Extension:Nuke|Nuke Extension]] will notice that mass deletions done with this tool have the "Nuke" tag. This change will make reviewing and analyzing deletions performed with the tool easier. [https://phabricator.wikimedia.org/T366068] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:57, 28 October 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27668811 --> == Wikipedia translation of the week: 2024-45 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Placenta cake]]'''<br /> <small>''([[:simple:Placenta cake]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Bucharest, Greek pie-maker, 1880.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Placenta cake''' is a dish from ancient Greece and Rome consisting of many dough layers interspersed with a mixture of cheese and honey and flavored with bay leaves, baked and then covered in honey. The dessert is mentioned in classical texts such as the Greek poems of Archestratos and Antiphanes, as well as the De agri cultura of Cato the Elder. It is often seen as the predecessor of baklava and börek. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:16, 4 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27647428 --> == Tech News: 2024-45 == <section begin="technews-2024-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/45|Translations]] are available. '''Updates for editors''' * Stewards can now make [[m:Special:MyLanguage/Global blocks|global account blocks]] cause global [[mw:Special:MyLanguage/Autoblock|autoblocks]]. This will assist stewards in preventing abuse from users who have been globally blocked. This includes preventing globally blocked temporary accounts from exiting their session or switching browsers to make subsequent edits for 24 hours. Previously, temporary accounts could exit their current session or switch browsers to continue editing. This is an anti-abuse tool improvement for the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] project. You can read more about the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|progress on key features for temporary accounts]]. [https://phabricator.wikimedia.org/T368949] * Wikis that have the [[m:Special:MyLanguage/CampaignEvents/Deployment status|CampaignEvents extension enabled]] can now use the [[m:Special:MyLanguage/Campaigns/Foundation Product Team/Event list#October 29, 2024: Collaboration List launched|Collaboration List]] feature. This list provides a new, easy way for contributors to learn about WikiProjects on their wikis. Thanks to the Campaign team for this work that is part of [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2024-2025/Product %26 Technology OKRs#WE KRs|the 2024/25 annual plan]]. If you are interested in bringing the CampaignEvents extension to your wiki, you can [[m:Special:MyLanguage/CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|follow these steps]] or you can reach out to User:Udehb-WMF for help. * The text color for red links will be slightly changed later this week to improve their contrast in light mode. [https://phabricator.wikimedia.org/T370446] * View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, on multilingual wikis, users [[phab:T216368|can now]] hide translations from the WhatLinksHere special page. '''Updates for technical contributors''' * XML [[m:Special:MyLanguage/Data dumps|data dumps]] have been temporarily paused whilst a bug is investigated. [https://lists.wikimedia.org/hyperkitty/list/xmldatadumps-l@lists.wikimedia.org/message/BXWJDPO5QI2QMBCY7HO36ELDCRO6HRM4/] '''In depth''' * Temporary Accounts have been deployed to six wikis; thanks to the Trust and Safety Product team for [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|this work]], you can read about [[phab:T340001|the deployment plans]]. Beginning next week, Temporary Accounts will also be enabled on [[phab:T378336|seven other projects]]. If you are active on these wikis and need help migrating your tools, please reach out to [[m:User:Udehb-WMF|User:Udehb-WMF]] for assistance. * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2024/October|Language and Internationalization newsletter]] is available. It includes: New languages supported in translatewiki or in MediaWiki; New keyboard input methods for some languages; details about recent and upcoming meetings, and more. '''Meetings and events''' * [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2024|MediaWiki Users and Developers Conference Fall 2024]] is happening in Vienna, Austria and online from 4 to 6 November 2024. The conference will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:51, 4 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27693917 --> == Wikipedia translation of the week: 2024-46 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Trisomy 16]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Chromosome 16.svg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Trisomy 16''' is a chromosomal abnormality in which there are 3 copies of chromosome 16 rather than two. It is the most common trisomy leading to miscarriage and the second most common chromosomal cause of it, closely following X-chromosome monosomy. About 6% of miscarriages have trisomy 16. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:09, 11 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27708700 --> == Tech News: 2024-46 == <section begin="technews-2024-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/46|Translations]] are available. '''Updates for editors''' * On wikis with the [[mw:Special:MyLanguage/Help:Extension:Translate|Translate extension]] enabled, users will notice that the FuzzyBot will now automatically create translated versions of categories used on translated pages. [https://phabricator.wikimedia.org/T285463] * View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the submitted task to use the [[mw:Special:MyLanguage/Extension:SecurePoll|SecurePoll extension]] for English Wikipedia's special [[w:en:Wikipedia:Administrator elections|administrator election]] was resolved on time. [https://phabricator.wikimedia.org/T371454] '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] In <code dir="ltr">[[mw:MediaWiki_1.44/wmf.2|1.44.0-wmf-2]]</code>, the logic of Wikibase function <code>getAllStatements</code> changed to behave like <code>getBestStatements</code>. Invoking the function now returns a copy of values which are immutable. [https://phabricator.wikimedia.org/T270851] * [https://en.wikipedia.org/api/rest_v1/ Wikimedia REST API] users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. The API will be rerouting some page content endpoints from RESTbase to the newer [[mw:Special:MyLanguage/API:REST API|MediaWiki REST API]] endpoints. The [[phab:T374683|impacted endpoints]] include getting page/revision metadata and rendered HTML content. These changes will be available on testwiki later this week, with other projects to follow. This change should not affect existing functionality, but active users of the impacted endpoints should verify behavior on testwiki, and raise any concerns on the related [[phab:T374683|Phabricator ticket]]. '''In depth''' * Admins and users of the Wikimedia projects [[mw:Special:MyLanguage/Moderator_Tools/Automoderator#Usage|where Automoderator is enabled]] can now monitor and evaluate important metrics related to Automoderator's actions. [https://superset.wmcloud.org/superset/dashboard/unified-automoderator-activity-dashboard/ This Superset dashboard] calculates and aggregates metrics about Automoderator's behaviour on the projects in which it is deployed. Thanks to the Moderator Tools team for this Dashboard; you can visit [[mw:Special:MyLanguage/Moderator Tools/Automoderator/Unified Activity Dashboard|the documentation page]] for more information about this work. [https://phabricator.wikimedia.org/T369488] '''Meetings and events''' * 21 November 2024 ([[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 8:00 UTC|8:00 UTC]] & [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 16:00 UTC|16:00 UTC]]) - [[c:Commons:WMF support for Commons/Commons community calls|Community call]] with Wikimedia Commons volunteers and stakeholders to help prioritize support efforts for 2025-2026 Fiscal Year. The theme of this call is how content should be organised on Wikimedia Commons. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:08, 12 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27732268 --> == Wikipedia translation of the week: 2024-47 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Boana platanera]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Rana platanera - Boana platanera.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Boana platanera''''', commonly known as the banana tree dwelling frog, is a species of tree frog in the family Hylidae. It is distributed within Venezuela, Colombia, Panama, and Trinidad and Tobago. Boana platanera was described in 2021, and individuals of the species were previously classified as Boana crepitans or Boana xerophylla. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:53, 18 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27735014 --> == Tech News: 2024-47 == <section begin="technews-2024-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/47|Translations]] are available. '''Updates for editors''' * Users of Wikimedia sites will now be warned when they create a [[mw:Special:MyLanguage/Help:Redirects|redirect]] to a page that doesn't exist. This will reduce the number of broken redirects to red links in our projects. [https://phabricator.wikimedia.org/T326057] * View all {{formatnum:42}} community-submitted {{PLURAL:42|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[mw:Special:MyLanguage/Manual:Pywikibot/Overview|Pywikibot]], which automates work on MediaWiki sites, was upgraded to 9.5.0 on Toolforge. [https://phabricator.wikimedia.org/T378676] '''Updates for technical contributors''' * On wikis that use the [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs extension]], pages created or moved by users with the appropriate permissions are marked as flagged automatically. This feature has not been working recently, and changes fixing it should be deployed this week. Thanks to Daniel and Wargo for working on this. [https://phabricator.wikimedia.org/T379218][https://phabricator.wikimedia.org/T368380] '''In depth''' * There is a new [https://diff.wikimedia.org/2024/11/05/say-hi-to-temporary-accounts-easier-collaboration-with-logged-out-editors-with-better-privacy-protection Diff post] about Temporary Accounts, available in more than 15 languages. Read it to learn about what Temporary Accounts are, their impact on different groups of users, and the plan to introduce the change on all wikis. '''Meetings and events''' * Technical volunteers can now register for the [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]], which will take place in Istanbul, Turkey. [https://pretix.eu/wikimedia/hackathon2025/ Application for travel and accommodation scholarships] is open from '''November 12 to December 10 2024'''. The registration for the event will close in mid-April 2025. The Wikimedia Hackathon is an annual gathering that unites the global technical community to collaborate on existing projects and explore new ideas. * Join the [[C:Special:MyLanguage/Commons:WMF%20support%20for%20Commons/Commons%20community%20calls|Wikimedia Commons community calls]] this week to help prioritize support for Commons which will be planned for 2025–2026. The theme will be how content should be organised on Wikimedia Commons. This is an opportunity for volunteers who work on different things to come together and talk about what matters for the future of the project. The calls will take place '''November 21, 2024, [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 8:00 UTC|8:00 UTC]] and [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 16:00 UTC|16:00 UTC]]'''. * A [[mw:Special:MyLanguage/Wikimedia_Language_and_Product_Localization/Community meetings#29 November 2024|Language community meeting]] will take place '''November 29, 16:00 UTC''' to discuss updates and technical problem-solving. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:01, 19 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27806858 --> == Wikipedia translation of the week: 2024-48 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Wang Su-bok]]'''<br /> <small>''([[:fa:وانگ سو بوک]])&#32;([[:ko:왕수복]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Wang Su-bok''' was a singer from North Korea, who was the most popular singer in Japanese-occupied Korea in 1935. She was credited as a ground-breaking female artist, whose work led the way for the modern K-pop phenomenon. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 25 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-48 == <section begin="technews-2024-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/48|Translations]] are available. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new version of the standard wikitext editor-mode [[mw:Special:MyLanguage/Extension:CodeMirror|syntax highlighter]] will be available as a [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] later this week. This brings many new features and bug fixes, including right-to-left support, [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Template folding|template folding]], [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Autocompletion|autocompletion]], and an improved search panel. You can learn more on the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|help page]]. * The 2010 wikitext editor now supports common keyboard shortcuts such <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>B</code></bdi> for bold and <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>I</code></bdi> for italics. A full [[mw:Help:Extension:WikiEditor#Keyboard shortcuts|list of all six shortcuts]] is available. Thanks to SD0001 for this improvement. [https://phabricator.wikimedia.org/T62928] * Starting November 28, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: <bdi>bswiki</bdi>{{int:comma-separator/en}}<bdi>elwiki</bdi>{{int:comma-separator/en}}<bdi>euwiki</bdi>{{int:comma-separator/en}}<bdi>fawiki</bdi>{{int:comma-separator/en}}<bdi>fiwiki</bdi>{{int:comma-separator/en}}<bdi>frwikiquote</bdi>{{int:comma-separator/en}}<bdi>frwikisource</bdi>{{int:comma-separator/en}}<bdi>frwikiversity</bdi>{{int:comma-separator/en}}<bdi>frwikivoyage</bdi>{{int:comma-separator/en}}<bdi>idwiki</bdi>{{int:comma-separator/en}}<bdi>lvwiki</bdi>{{int:comma-separator/en}}<bdi>plwiki</bdi>{{int:comma-separator/en}}<bdi>ptwiki</bdi>{{int:comma-separator/en}}<bdi>urwiki</bdi>{{int:comma-separator/en}}<bdi>viwikisource</bdi>{{int:comma-separator/en}}<bdi>zhwikisource</bdi>. This is done as part of [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|StructuredDiscussions deprecation work]]. If you need any assistance to archive your page in advance, please contact [[m:User:Trizek (WMF)|Trizek (WMF)]]. * View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a user creating a new AbuseFilter can now only set the filter to "protected" [[phab:T377765|if it includes a protected variable]]. '''Updates for technical contributors''' * The [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]], which can be used in JavaScript, CSS, JSON, and Lua pages, [[phab:T377663|now offers]] live autocompletion. Thanks to SD0001 for this improvement. The feature can be temporarily disabled on a page by pressing <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>,</code></bdi> and un-selecting "<bdi lang="en" dir="ltr">Live Autocompletion</bdi>". * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Tool-maintainers who use the Graphite system for tracking metrics, need to migrate to the newer Prometheus system. They can check [https://grafana.wikimedia.org/d/K6DEOo5Ik/grafana-graphite-datasource-utilization?orgId=1 this dashboard] and the list in the Description of the [[phab:T350592|task T350592]] to see if their tools are listed, and they should claim metrics and dashboards connected to their tools. They can then disable or migrate all existing metrics by following the instructions in the task. The Graphite service will become read-only in April. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/KLUV4IOLRYXPQFWD6WKKJUHMWE77BMSZ/] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The [[mw:Special:MyLanguage/NewPP parser report|New PreProcessor parser performance report]] has been fixed to give an accurate count for the number of Wikibase entities accessed. It had previously been resetting after 400 entities. [https://phabricator.wikimedia.org/T279069] '''Meetings and events''' * A [[mw:Special:MyLanguage/Wikimedia_Language_and_Product_Localization/Community meetings#29 November 2024|Language community meeting]] will take place November 29 at [https://zonestamp.toolforge.org/1732896000 16:00 UTC]. There will be presentations on topics like developing language keyboards, the creation of the Mooré Wikipedia, the language support track at [[m:Wiki Indaba|Wiki Indaba]], and a report from the Wayuunaiki community on their experiences with the Incubator and as a new community over the last 3 years. This meeting will be in English and will also have Spanish interpretation. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:42, 25 November 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27847039 --> == Wikipedia translation of the week: 2024-49 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Storm Filomena]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Spain’s chilly blanket ESA22415247.jpeg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Storm Filomena''' was an extratropical cyclone in early January 2021 that was most notable for bringing unusually heavy snowfall to parts of Spain, with Madrid recording its heaviest snowfall in over a century, and with Portugal being hit less severely. The eighth named storm of the 2020–21 European windstorm season, Filomena formed over the Atlantic Ocean close to the Canary Islands on 7 January, subsequently taking a slow track north-eastwards towards the Iberian Peninsula and then eastwards across the Mediterranean Sea. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:48, 2 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-49 == <section begin="technews-2024-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/49|Translations]] are available. '''Updates for editors''' * Two new parser functions were added this week. The <code dir="ltr"><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic words#interwikilink|#interwikilink]]<nowiki>}}</nowiki></code> function adds an [[mw:Special:MyLanguage/Help:Links#Interwiki links|interwiki link]] and the <code dir="ltr"><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic words#interlanguagelink|#interlanguagelink]]<nowiki>}}</nowiki></code> function adds an [[mw:Special:MyLanguage/Help:Links#Interlanguage links|interlanguage link]]. These parser functions are useful on wikis where namespaces conflict with interwiki prefixes. For example, links beginning with <bdi lang="zxx" dir="ltr"><code>MOS:</code></bdi> on English Wikipedia [[phab:T363538|conflict with the <code>mos</code> language code prefix of Mooré Wikipedia]]. * Starting this week, Wikimedia wikis no longer support connections using old RSA-based HTTPS certificates, specifically rsa-2048. This change is to improve security for all users. Some older, unsupported browser or smartphone devices will be unable to connect; Instead, they will display a connectivity error. See the [[wikitech:HTTPS/Browser_Recommendations|HTTPS Browser Recommendations page]] for more-detailed information. All modern operating systems and browsers are always able to reach Wikimedia projects. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/CTYEHVNSXUD3NFAAMG3BLZVTVQWJXJAH/] * Starting December 16, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: <bdi>arwiki</bdi>{{int:comma-separator/en}}<bdi>cawiki</bdi>{{int:comma-separator/en}}<bdi>frwiki</bdi>{{int:comma-separator/en}}<bdi>mediawikiwiki</bdi>{{int:comma-separator/en}}<bdi>orwiki</bdi>{{int:comma-separator/en}}<bdi>wawiki</bdi>{{int:comma-separator/en}}<bdi>wawiktionary</bdi>{{int:comma-separator/en}}<bdi>wikidatawiki</bdi>{{int:comma-separator/en}}<bdi>zhwiki</bdi>. This is done as part of [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|StructuredDiscussions deprecation work]]. If you need any assistance to archive your page in advance, please contact [[m:User:Trizek (WMF)|Trizek (WMF)]]. [https://phabricator.wikimedia.org/T380910] * This month the Chart extension was deployed to production and is now available on Commons and Testwiki. With the security review complete, pilot wiki deployment is expected to start in the first week of December. You can see a working version [[testwiki:Charts|on Testwiki]] and read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|the November project update]] for more details. * View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug with the "Download as PDF" system was fixed. [https://phabricator.wikimedia.org/T376438] '''Updates for technical contributors''' * In late February, temporary accounts will be rolled out on at least 10 large wikis. This deployment will have a significant effect on the community-maintained code. This is about Toolforge tools, bots, gadgets, and user scripts that use IP address data or that are available for logged-out users. The Trust and Safety Product team wants to identify this code, monitor it, and assist in updating it ahead of the deployment to minimize disruption to workflows. The team asks technical editors and volunteer developers to help identify such tools by adding them to [[mw:Trust and Safety Product/Temporary Accounts/For developers/Impacted tools|this list]]. In addition, review the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|updated documentation]] to learn how to adjust the tools. Join the discussions on the [[mw:Talk:Trust and Safety Product/Temporary Accounts|project talk page]] or in the [[discord:channels/221049808784326656/1227616742340034722|dedicated thread]] on the [[w:Wikipedia:Discord|Wikimedia Community Discord server (in English)]] for support and to share feedback. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:23, 2 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27873992 --> == Wikipedia translation of the week: 2024-50 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Syrian literature]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Poem about Baybars page 1 from Hakawati book.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Syrian literature''' is modern fiction written or orally performed in Arabic by writers from Syria since the independence of the Syrian Arab Republic in 1946. It is part of the historically and geographically wider Arabic literature. The modern states of Syria, Lebanon, Jordan, Israel as well as the Palestinian autonomous areas only came into being in the mid-20th century. Therefore, Syrian literature has since been referred to by literary scholarship as the national literature of the Syrian Arab Republic, as well as the works created in Arabic by Syrian writers in the diaspora. This literature has been influenced by the country's political history, the literature of other Arabic-speaking countries and, especially in its early days, by French literature. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 9 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-50 == <section begin="technews-2024-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/50|Translations]] are available. '''Weekly highlight''' * Technical documentation contributors can find updated resources, and new ways to connect with each other and the Wikimedia Technical Documentation Team, at the [[mw:Special:MyLanguage/Documentation|Documentation hub]] on MediaWiki.org. This page links to: resources for writing and improving documentation, a new <bdi lang="zxx" dir="ltr">#wikimedia-techdocs</bdi> IRC channel on libera.chat, a listing of past and upcoming documentation events, and ways to request a documentation consultation or review. If you have any feedback or ideas for improvements to the documentation ecosystem, please [[mw:Wikimedia Technical Documentation Team#Contact us|contact the Technical Documentation Team]]. '''Updates for editors''' [[File:Edit Check on Desktop.png|thumb|Layout change for the Edit Check feature]] * Later this week, [[mw:Special:MyLanguage/Edit check|Edit Check]] will be relocated to a sidebar on desktop. Edit check is the feature for new editors to help them follow policies and guidelines. This layout change creates space to present people with [[mw:Edit check#1 November 2024|new Checks]] that appear ''while'' they are typing. The [[mw:Special:MyLanguage/Edit check#Reference Check A/B Test|initial results]] show newcomers encountering Edit Check are 2.2 times more likely to publish a new content edit that includes a reference and is not reverted. * The Chart extension, which enables editors to create data visualizations, was successfully made available on MediaWiki.org and three pilot wikis (Italian, Swedish, and Hebrew Wikipedias). You can see a working examples [[testwiki:Charts|on Testwiki]] and read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|the November project update]] for more details. * Translators in wikis where the [[mw:Special:MyLanguage/Content translation/Section translation#Try the tool|mobile experience of Content Translation is available]], can now discover articles in Wikiproject campaigns of their interest from the "[https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=specialcx&filter-type=automatic&filter-id=collections&active-list=suggestions&from=es&to=en All collection]" category in the articles suggestion feature. Wikiproject Campaign organizers can use this feature, to help translators to discover articles of interest, by adding the <code dir=ltr><nowiki><page-collection> </page-collection></nowiki></code> tag to their campaign article list page on Meta-wiki. This will make those articles discoverable in the Content Translation tool. For more detailed information on how to use the tool and tag, please refer to [[mw:Special:MyLanguage/Translation suggestions: Topic-based & Community-defined lists/How to use the features|the step-by-step guide]]. [https://phabricator.wikimedia.org/T378958] * The [[mw:Special:MyLanguage/Extension:Nuke|Nuke]] feature, which enables administrators to mass delete pages, now has a [[phab:T376379#10310998|multiselect filter for namespace selection]]. This enables users to select multiple specific namespaces, instead of only one or all, when fetching pages for deletion. * The Nuke feature also now [[phab:T364225#10371365|provides links]] to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions. Thanks to Chlod and the Moderator Tools team for both of these improvements. [https://phabricator.wikimedia.org/T364225#10371365] * The Editing Team is working on making it easier to populate citations from archive.org using the [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|Citoid]] tool, the auto-filled citation generator. They are asking communities to add two parameters preemptively, <code dir=ltr>archiveUrl</code> and <code dir=ltr>archiveDate</code>, within the TemplateData for each citation template using Citoid. You can see an [https://en.wikipedia.org/w/index.php?title=Template%3ACite_web%2Fdoc&diff=1261320172&oldid=1260788022 example of a change in a template], and a [https://global-search.toolforge.org/?namespaces=10&q=%5C%22citoid%5C%22%3A%20%5C%7B&regex=1&title= list of all relevant templates]. [https://phabricator.wikimedia.org/T374831] * One new wiki has been created: a {{int:project-localized-name-group-wikivoyage}} in [[d:Q9240|Indonesian]] ([[voy:id:|<code>voy:id:</code>]]) [https://phabricator.wikimedia.org/T380726] * Last week, all wikis had problems serving pages to logged-in users and some logged-out users for 30–45 minutes. This was caused by a database problem, and investigation is ongoing. [https://www.wikimediastatus.net/incidents/3g2ckc7bp6l9] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug in the [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add Link]] feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases. [https://phabricator.wikimedia.org/T380455][https://phabricator.wikimedia.org/T380329] '''Updates for technical contributors''' * [[mw:Special:MyLanguage/Codex|Codex]], the design system for Wikimedia, now has an early-stage [[gitiles:design/codex-php|implementation in PHP]]. It is available for general use in MediaWiki extensions and Toolforge apps through [https://packagist.org/packages/wikimedia/codex Composer], with use in MediaWiki core coming soon. More information is available in [[wmdoc:design-codex-php/main/index.html|the documentation]]. Thanks to Doğu for the inspiration and many contributions to the library. [https://phabricator.wikimedia.org/T379662] * [https://en.wikipedia.org/api/rest_v1/ Wikimedia REST API] users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. On December 4, the MediaWiki Interfaces team began rerouting page/revision metadata and rendered HTML content endpoints on [[testwiki:|testwiki]] from RESTbase to comparable MediaWiki REST API endpoints. The team encourages active users of these endpoints to verify their tool's behavior on testwiki and raise any concerns on the related [[phab:T374683|Phabricator ticket]] before the end of the year, as they intend to roll out the same change across all Wikimedia projects in early January. These changes are part of the work to replace the outdated [[mw:RESTBase/deprecation|RESTBase]] system. * The [https://wikimediafoundation.limesurvey.net/986172 2024 Developer Satisfaction Survey] is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 3 January 2025, and has an associated [[foundation:Legal:Developer Satisfaction Survey 2024 Privacy Statement|privacy statement]]. * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Meetings and events''' * The next meeting in the series of [[c:Commons:WMF support for Commons/Commons community calls|Wikimedia Foundation discussions with the Wikimedia Commons community]] will take place on [[m:Event:Commons community discussion - 12 December 2024 08:00 UTC|December 12 at 8:00 UTC]] and [[m:Event:Commons community discussion - 12_December 2024 16:00 UTC|at 16:00 UTC]]. The topic of this call is new media and new contributors. Contributors from all wikis are welcome to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:16, 9 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27919424 --> == Wikipedia translation of the week: 2024-51 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Mars ocean theory]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:AncientMars.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Mars ocean theory''' states that nearly a third of the surface of Mars was covered by an ocean of liquid water early in the planet's geologic history. This primordial ocean, dubbed Paleo-Ocean or Oceanus Borealis (/oʊˈsiːənəs ˌbɒriˈælɪs/ oh-SEE-ə-nəs BORR-ee-AL-iss), would have filled the basin Vastitas Borealis in the northern hemisphere, a region that lies 4–5 km (2.5–3 miles) below the mean planetary elevation, at a time period of approximately 4.1–3.8 billion years ago. Evidence for this ocean includes geographic features resembling ancient shorelines, and the chemical properties of the Martian soil and atmosphere <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:44, 16 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27933909 --> == Tech News: 2024-51 == <section begin="technews-2024-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/51|Translations]] are available. '''Weekly highlight''' * Interested in improving event management on your home wiki? The [[m:Special:MyLanguage/CampaignEvents|CampaignEvents extension]] offers organizers features like event registration management, event/wikiproject promotion, finding potential participants, and more - all directly on-wiki. If you are an organizer or think your community would benefit from this extension, start a discussion to enable it on your wiki today. To learn more about how to enable this extension on your wiki, visit the [[m:CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|deployment status page]]. '''Updates for editors''' * Users of the iOS Wikipedia App in Italy and Mexico on the Italian, Spanish, and English Wikipedias, can see a [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Personalized Wikipedia Year in Review|personalized Year in Review]] with insights based on their reading and editing history. * Users of the Android Wikipedia App in Sub-Saharan Africa and South Asia can see the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Rabbit Holes|Rabbit Holes]] feature. This feature shows a suggested search term in the Search bar based on the current article being viewed, and a suggested reading list generated from the user’s last two visited articles. * The [[m:Special:MyLanguage/Global reminder bot|global reminder bot]] is now active and running on nearly 800 wikis. This service reminds most users holding temporary rights when they are about to expire, so that they can renew should they want to. See [[m:Global reminder bot/Technical details|the technical details page]] for more information. * The next issue of Tech News will be sent out on 13 January 2025 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was [[phab:T374988|fixed]] in the Android Wikipedia App which had caused translatable SVG images to show the wrong language when they were tapped. '''Updates for technical contributors''' * There is no new MediaWiki version next week. The next deployments will start on 14 January. [https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar/2025] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:25, 16 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27942374 --> == Wikipedia translation of the week: 2024-52 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2023 Slovenia floods]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Sava v Tacnu 4. avgusta ob 16h.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> In August 2023, major floods occurred in large part of Slovenia and neighbouring areas of Austria and Croatia due to heavy rain. Amongst others, the level of rivers Sava, Mur and Drava was exceptionally high. Several settlements and transport links in Slovene Littoral, Upper Carniola and Slovenian Carinthia were flooded. Due to the amount of rain, the streams in Idrija, Cerkno and Škofja Loka Hills overflowed. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:55, 23 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27933909 --> == Wikipedia translation of the week: 2025-01 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Uganda Railways Corporation]]'''<br /> <small>''([[:de:Schienenverkehr in Uganda]])&#32;([[:no:Uganda Railways Corporation]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:9620 mit Güterzug.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Uganda Railways Corporation''' (URC) is the parastatal railway of Uganda. It was formed after the breakup of the East African Railways Corporation (EARC) in 1977 when it took over the Ugandan part of the East African railways. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:37, 30 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28019313 --> == Wikipedia translation of the week: 2025-02 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Internment of Japanese Canadians]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Japanese road camp.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> From 1942 to 1949, Canada forcibly relocated and incarcerated over 22,000 Japanese Canadians—comprising over 90% of the total Japanese Canadian population—from British Columbia in the name of "national security". The majority were Canadian citizens by birth and were targeted based on their ancestry. This decision followed the events of the Japanese Empire's war in the Pacific against the Western Allies, such as the invasion of Hong Kong, the attack on Pearl Harbor in Hawaii, and the Fall of Singapore which led to the Canadian declaration of war on Japan during World War II. Similar to the actions taken against Japanese Americans in neighbouring United States, this forced relocation subjected many Japanese Canadians to government-enforced curfews and interrogations, job and property losses, and forced repatriation to Japan <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:56, 6 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28070038 --> == Wikipedia translation of the week: 2025-03 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Christmas seals]]'''<br /> <small>''([[:no:Julemerke]])&#32;([[:ru:Рождественская виньетка]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:1915 US Christmas Seal.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Christmas seals''' are adhesive labels that are similar in appearance to postage stamps that are sold then affixed to mail during the Christmas season to raise funds and awareness for charitable programs. Christmas seals have become particularly associated with lung diseases such as tuberculosis, and with child welfare in general. They were first issued in Denmark beginning in 1904, with Sweden and Iceland following with issues that same year. Thereafter the use of Christmas seals proved to be popular and spread quickly around the world, with 130 countries producing their own issues. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 13 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28086717 --> == Tech News: 2025-03 == <section begin="technews-2025-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/03|Translations]] are available. '''Weekly highlight''' * The Single User Login system is being updated over the next few months. This is the system which allows users to fill out the login form on one Wikimedia site and get logged in on all others at the same time. It needs to be updated because of the ways that browsers are increasingly restricting cross-domain cookies. To accommodate these restrictions, login and account creation pages will move to a central domain, but it will still appear to the user as if they are on the originating wiki. The updated code will be enabled this week for users on test wikis. This change is planned to roll out to all users during February and March. See [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3#Deployment|the SUL3 project page]] for more details and a timeline. '''Updates for editors''' * On wikis with [[mw:Special:MyLanguage/Extension:PageAssessments|PageAssessments]] installed, you can now [[mw:Special:MyLanguage/Extension:PageAssessments#Search|filter search results]] to pages in a given WikiProject by using the <code dir=ltr>inproject:</code> keyword. (These wikis: {{int:project-localized-name-arwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwikivoyage/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-huwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zhwiki/en}}) [https://phabricator.wikimedia.org/T378868] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q34129|Tigre]] ([[w:tig:|<code>w:tig:</code>]]) [https://phabricator.wikimedia.org/T381377] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:35}} community-submitted {{PLURAL:35|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a bug with updating a user's edit-count after making a rollback edit, which is now fixed. [https://phabricator.wikimedia.org/T382592] '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. Starting the week of January 13, we will begin rerouting [[phab:T374683|some page content endpoints]] from RESTbase to the newer MediaWiki REST API endpoints for all wiki projects. This change was previously available on testwiki and should not affect existing functionality, but active users of the impacted endpoints may raise issues directly to the [[phab:project/view/6931/|MediaWiki Interfaces Team]] in Phabricator if they arise. * Toolforge tool maintainers can now share their feedback on Toolforge UI, an initiative to provide a web platform that allows creating and managing Toolforge tools through a graphic interface, in addition to existing command-line workflows. This project aims to streamline active maintainers’ tasks, as well as make registration and deployment processes more accessible for new tool creators. The initiative is still at a very early stage, and the Cloud Services team is in the process of collecting feedback from the Toolforge community to help shape the solution to their needs. [[wikitech:Wikimedia Cloud Services team/EnhancementProposals/Toolforge UI|Read more and share your thoughts about Toolforge UI]]. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] For tool and library developers who use the OAuth system: The identity endpoint used for [[mw:Special:MyLanguage/OAuth/For Developers#Identifying the user|OAuth 1]] and [[mw:Special:MyLanguage/OAuth/For Developers#Identifying the user 2|OAuth 2]] returned a JSON object with an integer in its <code>sub</code> field, which was incorrect (the field must always be a string). This has been fixed; the fix will be deployed to Wikimedia wikis on the week of January 13. [https://phabricator.wikimedia.org/T382139] * Many wikis currently use [[:mw:Parsoid/Parser Unification/Cite CSS|Cite CSS]] to render custom footnote markers in Parsoid output. Starting January 20 these rules will be disabled, but the developers ask you to ''not'' clean up your <bdi lang="en" dir="ltr">[[MediaWiki:Common.css]]</bdi> until February 20 to avoid issues during the migration. Your wikis might experience some small changes to footnote markers in Visual Editor and when using experimental Parsoid read mode, but if there are changes these are expected to bring the rendering in line with the legacy parser output. [https://phabricator.wikimedia.org/T370027] '''Meetings and events''' * The next meeting in the series of [[c:Special:MyLanguage/Commons:WMF support for Commons/Commons community calls|Wikimedia Foundation Community Conversations with the Wikimedia Commons community]] will take place on [[m:Special:MyLanguage/Event:Commons community discussion - 15 January 2025 08:00 UTC|January 15 at 8:00 UTC]] and [[m:Special:MyLanguage/Event:Commons community discussion - 15 January 2025 16:00 UTC|at 16:00 UTC]]. The topic of this call is defining the priorities in tool investment for Commons. Contributors from all wikis, especially users who are maintaining tools for Commons, are welcome to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:42, 14 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28048614 --> == Wikipedia translation of the week: 2025-04 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2010 Nagorno-Karabakh clashes]]'''<br /> <small>''([[:it:Scontri del Nagorno Karabakh del 2010]])&#32;([[:tr:2010 Dağlık Karabağ çatışmaları]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''2010 Nahorno karabakh war''' were a series of exchanges of gunfire that took place on February 18 on the line of contact dividing Azerbaijani and the Karabakh Armenian military forces. Azerbaijan accused the Armenian forces of firing on the Azerbaijani positions near Tap Qaraqoyunlu, Qızıloba, Qapanlı, Yusifcanlı and Cavahirli villages, as well as in uplands of Agdam Rayon with small arms fire including snipers. As a result, three Azerbaijani soldiers were killed and one wounded. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:20, 20 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28099770 --> == Tech News: 2025-04 == <section begin="technews-2025-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/04|Translations]] are available. '''Updates for editors''' * Administrators can mass-delete multiple pages created by a user or IP address using [[mw:Special:MyLanguage/Extension:Nuke|Extension:Nuke]]. It previously only allowed deletion of pages created in the last 30 days. It can now delete pages from the last 90 days, provided it is targeting a specific user or IP address. [https://phabricator.wikimedia.org/T380846] * On [[phab:P72148|wikis that use]] the [[mw:Special:MyLanguage/Help:Patrolled edits|Patrolled edits]] feature, when the rollback feature is used to revert an unpatrolled page revision, that revision will now be marked as "manually patrolled" instead of "autopatrolled", which is more accurate. Some editors that use [[mw:Special:MyLanguage/Help:New filters for edit review/Filtering|filters]] on Recent Changes may need to update their filter settings. [https://phabricator.wikimedia.org/T302140] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Visual Editor's "Insert link" feature did not always suggest existing pages properly when an editor started typing, which has now been [[phab:T383497|fixed]]. '''Updates for technical contributors''' * The Structured Discussion extension (also known as Flow) is being progressively removed from the wikis. This extension is unmaintained and causes issues. It will be replaced by [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]], which is used on any regular talk page. [[mw:Special:MyLanguage/Structured Discussions/Deprecation#Deprecation timeline|The last group of wikis]] ({{int:project-localized-name-cawikiquote/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiwikimedia/en}}{{int:comma-separator/en}}{{int:project-localized-name-gomwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kabwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwikibooks/en}}{{int:comma-separator/en}}{{int:project-localized-name-sewikimedia/en}}) will soon be contacted. If you have questions about this process, please ping [[m:User:Trizek (WMF)|Trizek (WMF)]] at your wiki. [https://phabricator.wikimedia.org/T380912] * The latest quarterly [[mw:Technical_Community_Newsletter/2025/January|Technical Community Newsletter]] is now available. This edition includes: updates about services from the Data Platform Engineering teams, information about Codex from the Design System team, and more. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:37, 21 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28129769 --> == Wikipedia translation of the week: 2025-05 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Jinnah's birthday]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Yorkstatue.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Jinnah's Birthday''', officially Quaid-e-Azam Day and sometimes known as Quaid Day, is a public holiday in Pakistan observed annually on 25 December to celebrate the birthday of the founder of Pakistan, Muhammad Ali Jinnah, known as Quaid-i-Azam ("Great Leader"). A major holiday, commemorations for Jinnah began during his lifetime in 1942, and have continued ever since. The event is primarily observed by the government and the citizens of the country where the national flag is hoisted at major architectural structures such as private and public buildings, particularly at the top of Quaid-e-Azam House in Karachi. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:30, 27 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28156501 --> == Tech News: 2025-05 == <section begin="technews-2025-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/05|Translations]] are available. '''Weekly highlight''' * Patrollers and admins - what information or context about edits or users could help you to make patroller or admin decisions more quickly or easily? The Wikimedia Foundation wants to hear from you to help guide its upcoming annual plan. Please consider sharing your thoughts on this and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|13 other questions]] to shape the technical direction for next year. '''Updates for editors''' * iOS Wikipedia App users worldwide can now access a [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Personalized Wikipedia Year in Review/How your data is used|personalized Year in Review]] feature, which provides insights based on their reading and editing history on Wikipedia. This project is part of a broader effort to help welcome new readers as they discover and interact with encyclopedic content. * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Edit patrollers now have a new feature available that can highlight potentially problematic new pages. When a page is created with the same title as a page which was previously deleted, a tag ('Recreated') will now be added, which users can filter for in [[{{#special:RecentChanges}}]] and [[{{#special:NewPages}}]]. [https://phabricator.wikimedia.org/T56145] * Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (a [[mw:Special:MyLanguage/Help:Redirects#Double redirects|double redirect]]). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement. [https://phabricator.wikimedia.org/T326056] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia wikis allow [[w:en:WebAuthn|WebAuthn]]-based second factor checks (such as hardware tokens) during login, but the feature is [[m:Community Wishlist Survey 2023/Miscellaneous/Fix security key (WebAuthn) support|fragile]] and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout of [[mw:MediaWiki Platform Team/SUL3|SUL3]] (single user login version 3). Existing keys are unaffected. [https://phabricator.wikimedia.org/T378402] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * For developers that use the [[wikitech:Data Platform/Data Lake/Edits/MediaWiki history dumps|MediaWiki History dumps]]: The Data Platform Engineering team has added a couple of new fields to these dumps, to support the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] initiative. If you maintain software that reads those dumps, please review your code and the updated documentation, since the order of the fields in the row will change. There will also be one field rename: in the <bdi lang="zxx" dir="ltr"><code>mediawiki_user_history</code></bdi> dump, the <bdi lang="zxx" dir="ltr"><code>anonymous</code></bdi> field will be renamed to <bdi lang="zxx" dir="ltr"><code>is_anonymous</code></bdi>. The changes will take effect with the next release of the dumps in February. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/LKMFDS62TXGDN6L56F4ABXYLN7CSCQDI/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:15, 27 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28149374 --> == Wikipedia translation of the week: 2025-06 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:French conquest of Corsica]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Bataille de Ponte Novu.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''French conquest of Corsica''' was a successful expedition by French forces of the Kingdom of France under Comte de Vaux, against Corsican forces under Pasquale Paoli of the Corsican Republic. The expedition was launched in May 1768, in the aftermath of the Seven Years' War. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:20, 3 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28200320 --> == Tech News: 2025-06 == <section begin="technews-2025-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/06|Translations]] are available. '''Updates for editors''' * Editors who use the "Special characters" editing-toolbar menu can now see the 32 special characters you have used most recently, across editing sessions on that wiki. This change should help make it easier to find the characters you use most often. The feature is in both the 2010 wikitext editor and VisualEditor. [https://phabricator.wikimedia.org/T110722] * Editors using the 2010 wikitext editor can now create sublists with correct indentation by selecting the line(s) you want to indent and then clicking the toolbar buttons.[https://phabricator.wikimedia.org/T380438] You can now also insert <code><nowiki><code></nowiki></code> tags using a new toolbar button.[https://phabricator.wikimedia.org/T383010] Thanks to user stjn for these improvements. * Help is needed to ensure the [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|citation generator]] works properly on each wiki. ** (1) Administrators should update the local versions of the page <code dir=ltr>MediaWiki:Citoid-template-type-map.json</code> to include entries for <code dir=ltr>preprint</code>, <code dir=ltr>standard</code>, and <code dir=ltr>dataset</code>; Here are example diffs to replicate [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&diff=1189164774&oldid=1165783565 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&diff=1270832208&oldid=1270828390 for 'standard' and 'dataset']. ** (2.1) If the citoid map in the citation template used for these types of references is missing, [[mediawikiwiki:Citoid/Enabling Citoid on your wiki#Step 2.a: Create a 'citoid' maps value for each citation template|one will need to be added]]. (2.2) If the citoid map does exist, the TemplateData will need to be updated to include new field names. Here are example updates [https://en.wikipedia.org/w/index.php?title=Template%3ACitation%2Fdoc&diff=1270829051&oldid=1262470053 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=Template%3ACitation%2Fdoc&diff=1270831369&oldid=1270829480 for 'standard' and 'dataset']. The new fields that may need to be supported are <code dir=ltr>archiveID</code>, <code dir=ltr>identifier</code>, <code dir=ltr>repository</code>, <code dir=ltr>organization</code>, <code dir=ltr>repositoryLocation</code>, <code dir=ltr>committee</code>, and <code dir=ltr>versionNumber</code>. [https://phabricator.wikimedia.org/T383666] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q15637215|Central Kanuri]] ([[w:knc:|<code>w:knc:</code>]]) [https://phabricator.wikimedia.org/T385181] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[mediawikiwiki:Special:MyLanguage/Help:Extension:Wikisource/Wikimedia OCR|OCR (optical character recognition) tool]] used for Wikisource now supports a new language, Church Slavonic. [https://phabricator.wikimedia.org/T384782] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:09, 4 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28203495 --> == Wikipedia translation of the week: 2025-07 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Assassination of Spencer Perceval]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:PercevalShooting.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> On 11 May 1812, at about 5:15 pm, Spencer Perceval, the prime minister of the United Kingdom of Great Britain and Ireland, was shot dead in the lobby of the House of Commons by John Bellingham, a Liverpool merchant with a grievance against the government. Bellingham was detained; four days after the murder, he was tried, convicted and sentenced to death. He was hanged at Newgate Prison on 18 May, one week after the assassination and one month before the start of the War of 1812. Perceval remains the sole British prime minister to have been assassinated. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 10 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28200320 --> == Tech News: 2025-07 == <section begin="technews-2025-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/07|Translations]] are available. '''Weekly highlight''' * The Product and Technology Advisory Council (PTAC) has published [[m:Special:MyLanguage/Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback|a draft of their recommendations]] for the Wikimedia Foundation's Product and Technology department. They have recommended focusing on [[m:Special:MyLanguage/Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback/Mobile experiences|mobile experiences]], particularly contributions. They request community [[m:Talk:Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback|feedback at the talk page]] by 21 February. '''Updates for editors''' * The "Special pages" portlet link will be moved from the "Toolbox" into the "Navigation" section of the main menu's sidebar by default. This change is because the Toolbox is intended for tools relating to the current page, not tools relating to the site, so the link will be more logically and consistently located. To modify this behavior and update CSS styling, administrators can follow the instructions at [[phab:T385346|T385346]]. [https://phabricator.wikimedia.org/T333211] * As part of this year's work around improving the ways readers discover content on the wikis, the Web team will be running an experiment with a small number of readers that displays some suggestions for related or interesting articles within the search bar. Please check out [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments#Experiment 1: Display article recommendations in more prominent locations, search|the project page]] for more information. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Template editors who use TemplateStyles can now customize output for users with specific accessibility needs by using accessibility related media queries (<code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion prefers-reduced-motion]</code>, <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-transparency prefers-reduced-transparency]</code>, <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-contrast prefers-contrast]</code>, and <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/forced-colors forced-colors]</code>). Thanks to user Bawolff for these improvements. [https://phabricator.wikimedia.org/T384175] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:22}} community-submitted {{PLURAL:22|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the global blocks log will now be shown directly on the {{#special:CentralAuth}} page, similarly to global locks, to simplify the workflows for stewards. [https://phabricator.wikimedia.org/T377024] '''Updates for technical contributors''' * Wikidata [[d:Special:MyLanguage/Help:Default values for labels and aliases|now supports a special language as a "default for all languages"]] for labels and aliases. This is to avoid excessive duplication of the same information across many languages. If your Wikidata queries use labels, you may need to update them as some existing labels are getting removed. [https://phabricator.wikimedia.org/T312511] * The function <code dir="ltr">getDescription</code> was invoked on every Wiki page read and accounts for ~2.5% of a page's total load time. The calculated value will now be cached, reducing load on Wikimedia servers. [https://phabricator.wikimedia.org/T383660] * As part of the RESTBase deprecation [[mw:RESTBase/deprecation|effort]], the <code dir="ltr">/page/related</code> endpoint has been blocked as of February 6, 2025, and will be removed soon. This timeline was chosen to align with the deprecation schedules for older Android and iOS versions. The stable alternative is the "<code dir="ltr">morelike</code>" action API in MediaWiki, and [[gerrit:c/mediawiki/services/mobileapps/+/982154/13/pagelib/src/transform/FooterReadMore.js|a migration example]] is available. The MediaWiki Interfaces team [[phab:T376297|can be contacted]] for any questions. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/GFC2IJO7L4BWO3YTM7C5HF4MCCBE2RJ2/] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/January|Language and Internationalization newsletter]] is available. It includes: Updates about the "Contribute" menu; details on some of the newest language editions of Wikipedia; details on new languages supported by the MediaWiki interface; updates on the Community-defined lists feature; and more. * The latest [[mw:Extension:Chart/Project/Updates#January 2025: Better visibility into charts and tabular data usage|Chart Project newsletter]] is available. It includes updates on the progress towards bringing better visibility into global charts usage and support for categorizing pages in the Data namespace on Commons. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:12, 11 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28231022 --> == Wikipedia translation of the week: 2025-08 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2010 Malagasy constitutional referendum]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A constitutional referendum was held in Madagascar on 17 November 2010, in which voters approved a proposal for the state's fourth Constitution. The Malagasy people were asked to answer "Yes" or "No" to the proposed new constitution, which was considered to help consolidate Andry Rajoelina's grip on power. At the time of the referendum, Rajoelina headed the governing Highest Transitional Authority (HAT), an interim junta established following the military-backed coup d'état against then President Marc Ravalomanana in March 2009. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:21, 17 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28245290 --> == Tech News: 2025-08 == <section begin="technews-2025-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/08|Translations]] are available. '''Weekly highlight''' * Communities using growth tools can now showcase one event on the <code>{{#special:Homepage}}</code> for newcomers. This feature will help newcomers to be informed about editing activities they can participate in. Administrators can create a new event to showcase at <code>{{#special:CommunityConfiguration}}</code>. To learn more about this feature, please read [[diffblog:2025/02/12/community-updates-module-connecting-newcomers-to-your-initiatives/|the Diff post]], have a look [[mw:Special:MyLanguage/Help:Growth/Tools/Community updates module|at the documentation]], or contact [[mw:Talk:Growth|the Growth team]]. '''Updates for editors''' [[File:Page Frame Features on desktop.png|thumb|Highlighted talk pages improvements]] * Starting next week, talk pages at these wikis – {{int:project-localized-name-eswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jawiki/en}} – will get [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|a new design]]. This change was extensively tested as a Beta feature and is the last step of [[mw:Special:MyLanguage/Talk pages project/Feature summary|talk pages improvements]]. [https://phabricator.wikimedia.org/T379102] * You can now navigate to view a redirect page directly from its action pages, such as the history page. Previously, you were forced to first go to the redirect target. This change should help editors who work with redirects a lot. Thanks to user stjn for this improvement. [https://phabricator.wikimedia.org/T5324] * When a Cite reference is reused many times, wikis currently show either numbers like "1.23" or localized alphabetic markers like "a b c" in the reference list. Previously, if there were so many reuses that the alphabetic markers were all used, [[MediaWiki:Cite error references no backlink label|an error message]] was displayed. As part of the work to [[phab:T383036|modernize Cite customization]], these errors will no longer be shown and instead the backlinks will fall back to showing numeric markers like "1.23" once the alphabetic markers are all used. * The log entries for each change to an editor's user-groups are now clearer by specifying exactly what has changed, instead of the plain before and after listings. Translators can [[phab:T369466|help to update the localized versions]]. Thanks to user Msz2001 for these improvements. * A new filter has been added to the [[{{#special:Nuke}}]] tool, which allows administrators to mass delete pages, to enable users to filter for pages in a range of page sizes (in bytes). This allows, for example, deleting pages only of a certain size or below. [https://phabricator.wikimedia.org/T378488] * Non-administrators can now check which pages are able to be deleted using the [[{{#special:Nuke}}]] tool. Thanks to user MolecularPilot for this and the previous improvements. [https://phabricator.wikimedia.org/T376378] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed in the configuration for the AV1 video file format, which enables these files to play again. [https://phabricator.wikimedia.org/T382193] '''Updates for technical contributors''' * Parsoid Read Views is going to be rolling out to most Wiktionaries over the next few weeks, following the successful transition of Wikivoyage to Parsoid Read Views last year. For more information, see the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parsoid/Parser Unification]] project page. [https://phabricator.wikimedia.org/T385923][https://phabricator.wikimedia.org/T371640] * Developers of tools that run on-wiki should note that <code dir=ltr>mw.Uri</code> is deprecated. Tools requiring <code dir=ltr>mw.Uri</code> must explicitly declare <code dir=ltr>mediawiki.Uri</code> as a ResourceLoader dependency, and should migrate to the browser native <code dir=ltr>URL</code> API soon. [https://phabricator.wikimedia.org/T384515] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:17, 17 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28275610 --> == Wikipedia translation of the week: 2025-09 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cooler Heads Coalition]]'''<br /> <small>''([[:de:Cooler Heads Coalition]])&#32;([[:fr:Cooler Heads Coalition]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Cooler Heads Coalition''' is a politically conservative "informal and ad-hoc group" in the United States, financed and operated by the Competitive Enterprise Institute. The group, which rejects the scientific consensus on climate change, made efforts to stop the government from addressing climate change. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 24 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28300238 --> == Tech News: 2025-09 == <section begin="technews-2025-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/09|Translations]] are available. '''Updates for editors''' * Administrators can now customize how the [[m:Special:MyLanguage/User language|Babel feature]] creates categories using [[{{#special:CommunityConfiguration/Babel}}]]. They can rename language categories, choose whether they should be auto-created, and adjust other settings. [https://phabricator.wikimedia.org/T374348] * The <bdi lang="en" dir="ltr">[https://www.wikimedia.org/ wikimedia.org]</bdi> portal has been updated – and is receiving some ongoing improvements – to modernize and improve the accessibility of our portal pages. It now has better support for mobile layouts, updated wording and links, and better language support. Additionally, all of the Wikimedia project portals, such as <bdi lang="en" dir="ltr">[https://wikibooks.org wikibooks.org]</bdi>, now support dark mode when a reader is using that system setting. [https://phabricator.wikimedia.org/T373204][https://phabricator.wikimedia.org/T368221][https://meta.wikimedia.org/wiki/Project_portals] * One new wiki has been created: a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q33965|Santali]] ([[wikt:sat:|<code>wikt:sat:</code>]]) [https://phabricator.wikimedia.org/T386619] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that prevented clicking on search results in the web-interface for some Firefox for Android phone configurations. [https://phabricator.wikimedia.org/T381289] '''Meetings and events''' * The next Language Community Meeting is happening soon, February 28th at [https://zonestamp.toolforge.org/1740751200 14:00 UTC]. This week's meeting will cover: highlights and technical updates on keyboard and tools for the Sámi languages, Translatewiki.net contributions from the Bahasa Lampung community in Indonesia, and technical Q&A. If you'd like to join, simply [[mw:Wikimedia Language and Product Localization/Community meetings#28 February 2025|sign up on the wiki page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:42, 25 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28296129 --> == Wikipedia translation of the week: 2025-10 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:pt:Transmissor de Ondas]]'''<br /> <small>''([[:en:Wave Transmitter]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Esq eletr transm ondas color.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Transmissor de Ondas''' é um equipamento precursor do rádio, desenvolvido por Roberto Landell de Moura na década de 1890, capaz de transmitir áudio via ondas eletromagnéticas, com sua primeira demonstração pública documentada tendo ocorrido no dia 16 de julho de 1899. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:49, 3 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28317097 --> == Tech News: 2025-10 == <section begin="technews-2025-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/10|Translations]] are available. '''Updates for editors''' * All logged-in editors using the mobile view can now edit a full page. The "{{int:Minerva-page-actions-editfull}}" link is accessible from the "{{int:minerva-page-actions-overflow}}" menu in the toolbar. This was previously only available to editors using the [[mw:Special:MyLanguage/Reading/Web/Advanced mobile contributions|Advanced mobile contributions]] setting. [https://phabricator.wikimedia.org/T387180] * Interface administrators can now help to remove the deprecated Cite CSS code matching "<code dir="ltr">mw-ref</code>" from their local <bdi lang="en" dir="ltr">[[MediaWiki:Common.css]]</bdi>. The list of wikis in need of cleanup, and the code to remove, [https://global-search.toolforge.org/?q=mw-ref%5B%5E-a-z%5D&regex=1&namespaces=8&title=.*css can be found with this global search] and in [https://ace.wikipedia.org/w/index.php?title=MediaWiki:Common.css&oldid=145662#L-139--L-144 this example], and you can learn more about how to help on the [[mw:Parsoid/Parser Unification/Cite CSS|CSS migration project page]]. The Cite footnote markers ("<code dir="ltr">[1]</code>") are now rendered by [[mw:Special:MyLanguage/Parsoid|Parsoid]], and the deprecated CSS is no longer needed. The CSS for backlinks ("<code dir="ltr">mw:referencedBy</code>") should remain in place for now. This cleanup is expected to cause no visible changes for readers. Please help to remove this code before March 20, after which the development team will do it for you. * When editors embed a file (e.g. <code><nowiki>[[File:MediaWiki.png]]</nowiki></code>) on a page that is protected with cascading protection, the software will no longer restrict edits to the file description page, only to new file uploads.[https://phabricator.wikimedia.org/T24521] In contrast, transcluding a file description page (e.g. <code><nowiki>{{:File:MediaWiki.png}}</nowiki></code>) will now restrict edits to the page.[https://phabricator.wikimedia.org/T62109] * When editors revert a file to an earlier version it will now require the same permissions as ordinarily uploading a new version of the file. The software now checks for 'reupload' or 'reupload-own' rights,[https://phabricator.wikimedia.org/T304474] and respects cascading protection.[https://phabricator.wikimedia.org/T140010] * When administrators are listing pages for deletion with the Nuke tool, they can now also list associated talk pages and redirects for deletion, alongside pages created by the target, rather than needing to manually delete these pages afterwards. [https://phabricator.wikimedia.org/T95797] * The [[m:Special:MyLanguage/Tech/News/2025/03|previously noted]] update to Single User Login, which will accommodate browser restrictions on cross-domain cookies by moving login and account creation to a central domain, will now roll out to all users during March and April. The team plans to enable it for all new account creation on [[wikitech:Deployments/Train#Tuesday|Group0]] wikis this week. See [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3#Deployment|the SUL3 project page]] for more details and an updated timeline. * Since last week there has been a bug that shows some interface icons as black squares until the page has fully loaded. It will be fixed this week. [https://phabricator.wikimedia.org/T387351] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q2044560|Sylheti]] ([[w:syl:|<code>w:syl:</code>]]) [https://phabricator.wikimedia.org/T386441] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed with loading images in very old versions of the Firefox browser on mobile. [https://phabricator.wikimedia.org/T386400] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.19|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:31, 4 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28334563 --> == Wikipedia translation of the week: 2025-11 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Smoky (mascotte olimpica)]]'''<br /> <small>''([[:en:Smoky (Olympic mascot)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Smoky 1932 Olympic Village Mascot.webp|center|300px]] <div style="text-align:left; padding: .4em;"> '''Smoky''' (Los Angeles, 1931 o 1932 - Los Angeles, aprile 1934), occasionalmente scritto Smokey, è stato un cane che divenne la mascotte del villaggio olimpico estivo del 1932 e, successivamente, dell'evento generale. Pur non essendo oggi riconosciuto dal CIO, è stato, seppur non in modo ufficiale, la prima mascotte olimpica dei Giochi, oltre che a essere attualmente l'unica a essere stata un animale vero. Le successive edizioni non ebbero mascotte, dovendo aspettare i X Giochi olimpici invernali di Grenoble nel 1968 per ritrovarne una ufficialmente riconosciuta, lo sciatore stilizzato Schuss, allora non considerato ufficiale ma successivamente riconosciuto come tale. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:50, 10 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28317097 --> == Tech News: 2025-11 == <section begin="technews-2025-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/11|Translations]] are available. '''Updates for editors''' * Editors who use password managers at multiple wikis may notice changes in the future. The way that our wikis provide information to password managers about reusing passwords across domains has recently been updated, so some password managers might now offer you login credentials that you saved for a different Wikimedia site. Some password managers already did this, and are now doing it for more Wikimedia domains. This is part of the [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3|SUL3 project]] which aims to improve how our unified login works, and to keep it compatible with ongoing changes to the web-browsers we use. [https://phabricator.wikimedia.org/T385520][https://phabricator.wikimedia.org/T384844] * The Wikipedia Apps Team is inviting interested users to help improve Wikipedia’s offline and limited internet use. After discussions in [[m:Afrika Baraza|Afrika Baraza]] and the last [[m:Special:MyLanguage/ESEAP Hub/Meetings|ESEAP call]], key challenges like search, editing, and offline access are being explored, with upcoming focus groups to dive deeper into these topics. All languages are welcome, and interpretation will be available. Want to share your thoughts? [[mw:Special:MyLanguage/Wikimedia Apps/Improving Wikipedia Mobile Apps for Offline & Limited Internet Use|Join the discussion]] or email <bdi lang="en" dir="ltr">aramadan@wikimedia.org</bdi>! * All wikis will be read-only for a few minutes on March 19. This is planned at [https://zonestamp.toolforge.org/1742392800 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.20|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/33|Growth newsletter]] is available. It includes: the launch of the Community Updates module, the most recent changes in Community Configuration, and the upcoming test of in-article suggestions for first-time editors. * An old API that was previously used in the Android Wikipedia app is being removed at the end of March. There are no current software uses, but users of the app with a version that is older than 6 months by the time of removal (2025-03-31), will no longer have access to the Suggested Edits feature, until they update their app. You can [[diffblog:2025/02/24/sunset-of-wikimedia-recommendation-api/|read more details about this change]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:10, 10 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28372257 --> == Wikipedia translation of the week: 2025-12 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Amazonas, o maior rio do mundo]]'''<br /> <small>''([[:pt:Amazonas, o maior rio do mundo]])&#32;([[:es:Amazonas, o maior rio do mundo]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Frame A from Amazonas, o maior rio do mundo.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''''Amazonas, o maior rio do mundo''''' (lit. 'Amazon: The Greatest River in the World') is a 1922 Brazilian silent documentary film produced in 1918 by Silvino Santos. It is a black-and-white film that portrays life in the Amazon rainforest. Completed in 1920, it is considered one of the oldest cinematic records of the Amazon. It was presumed lost in 1931 and only rediscovered in 2023 at the Czech Film Archive. Silvino Santos produced the work over three years using sophisticated cinematic techniques, which led it to be deemed of "immense artistic value" by Le Monde. It has also been described as the "Holy Grail of Brazilian silent cinema" by The Guardian. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 17 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28392163 --> == Tech News: 2025-12 == <section begin="technews-2025-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/12|Translations]] are available. '''Weekly highlight''' * Twice a year, around the equinoxes, the Wikimedia Foundation's Site Reliability Engineering (SRE) team performs [[m:Special:MyLanguage/Tech/Server switch|a datacenter server switchover]], redirecting all traffic from one primary server to its backup. This provides reliability in case of a crisis, as we can always fall back on the other datacenter. [http://listen.hatnote.com/ Thanks to the Listen to Wikipedia] tool, you can hear the switchover take place: Before it begins, you'll hear the steady stream of edits; Then, as the system enters a brief read-only phase, the sound stops for a couple of minutes, before resuming after the switchover. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the background and details of this process on the Diff blog]]. If you want to keep an ear out for the next server switchover, listen to the wikis on [https://zonestamp.toolforge.org/1742392800 March 19 at 14:00 UTC]. '''Updates for editors''' * The [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en&to=es improved Content Translation tool dashboard] is now available in [[phab:T387820|10 Wikipedias]] and will be available for all Wikipedias [[phab:T387821|soon]]. With [[mw:Special:MyLanguage/Content translation#Improved translation experience|the unified dashboard]], desktop users can now: Translate new sections of an article; Discover and access topic-based [https://ig.m.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions&from=en&to=ig&filter-type=automatic&filter-id=previous-edits article suggestion filters] (initially available only for mobile device users); Discover and access the [[mw:Special:MyLanguage/Translation suggestions: Topic-based & Community-defined lists|Community-defined lists]] filter, also known as "Collections", from wiki-projects and campaigns. * On Wikimedia Commons, a [[c:Commons:WMF support for Commons/Upload Wizard Improvements#Improve category selection|new system to select the appropriate file categories]] has been introduced: if a category has one or more subcategories, users will be able to click on an arrow that will open the subcategories directly within the form, and choose the correct one. The parent category name will always be shown on top, and it will always be possible to come back to it. This should decrease the amount of work for volunteers in fixing/creating new categories. The change is also available on mobile. These changes are part of planned improvements to the UploadWizard. * The Community Tech team is seeking wikis to join a pilot for the [[m:Special:MyLanguage/Community Wishlist Survey 2023/Multiblocks|Multiblocks]] feature and a refreshed Special:Block page in late March. Multiblocks enables administrators to impose multiple different types of blocks on the same user at the same time. If you are an admin or steward and would like us to discuss joining the pilot with your community, please leave a message on the [[m:Talk:Community Wishlist Survey 2023/Multiblocks|project talk page]]. * Starting March 25, the Editing team will test a new feature for Edit Check at [[phab:T384372|12 Wikipedias]]: [[mw:Special:MyLanguage/Help:Edit check#Multi-check|Multi-Check]]. Half of the newcomers on these wikis will see all [[mw:Special:MyLanguage/Help:Edit check#ref|Reference Checks]] during their edit session, while the other half will continue seeing only one. The goal of this test is to see if users are confused or discouraged when shown multiple Reference Checks (when relevant) within a single editing session. At these wikis, the tags used on edits that show References Check will be simplified, as multiple tags could be shown within a single edit. Changes to the tags are documented [[phab:T373949|on Phabricator]]. [https://phabricator.wikimedia.org/T379131] * The [[m:Special:MyLanguage/Global reminder bot|Global reminder bot]], which is a service for notifying users that their temporary user-rights are about to expire, now supports using the localized name of the user-rights group in the message heading. Translators can see the [[m:Global reminder bot/Translation|listing of existing translations and documentation]] to check if their language needs updating or creation. * The [[Special:GlobalPreferences|GlobalPreferences]] gender setting, which is used for how the software should refer to you in interface messages, now works as expected by overriding the local defaults. [https://phabricator.wikimedia.org/T386584] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:26}} community-submitted {{PLURAL:26|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Wikipedia App for Android had a bug fixed for when a user is browsing and searching in multiple languages. [https://phabricator.wikimedia.org/T379777] '''Updates for technical contributors''' * Later this week, the way that Codex styles are loaded will be changing. There is a small risk that this may result in unstyled interface message boxes on certain pages. User generated content (e.g. templates) is not impacted. Gadgets may be impacted. If you see any issues [[phab:T388847|please report them]]. See the linked task for details, screenshots, and documentation on how to fix any affected gadgets. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.21|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:48, 17 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28412594 --> == Wikipedia translation of the week: 2025-13 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ali of the Eretnids]]'''<br /> <small>''([[:tr:Alaaddin Ali Bey]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Ala al-Din Ali''' (January 1353 – August 1380) was the third Sultan of the Eretnids ruling from 1366 until his death. He inherited the throne at a very early age and was removed from administrative matters. He was characterized as particularly keen on personal pleasures, which later discredited his authority. During his rule, emirs under the Eretnids enjoyed considerable autonomy, and the state continued to shrink as neighboring powers captured several towns. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 24 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28433698 --> == Tech News: 2025-13 == <section begin="technews-2025-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/13|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation is seeking your feedback on the [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|drafts of the objectives and key results that will shape the Foundation's Product and Technology priorities]] for the next fiscal year (starting in July). The objectives are broad high-level areas, and the key-results are measurable ways to track the success of their objectives. Please share your feedback on the talkpage, in any language, ideally before the end of April. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] will be released to multiple wikis (see [[m:Special:MyLanguage/CampaignEvents/Deployment status#Global Deployment Plan|deployment plan]] for details) in April 2025, and the team has begun the process of engaging communities on the identified wikis. The extension provides tools to organize, manage, and promote collaborative activities (like events, edit-a-thons, and WikiProjects) on the wikis. The extension has three tools: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Special:MyLanguage/Campaigns/Foundation Product Team/Invitation list|Invitation Lists]]. It is currently on 13 Wikipedias, including English Wikipedia, French Wikipedia, and Spanish Wikipedia, as well as Wikidata. Questions or requests can be directed to the [[mw:Help talk:Extension:CampaignEvents|extension talk page]] or in Phabricator (with <bdi lang="en" dir="ltr" style="white-space: nowrap;">#campaigns-product-team</bdi> tag). * Starting the week of March 31st, wikis will be able to set which user groups can view private registrants in [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], as part of the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents]] extension. By default, event organizers and the local wiki admins will be able to see private registrants. This is a change from the current behavior, in which only event organizers can see private registrants. Wikis can change the default setup by [[m:Special:MyLanguage/Requesting wiki configuration changes|requesting a configuration change]] in Phabricator (and adding the <bdi lang="en" dir="ltr" style="white-space: nowrap;">#campaigns-product-team</bdi> tag). Participants of past events can cancel their registration at any time. * Administrators at wikis that have a customized <bdi lang="en" dir="ltr">[[MediaWiki:Sidebar]]</bdi> should check that it contains an entry for the {{int:specialpages}} listing. If it does not, they should add it using <code dir=ltr style="white-space: nowrap;">* specialpages-url|specialpages</code>. Wikis with a default sidebar will see the link moved from the page toolbox into the sidebar menu in April. [https://phabricator.wikimedia.org/T388927] * The Minerva skin (mobile web) combines both Notice and Alert notifications within the bell icon ([[File:OOjs UI icon bell.svg|16px|link=|class=skin-invert]]). There was a long-standing bug where an indication for new notifications was only shown if you had unseen Alerts. This bug is now fixed. In the future, Minerva users will notice a counter atop the bell icon when you have 1 or more unseen Notices and/or Alerts. [https://phabricator.wikimedia.org/T344029] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * VisualEditor has introduced a [[mw:VisualEditor/Hooks|new client-side hook]] for developers to use when integrating with the VisualEditor target lifecycle. This hook should replace the existing lifecycle-related hooks, and be more consistent between different platforms. In addition, the new hook will apply to uses of VisualEditor outside of just full article editing, allowing gadgets to interact with the editor in DiscussionTools as well. The Editing Team intends to deprecate and eventually remove the old lifecycle hooks, so any use cases that this new hook does not cover would be of interest to them and can be [[phab:T355555|shared in the task]]. * Developers who use the <code dir=ltr>mw.Api</code> JavaScript library, can now identify the tool using it with the <code dir=ltr>userAgent</code> parameter: <code dir=ltr>var api = new mw.Api( { userAgent: 'GadgetNameHere/1.0.1' } );</code>. If you maintain a gadget or user script, please set a user agent, because it helps with library and server maintenance and with differentiating between legitimate and illegitimate traffic. [https://phabricator.wikimedia.org/T373874][https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:43, 24 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28443127 --> == Wikipedia translation of the week: 2025-14 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Chilembwe uprising]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Chilembwe supporters being led to be executed (cropped).jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Chilembwe uprising''' was a rebellion against British colonial rule in Nyasaland (modern-day Malawi) which took place in January 1915. It was led by John Chilembwe, an American-educated Baptist minister. Based around his church in the village of Mbombwe in the south-east of the colony, the leaders of the revolt were mainly from an emerging black middle class. They were motivated by grievances against the British colonial system, which included forced labour, racial discrimination and new demands imposed on the African population following the outbreak of World War I. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:52, 31 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-14 == <section begin="technews-2025-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/14|Translations]] are available. '''Updates for editors''' * The Editing team is working on a new [[mw:Special:MyLanguage/Edit Check|Edit check]]: [[mw:Special:MyLanguage/Edit check#26 March 2025|Peacock check]]. This check's goal is to identify non-neutral terms while a user is editing a wikipage, so that they can be informed that their edit should perhaps be changed before they publish it. This project is at the early stages, and the team is looking for communities' input: [[phab:T389445|in this Phabricator task]], they are gathering on-wiki policies, templates used to tag non-neutral articles, and the terms (jargon and keywords) used in edit summaries for the languages they are currently researching. You can participate by editing the table on Phabricator, commenting on the task, or directly messaging [[m:user:Trizek (WMF)|Trizek (WMF)]]. * [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3|Single User Login]] has now been updated on all wikis to move login and account creation to a central domain. This makes user login compatible with browser restrictions on cross-domain cookies, which have prevented users of some browsers from staying logged in. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:35}} community-submitted {{PLURAL:35|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Starting on March 31st, the MediaWiki Interfaces team will begin a limited release of generated OpenAPI specs and a SwaggerUI-based sandbox experience for [[mw:Special:MyLanguage/API:REST API|MediaWiki REST APIs]]. They invite developers from a limited group of non-English Wikipedia communities (Arabic, German, French, Hebrew, Interlingua, Dutch, Chinese) to review the documentation and experiment with the sandbox in their preferred language. In addition to these specific Wikipedia projects, the sandbox and OpenAPI spec will be available on the [[testwiki:Special:RestSandbox|on the test wiki REST Sandbox special page]] for developers with English as their preferred language. During the preview period, the MediaWiki Interfaces Team also invites developers to [[mw:MediaWiki Interfaces Team/Feature Feedback/REST Sandbox|share feedback about your experience]]. The preview will last for approximately 2 weeks, after which the sandbox and OpenAPI specs will be made available across all wiki projects. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.23|MediaWiki]] '''In depth''' * Sometimes a small, [[gerrit:c/operations/cookbooks/+/1129184|one line code change]] can have great significance: in this case, it means that for the first time in years we're able to run all of the stack serving <bdi lang="en" dir="ltr">[http://maps.wikimedia.org/ maps.wikimedia.org]</bdi> - a host dedicated to serving our wikis and their multi-lingual maps needs - from a single core datacenter, something we test every time we perform a [[m:Special:MyLanguage/Tech/Server switch|datacenter switchover]]. This is important because it means that in case one of our datacenters is affected by a catastrophe, we'll still be able to serve the site. This change is the result of [[phab:T216826|extensive work]] by two developers on porting the last component of the maps stack over to [[w:en:Kubernetes|kubernetes]], where we can allocate resources more efficiently than before, thus we're able to withstand more traffic in a single datacenter. This work involved a lot of complicated steps because this software, and the software libraries it uses, required many long overdue upgrades. This type of work makes the Wikimedia infrastructure more sustainable. '''Meetings and events''' * [[mw:Special:MyLanguage/MediaWiki Users and Developers Workshop Spring 2025|MediaWiki Users and Developers Workshop Spring 2025]] is happening in Sandusky, USA, and online, from 14–16 May 2025. The workshop will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. Registration and presentation signup is now available at the workshop's website. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 1 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28473566 --> == Wikipedia translation of the week: 2025-15 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:1930 Bago earthquake]]'''<br /> <small>''([[:my:၁၉၃၀ ပဲခူးငလျင်]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Thiao Mueang Phama (1955, p. 165).jpg|center|300px]] <div style="text-align:left; padding: .4em;"> An earthquake affected Myanmar on 5 May 1930 with a moment magnitude (Mw ) 7.4. The shock occurred 35 km (22 mi) beneath the surface with a maximum Rossi–Forel intensity of IX (Devastating tremor). The earthquake was the result of rupture along a 131 km (81 mi) segment of the Sagaing Fault—a major strike-slip fault that runs through the country. Extensive damage was reported in the southern part of the country, particularly in Bago and Yangon, where buildings collapsed and fires erupted. At least 550, and possibly up to 7,000 people were killed. A moderate tsunami struck the Burmese coast which caused minor damage to ships and a port. It was felt for over 570,000 km2 (220,000 sq mi) and as far as Shan State and Thailand. The mainshock was followed by many aftershocks; several were damaging. The December earthquake was similarly sized which also occurred along the Sagaing Fault. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 7 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-15 == <section begin="technews-2025-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/15|Translations]] are available. '''Updates for editors''' * From now on, [[m:Special:MyLanguage/Interface administrators|interface admins]] and [[m:Special:MyLanguage/Central notice administrators|centralnotice admins]] are technically required to enable [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] before they can use their privileges. In the future this might be expanded to more groups with advanced user-rights. [https://phabricator.wikimedia.org/T150898] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The Design System Team is preparing to release the next major version of Codex (v2.0.0) on April 29. Editors and developers who use CSS from Codex should see the [[mw:Codex/Release Timeline/2.0|2.0 overview documentation]], which includes guidance related to a few of the breaking changes such as <code dir=ltr style="white-space: nowrap;">font-size</code>, <code dir=ltr style="white-space: nowrap;">line-height</code>, and <code dir=ltr style="white-space: nowrap;">size-icon</code>. * The results of the [[mw:Developer Satisfaction Survey/2025|Developer Satisfaction Survey (2025)]]  are now available. Thank you to all participants. These results help the Foundation decide what to work on next and to review what they recently worked on. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.24|MediaWiki]] '''Meetings and events''' * The [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]] will take place in Istanbul, Turkey, between 2–4 May. Registration for attending the in-person event will close on 13 April. Before registering, please note the potential need for a [https://www.mfa.gov.tr/turkish-representations.en.mfa visa] or [https://www.mfa.gov.tr/visa-information-for-foreigners.en.mfa e-visa] to enter the country. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 7 April 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28507470 --> == Wikipedia translation of the week: 2025-16 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Museum of Zoology of the University of São Paulo]]'''<br /> <small>''([[:pt:Museu de Zoologia da Universidade de São Paulo]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Museu de Zoologia da USP 02.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Museum of Zoology of the University of São Paulo''' (Portuguese: Museu de Zoologia da Universidade de São Paulo, abbreviated MZUSP) is a public natural history museum located in the historic Ipiranga district of São Paulo, Brazil. The MZUSP is an educational and research institution that is part of the University of São Paulo. The museum began at the end of the 19th century as part of the Museu Paulista; in 1941, it moved into a dedicated building. In 1969 the museum became a part of the University of São Paulo, receiving its current name. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 14 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-16 == <section begin="technews-2025-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/16|Translations]] are available. '''Weekly highlight''' * Later this week, the default thumbnail size will be increased from 220px to 250px. This changes how pages are shown in all wikis and has been requested by some communities for many years, but wasn't previously possible due to technical limitations. [https://phabricator.wikimedia.org/T355914] * File thumbnails are now stored in discrete sizes. If a page specifies a thumbnail size that's not among the standard sizes (20, 40, 60, 120, 250, 330, 500, 960), then MediaWiki will pick the closest larger thumbnail size but will tell the browser to downscale it to the requested size. In these cases, nothing will change visually but users might load slightly larger images. If it doesn't matter which thumbnail size is used in a page, please pick one of the standard sizes to avoid the extra in-browser down-scaling step. [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Images#Thumbnail_sizes][https://phabricator.wikimedia.org/T355914] '''Updates for editors''' * The Wikimedia Foundation are working on a system called [[m:Edge Uniques|Edge Uniques]] which will enable [[:w:en:A/B testing|A/B testing]], help protect against [[:w:en:Denial-of-service attack|Distributed denial-of-service attacks]] (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is so that they can more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. * To improve security for users, a small percentage of logins will now require that the account owner input a one-time password [[mw:Special:MyLanguage/Help:Extension:EmailAuth|emailed to their account]]. It is recommended that you [[Special:Preferences#mw-prefsection-personal-email|check]] that the email address on your account is set correctly, and that it has been confirmed, and that you have an email set for this purpose. [https://phabricator.wikimedia.org/T390662] * "Are you interested in taking a short survey to improve tools used for reviewing or reverting edits on your Wiki?" This question will be [[phab:T389401|asked at 7 wikis starting next week]], on Recent Changes and Watchlist pages. The [[mw:Special:MyLanguage/Moderator Tools|Moderator Tools team]] wants to know more about activities that involve looking at new edits made to your Wikimedia project, and determining whether they adhere to your project's policies. * On April 15, the full Wikidata graph will no longer be supported on <bdi lang="zxx" dir="ltr">[https://query.wikidata.org/ query.wikidata.org]</bdi>. After this date, scholarly articles will be available through <bdi lang="zxx" dir="ltr" style="white-space:nowrap;">[https://query-scholarly.wikidata.org/ query-scholarly.wikidata.org]</bdi>, while the rest of the data hosted on Wikidata will be available through the <bdi lang="zxx" dir="ltr">[https://query.wikidata.org/ query.wikidata.org]</bdi> endpoint. This is part of the scheduled split of the Wikidata Graph, which was [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/September 2024 scaling update|announced in September 2024]]. More information is [[d:Wikidata:SPARQL query service/WDQS graph split|available on Wikidata]]. * The latest quarterly [[m:Special:MyLanguage/Wikimedia Apps/Newsletter/First quarter of 2025|Wikimedia Apps Newsletter]] is now available. It covers updates, experiments, and improvements made to the Wikipedia mobile apps. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The latest quarterly [[mw:Technical Community Newsletter/2025/April|Technical Community Newsletter]] is now available. This edition includes: an invitation for tool maintainers to attend the Toolforge UI Community Feedback Session on April 15th; recent community metrics; and recent technical blog posts. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.25|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:25, 15 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28540654 --> == Wikipedia translation of the week: 2025-17 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Fear of crime]]'''<br /> <small>''([[:ar:الخوف من الجريمة]])&#32;([[:it:Criminofobia]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Fear of crime''' refers to the fear of being a victim of crime, which is not necessarily reflective of the actual probability of being such a victim. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 21 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28559524 --> == Tech News: 2025-17 == <section begin="technews-2025-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/17|Translations]] are available. '''Updates for editors''' * [[f:Special:MyLanguage/Wikifunctions:Main Page|Wikifunctions]] is now integrated with [[w:dag:Solɔɣu|Dagbani Wikipedia]] since April 15. It is the first project that will be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them in articles. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of [[f:Special:MyLanguage/Wikifunctions:Catalogue|a stable and global function]], rather than via a local template. [https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Status_updates/2025-04-16] * A new type of lint error has been created: [[Special:LintErrors/empty-heading|{{int:linter-category-empty-heading}}]] ([[mw:Special:MyLanguage/Help:Lint errors/empty-heading|documentation]]). The [[mw:Special:MyLanguage/Help:Extension:Linter|Linter extension]]'s purpose is to identify wikitext patterns that must or can be fixed in pages and provide some guidance about what the problems are with those patterns and how to fix them. [https://phabricator.wikimedia.org/T368722] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:37}} community-submitted {{PLURAL:37|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Following its publication on HuggingFace, the "Structured Contents" dataset, developed by Wikimedia Enterprise, is [https://enterprise.wikimedia.com/blog/kaggle-dataset/ now also available on Kaggle]. This Beta initiative is focused on making Wikimedia data more machine-readable for high-volume reusers. They are releasing this beta version in a location that open dataset communities already use, in order to seek feedback, to help improve the product for a future wider release. You can read more about the overall [https://enterprise.wikimedia.com/blog/structured-contents-snapshot-api/#open-datasets Structured Contents project], and about the [https://enterprise.wikimedia.com/blog/structured-contents-wikipedia-infobox/ first release that's freely usable]. * There is no new MediaWiki version this week. '''Meetings and events''' * The Editing and Machine Learning Teams invite interested volunteers to a video meeting to discuss [[mw:Special:MyLanguage/Edit check/Peacock check|Peacock check]], which is the latest [[mw:Special:MyLanguage/Edit check|Edit check]] that will detect "peacock" or "overly-promotional" or "non-neutral" language whilst an editor is typing. Editors who work with newcomers, or help to fix this kind of writing, or are interested in how we use artificial intelligence in our projects are encouraged to attend. The [[mw:Special:MyLanguage/Editing team/Community Conversations#Next Conversation|meeting will be on April 28, 2025]] at [https://zonestamp.toolforge.org/1745863200 18:00–19:00 UTC] and hosted on Zoom. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:01, 21 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28578245 --> == Wikipedia translation of the week: 2025-18 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Heritage preservation in South Korea]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Korean.Dance-03.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The heritage preservation system of South Korea is a multi-level program aiming to preserve and cultivate Korean cultural heritage. The program is administered by the Cultural Heritage Administration (CHA), and the legal framework is provided by the Cultural Heritage Protection Act of 1962, last updated in 2012. The program started in 1962 and has gradually been extended and upgraded since then. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:57, 28 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28583422 --> == Tech News: 2025-18 == <section begin="technews-2025-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/18|Translations]] are available. '''Updates for editors''' * Event organizers who host collaborative activities on [[m:Special:MyLanguage/CampaignEvents/Deployment status#Global Deployment Plan|multiple wikis]], including Bengali, Japanese, and Korean Wikipedias, will have access to the [[mw:Special:MyLanguage/Extension:CampaignEvents|CampaignEvents extension]] this week. Also, admins in the Wikipedia where the extension is enabled will automatically be granted the event organizer right soon. They won't have to manually grant themselves the right before they can manage events as [[phab:T386861|requested by a community]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The release of the next major version of [[mw:Special:MyLanguage/Codex|Codex]], the design system for Wikimedia, is scheduled for 29 April 2025. Technical editors will have access to the release by the week of 5 May 2025. This update will include a number of [[mw:Special:MyLanguage/Codex/Release_Timeline/2.0#Breaking_changes|breaking changes]] and minor [[mw:Special:MyLanguage/Codex/Release_Timeline/2.0#Visual_changes|visual changes]]. Instructions on handling the breaking and visual changes are documented on [[mw:Special:MyLanguage/Codex/Release Timeline/2.0#|this page]]. Pre-release testing is reported in [[phab:T386298|T386298]], with post-release issues tracked in [[phab:T392379|T392379]] and [[phab:T392390|T392390]]. * Users of [[wikitech:Special:MyLanguage/Help:Wiki_Replicas|Wiki Replicas]] will notice that the database views of <code dir="ltr">ipblocks</code>, <code dir="ltr">ipblocks_ipindex</code>, and <code dir="ltr">ipblocks_compat</code> are [[phab:T390767|now deprecated]]. Users can query the <code dir="ltr">[[mw:Special:MyLanguage/Manual:Block_table|block]]</code> and <code dir="ltr">[[mw:Special:MyLanguage/Manual:Block_target_table|block_target]]</code> new views that mirror the new tables in the production database instead. The deprecated views will be removed entirely from Wiki Replicas in June, 2025. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.27|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April|Language and Internationalization Newsletter]] is now available. This edition includes an overview of the improved [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=contributionsmenu&to=es&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en#/ Content Translation Dashboard Tool], [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April#Language Support for New and Existing Languages|support for new languages]], [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April#Wiki Loves Ramadan Articles Made In Content Translation Mobile Workflow|highlights from the Wiki Loves Ramadan campaign]], [[m:Special:MyLanguage/Research:Languages Onboarding Experiment 2024 - Executive Summary|results from the Language Onboarding Experiment]], an analysis of topic diversity in articles, and information on upcoming community meetings and events. '''Meetings and events''' * The [[Special:MyLanguage/Grants:Knowledge_Sharing/Connect/Calendar|Let's Connect Learning Clinic]] will take place on [https://zonestamp.toolforge.org/1745937000 April 29 at 14:30 UTC]. This edition will focus on "Understanding and Navigating Conflict in Wikimedia Projects". You can [[m:Special:MyLanguage/Event:Learning Clinic %E2%80%93 Understanding and Navigating Conflict in Wikimedia Projects (Part_1)|register now]] to attend. * The [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]], which brings the global technical community together to connect, brainstorm, and hack existing projects, will take place from May 2 to 4th, 2025, at Istanbul, Turkey. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:32, 28 April 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28585685 --> == Wikipedia translation of the week: 2025-19 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lhamana]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:We-Wa, a Zuni berdache, weaving - NARA - 523796 (cropped).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lhamana''', in traditional Zuni culture, are biologically male people who take on the social and ceremonial roles usually performed by women in their culture, at least some of the time. They wear a mixture of women's and men's clothing and much of their work is in the areas usually occupied by Zuni women. Some contemporary lhamana participate in the pan-Indian two-spirit community. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 07:28, 5 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28583422 --> == Tech News: 2025-19 == <section begin="technews-2025-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/19|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation has shared the latest draft update to their [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|annual plan]] for next year (July 2025–June 2026). This includes an [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|executive summary]] (also on [[diffblog:2025/04/25/sharing-the-wikimedia-foundations-2025-2026-draft-annual-plan/|Diff]]), details about the three main [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals|goals]] ([[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|Infrastructure]], [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals/Volunteer Support|Volunteer Support]], and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals/Effectiveness|Effectiveness]]), [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Global Trends|global trends]], and the [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Budget Overview|budget]] and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Financial Model|financial model]]. Feedback and questions are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2025-2026|talk page]] until the end of May. '''Updates for editors''' * For wikis that have the [[m:Special:MyLanguage/CampaignEvents/Deployment status|CampaignEvents extension enabled]], two new feature improvements have been released: ** Admins can now choose which namespaces are permitted for [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] via [[mw:Special:MyLanguage/Community Configuration|Community Configuration]] ([[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Permitted namespaces|documentation]]). The default setup is for event registration to be permitted in the Event namespace, but other namespaces (such as the project namespace or WikiProject namespace) can now be added. With this change, communities like WikiProjects can now more easily use Event Registration for their collaborative activities. ** Editors can now [[mw:Special:MyLanguage/Transclusion|transclude]] the Collaboration List on a wiki page ([[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Collaboration list/Transclusion|documentation]]). The Collaboration List is an automated list of events and WikiProjects on the wikis, accessed via {{#special:AllEvents}} ([[w:en:Special:AllEvents|example]]). Now, the Collaboration List can be added to all sorts of wiki pages, such as: a wiki mainpage, a WikiProject page, an affiliate page, an event page, or even a user page. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers who use the <code dir=ltr>moment</code> library in gadgets and user scripts should revise their code to use alternatives like the <code dir=ltr>Intl</code> library or the new <code dir=ltr>mediawiki.DateFormatter</code> library. The <code dir=ltr>moment</code> library has been deprecated and will begin to log messages in the developer console. You can see a global search for current uses, and [[phab:T392532|ask related questions in this Phabricator task]]. * Developers who maintain a tool that queries the Wikidata term store tables (<code dir=ltr style="white-space: nowrap;">wbt_*</code>) need to update their code to connect to a separate database cluster. These tables are being split into a separate database cluster. Tools that query those tables via the wiki replicas must be adapted to connect to the new cluster instead. [[wikitech:News/2025 Wikidata term store database split|Documentation and related links are available]]. [https://phabricator.wikimedia.org/T390954] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.28|MediaWiki]] '''In depth''' * The latest [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|Chart Project newsletter]] is available. It includes updates on preparing to expand the deployment to additional wikis as soon as this week (starting May 6) and scaling up over the following weeks, plus exploring filtering and transforming source data. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:15, 6 May 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28665011 --> == Wikipedia translation of the week: 2025-20 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Gruppo del Sileno]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Parco3.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> '''Sileno ed Egle con Mnasilo e Cromi''', meglio noto come Gruppo del Sileno, è un monumento in marmo di Carrara, realizzato da Jean-Baptiste Boudard nel 1765 per il Giardino Ducale di Parma; sostituito nel 1991 con una copia in polvere di marmo e resina, l'originale si trova provvisoriamente nel chiostro della Fontana del monastero di San Paolo, in attesa della definitiva collocazione prevista all'interno del palazzetto Eucherio Sanvitale nel parco Ducale. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:28, 12 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28709947 --> == Tech News: 2025-20 == <section begin="technews-2025-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/20|Translations]] are available. '''Weekly highlight''' * The [[m:Special:MyLanguage/Wikimedia URL Shortener|"Get shortened URL"]] link on the sidebar now includes a [[phab:T393309|QR code]]. Wikimedia site users can now use it by scanning or downloading it to quickly share and access shared content from Wikimedia sites, conveniently. '''Updates for editors''' * The Wikimedia Foundation is working on a system called [[m:Edge Uniques|Edge Uniques]], which will enable [[w:en:A/B testing|A/B testing]], help protect against [[w:en:Denial-of-service attack|distributed denial-of-service attacks]] (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is to help more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. Tech News has [[m:Special:MyLanguage/Tech/News/2025/16|previously written about this]]. The deployment will be gradual. Some might see the Edge Uniques cookie the week of 19 May. You can discuss this on the [[m:Talk:Edge Uniques|talk page]]. * Starting May 19, 2025, Event organisers in wikis with the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] enabled can use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] in the project namespace (e.g., Wikipedia namespace, Wikidata namespace). With this change, communities don't need admins to use the feature. However, wikis that don't want this change can remove and add the permitted namespaces at [[Special:CommunityConfiguration/CampaignEvents]]. * The Wikipedia project now has a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q36720|Nupe]] ([[w:nup:|<code>w:nup:</code>]]). This is a language primarily spoken in the North Central region of Nigeria. Speakers of this language are invited to contribute to [[w:nup:Tatacin feregi|new Wikipedia]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers can now access pre-parsed Dutch Wikipedia, amongst others (English, German, French, Spanish, Italian, and Portuguese) through the [https://enterprise.wikimedia.com/docs/snapshot/#structured-contents-snapshot-bundle-info-beta Structured Contents snapshots (beta)]. The content includes parsed Wikipedia abstracts, descriptions, main images, infoboxes, article sections, and references. * The <code dir="ltr">/page/data-parsoid</code> REST API endpoint is no longer in use and will be deprecated. It is [[phab:T393557|scheduled to be turned off]] on June 7, 2025. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.1|MediaWiki]] '''In depth''' * The [https://wikitech.wikimedia.org/wiki/News/2025_Cloud_VPS_VXLAN_IPv6_migration IPv6 support] is a newly introduced Cloud virtual network that significantly boosts Wikimedia platforms' scalability, security, and readiness for the future. If you are a technical contributor eager to learn more, check out [https://techblog.wikimedia.org/2025/05/06/wikimedia-cloud-vps-ipv6-support/ this blog post] for an in-depth look at the journey to IPv6. '''Meetings and events''' * The 2nd edition of 2025 of [[m:Special:MyLanguage/Afrika Baraza|Afrika Baraza]], a virtual platform for African Wikimedians to connect, will take place on [https://zonestamp.toolforge.org/1747328400 May 15 at 17:00 UTC]. This edition will focus on discussions regarding [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|Wikimedia Annual planning and progress]]. * The [[m:Special:MyLanguage/MENA Connect Community Call|MENA Connect Community Call]], a virtual meeting for [[w:en:Middle East and North Africa|MENA]] Wikimedians to connect, will take place on [https://zonestamp.toolforge.org/1747501200 May 17 at 17:00 UTC]. You can [[m:Event:MENA Connect (Wiki_Diwan) APP Call|register now]] to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:38, 12 May 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28714188 --> == Wikipedia translation of the week: 2025-21 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lorrin A. Thurston]]'''<br /> <small>''([[:fi:Lorrin Thurston]])&#32;([[:ko:로린 A. 서스턴]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Lorrinandrewsthurston1892.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lorrin Andrews Thurston''' (July 31, 1858 – May 11, 1931) was a Hawaiian citizen lawyer, politician, and businessman. Thurston played a prominent role in the revolution that overthrew the Hawaiian Kingdom to replace Queen Liliʻuokalani with the Republic of Hawaii, with discreet US support for which Congress much later apologized. He published the Pacific Commercial Advertiser (a forerunner of the present-day Honolulu Star-Advertiser), and owned other enterprises. From 1906 to 1916, he and his network lobbied with national politicians to create a national park to preserve the Hawaiian volcanoes. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 19 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28731710 --> == Tech News: 2025-21 == <section begin="technews-2025-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/21|Translations]] are available. '''Weekly highlight''' * The Editing Team and the Machine Learning Team are working on a new check for newcomers: [[mw:Edit check/Peacock check|Peacock check]]. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Peacock language model for the following languages: Arabic, Spanish, Portuguese, English, and Japanese. Users from these wikis interested in reviewing this model are [[mw:Edit check/Peacock check/model test|invited to sign up at MediaWiki.org]]. The deadline to sign up is on May 23, which will be the start date of the test. '''Updates for editors''' * From May 20, 2025, [[m:Special:MyLanguage/Oversight policy|oversighters]] and [[m:Special:MyLanguage/Meta:CheckUsers|checkusers]] will need to have their accounts secured with two-factor authentication (2FA) to be able to use their advanced rights. All users who belong to these two groups and do not have 2FA enabled have been informed. In the future, this requirement may be extended to other users with advanced rights. [[m:Special:MyLanguage/Mandatory two-factor authentication for users with some extended rights|Learn more]]. * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] [[m:Special:MyLanguage/Community Wishlist Survey 2023/Multiblocks|Multiblocks]] will begin mass deployment by the end of the month: all non-Wikipedia projects plus Catalan Wikipedia will adopt Multiblocks in the week of May 26, while all other Wikipedias will adopt it in the week of June 2. Please [[m:Talk:Community Wishlist Survey 2023/Multiblocks|contact the team]] if you have concerns. Administrators can test the new user interface now on your own wiki by browsing to [{{fullurl:Special:Block|usecodex=1}} {{#special:Block}}?usecodex=1], and can test the full multiblocks functionality [[testwiki:Special:Block|on testwiki]]. Multiblocks is the feature that makes it possible for administrators to impose different types of blocks on the same user at the same time. See the [[mw:Special:MyLanguage/Help:Manage blocks|help page]] for more information. [https://phabricator.wikimedia.org/T377121] * Later this week, the [[{{#special:SpecialPages}}]] listing of almost all special pages will be updated with a new design. This page has been [[phab:T219543|redesigned]] to improve the user experience in a few ways, including: The ability to search for names and aliases of the special pages, sorting, more visible marking of restricted special pages, and a more mobile-friendly look. The new version can be [https://meta.wikimedia.beta.wmflabs.org/wiki/Special:SpecialPages previewed] at Beta Cluster now, and feedback shared in the task. [https://phabricator.wikimedia.org/T219543] * The [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] is being enabled on more wikis. For a detailed list of when the extension will be enabled on your wiki, please read the [[mw:Special:MyLanguage/Extension:Chart/Project#Deployment Timeline|deployment timeline]]. * [[f:Special:MyLanguage/Wikifunctions:Main Page|Wikifunctions]] will be deployed on May 27 on five Wiktionaries: [[wikt:ha:|Hausa]], [[wikt:ig:|Igbo]], [[wikt:bn:|Bengali]], [[wikt:ml:|Malayalam]], and [[wikt:dv:|Dhivehi/Maldivian]]. This is the second batch of deployment planned for the project. After deployment, the projects will be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them in their pages. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of [[f:Special:MyLanguage/Wikifunctions:Catalogue|a stable and global function]], rather than via a local template. * Later this week, the Wikimedia Foundation will publish a hub for [[diffblog:2024/07/09/on-the-value-of-experimentation/|experiments]]. This is to showcase and get user feedback on product experiments. The experiments help the Wikimedia movement [[diffblog:2023/07/13/exploring-paths-for-the-future-of-free-knowledge-new-wikipedia-chatgpt-plugin-leveraging-rich-media-social-apps-and-other-experiments/|understand new users]], how they interact with the internet and how it could affect the Wikimedia movement. Some examples are [[m:Special:MyLanguage/Future Audiences/Generated Video|generated video]], the [[m:Special:MyLanguage/Future Audiences/Roblox game|Wikipedia Roblox speedrun game]] and [[m:Special:MyLanguage/Future Audiences/Discord bot|the Discord bot]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a bug with creating an account using the API, which has now been fixed. [https://phabricator.wikimedia.org/T390751] '''Updates for technical contributors''' * Gadgets and user scripts that interact with [[{{#special:Block}}]] may need to be updated to work with the new [[mw:Special:MyLanguage/Help:Manage blocks|manage blocks interface]]. Please review the [[mw:Help:Manage blocks/Developers|developer guide]] for more information. If you need help or are unable to adapt your script to the new interface, please let the team know on the [[mw:Help talk:Manage blocks/Developers|talk page]]. [https://phabricator.wikimedia.org/T377121] * The <code dir=ltr>mw.title</code> object allows you to get information about a specific wiki page in the [[w:en:Wikipedia:Lua|Lua]] programming language. Starting this week, a new property will be added to the object, named <code dir=ltr>isDisambiguationPage</code>. This property allows you to check if a page is a disambiguation page, without the need to write a custom function. [https://phabricator.wikimedia.org/T71441] * [[File:Octicons-tools.svg|15px|link=|class=skin-invert|Advanced item]] User script developers can use a [[toolforge:gitlab-content|new reverse proxy tool]] to load javascript and css from [[gitlab:|gitlab.wikimedia.org]] with <code dir=ltr>mw.loader.load</code>. The tool's author hopes this will enable collaborative development workflows for user scripts including linting, unit tests, code generation, and code review on <bdi lang="zxx" dir="ltr">gitlab.wikimedia.org</bdi> without a separate copy-and-paste step to publish scripts to a Wikimedia wiki for integration and acceptance testing. See [[wikitech:Tool:Gitlab-content|Tool:Gitlab-content on Wikitech]] for more information. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.2|MediaWiki]] '''Meetings and events''' * The 12th edition of [[m:Special:MyLanguage/Wiki Workshop 2025|Wiki Workshop 2025]], a forum that brings together researchers that explore all aspects of Wikimedia projects, will be held virtually on 21-22 May. Researchers can [https://pretix.eu/wikimedia/wikiworkshop2025/ register now]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W21"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:13, 19 May 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28724712 --> == Wikipedia translation of the week: 2025-22 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Lamiera bugnata]]'''<br /> <small>''([[:en:Tread plate]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Diamond Plate.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Una '''lamiera bugnata''' o mandorlata è una lamiera di metallo ottenuta dalla laminazione di una bramma attraverso rulli che, tramite punzonatura o goffratura, imprimono sulla lamina rilievi a forma di rombo o ellisse, detti bugne. Nel caso questi rilievi siano alternati singolarmente nei due assi, si parla di lamiera diamantata, mentre se le forme sono predisposte in maniera parallela per formare piccoli quadranti tra di loro tangenti, questo pattern viene identificato con il nome di mandorlato. We tend to ignore the fact that this type of plate is the only reason we don't slip when we walk on steel and wet or frozen surfaces. The Italian article it's short but quite complete, and has just the right amount of citations, unlike other poor languages' versions. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 06:03, 26 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28751788 --> == Tech News: 2025-22 == <section begin="technews-2025-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/22|Translations]] are available. '''Weekly highlight''' * A community-wide discussion about a very delicate issue for the development of [[m:Special:MyLanguage/Abstract Wikipedia|Abstract Wikipedia]] is now open on Meta: where to store the abstract content that will be developed through functions from Wikifunctions and data from Wikidata. The discussion is open until June 12 at [[m:Special:MyLanguage/Abstract Wikipedia/Location of Abstract Content|Abstract Wikipedia/Location of Abstract Content]], and every opinion is welcomed. The decision will be made and communicated after the consultation period by the Foundation. '''Updates for editors''' * Since last week, on all wikis except [[phab:T388604|the largest 20]], people using the mobile visual editor will have [[phab:T385851|additional tools in the menu bar]], accessed using the new <code>+</code> toolbar button. To start, the new menu will include options to add: citations, hieroglyphs, and code blocks. Deployment to the remaining wikis is [[phab:T388605|scheduled]] to happen in June. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The <code dir=ltr>[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##ifexist|#ifexist]]</code> parser function will no longer register a link to its target page. This will improve the usefulness of [[{{#special:WantedPages}}]], which will eventually only list pages that are the target of an actual red link. This change will happen gradually as the source pages are updated. [https://phabricator.wikimedia.org/T14019] * This week, the Moderator Tools team will launch [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], starting at Indonesian Wikipedia. This new filter highlights edits that are likely to be reverted. The goal is to help Recent Changes patrollers identify potentially problematic edits. Other wikis will benefit from this filter in the future. * Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading. The feature will be available on both desktop and mobile. Readers of Catalan, Hebrew, and Italian Wikipedias and some sister projects will receive the change between May 21 and mid-June. Readers of other wikis will receive the change later. The goal is to encourage users to read the wikis more. [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments/Search Suggestions|Learn more]]. * Some users of the Wikipedia Android app can use a new feature for readers, [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/TrivaGame|WikiGames]], a daily trivia game based on real historical events. The release has started as an A/B test, available to 50% of users in the following languages: English, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. * The [[mw:Special:MyLanguage/Extension:Newsletter|Newsletter extension]] that is available on MediaWiki.org allows the creation of [[mw:Special:Newsletters|various newsletters]] for global users. The extension can now publish new issues as section links on an existing page, instead of requiring a new page for each issue. [https://phabricator.wikimedia.org/T393844] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The previously deprecated <code dir=ltr>[[mw:Special:MyLanguage/Manual:Ipblocks table|ipblocks]]</code> views in [[wikitech:Help:Wiki Replicas|Wiki Replicas]] will be removed in the beginning of June. Users are encouraged to query the new <code dir=ltr>[[mw:Special:MyLanguage/Manual:Block table|block]]</code> and <code dir=ltr>[[mw:Special:MyLanguage/Manual:Block target table|block_target]]</code> views instead. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.3|MediaWiki]] '''Meetings and events''' * [[d:Special:MyLanguage/Event:Wikidata and Sister Projects|Wikidata and Sister Projects]] is a multi-day online event that will focus on how Wikidata is integrated to Wikipedia and the other Wikimedia projects. The event runs from May 29 – June 1. You can [[d:Special:MyLanguage/Event:Wikidata and Sister Projects#Sessions|read the Program schedule]] and [[d:Special:RegisterForEvent/1291|register]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:05, 26 May 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28788673 --> == Wikipedia translation of the week: 2025-23 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Angelo azzurro (cocktail)]]'''<br /> <small>''([[:es:Ángel azul (cóctel)]])&#32;([[:fr:Ange bleu (cocktail)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Angelo Azzurro Cocktail.png|300px|center]] <div style="text-align:left; padding: .4em;"> L''''angelo azzurro''' è un cocktail alcolico italiano. È considerato uno dei cocktail più popolari in Italia negli anni novanta, insieme al B-52 e all'Invisibile. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 05:39, 2 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-23 == <section begin="technews-2025-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/23|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] is now available on all Wikimedia wikis. Editors can use this new extension to create interactive data visualizations like bar, line, area, and pie charts. Charts are designed to replace many of the uses of the legacy [[mw:Special:MyLanguage/Extension:Graph|Graph extension]]. '''Updates for editors''' * It is now easier to configure automatic citations for your wiki within the visual editor's [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|citation generator]]. Administrators can now set a default template by using the <code dir=ltr>_default</code> key in the local <bdi lang="en" dir="ltr">[[MediaWiki:Citoid-template-type-map.json]]</bdi> page ([[mw:Special:Diff/6969653/7646386|example diff]]). Setting this default will also help to future-proof your existing configurations when [[phab:T347823|new item types]] are added in the future. You can still set templates for individual item types as they will be preferred to the default template. [https://phabricator.wikimedia.org/T384709] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Starting the week of June 2, bots logging in using <code dir=ltr>action=login</code> or <code dir=ltr>action=clientlogin</code> will fail more often. This is because of stronger protections against suspicious logins. Bots using [[mw:Special:MyLanguage/Manual:Bot passwords|bot passwords]] or using a loginless authentication method such as [[mw:Special:MyLanguage/OAuth/Owner-only consumers|OAuth]] are not affected. If your bot is not using one of those, you should update it; using <code dir=ltr>action=login</code> without a bot password was deprecated [[listarchive:list/wikitech-l@lists.wikimedia.org/message/3EEMN7VQX5G7WMQI5K2GP5JC2336DPTD/|in 2016]]. For most bots, this only requires changing what password the bot uses. [https://phabricator.wikimedia.org/T395205] * From this week, Wikimedia wikis will allow ES2017 features in JavaScript code for official code, gadgets, and user scripts. The most visible feature of ES2017 is <bdi lang="zxx" dir="ltr"><code>async</code>/<code>await</code></bdi> syntax, allowing for easier-to-read code. Until this week, the platform only allowed up to ES2016, and a few months before that, up to ES2015. [https://phabricator.wikimedia.org/T381537] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.4|MediaWiki]] '''Meetings and events''' * Scholarship applications to participate in the [[m:Special:MyLanguage/GLAM Wiki 2025|GLAM Wiki Conference 2025]] are now open. The conference will take place from 30 October to 1 November, in Lisbon, Portugal. GLAM contributors who lack the means to support their participation can [[m:Special:MyLanguage/GLAM Wiki 2025/Scholarships|apply here]]. Scholarship applications close on June 7th. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:55, 2 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28819186 --> == Wikipedia translation of the week: 2025-24 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fi:Kotiryssä]]'''<br /> <small>''([[:en:Kotiryssä]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A '''kotiryssä''' (jocular Finnish: one’s home Russky or home Russian) was a Soviet or Russian contact person of a Finnish politician, bureaucrat, businessman or other important person. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 9 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-24 == <section begin="technews-2025-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/24|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Trust and Safety Product|Trust and Safety Product team]] is finalizing work needed to roll out [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] on large Wikipedias later this month. The team has worked with stewards and other users with extended rights to predict and address many use cases that may arise on larger wikis, so that community members can continue to effectively moderate and patrol temporary accounts. This will be the second of three phases of deployment – the last one will take place in September at the earliest. For more information about the recent developments on the project, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|see this update]]. If you have any comments or questions, write on the [[mw:Talk:Trust and Safety Product/Temporary Accounts|talk page]], and [[m:Event:CEE Catch up Nr. 10 (June 2025)|join a CEE Catch Up]] this Tuesday. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] The [[mw:Special:MyLanguage/Help:Watchlist expiry|watchlist expiry]] feature allows editors to watch pages for a limited period of time. After that period, the page is automatically removed from your watchlist. Starting this week, you can set a preference for the default period of time to watch pages. The [[Special:Preferences#mw-prefsection-watchlist-pageswatchlist|preferences]] also allow you to set different default watch periods for editing existing pages, pages you create, and when using rollback. [https://phabricator.wikimedia.org/T265716] [[File:Talk pages default look (April 2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages will change at almost all Wikipedias ([[m:Special:MyLanguage/Tech/News/2024/19|some]] have already received this design change, [[phab:T379264|a few]] will get these changes later). You can read details about the changes [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. It is possible to opt out of these changes [[Special:Preferences#mw-prefsection-editing-discussion|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). [https://phabricator.wikimedia.org/T319146][https://phabricator.wikimedia.org/T392121] * Users with specific extended rights (including administrators, bureaucrats, checkusers, oversighters, and stewards) can now have IP addresses of all temporary accounts [[phab:T358853|revealed automatically]] during time-limited periods where they need to combat high-speed account-hopping vandalism. This feature was requested by stewards. [https://phabricator.wikimedia.org/T386492] * This week, the Moderator Tools and Machine Learning teams will continue the rollout of [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], releasing it to several more Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: {{int:project-localized-name-afwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-simplewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}. The rollout will continue in the coming weeks to include [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|the rest of the Wikipedias in this project]]. [https://phabricator.wikimedia.org/T391964] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * AbuseFilter editors active on Meta-Wiki and large Wikipedias are kindly asked to update AbuseFilter to make it compatible with temporary accounts. A link to the instructions and the private lists of filters needing verification are [[phab:T369611|available on Phabricator]]. * Lua modules now have access to the name of a page's associated thumbnail image, and on [https://gerrit.wikimedia.org/g/operations/mediawiki-config/+/2e4ab14aa15bb95568f9c07dd777065901eb2126/wmf-config/InitialiseSettings.php#10849 some wikis] to the WikiProject assessment information. This is possible using two new properties on [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#added-by-extensions|mw.title objects]], named <code dir=ltr>pageImage</code> and <code dir=ltr>pageAssessments</code>. [https://phabricator.wikimedia.org/T131911][https://phabricator.wikimedia.org/T380122] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.5|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:17, 10 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28846858 --> == Wikipedia translation of the week: 2025-25 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Future self]]'''<br /> <small>''([[:pl:Przyszła jaźń]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In the psychology of self, the '''future self''' concerns the processes and consequences associated with thinking about oneself in the future. People think about their future selves similarly to how they think about other people. The extent to which people feel psychologically connected (e.g., similarity, closeness) to their future self influences how well they treat their future self. When people feel connected to their future self, they are more likely to save for retirement, make healthy decisions, and avoid ethical transgressions. Interventions that increase feelings of connectedness with future selves can improve future-oriented decision making across these domains. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 16 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-25 == <section begin="technews-2025-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/25|Translations]] are available. '''Updates for editors''' * You can [https://wikimediafoundation.limesurvey.net/359761?lang=en nominate your favorite tools] for the sixth edition of the [[m:Special:MyLanguage/Coolest Tool Award|Coolest Tool Award]]. Nominations are anonymous and will be open until June 25. You can re-use the survey to nominate multiple tools. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:33}} community-submitted {{PLURAL:33|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.6|MediaWiki]] '''In depth''' * Foundation staff and technical volunteers use Wikimedia APIs to build the tools, applications, features, and integrations that enhance user experiences. Over the coming years, the MediaWiki Interfaces team will be investing in Wikimedia web (HTTP) APIs to better serve technical volunteer needs and protect Wikimedia infrastructure from potential abuse. You can [https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/ read more about their plans to evolve the APIs in this Techblog post]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:39, 16 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28870688 --> == Wikipedia translation of the week: 2025-26 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pictorial map]]'''<br /> <small>''([[:fa:نقشه تصویری]])&#32;([[:ja:絵地図]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Blake Britain Spearhead of Attack.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Pictorial maps''' (also known as illustrated maps, panoramic maps, perspective maps, bird's-eye view maps, and geopictorial maps) depict a given territory with a more artistic rather than technical style. It is a type of map in contrast to road map, atlas, or topographic map. The cartography can be a sophisticated 3-D perspective landscape or a simple map graphic enlivened with illustrations of buildings, people and animals. They can feature all sorts of varied topics like historical events, legendary figures or local agricultural products and cover anything from an entire continent to a college campus. Drawn by specialized artists and illustrators, pictorial maps are a rich, centuries-old tradition and a diverse art form that ranges from cartoon maps on restaurant placemats to treasured art prints in museums. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:18, 23 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-26 == <section begin="technews-2025-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/26|Translations]] are available. '''Weekly highlight''' * This week, the Moderator Tools and Machine Learning teams will continue the rollout of [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], releasing it to the third and last batch of Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: {{int:project-localized-name-azwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-swwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tlwiki/en}}. The rollout will continue in the coming weeks to include [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|the rest of the Wikipedias in this project]]. [https://phabricator.wikimedia.org/T391964] '''Updates for editors''' * Last week, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] were rolled out on Czech, Korean, and Turkish Wikipedias. This and next week, deployments on larger Wikipedias will follow. [[mw:Talk:Trust and Safety Product/Temporary Accounts|Share your thoughts]] about the project. [https://phabricator.wikimedia.org/T340001] * Later this week, the Editing team will release [[mw:Special:MyLanguage/Help:Edit check#Multi check|Multi Check]] to all Wikipedias (except English Wikipedia). This feature shows multiple [[mw:Special:MyLanguage/Help:Edit check#Reference check|Reference checks]] within the editing experience. This encourages users to add citations when they add multiple new paragraphs to a Wikipedia article. This feature was previously available as an A/B test. [https://analytics.wikimedia.org/published/reports/editing/multi_check_ab_test_report_final.html#summary-of-results The test shows] that users who are shown multiple checks are 1.3 times more likely to add a reference to their edit, and their edit is less likely to be reverted (-34.7%). [https://phabricator.wikimedia.org/T395519] * A few pages need to be renamed due to software updates and to match more recent Unicode standards. All of these changes are related to title-casing changes. Approximately 71 pages and 3 files will be renamed, across 15 wikis; the complete list is in [[phab:T396903|the task]]. The developers will rename these pages next week, and they will fix redirects and embedded file links a few minutes later via a system settings update. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that had caused pages to scroll upwards when text near the top was selected. [https://phabricator.wikimedia.org/T364023] '''Updates for technical contributors''' * Editors can now use Lua modules to filter and transform tabular data for use with [[mw:Special:MyLanguage/Extension:Chart|Extension:Chart]]. This can be used for things like selecting a subset of rows or columns from the source data, converting between units, statistical processing, and many other useful transformations. [[mw:Special:MyLanguage/Extension:Chart/Transforms|Information on how to use transforms is available]]. [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Chart/Project/Updates] * The <code dir=ltr>all_links</code> variable in [[Special:AbuseFilter|AbuseFilter]] is now renamed to <code dir=ltr>new_links</code> for consistency with other variables. Old usages will still continue to work. [https://phabricator.wikimedia.org/T391811] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.7|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/34|Growth newsletter]] is available. It includes: the recent updates for the "Add a Link" Task, two new Newcomer Engagement Features, and updates to Community Configuration. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:21, 23 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28870688 --> == Wikipedia translation of the week: 2025-27 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Queen Elizabeth University Hospital]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:QEUH.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Queen Elizabeth University Hospital''' (QEUH) is a 1,677-bed acute hospital located in Govan, in the south-west of Glasgow, Scotland. The hospital is built on the site of the former Southern General Hospital and opened at the end of April 2015. The hospital comprises a 1,109-bed adult hospital, a 256-bed children's hospital and two major Emergency Departments; one for adults and one for children. There is also an Immediate Assessment Unit for local GPs and out-of-hours services, to send patients directly, without having to be processed through the Emergency Department. The retained buildings from the former Southern General Hospital include the Maternity Unit, the Institute of Neurological Sciences, the Langlands Unit for medicine of the elderly and the laboratory. The whole facility is operated by NHS Greater Glasgow and Clyde, and is one of the largest acute hospital campuses in Europe. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 30 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-27 == <section begin="technews-2025-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/27|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] has been enabled on all Wikipedias. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. The extension has three features: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Campaigns/Foundation Product Team/Invitation list|Invitation List]]. To request the extension for your wiki, visit the [[m:Special:MyLanguage/CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|Deployment information page]]. '''Updates for editors''' * AbuseFilter maintainers can now [[mw:Special:MyLanguage/Extension:IPReputation/AbuseFilter variables|match against IP reputation data]] in [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilters]]. IP reputation data is information about the proxies and VPNs associated with the user's IP address. This data is not shown publicly and is not generated for actions performed by registered accounts. [https://phabricator.wikimedia.org/T354599] * Hidden content that is within [[mw:Special:MyLanguage/Manual:Collapsible elements|collapsible parts of wikipages]] will now be revealed when someone searches the page using the web browser's "Find in page" function (Ctrl+F or ⌘F) in supporting browsers. [https://phabricator.wikimedia.org/T327893][https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/hidden#browser_compatibility] * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new feature, called [[mw:Special:MyLanguage/Help:TemplateData/Template discovery|Favourite Templates]], will be deployed later this week on all projects (except English Wikipedia, which will receive the feature next week), following a piloting phase on Polish and Arabic Wikipedia, and Italian and English Wikisource. The feature will provide a better way for new and experienced contributors to recall and discover templates via the template dialog, by allowing users to put templates on a special "favourite list". The feature works with both the visual editor and the wikitext editor. The feature is a [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|community wishlist focus area]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that had caused some Notifications to be sent multiple times. [https://phabricator.wikimedia.org/T397103] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.8|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:41, 30 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28917415 --> == Wikipedia translation of the week: 2025-28 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Non-constituency Member of Parliament]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A '''Non-constituency Member of Parliament''' (NCMP) is a member of an opposition political party in Singapore who, as stipulated in Article 39 of the Constitution and the Parliamentary Elections Act, is declared to have been elected a Member of Parliament (MP) without constituency representation, despite having lost in a general election, by virtue of having been one of the opposition candidates with the highest vote shares among the unelected. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:10, 7 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-28 == <section begin="technews-2025-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/28|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Help:Temporary accounts|Temporary accounts]] have been rolled out on 18 large and medium-sized Wikipedias, including German, Japanese, French, and Chinese. Now, about 1/3 of all logged-out activity across wikis is coming from temporary accounts. Users involved in patrolling may be interested in two new documentation pages: [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Access to IP|Access to IP]], explaining everything related to access to temporary account IP addresses, and [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Repository|Repository]] with a list of new gadgets and user scripts. '''Updates for editors''' * Anyone can play an experimental new game, [[mw:Special:MyLanguage/New Engagement Experiments/WikiRun|WikiRun]], that lets you race through Wikipedia by clicking from one article to another, aiming to reach a target page in as few steps and in as little time as possible. The project's goal is to explore new ways of engaging readers. [https://wikirun-game.toolforge.org/ Try playing the game] and let the team know what you think [[mw:Talk:New Engagement Experiments/WikiRun|on the talk page]]. * Users of the Wikipedia Android app in some languages can now play the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/TrivaGame|trivia game]]. ''Which came first?'' is a simple history game where you guess which of two events happened earlier on today's date. It was previously available as an A/B test. It is now available to all users in English, German, French, Spanish, Portuguese, Russian, Arabic, Turkish, and Chinese. The goal of the feature is to help engage with new generations of readers. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2025/22] * Users of the iOS Wikipedia App in some languages may see a new tabbed browsing feature that enables you to open multiple tabs while reading. This feature makes it easier to explore related topics and switch between articles. The A/B test is currently running in Arabic, English, and Japanese in selected regions. More details are available on the [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Tabbed Browsing (Tabs)|Tabbed Browsing project page]]. * Bureaucrats on Wikimedia wikis can now use [[{{#special:VerifyOATHForUser}}]] to check if users have enabled [[mw:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]]. [https://phabricator.wikimedia.org/T265726] * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new feature related to [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template Recall and Discovery]] will be deployed later this week to all Wikimedia projects: a [[mw:Special:MyLanguage/Help:TemplateData/Template discovery#Template categories|template category browser]] will be introduced to assist users in finding templates to put in their “favourite” list. The browser will allow users to browse a list of templates which have been organised into a given category tree. The feature has been requested by the community [[m:Special:MyLanguage/Community Wishlist/Wishes/Select templates by categories|through the Community Wishlist]]. * It is now possible to access watchlist preferences from the watchlist page. Also the redundant button to edit the watchlist has been removed. [https://www.mediawiki.org/wiki/Moderator_Tools/Watchlist] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * As part of [[mw:MediaWiki_1.44|MediaWiki 1.44]] there is now a unified built-in Notifications system that makes it easier for developers to send, manage, and customize notifications. Check out the updated documentation at [[mw:Manual:Notifications|Manual:Notifications]], information about migration in [[phab:T388663|T388663]] and details on deprecated hooks in [[phab:T389624|T389624]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.9|MediaWiki]] '''Meetings and events''' * [[d:Special:MyLanguage/Event:WikidataCon 2025|WikidataCon 2025]], the conference dedicated to Wikidata is now open for [https://pretalx.com/wikidatacon-2025/cfp session proposals] and for [[d:Special:RegisterForEvent/1340|registration]]. This year's event will be held online from October 31 – November 02 and will explore on the theme of "Connecting People through Linked Open Data". '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 8 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28930584 --> == Wikipedia translation of the week: 2025-29 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Immunolabeling]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Immunolabeling process image.png|300px|center]] <div style="text-align:left; padding: .4em;"> '''Immunolabeling''' is a biochemical process that enables the detection and localization of an antigen to a particular site within a cell, tissue, or organ. Antigens are organic molecules, usually proteins, capable of binding to an antibody. These antigens can be visualized using a combination of antigen-specific antibody as well as a means of detection, called a tag, that is covalently linked to the antibody <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> ---[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:44, 14 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28945528 --> == Tech News: 2025-29 == <section begin="technews-2025-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/29|Translations]] are available. '''Updates for editors''' * [[mw:Special:MyLanguage/Help:TemplateData/Template discovery#Featured templates|Featured templates]], a new feature related to [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template Recall and Discovery]] will be deployed this week to all Wikimedia projects: With this feature, editors will be able to quickly access a list of templates that are likely to be useful. These templates will be displayed in a list, under the "featured" tab of the template discovery interface. Administrators can define the list via the Community Configuration interface. The feature fulfills a request by the community [[m:Special:MyLanguage/Community Wishlist/Wishes/Easy access Templates|through the Community Wishlist]]. [https://phabricator.wikimedia.org/T367428][https://phabricator.wikimedia.org/T392896] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the request to add Malayalam fonts in the [[oldWikisource:Special:MyLanguage/Wikisource:WS Export|Wikisource Book Export Tool]] was resolved and now, the rendering of Malayalam letters in exported Wikisource books are accurate. [https://phabricator.wikimedia.org/T374457] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.10|MediaWiki]] '''In depth''' * Developers, designers, and all Wikimedians are invited to [https://phabricator.wikimedia.org/project/board/7953/ submit a project idea] for the Wikimania Hackathon 2025. Read [https://diff.wikimedia.org/2025/06/30/call-for-projects-wikimania-hackathon-2025-is-coming-to-nairobi/ this Diff blog post] for more details. '''Meetings and events''' * [[m:WikiIndaba conference 2025|WikiIndaba 2025]] scholarship application and program submission is open until 23:59 GMT on July 20. WikiIndaba is a regional conference for African Wikimedians both on the continent and in the diaspora to unite and grow together. Submit [https://docs.google.com/forms/d/e/1FAIpQLSdJTv68R1OPASXXDfpIl8EWiMLTM-TDwh6_5gNVvFuWccFZ2Q/viewform your scholarship application] and [https://ee.kobotoolbox.org/x/BI3omIfH program proposal] now! * [https://br.wikimedia.org/wiki/WikiCon_Brasil_2025 WikiCon Brasil 2025] will take place on July 19-20 in Salvador, Bahia, Brazil. The Brazilian community members are encouraged to register and attend! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:10, 14 July 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28980963 --> == Wikipedia translation of the week: 2025-30 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Vespa analis]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Plumpy hornet on the ground - 1.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Vespa analis''''', the yellow-vented hornet, is a species of common hornet found in Southeast Asia <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:28, 21 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28984647 --> == Tech News: 2025-30 == <section begin="technews-2025-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/30|Translations]] are available. '''Updates for editors''' * The Translation Suggestions feature in the [[mw:Special:MyLanguage/Content translation|Content Translation tool]] now has another level of article filters added to the "[https://en.wikipedia.org/w/index.php?title=Special:ContentTranslation&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en&to=fi#/ ... More]" category. Translators who use the Suggestions feature can now select and receive article suggestions that are customized to geographical locations of their interest using the new "{{int:Cx-sx-suggestions-filters-tab-regions}}" filter. [https://phabricator.wikimedia.org/T113257] * Administrators can now limit "Add a Link" to newcomers. The [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|"Add a Link"]] Structured Task [[mw:Special:MyLanguage/Growth/Constructive activation experimentation#Enwiki A/B test & "Add a Link" Improvements (Wiki Experiences 1.2.11 & 1.2.16)|helps new account holders start editing]], but some communities have requested the ability to restrict it to its intended audience: newcomers. Administrators can configure this setting within the [[Special:CommunityConfiguration/GrowthSuggestedEdits|Community Configuration]] feature. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * For AbuseFilter editors on [[phab:T392144|some wikis]], it is now possible to filter edits based on the RevertRisk score of the edit being attempted. It is only populated if the action being evaluated is an edit. For more information, please see the [[mw:Special:MyLanguage/Extension:ORES/AbuseFilter variables#What variables are available for use|ORES/AbuseFilter variables]] documentation. * The [[mw:Special:MyLanguage/Beta Cluster|Beta Cluster]] wikis have [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/YDABPV75LADRQCXMJAFWUP256N4EQ25B/|been moved]] from <code dir=ltr>beta.wmflabs.org</code> to <code dir=ltr>beta.wmcloud.org</code>. Users may need to update URLs in any tools, or in their password managers. Any related issues can be [[phab:T289318|reported in the task]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.11|MediaWiki]] '''Meetings and events''' * [[m:Special:MyLanguage/WikiCite 2025|WikiCite 2025]] will take place from 29–31 August, both online and in-person in Bern, Switzerland. The event's goals are to reconnect communities, institutions, and individuals working with open citations, bibliographic data, and the Wikidata/Wikibase ecosystem. Registration is open and the call for proposals will be announced soon. [https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/KQZUG3ETKLBWPBYSB2YAWZIRPWHS24TG/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:43, 21 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29005283 --> == Wikipedia translation of the week: 2025-31 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Fernando de Noronha Marine National Park]]'''<br /> <small>''([[:pt:Parque Nacional Marinho de Fernando de Noronha]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Baía dos Porcos - Fernando de Noronha (32811749914).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Fernando de Noronha Marine National Park''' (Portuguese: Parque Nacional Marinho de Fernando de Noronha) is a national park in the state of Pernambuco, Brazil. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:40, 28 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29047614 --> == Tech News: 2025-31 == <section begin="technews-2025-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/31|Translations]] are available. '''Weekly highlight''' * The Community Tech team will be focusing on wishes related to Watchlists and Recent Changes pages, over the next few months. They are looking for feedback. Please [[m:Special:MyLanguage/Community Wishlist/Updates#July 24, 2025: Watchlists and Recent Changes pages|read the latest update]], and if you have ideas, please [[m:Special:MyLanguage/Community Wishlist|submit a wish]] on the topic. '''Updates for editors''' * The Wikimedia Commons community has decided to block [[:mw:Special:MyLanguage/Upload dialog|cross-wiki uploads]] to Wikimedia Commons, for all users without autoconfirmed rights on that wiki, starting on August 16. This is because of [[:c:Commons:Cross-wiki media upload tool/History|widespread problems]] related to files that are uploaded by newcomers. Users who are affected by this will get an error message with a link to the less restrictive UploadWizard on Commons. Please help translating the [[:c:Special:MyLanguage/MediaWiki:Abusefilter-disallowed-cross-wiki-upload|message]] or give feedback on the message text. Please also update your local help pages to explain this restriction. [https://phabricator.wikimedia.org/T370598] * On wikis with temporary accounts enabled and Meta-Wiki, administrators may now set up a footer for the Special:Contributions pages of temporary accounts, similar to those which can be shown on IP and user-account pages. They may do it by creating the page named <code dir=ltr>MediaWiki:Sp-contributions-footer-temp</code>. [https://phabricator.wikimedia.org/T398347] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.12|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2025:Wikimania|Wikimania 2025]] will run from August 6–9. The [https://wikimedia.eventyay.com/talk/wikimania2025/schedule/ program is available] for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please [[wmania:Special:MyLanguage/2025:Registration|register]] for a free virtual ticket. For example, you may be interested in technical sessions such as: ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/KFEFVG/ Temporary Accounts: Enhancing privacy for our unregistered editors] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/TVCVAB/ Building a Sustainable Future for Wikimedia Contributors] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/WTRQCJ/ A dozen visions for wikitext!] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/8YKKP9/ Coordinate Across Stakeholders with the Product and Technology Advisory Council] * The [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2025|MediaWiki Users and Developers Conference, Fall 2025]] will be held 28–30 October 2025 in Hanover, Germany. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:27, 29 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29051727 --> == Wikipedia translation of the week: 2025-32 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Xie Zhiliu]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Xie Zhiliu''' (Chinese: 谢稚柳; 1910–1997) was a leading traditional painter, calligrapher, and art connoisseur of modern China. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:21, 4 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29077280 --> == Tech News: 2025-32 == <section begin="technews-2025-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/32|Translations]] are available. '''Updates for editors''' * Editors can now enable the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/User Info|User Info card]]. This feature adds an icon next to usernames on history pages and similar user-contribution log pages. When you tap or click on the icon, it displays data related to that user account such as the number of edits, reverted edits, blocks, and more. It's part of a broader project to make it easier for moderators to evaluate account trustworthiness. The feature can be enabled in [[testwiki:Special:GlobalPreferences#mw-prefsection-rendering|your global preferences]], and later this week it will be available in local preferences. [https://phabricator.wikimedia.org/T386439] * Everybody is invited to share comments on [[m:Special:MyLanguage/CampaignEvents/Collaborative contributions|Collaborative Contributions]], a project recently launched by the [[m:Special:MyLanguage/Connection Team|Connection team]]. The project aims to create a new way to display the impact of collaborative editing activities (such as edit-a-thons, backlog drives, and WikiProjects) on the wikis. Post your comments on the [[m:Talk:CampaignEvents/Collaborative contributions|project talk page]]. [https://phabricator.wikimedia.org/T378035] * Administrators can now define the default block duration for temporary accounts. To do that, they need to create a page named <code dir=ltr>MediaWiki:Ipb-default-expiry-temporary-account</code> and use a value defined in <code dir=ltr>MediaWiki:Ipboptions</code>. This allows administrators to easily block temporary accounts for 90 days, which is functionally equivalent to an indefinite block. The advantage of this solution is that it does not clutter Special:BlockList. [[mw:Special:MyLanguage/Manual:Block and unblock#Default block duration options|More documentation]] is available. [https://phabricator.wikimedia.org/T398626] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Gadgets can now include <code dir=ltr>.vue</code> files. This makes it easier to develop modern user interfaces using [[mw:Vue.js|Vue.js]], in particular using [[mw:Special:MyLanguage/Codex|Codex]], the official design system of Wikimedia. [[wmdoc:codex/latest/icons/overview.html|Codex icons]] can be loaded through the gadget definition. [[mw:Special:MyLanguage/Extension:Gadgets#Pages|The documentation]] has examples. For user scripts that use Vue.js, an [[mw:API:CodexIcons|API module]] now exists to load Codex icons. [https://phabricator.wikimedia.org/T340460][https://phabricator.wikimedia.org/T311099] * Module developers can now use a [[mw:Help:Extension:Translate/Message Bundles/Lua reference|Lua interface]] to simplify the preparation of Lua modules for translation on Meta-Wiki. This improvement makes it easier for translators to find and edit module strings without dealing with raw Lua code. It helps prevent mistakes that could break the module during translation. Module developers and translators are invited to [[commons:File:Translatable modules video demo July 2025.webm|watch the demo video]], read more about [[mw:Special:MyLanguage/Translatable modules|translatable modules]] to understand how it works, refer to Meta-Wiki's [[m:Module:User Wikimedia project|Module:User Wikimedia project]] for example usage, and [[mw:Talk:Translatable modules|share their feedback]] on how well it addresses the challenges in their workflow. The interface still has some performance issues, so it should not be used in widely used modules yet. [https://phabricator.wikimedia.org/T359918] * Developers of external tools that connect to Wikimedia pages must set a user-agent that complies with [[foundation:Special:MyLanguage/Policy:Wikimedia Foundation User-Agent Policy|the user-agent policy]]. This policy will start to be more strongly enforced in August because of external crawlers that are [[diffblog:2025/04/01/how-crawlers-impact-the-operations-of-the-wikimedia-projects/|overusing]] Wikimedia's resources. Tools that are hosted on Wikimedia's Toolforge or Cloud VPS will not be affected by this for now, but should still set a user-agent. [[phab:T400119|More technical details are available]], and related questions are welcome in that task. * Parsoid Read Views is going to be rolling out to some smaller Wikipedias over the next few weeks, following the successful transition of Wikivoyages and Wiktionaries to Parsoid Read Views. For more information, see the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parsoid/Parser Unification]] project page. [https://phabricator.wikimedia.org/project/profile/7694/] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.13|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2025:Wikimania|Wikimania 2025]] will run from August 6–9. The [https://wikimedia.eventyay.com/talk/wikimania2025/schedule/ program is available] for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please [[wmania:Special:MyLanguage/2025:Registration|register]] for a free virtual ticket. For example, you may be interested in technical sessions such as: ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/GEH9DH/ Wikimedia’s knowledge infrastructure in a changing internet: Establishing sustainable pathways for content reuse] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/7ELN9Q/ Wikifunctions is coming soon to a wiki near you!] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/ZMGVJV/ Shaping the Future of Wikipedia’s Reader Experience] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/KCKTFZ/ Making Wikipedia More Readable: What Comes Next] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:41, 5 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29083927 --> == Wikipedia translation of the week: 2025-33 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lethocerus patruelis]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lethocerus patruelis.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Lethocerus patruelis''''' is a giant water bug in the family Belostomatidae. It is native to southeastern Europe, through Southwest Asia, to Pakistan, India and Burma. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:20, 11 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29085671 --> == Tech News: 2025-33 == <section begin="technews-2025-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/33|Translations]] are available. '''Updates for editors''' * The WikiEditor toolbar now includes [[mw:Special:MyLanguage/Help:Extension:WikiEditor#Keyboard shortcuts|its keyboard shortcuts]] in the tooltips for its buttons. This will help to improve the discoverability of this feature. [https://phabricator.wikimedia.org/T400583] * The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] published a set of [[m:Special:MyLanguage/Product and Technology Advisory Council/August 2025 draft PTAC proposals for feedback|proposed experiments]] the Wikimedia Foundation can try to improve communication with community. Feedback on the proposals are welcomed until August 22 on [[m:Talk:Product and Technology Advisory Council/August 2025 draft PTAC proposals for feedback|this talk page]]. * The search bar on the Minerva skin (mobile) has been updated to use the same type-ahead search component that is used on the Vector 2022 skin. There are no changes in search functionality but there are minor visual changes. Specifically, the close-search button has been changed from an "X" to a back arrow. This helps to distinguish it from the other "X" button that is used to clear any text. [https://phabricator.wikimedia.org/T393944] * Editors on some wikis will see a new toggle for "Group results by page" on watchlist, related changes, and recent changes pages. This is [[mw:Special:MyLanguage/Moderator Tools/Watchlist/Experiment|an A/B experiment]] that is planned to start on August 11, and will run for 3–6 weeks on the Bengali, Chinese, Czech, French, Greek, Portuguese, and Urdu Wikipedias. The experiment will examine how making this feature more discoverable might affect editors' ability to find the edits they are looking for. [https://phabricator.wikimedia.org/T396789] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The multiwiki datasets of [[:wikt:en:Module:Unicode data|Unicode data]] have been moved to [[c:Category:Unicode Module Datasets|Category:Unicode Module Datasets]] on Wikimedia Commons, to follow the idea of "One common data source, multiple local wikis". Most wikis have been updated to use the Commons version. You can ask questions at [[c:Category talk:Unicode Module Datasets|the talkpage]]. [https://en.wiktionary.org/wiki/Module_talk:Unicode_data#Data_from_commons] * Lua code can add warnings when something is wrong, by using the <code dir=ltr>mw.addWarning()</code> function. It is now possible to add more than one warning, instead of new warnings replacing old ones. If you maintain a Lua module that used warnings, you should check it still works as expected. [https://phabricator.wikimedia.org/T398390] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.14|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:30, 11 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29106516 --> == Wikipedia translation of the week: 2025-34 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ikiza]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:CIA map of Burundi and surrounding countries during 1972 killings.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Ikiza''' (variously translated from Kirundi as the Catastrophe, the Great Calamity, and the Scourge), or the Ubwicanyi (Killings), was a series of mass killings—often characterised as a genocide—which were committed in Burundi in 1972 by the Tutsi-dominated army and government, primarily against educated and elite Hutus who lived in the country. Conservative estimates place the death toll of the event between 100,000 and 150,000 killed, while some estimates of the death toll go as high as 300,000. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 18 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29115447 --> == Tech News: 2025-34 == <section begin="technews-2025-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/34|Translations]] are available. '''Updates for editors''' * Later this week, people who are logged-in and have the "[[mw:Special:MyLanguage/Talk pages project/Feature summary|Discussion tools]]" [[Special:Preferences#mw-prefsection-betafeatures|Beta Feature]] enabled will gain the ability to "Thank" individual comments directly from talk pages, rather than needing to navigate to page history. [[mw:Special:MyLanguage/Talk pages project/Feature summary#Comment actions|Learn more about this feature]]. [https://phabricator.wikimedia.org/T400849] * An A/B test comparing two versions of the desktop donate link launched on testwiki on 12 August and on English Wikipedia 14 August for 0.1% of logged out users on the desktop site. The experiment will run for three weeks, ending on 12 September. [https://phabricator.wikimedia.org/T395716] * An A/A test to measure the baseline for reader retention was launched 12 August using [[wikitech:Experimentation Lab|Experimentation Lab]]. This measures the percentage of users who revisit a wiki after their initial visit over a 14-day period. No visual changes are expected. The experiment will run through 31 August. [https://phabricator.wikimedia.org/T399227] * Five new wikis have been created: ** a {{int:project-localized-name-group-wikisource/en}} in [[d:Q34057|Tagalog]] ([[s:tl:|<code>s:tl:</code>]]) [https://phabricator.wikimedia.org/T388639] ** a {{int:project-localized-name-group-wikisource/en}} in [[d:Q36213|Madurese]] ([[s:mad:|<code>s:mad:</code>]]) [https://phabricator.wikimedia.org/T391747] ** a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q3450749|Rakhine]] ([[w:rki:|<code>w:rki:</code>]]) [https://phabricator.wikimedia.org/T392490] ** a {{int:project-localized-name-group-wikibooks/en}} in [[d:Q13324|Minangkabau]] ([[b:min:|<code>b:min:</code>]]) [https://phabricator.wikimedia.org/T395452] ** a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q7598268|Standard Moroccan Amazigh]] ([[wikt:zgh:|<code>wikt:zgh:</code>]]) [https://phabricator.wikimedia.org/T399684] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:46}} community-submitted {{PLURAL:46|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.15|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W34"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:39, 19 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29127690 --> == Wikipedia translation of the week: 2025-35 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Corallite]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Recent azooxanthellate Scleractinia (Cnidaria, Anthozoa) - ZooKeys-227-001-g004.jpeg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''corallite''' is the skeletal cup, formed by an individual stony coral polyp, in which the polyp sits and into which it can retract. The cup is composed of aragonite, a crystalline form of calcium carbonate, and is secreted by the polyp. Corallites vary in size, but in most colonial corals they are less than 3 mm (0.12 in) in diameter. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 25 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29115447 --> == Tech News: 2025-35 == <section begin="technews-2025-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/35|Translations]] are available. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Template authors can now use additional CSS properties, since the CSS sanitizer used by [[mw:Special:MyLanguage/Help:TemplateStyles|TemplateStyles]] was updated. For example: <code>width: fit-content</code>; <code>ruby-align</code>; relative units such as <code>lh</code>; and custom strings in <code>list-style-type</code>. These improvements are a [[m:Special:MyLanguage/Community Wishlist/Wishes/Allow use of modern CSS in templates by updating the TemplateStyles CSS sanitizer|Community Wishlist wish]]. [https://phabricator.wikimedia.org/T271958][https://phabricator.wikimedia.org/T277755][https://phabricator.wikimedia.org/T293633][https://phabricator.wikimedia.org/T295088][https://phabricator.wikimedia.org/T326906][https://phabricator.wikimedia.org/T340057][https://phabricator.wikimedia.org/T360725][https://phabricator.wikimedia.org/T371809][https://phabricator.wikimedia.org/T375344][https://phabricator.wikimedia.org/T394619] * On large wikis, the default time period to display edits from, within the Special:RecentChanges page, has been changed from 7 days to 1 day. This is part of a performance improvement project. This should have no user-facing impact due to the quantity of edits on these wikis. [https://phabricator.wikimedia.org/T399455] * Administrators can now access the [[{{#special:BlockedExternalDomains}}]] page from the [[{{#special:CommunityConfiguration}}]] list page. This makes it easier to find. [https://phabricator.wikimedia.org/T393240] * Wikimedia Commons videos were not shown in the Videos tab in Google Search. The problem was investigated and reported to Google who have now fixed the issue. [https://phabricator.wikimedia.org/T396168][https://meta.wikimedia.org/wiki/Community_Wishlist/Wishes/Do_something_about_Google_%26_DuckDuckGo_search_not_indexing_media_files_and_categories_on_Commons] * One new wiki has been created: a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q33014|Betawi]] ([[wikt:bew:|<code>wikt:bew:</code>]]) [https://phabricator.wikimedia.org/T402130] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:39}} community-submitted {{PLURAL:39|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Two fields of the [[mw:Special:MyLanguage/Manual:Recentchanges table|recentchanges database table]] are being removed. <code>rc_new</code> and <code>rc_type</code> are being removed in favor of <code>rc_source</code>. Queries to these older fields will start to fail starting this week and developers should use <code>rc_source</code> instead. These older fields were deprecated over 10 years ago and should not be in use. This is part of work to improve the performance and stability of queries to the recentchanges table. [https://phabricator.wikimedia.org/T400696] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.16|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/July|Language and Internationalization Newsletter]] is now available. This edition includes: support for new languages in MediaWiki and translatewiki; the start of the Language Onboarding and Development project to help support the growth of new and small wikis; updates on research projects; and more. '''Meetings and events''' * The next [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Community meetings#29 August 2025|Language Community Meeting]] is happening soon, August 29th at [https://zonestamp.toolforge.org/1756479600 15:00 UTC]. This week's meeting will cover: the Avro keyboard developers from Wikimedia Bangladesh, who were recently awarded a national award for their contributions to this keyboard; and other topics. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:13, 26 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29175124 --> == Wikipedia translation of the week: 2025-36 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Diksam Plateau]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Dixam plateau (6407168437).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Diksam Plateau''' or Dixam Plateau (Arabic: دكسم) is a limestone plateau in Socotra, Yemen. The Firmihin forest, located east of the Dirhur canyon within the plateau, has the highest concentration of Dragon's Blood Trees on the entire island. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:40, 1 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29195081 --> == Tech News: 2025-36 == <section begin="technews-2025-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/36|Translations]] are available. '''Weekly highlight''' * The Editing team wants to compile a list of templates, jargon terms, and policies used in edit summaries when a copyright violation is removed. This will help them identify the number of edits reverted due to copyright issues. We invite community members from the following Wikis to list these terms in [[Phab:T402601|T402601]], or to share their list with [[User:Trizek (WMF)|Trizek_(WMF)]]: {{int:project-localized-name-arwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-idwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-plwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ukwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-viwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zhwiki/en}}. This project is open until September 9th 2025. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] has been enabled for all Wikisources. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. The extension has three features: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Special:MyLanguage/Connection Team/Invitation list|Invitation List]]. To request the extension for your wiki, visit the Deployment information page. [https://meta.wikimedia.org/wiki/CampaignEvents/Deployment_status#How_to_Request_the_CampaignEvents_Extension_for_your_wiki] * The lists in the footer of the editing interface, such as "Templates used on this page," will now be organized into columns when there is enough space. This enhancement minimizes scrolling when editing lengthy articles on Wikipedia. [https://phabricator.wikimedia.org/T401066] * On September 3rd, 2025 we will increase the sampling percentages of our [[mw:Special:MyLanguage/Moderator Tools/Watchlist/Experiment#Scope of the experiment|group by toggle experiment]] of the <code>Special:RecentChanges</code>, <code>Special:Watchlist</code>, and <code>Special:RelatedChanges</code> pages on the Chinese, French, and Portuguese Wikipedias to 100 percent, allowing more editors to be part of this experiment. This adjustment is intended to ensure we have sufficient data to make informed decisions when evaluating the experiment results. [https://phabricator.wikimedia.org/T402958][https://phabricator.wikimedia.org/T396789] * Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading on English Wikipedia beginning the week of September 22. The feature will be available on both desktop and mobile. All non-English wikis received this change in June and July. The goal is to make it easier for users to find articles. [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments/Search Suggestions|Learn more]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:37}} community-submitted {{PLURAL:37|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.17|MediaWiki]] '''In depth''' * Wikifunctions now has a new capability called "lightweight enumeration types", an enumeration type is simply a fixed set of values that's in the type's definition. This capability makes it quick and easy to define such a type, and allows for the reuse of values that are already present in Wikidata. Here is [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-07-19|a newsletter]] to learn more. * The latest [[mw:Special:MyLanguage/Readers/Newsletter updates#August 2025: Newsletter #1|Readers Newsletter]] is now available. This edition includes: the formation of two new teams — Reader Growth and Reader Experience; insights into declining pageviews and account creations; highlights from the Wikimania Nairobi panel on improving the reading experience; upcoming experiments to engage new and existing readers; and more. '''Meetings and events''' * Spotlight on some Wikimania 2025 Sessions: ** Identifying AI-generated text by searching for ISBNs whose checksums fail: Mathias Schindler of WMDE [https://www.youtube.com/watch?v=Dw9o8Lsl974&t=15910s shared tools to help communities search for these]. ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/TCHZKH/ La durabilité du mouvement Wikimedia face aux défis actuels et futurs]: This session explored how Wikimedia can stay a trusted source of knowledge in the age of generative AI, information overload, and disinformation. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:51, 1 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29196010 --> == Wikipedia translation of the week: 2025-37 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Ttongsul]]'''<br /> <small>''([[:ja:トンスル]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Ttongsul (imitation).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''ttongsul''' (똥술), o vino di feci, è una tradizionale preparazione medicinale coreana con gradazione alcolica al 9% a base di feci, solitamente umane e preferibilmente di bambino. Nato probabilmente traendo spunto dalla medicina tradizionale cinese, nelle credenze popolari il vino di feci avrebbe proprietà benefiche per molti tipi di malesseri: sarebbe un rimedio per dolori muscolari, ustioni, infiammazioni, epilessia e fratture ossee. Sebbene alcuni media occidentali abbiano in passato riportato che questa bevanda sia diffusa tra la popolazione coreana, al giorno d'oggi un numero molto limitato di persone ne fa uso, dopo aver subito un declino di popolarità nei secoli scorsi, tanto che la maggioranza dei giovani coreani non ne ha mai sentito parlare. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:28, 8 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29195081 --> == Tech News: 2025-37 == <section begin="technews-2025-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/37|Translations]] are available. '''Weekly highlight''' * The Editing team is working on a new check: [[mw:Special:MyLanguage/Paste check|Paste check]]. This check informs newcomers who paste text into Wikipedia that the content might not be accepted. This check is an effort to increase the likelihood that the new content people are adding to Wikipedia is aligned with the Movement's commitment to offering information under a free content license. This check will soon be tested at a few wikis. If your community is interested in this test, please [[phab:T403680|tell us in this task]], or [[mw:Talk:Edit check|contact the team]]. '''Updates for editors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Later this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will be able to use a [[w:en:Lint (software)|linting tool]] to see errors or other potential problems in wikitext in real time. See the [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|help page for more information]]. [https://phabricator.wikimedia.org/T381577] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] When browsing a wiki (like <code dir=ltr>en.wikipedia.org</code>), the software responds in one of two ways: a desktop page, or a redirect to a mobile version on an "m" domain (like <code dir=ltr>en.m.wikipedia.org</code>). Over the next three weeks, MediaWiki will start displaying the mobile version to mobile devices directly on the standard domain, without this redirect. This change does not affect existing m-dot URLs, or the "Desktop view" opt-out. [[mw:Requests for comment/Mobile domain sunsetting/2025 Announcement|Learn more]]. [https://phabricator.wikimedia.org/T214998] * When an edit changes the categories of a page, the changes to the category membership counts are now happening asynchronously. This improves the speed of saving edits, especially when moving many pages to or from the same category, and reduces the risk of site outages, but it means that the counts can show outdated information for a few minutes. [https://phabricator.wikimedia.org/T365303] * Edits on Wikidata to qualifiers (properties and values) and references (properties and values) in a Wikidata item statement will now not add entries to the RecentChanges or Watchlist pages on all other Wikis. This is a temporary change to improve performance while other solutions are created. Wikidata's own pages remain unchanged. [[m:Wikidata For Wikimedia Projects/Reduce change propagation noise#Phase 1: Turn off (temporarily) Qualifiers and References Wikidata edits to the Recent Changes tables|Learn more]]. [https://phabricator.wikimedia.org/T401286][https://phabricator.wikimedia.org/T400698] * Japanese-language wikis have had a major upgrade to the way that search works. The new search should generally give more accurate and more relevant search results. [https://phabricator.wikimedia.org/T318269] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.18|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:15, 9 September 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29238161 --> == Wikipedia translation of the week: 2025-38 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pak Kum-chol]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pak Kum-chol in 1961 (cropped).jpg|center]] <div style="text-align:left; padding: .4em;"> '''Pak Kum-chol''' was a North Korean politician. Having been a guerrilla during the anti-Japanese struggle, he became a high-ranking politician after the liberation of Korea. Pak aligned himself with his former guerrilla brothers in arms from the Kapsan Operation Committee to form a faction within the ruling Workers' Party of Korea (WPK) called the "Kapsan faction". This faction sought to replace Kim Il Sung with Pak. Kim retaliated by purging the faction in 1967 in what is known as the Kapsan faction incident. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 15 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29249252 --> == Tech News: 2025-38 == <section begin="technews-2025-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/38|Translations]] are available. '''Updates for editors''' * References lists that are made using the <code dir=ltr><nowiki><references/></nowiki></code> [[mw:Special:MyLanguage/Help:Cite#references-tag|tag]] will now automatically display with columns in Vector 2022 when readers are using its 'standard' settings for text-size and page-width. [https://phabricator.wikimedia.org/T334941] * Starting in the week of October 6, on [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/small.dblist|small wikis]] and [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/medium.dblist|medium wikis]] that have the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] enabled, all autoconfirmed users will be able to use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] as an organizer. No changes will be made for [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/large.dblist|large wikis]] unless requested in Phabricator. This change is being made to make it easier for more people to use Event Registration, especially on wikis that are less likely to have policies related to the Event Organizer right. [[m:Special:MyLanguage/CampaignEvents/Proposal to grant autoconfirmed users on small and medium wikis the organizer access to the event registration tool|Learn more]]. * Users that search using regular expressions (regex) can now use additional features including: ** for the <code dir=ltr>intitle:</code> keyword: [[mw:Special:MyLanguage/Help:CirrusSearch#Metacharacters|metacharacters]] for start-of-line (<code dir=ltr>^</code>) and end-of-line (<code dir=ltr>$</code>) anchors [https://phabricator.wikimedia.org/T317599] ** for both <code dir=ltr>intitle:</code> and <code dir=ltr>insource:</code> keywords: shorthand [[mw:Special:MyLanguage/Help:CirrusSearch#Character_Classes|character classes]] for digits (<code dir=ltr>\d</code>), whitespace (<code dir=ltr>\s</code>), and word characters (<code dir=ltr>\w</code>); and [[mw:Special:MyLanguage/Help:CirrusSearch#Escape codes|escape codes]] for line feed (<code dir=ltr>\r</code>), newline (<code dir=ltr>\n</code>), tab (<code dir=ltr>\t</code>), and unicode (e.g. <code dir=ltr>\uHHHH</code>). [https://phabricator.wikimedia.org/T403212] * When you search for text that looks like an IP, the system will now show search results. It used to take you to the contributions for that IP instead of showing search results. [https://phabricator.wikimedia.org/T306325] * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on September 24. This is planned at [https://zonestamp.toolforge.org/1758726000 15:00 UTC]. This is for the datacenter server switchover backup tests which happen twice a year. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the background and details of this process on the Diff blog]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that affected users who used the page-tabs to switch from wikitext editing of a section into the visualeditor. [https://phabricator.wikimedia.org/T401043] '''Updates for technical contributors''' * The MediaWiki Interfaces team is redesigning the Wikimedia REST API Sandbox with Codex. If you have feedback on improvements for the API documentation or what makes developer experiences smooth (or frustrating), you’re invited to [https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ2aZzbXeQvjOF7gB1fJXiwAYemQjKf4sXNaRODPA7_obFyNBwkzNkoVCoTF-aeov89kIjXHbCQm join an upcoming discovery interview], or [[mw:MediaWiki Interfaces Team/Developer Feedback/Wikimedia Web APIs|leave feedback onwiki]]. [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/C4FBAOA57PH6G5ORVMAUF5TGYBLZDU5Q/|Learn more]]. * Edits to Wikidata aliases (an alternative name for an item or a property) will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. [[m:Wikidata For Wikimedia Projects/Reduce change propagation noise#Phase 1: More granular Alias tracking|Learn more]]. [https://phabricator.wikimedia.org/T401288] * The new [https://www.unicode.org/versions/Unicode17.0.0/ Unicode 17.0] version has been released. The [[:c:Category:Unicode Module Datasets|datasets on Commons]] for the [[:d:Q39301585|Module:Unicode data]] have been updated. Wikipedias that do not use the Commons datasets should either update their own data or switch to the Commons datasets. * Users of the [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] Structured Contents endpoints can now access [https://enterprise.wikimedia.com/blog/parsed-wikipedia-tables/ Parsed Tables]. The new Parsed Tables feature extracts and represents Wikipedia tables in structured JSON. This improves machine accessibility as part of the [https://enterprise.wikimedia.com/api/structured-contents/ Structured Contents initiative]. Structured Contents output is freely available through the [https://enterprise.wikimedia.com/docs/on-demand/#article-structured-contents-beta On-demand API], or through Wikimedia Cloud Services. * A [https://www.kaggle.com/datasets/wikimedia-foundation/english-wikipedia-people-dataset dataset of English Wikipedia biographical information] from [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] has been published on Kaggle, for evaluation and research. This provides structured data from more than 1.5 million biographies, including birth and death dates, education, affiliations, careers, awards, and more (from a June 2024 snapshot). * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.19|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2026:Scholarships|Scholarship applications]] for Wikimania 2026 in Paris, France, are open until October 31. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:08, 15 September 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29263921 --> == Wikipedia translation of the week: 2025-39 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Federation of Central America (1921–1922)]]'''<br /> <small>''([[:es:Federación de Centro América (1921-1922)]])&#32;([[:ar:اتحاد أمريكا الوسطى (1921-1922)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Central America's Northern Triangle (orthographic projection).png|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Federation of Central America''' (Spanish: Federación de Centro América)[1] was a short-lived federal republic that existed in Central America between 1921 and 1922. The federation consisted of the Central American nations of El Salvador, Guatemala, and Honduras. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:45, 22 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29311347 --> == Tech News: 2025-39 == <section begin="technews-2025-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/39|Translations]] are available. '''Weekly highlight''' * [https://zonestamp.toolforge.org/1758726000 On September 24th at 15:00 UTC], all Wikimedia sites users will experience a brief read-only period due to a scheduled [[m:Special:MyLanguage/Tech/Server switch|datacenter server switchover]]. The Wikimedia Foundation's Site Reliability Engineering (SRE) team will redirect all traffic from one primary server to its backup. You can listen to the switchover using the [http://listen.hatnote.com/ "Listen to Wikipedia"] tool, where you will hear edits stop for a few minutes during the read-only phase, then resume. This twice-yearly datacenter server switchover ensures reliability by testing the backup datacenter, so that our sites can stay online even if the primary datacenter fails. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the process on the Diff blog]]. '''Updates for editors''' * Editors of [[f:Special:Mylanguage/Wikifunctions:Status updates/2025-09-12#Next round of Wiktionaries to receive embedded Wikifunctions calls|60 more Wiktionaries]] will soon be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them into their pages. A function takes one or more inputs and transforms them into a desired output, like adding numbers, converting miles to meters, calculating elapsed time, or declining a word into a case. They will join the other [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-29#Wikifunctions available on 65 Wiktionaries|65 Wiktionary language editions]], which already have access to embedded Wikifunctions calls. Later this year, plans are in place to expand to more Wiktionaries and the Incubator. * A new [[mw:Special:MyLanguage/Help:Magic words#Technical metadata of another page|parser function]] has been added: <code><nowiki>{{#contentmodel}}</nowiki></code>. Template editors and admins can use it to get the localized or canonical name of the [[mw:Special:MyLanguage/Help:ChangeContentModel|content model]] of a specific page. The function makes it easier to create and edit system messages, such as ''MediaWiki:editinginterface'', even when you switch types of pages, like wiki, JavaScript, CSS or JSON page. [https://phabricator.wikimedia.org/T328254] * Adding or editing a <code>DISPLAYTITLE</code> for an article using VisualEditor will no longer be broken. Editors who use VisualEditor mode to modify the <code><nowiki>{{DISPLAYTITLE}}</nowiki></code> would no longer have the literal text "DISPLAYTITLE" or its localized variant added to their articles. A list of pages that may have been affected and might need cleanup is documented in [[phab:P83438|this ticket]]. * Beta users of the Wikipedia Android app can now try the redesigned [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Activity Tab Experiment|Activity tab]], which replaces the Edits tab. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:12}} community-submitted {{PLURAL:12|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.20|MediaWiki]] '''In depth''' * Wikifunctions users can now import many essential facts involving [[f:Special:MyLanguage/Z6011|geo-coordinates]], [[f:Special:MyLanguage/Z6010|quantities]] and [[f:Special:MyLanguage/Z6064|time]] values from Wikidata. This is made possible by the creation of Wikifunctions types for these values, which makes them available for use by functions in Wikifunctions. Learn more about how this works in [[c:File:ImportingWikidataDatatypesIntoWikifunctions.webm|this video]] and Wikifunctions' [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-01#News in Types I: Wikidata quantity|August 1 newsletter]] (for quantities) and [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-22#News in Types: Wikidata geo-coordinate|August 22 newsletter]] (for geo-coordinates). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:56, 22 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29305556 --> == Wikipedia translation of the week: 2025-40 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Palazzo delle Poste (Latina)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Postelittoria2.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''Palazzo delle Poste''', fino al 1945 Ricevitoria Postelegrafonica di Littoria, è un edificio postale di Latina, situato in piazzale dei Bonificatori. Costruito nel 1932 in stile razionalista con influenze futuriste, riscontrabili nell'utilizzo di ampie superfici vetrate e di volumi verticali, oltre che per la presenza di l’utilizzo di materiali e scelte di design molto in voga all'epoca come, come i mattoni a vista, il travertino di Tivoli e l'Anticorodal (una lega di alluminio), ospita l'ufficio postale Latina Centro. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:58, 29 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-40 == <section begin="technews-2025-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/40|Translations]] are available. '''Weekly highlight''' * A major software upgrade has been made to [[phab:|Phabricator]]. The update introduces performance improvements, a refreshed search interface, enhancements to Maniphest task search, updates to user profile pages and project workboards, new Herald automation features, as well as general text input, mobile experience improvements and more. [https://phabricator.wikimedia.org/phame/post/view/321/iterative_improvements_september_2025/] '''Updates for editors''' * The Community Tech team will release the new Community Wishlist extension on October 1, that will improve the way wishes will be submitted. The new extension will allow users to add tags to their wishes to better categorise them, and (in a future iteration) to filter them by status, tags and focus areas. It will also be possible to support individual wishes again, as requested by the community in many instances. The old system will be retired. There will be a brief period of downtime while the extension is deployed and wishes are migrated to the new system. You can read more about this [[:m:Special:MyLanguage/Community Wishlist/Updates|in the latest update]] or you can consult the [[:mw:Special:MyLanguage/Help:Extension:CommunityRequests|current documentation on MediaWiki]]. * As announced [[diffblog:2025/09/02/better-detecting-bots-and-replacing-our-captcha/|on Diff blog]], the production trial of the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/hCaptcha|hCaptcha]] service for bot detection has begun. The trial is currently using hCaptcha to protect account creation on Chinese, Persian, Portuguese, Indonesian, Japanese, and Turkish Wikipedias, where it will replace our existing [[mw:Special:MyLanguage/Extension:ConfirmEdit#FancyCaptcha|CAPTCHA]] (FancyCaptcha). The goal with the trial is to better block bots while also improving usability and accessibility for users who encounter CAPTCHA challenges. * The [[mw:Special:MyLanguage/Extension:CampaignEvents|CampaignEvents]] extension has been [[m:Special:MyLanguage/CampaignEvents/Deployment status|deployed]] to Wikimedia Commons. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. On Commons, anyone who is a registered user can use it as an event participant. To use it as an organizer, someone needs to have the [[c:Special:MyLanguage/Commons:Event organizers|event organizer right]]. * [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new feature to re-use references with different details has been released to German Wikipedia. You can [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#test|test the feature]] on testwiki or [https://en.wikipedia.beta.wmcloud.org/wiki/Sub-referencing on betawiki] as well. Please share your thoughts on [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Templates used in sub-references|using templates in sub-references]] or [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Pilot wikis|volunteer to become a pilot wiki]]. * On wikis using the [[mw:Special:MyLanguage/Help:Growth/Mentorship|Mentorship]] system, communities can now opt experienced editors out of Mentorship through [[{{#special:CommunityConfiguration/Mentorship}}]]. Within this setting, communities may define thresholds, based on edit count and account age, to decide when an editor is considered experienced enough to no longer receive Mentorship. [https://phabricator.wikimedia.org/T403563] * The Editing Team and the Machine Learning Team are working on a new check for newcomers: [[mw:Special:MyLanguage/Edit check/Tone Check|Tone check]]. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Tone language model for the following languages: Arabic, Czech, German, Hebrew, Indonesian, Dutch, Polish, Russian, Turkish, Chinese, Farsi, Italian, Norwegian, Romanian and Latvian. Users from these wikis interested in reviewing this model are [[mw:Special:MyLanguage/Edit_check/Tone_Check/Model_evaluation|invited to sign up at MediaWiki.org]]. The deadline to sign up is on October 3, which will be the start date of the test. * The rollout of [[:mw:Special:MyLanguage/Help:Manage blocks|multiblocks]] had the side effect that non-active block logs may have been shown on {{#special:Contributions}} and on blocked users' user and user_talk pages. This issue will be fully resolved in a few days. As part of the fix, [{{fullurl:Special:Allmessages|prefix=sp-contributions-blocked-notice}} messages prefixed with <code>sp-contributions-blocked-notice</code>] will be removed and replaced with [{{fullurl:Special:Allmessages|prefix=blocked-notice-logextract}} those prefixed with <code>blocked-notice-logextract</code>] in a few weeks. Please help translate the new messages and update any local overrides if needed. * There was a bug with links added using visual editor if they included characters such as <code dir=ltr><nowiki>[ ] |</nowiki></code> after the fragment identifier (<code><nowiki>#</nowiki></code>). They were not encoded properly creating an incorrect link. This has been fixed. [https://phabricator.wikimedia.org/T404823] * One new wiki has been created: a {{int:project-localized-name-group-wikiquote/en}} in [[d:Q9237|Malay]] ([[q:ms:|<code>q:ms:</code>]]) [https://phabricator.wikimedia.org/T404698] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/User Info|User Info Card]] now displays currently active global lock/blocks. [https://phabricator.wikimedia.org/T401128] '''Updates for technical contributors''' * Later this week, editors using Lua modules will be able to use the <code>[[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#mw.title.newBatch|mw.title.newBatch]]</code> function to look up the existence of up to 25 pages at once, in a way that only increases the [[mw:Special:MyLanguage/Manual:Parser functions#Expensive parser functions|expensive function]] count once. * A new [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|Unsupported Tools Working Group]] has been formed as part of ongoing efforts to collectively determine technical work priorities, similar to the [[m:Special:MyLanguage/Product and Technology Advisory Council|Product & Technology Advisory Council]] (PTAC). The working group will help prioritize and review requests for support of unmaintained extensions, gadgets, bots, and tools. For the first cycle, the group will be prioritizing an unsupported Wikimedia Commons tool. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.21|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:54, 29 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29355230 --> == Wikipedia translation of the week: 2025-41 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Majed Abu Maraheel]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Majed Abu Maraheel''' was a Palestinian long-distance runner, football player, security officer, and athletics coach, who was the first Palestinian to compete at the Olympic Games. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:48, 6 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-41 == <section begin="technews-2025-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/41|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Help:Edit check#paste|Paste Check]] is a new Edit Check feature to help avoid and fight copyright violations. When editors paste text into an article, Paste Check prompts them to confirm the origin and licensing of the content. Starting Wednesday, 8 October, [[phab:T403680|22 wikis will test Paste Check]]. Paste Check will help new volunteers understand and follow the policies and guidelines necessary to make constructive contributions to Wikipedia projects. '''Updates for editors''' * Mobile devices will receive mobile articles directly on the standard domain (like <code>en.wikipedia.org</code>), instead of via a redirect to an "m" domain (like <code>en.m.wikipedia.org</code>). This change improves performance. This week it will be enabled on Wikipedias. The existing mobile URLs and the "Desktop view" opt-out remain available. [[mw:Requests for comment/Mobile domain sunsetting/2025 Announcement|Learn more]]. [https://phabricator.wikimedia.org/T214998] * New [[mw:Special:MyLanguage/Help:CirrusSearch#creationdate and lasteditdate|date filters]], <code dir=ltr>creationdate:</code> and <code dir=ltr>lasteditdate:</code>, are now available in the wiki search engine. This allows users to filter search results by a page's first or last revision date. The filters support comparison operators (e.g. <code dir=ltr>>2024</code>) and relative dates (e.g. <code dir=ltr>today-1d</code>), making it easier to find recently updated content or pages within specific age ranges. [https://phabricator.wikimedia.org/T403593] * [[f:|Wikifunctions]] now supports rich text in embedded calls across the 150 wikis where it's enabled. To showcase this, the team created a [[f:Z26333|Latin declination table]] that Wiktionary editors can use to automatically generate noun forms, producing clear, formatted results — see an [[f:Wikifunctions:Embedded function calls/Wiktionary tables demonstration|example output]]. If you need any help or have any feedback, please [[f:Wikifunctions:Project chat|contact the Wikifunctions Team]]. [https://phabricator.wikimedia.org/T397402] * An edit link will now appear inside the categories box on article pages for logged in users, which will directly launch the VisualEditor category dialog. [https://phabricator.wikimedia.org/T291691] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:34}} community-submitted {{PLURAL:34|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a problem downloading pdf files last week and that has been resolved. [https://phabricator.wikimedia.org/T405957] '''Updates for technical contributors''' * The field <code dir=ltr>rev_sha1</code> in the revision database table is being removed in favor of <code dir=ltr>content_sha1</code> in the content database table. See [https://lists.wikimedia.org/hyperkitty/list/cloud@lists.wikimedia.org/thread/2D2M3SP4WHR6BXXKTZ2PBLZQYR3EGQVR/ the announcement] for more information. * The [[mw:Special:MyLanguage/Reading/Web|Reader Experience team]] will roll out [[w:en:Light-on-dark color scheme|Dark Mode]] user interface on all Wikimedia sites on October 29, 2025. All anonymous users of Wikimedia sites will have the option to activate a color scheme that features light-colored text on a dark background. This is designed to provide a more comfortable reading experience, especially in low-light situations. Template authors and technical contributors are encouraged to [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-04|learn how to make pages ready for Dark mode]] and address any compatibility issues found in templates in their wiki before the enablement. Please contact the Web team for questions or any support on [[mw:Talk:Reading/Web/Accessibility for reading#|this talk page]] before the enablement. [https://phabricator.wikimedia.org/T395628] * Starting on Monday, October 6, API endpoints under the <code>rest.php</code> path will be rerouted through a new internal API Gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the [[phab:tag/serviceops/|Service Ops team board]]. [https://phabricator.wikimedia.org/T400130] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:24, 6 October 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29400897 --> == Wikipedia translation of the week: 2025-42 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Abortion in Eritrea]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In Eritrea, abortion is banned except on the grounds of pregnancy from rape or incest, pregnancy of a minor, or risk to physical or mental health. Legal abortions require medical or judicial approval. Prior to Eritrea's independence, it applied Ethiopia's abortion law of the 1950s, which banned abortion unless life-saving. After independence, the 1991 penal code adapted this law to lift punishments on abortions on the grounds of rape, incest, or risk to life or health, but legal abortions did not exist in effect. The penal codes of 2001 and 2015 required physicians to prove health grounds for abortion. Unsafe abortion is common and contributes to maternal mortality in Eritrea. Post-abortion care is unavailable in some regions. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:06, 13 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-42 == <section begin="technews-2025-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/42|Translations]] are available. '''Weekly highlight''' * Last week, improvements to account security and two-factor authentication (2FA) features were enabled across all wikis. These changes include user interface improvements for [https://auth.wikimedia.org/metawiki/wiki/Special:AccountSecurity Special:AccountSecurity], the support of multiple 2FA methods via authenticator apps and portable security keys (previously users could only enable one method), and a new Recovery Codes module which facilitates fewer account lockouts due to lost two-factor apps and devices. As part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project, work is continuing through the rest of 2025 on further user experience improvements, and support for passkeys as an alternate second factor. '''Updates for editors''' * Another part of the Account security project is making 2FA generally available to all users. Along with editors with advanced privileges, such as administrators and bureaucrats, 40% of editors now have access to 2FA. You can check if you have access at [https://auth.wikimedia.org/metawiki/wiki/Special:AccountSecurity Special:AccountSecurity]. Instructions for activation are on the linked page. The plan is to continue increasing availability if it is determined that the user support capabilities are able to support global usage. [https://phabricator.wikimedia.org/T400579] * This week, users at wikis where talk page [[mw:Special:MyLanguage/Talk pages project/Usability|Usability Improvements]] are already available by default (everywhere ''except'' the 12 wikis listed in [[phab:T379264|T379264]]) will gain the ability to Thank a comment directly from the talk page it appears on. Before this change, Thanking could only be done by visiting the revision history of the talk page. You can [[diffblog:2025/10/13/revolutionizing-gratitude-a-new-era-of-thanking-comments/|learn more about this change]]. [https://phabricator.wikimedia.org/T366095] * Users who have not [[Special:Preferences#mw-prefsection-personal-email|verified their email address]] will soon be receiving monthly Notification reminders to do so. This is because users who have verified their email can more easily recover their account. These reminders will not be sent if the user is inactive or removes the unverified email from their account. [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Email_confirmation][https://phabricator.wikimedia.org/T58074] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a fix was made for an occasional error with saving translated paragraphs in the Content Translation tool, and the related error messages are now easier to see. [https://phabricator.wikimedia.org/T376531] '''Updates for technical contributors''' * The Unsupported Tools Working Group has chosen [[c:Special:MyLanguage/Commons:Video2commons|Video2Commons]] as the first tool for its pilot cycle. The group will explore ways to improve and sustain the tool over the coming months. [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|Learn more on Meta]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.23|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:00, 13 October 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29434481 --> == Wikipedia translation of the week: 2025-43 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Liberation of Auschwitz concentration camp]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Auschwitz Liberated January 1945.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> On 27 January 1945, Auschwitz—a Nazi concentration camp and extermination camp in occupied Poland where more than a million people were murdered as part of the Nazis' "Final Solution" to the Jewish question—was liberated by the Soviet Red Army during the Vistula–Oder Offensive. Although most of the prisoners had been forced onto a death march, about 7,000 had been left behind. The Soviet soldiers attempted to help the survivors and were shocked at the scale of Nazi crimes. The date is recognized as International Holocaust Remembrance Day. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 20 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29452019 --> == Tech News: 2025-43 == <section begin="technews-2025-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/43|Translations]] are available. '''Updates for editors''' * To optimize how user data is stored in our databases, the saved preferences of users who haven't logged in for over five years and have fewer than 100 edits will be cleared. When those users return, default settings will apply. [https://phabricator.wikimedia.org/T406724] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a broken link from the GlobalContributions interface message to the XTools GlobalContributions page which has now been fixed. [https://phabricator.wikimedia.org/T406415] '''Updates for technical contributors''' * The work to reroute all traffic to API endpoints under the <code dir=ltr><nowiki>rest.php</nowiki></code> route through a common API gateway is now complete. If any issues are observed, please file a phabricator ticket to the [[phab:tag/serviceops/|Service Ops team board]]. * Edits to Wikidata references or qualifiers will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. [https://phabricator.wikimedia.org/T401290] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.24|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:37, 20 October 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29478670 --> == Wikipedia translation of the week: 2025-44 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Black Diaries]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Black Diaries''' are diaries purported to have been written by the Irish revolutionary Roger Casement, which contained accounts of homosexual liaisons with young men. They cover the years 1903, 1910 and 1911 (two) and were handed in to Scotland Yard after his capture in April 1916. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:51, 27 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29487357 --> == Tech News: 2025-44 == <section begin="technews-2025-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/44|Translations]] are available. '''Updates for editors''' * The Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You can [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Tabbed Browsing (Tabs)/New Tab Experience and Recommendations Experiment|read more on the project page]]. * Autoconfirmed users on [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/small.dblist|small]] and [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/medium.dblist|medium wikis]] with the CampaignEvents extension can now use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed. [https://phabricator.wikimedia.org/T402285] '''Updates for technical contributors''' * The CampaignEvents extension will be deployed to all remaining wikis during the week of 17 November 2025. The extension currently includes three features: Event Registration, Collaboration List, and Invitation List. For this rollout, Invitation List will not be enabled on Wikifunctions and MediaWiki unless requested by those communities. [[m:Special:MyLanguage/CampaignEvents/Deployment status|Visit the deployment page to learn more]]. * The SwaggerUI-based REST sandbox experience is now live on all wiki projects. The sandbox can be accessed through the [[{{#special:RestSandbox}}]] page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on the [[mw:Special:MyLanguage/MediaWiki Interfaces Team/Feature Feedback/REST Sandbox|project launch]] page. [https://phabricator.wikimedia.org/project/board/6931/] * Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using the [https://test.wikipedia.org/w/index.php?api=mw-extra&title=Special%3ARestSandbox REST Sandbox]. See the [[mw:API/Deprecation|MediaWiki REST API Deprecation]] page for more detailed information about the API deprecation policies and procedures. * A dedicated [[mw:API:REST API/Changelog|changelog now exists for the MediaWiki REST API]]. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, please [[mw:API talk:REST API/Changelog|join the discussion]]. * Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked from [[d:Q130635582#sitelinks-wikipedia|Q130635582]]. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited. [https://phabricator.wikimedia.org/T378352] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.25|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:32, 27 October 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29513638 --> |} == Wikipedia translation of the week: 2025-45 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Consolations (Liszt)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Franz Liszt - Consolation No. 3, Lento placido.ogg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Consolations''', S. 171a/172 (German: Tröstungen) are a set of six solo piano works by Franz Liszt. The compositions take the musical style of nocturnes with each having its own distinctive style. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 3 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29558323 --> == Tech News: 2025-45 == <section begin="technews-2025-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/45|Translations]] are available. '''Updates for editors''' * Administrators will now find that [[{{#special:MergeHistory}}]] is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). [https://phabricator.wikimedia.org/T382958] * For users with "{{int:discussiontools-preference-autotopicsub}}" [[Special:Preferences#mw-prefsection-editing|enabled in their preferences]], starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "{{int:Skin-action-addsection}}" or "{{int:Discussiontools-replybutton}}" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time. [https://phabricator.wikimedia.org/T290778] * Scribunto modules can now be used to [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#SVG library|generate SVG images]]. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files. [https://phabricator.wikimedia.org/T405861] * Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. [https://phabricator.wikimedia.org/T395628] * Users with large watchlists have long faced timeouts when editing [[Special:EditWatchlist|Special:EditWatchlist]]. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. A [https://meta.wikimedia.org/wiki/Community_Wishlist/W454 community wish] has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish! [https://phabricator.wikimedia.org/T41510] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query. [https://phabricator.wikimedia.org/T407318] '''Updates for technical contributors''' * Since 2019 the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]] at https://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means <code>/s/</code> URLs will not be advertised under article titles via HTML <code dir=ltr>class="title-shortlink"</code>. The <code>/s/</code> URLs will keep working. [https://phabricator.wikimedia.org/T107188] * On Thursday, October 30, the [[:mw:Special:MyLanguage/MediaWiki Interfaces Team|MediaWiki Interfaces]] and [[:mw:Special:MyLanguage/Wikimedia Site Reliability Engineering|SRE Service Operations]] teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the [https://phabricator.wikimedia.org/tag/serviceops/ Service Ops team] board. * MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/SMWTEAES4SDLDUSK4HMWNBSKNCXZAWYN/] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.26|MediaWiki]] '''In depth''' * In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia in [[diffblog:2025/10/17/new-user-trends-on-wikipedia/|a Diff blog post]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:35, 3 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29552512 --> == Wikipedia translation of the week: 2025-46 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Marine coastal ecosystem]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Vegetation and fauna processes controlling benthic biogeochemical fluxes.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> A '''marine coastal ecosystem''' is a marine ecosystem which occurs where the land meets the ocean. Worldwide there is about 620,000 kilometres (390,000 mi) of coastline. Coastal habitats extend to the margins of the continental shelves, occupying about 7 percent of the ocean surface area. Marine coastal ecosystems include many very different types of marine habitats, each with their own characteristics and species composition. They are characterized by high levels of biodiversity and productivity. For example, estuaries are areas where freshwater rivers meet the saltwater of the ocean, creating an environment that is home to a wide variety of species, including fish, shellfish, and birds. Salt marshes are coastal wetlands which thrive on low-energy shorelines in temperate and high-latitude areas, populated with salt-tolerant plants such as cordgrass and marsh elder that provide important nursery areas for many species of fish and shellfish. Mangrove forests survive in the intertidal zones of tropical or subtropical coasts, populated by salt-tolerant trees that protect habitat for many marine species, including crabs, shrimp, and fish. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 10 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29584005 --> == Tech News: 2025-46 == <section begin="technews-2025-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/46|Translations]] are available. '''Updates for editors''' [[File:Talk pages default look (April 2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * Starting November 12, users will see a change in the [[m:Special:MyLanguage/Talk pages project/Feature summary#Usability improvements|appearance of talk pages]] on [[Phab:T379264|some Wikipedias]]. Almost [[phab:T392121|all wikis]] have received this design change; [[phab:T409297|English Wikipedia]] will get these changes later. You can read more [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. Users can opt out of these changes [[Special:Preferences#mw-prefsection-editing|in their user preferences]] in "{{int:discussiontools-preference-visualenhancements}}". [https://phabricator.wikimedia.org/T379264] * MediaWiki can now display a [[mw:Special:MyLanguage/Help:Protection indicators|page indicator]] automatically while a page is protected. This feature is disabled by default. It can be enabled by [[m:Special:MyLanguage/Requesting wiki configuration changes|community request]]. [https://phabricator.wikimedia.org/T12347] * Using the "{{int:showpreview}}" or "{{int:showdiff}}" buttons in the wikitext editor will now carry over certain URL parameters like '[[mw:Special:MyLanguage/Manual:Parameters to index.php#useskin|useskin]]', '[[mw:Special:MyLanguage/Manual:Parameters to index.php#uselang|uselang]]' and '[[mw:Special:MyLanguage/Help:Section#Editing sections|section]]'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content. [https://phabricator.wikimedia.org/T62744][https://phabricator.wikimedia.org/T24029][https://phabricator.wikimedia.org/T155097] * Wikivoyage wikis can use [[mw:Special:MyLanguage/Help:Extension:Kartographer#Markers and counters|colored map markers in the article text]]. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed. [https://phabricator.wikimedia.org/T369454] * The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. [https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Activity_Tab_Experiment] * The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis. [https://www.mediawiki.org/wiki/Readers/Reader_Growth/WE3.1.3_Image_Browsing] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example the inability to lock accounts on mobile sites has been fixed. [https://phabricator.wikimedia.org/T256185] '''Updates for technical contributors''' * [[wikitech:Help talk:Toolforge/Toolforge standards committee#November 2025 committee nominations|Nominations are open on Wikitech]] for new [[wikitech:Help:Toolforge/Toolforge standards committee|Toolforge standards committee]] members. The committee oversees the Toolforge [[wikitech:Help:Toolforge/Right to fork policy|Right to fork policy]] and [[wikitech:Help:Toolforge/Abandoned tool policy|Abandoned tool policy]] among other duties. Nominations will remain open through 2025-11-28. * The [[w:JSON Web Token#Standard fields|JWT issuer field]] in [[mw:Special:MyLanguage/OAuth/For Developers#OAuth 2|OAuth 2 access tokens]] for [[m:Special:MyLanguage/Help:Unified login|SUL wikis]] has been changed to <code><nowiki>https://meta.wikimedia.org</nowiki></code>. Old access tokens will still work. [https://phabricator.wikimedia.org/T399199] * The [[w:JSON Web Token#Standard fields|JWT subject field]] in [[mw:Special:MyLanguage/OAuth/For Developers#OAuth 2|OAuth 2 access tokens]] will soon change from <code><user id></code> to <code dir=ltr style="white-space:nowrap">mw:<identity type>:<user id></code>, where <code><identity type></code> is typically <code dir=ltr>CentralAuth:</code><!-- not a typo --> (for [[m:Special:MyLanguage/Help:Unified login|SUL wikis]]) or <code dir=ltr style="white-space:nowrap">local:<wiki id></code> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and the <code>sessionJwt</code> cookie more similar. Old access tokens will still work. [https://phabricator.wikimedia.org/T399199] * MediaWiki's block messages ([[MediaWiki:Blockedtext|blockedtext]], [[MediaWiki:Blockedtext-partial|blockedtext-partial]], [[MediaWiki:Autoblockedtext|autoblockedtext]], [[MediaWiki:Systemblockedtext|systemblockedtext]], [[MediaWiki:Blockedtext-tempuser|blockedtext-tempuser]], [[MediaWiki:Autoblockedtext-tempuser|autoblockedtext-tempuser]]) now support additional parameters indicating whether the user is blocked from editing their own user talk page <code><nowiki>$9</nowiki></code> or emailing other users <code><nowiki>$</nowiki><nowiki>10</nowiki></code>. [https://phabricator.wikimedia.org/T285612] * A <code>REL1_45</code> branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/ZUY7TY3Z6XPZWZVAZV63OPO5OW52Q6GE/] * The process for generating CirrusSearch dumps has been updated due to slowing performance. If you encounter any issues migrating to the replacement dumps, please contact the Search Platform Team for support. [https://phabricator.wikimedia.org/T366248][https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/3KQPOR6ACVN6OVLMLZPIBXQSWQKW4E3K/] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.2|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:38, 10 November 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29606150 --> == Wikipedia translation of the week: 2025-47 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Elephant communication]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Three elephant's curly kisses.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Elephants communicate''' via touching, visual displays, vocalisations, seismic vibrations, and semiochemicals. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 17 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29627457 --> == Tech News: 2025-47 == <section begin="technews-2025-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/47|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] is experimenting with [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4_Reading lists|reading lists on mobile web]], allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November. * Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security#Why are you requiring me to enter a code from my email to log in? Can I opt out of this?|Learn more]]. * One new wiki has been created: a {{int:project-localized-name-group-wikisource}} in [[d:Q13324|Minangkabau]] ([[s:min:|<code>s:min:</code>]]) [https://phabricator.wikimedia.org/T408317] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * As part of the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parser Unification]] project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in the [[mw:Special:MyLanguage/Help:Extension:ParserMigration|Extension:ParserMigration]] documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the ''"Report Visual Bug"'' link in the Tools sidebar or create a phab ticket and tag the [[phab:project/view/5846|Content Transform Team in Phabricator]]. * Unsupported Tools: Several issues with [[:c:Special:MyLanguage/Commons:Video2commons|Video2Commons]] have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check the [[phab:tag/video2commons/|Phabricator board]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.3|MediaWiki]] '''Meetings and events''' * Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026. [https://pretix.eu/wikimedia/Hackathon-2026/ Scholarship applications are currently open], and will close on November 28, 2025. If you have any questions, please email <bdi lang="en" dir="ltr">hackathon@wikimedia.org</bdi>. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:27, 17 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29627455 --> == Wikipedia translation of the week: 2025-48 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Animal-made art]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Painting Queen 1024x768.png|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Animal-made art''' consists of works by non-human animals, that have been considered by humans to be artistic, including visual works, music, photography, and videography. Some of these are created naturally by animals, often as courtship displays, while others are created with human involvement. There have been debates about the copyright status of these works, with the United States Copyright Office stating in 2014 that works that lack human authorship cannot have their copyright registered at the US Copyright Office. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 24 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29627457 --> == Tech News: 2025-48 == <section begin="technews-2025-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/48|Translations]] are available. '''Updates for editors''' * Last week, the [[mw:Special:MyLanguage/Wikimedia Search Platform|Wikimedia Search Team]] recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching for ''<span lang="und" dir="ltr">cxfcnmt</span>'' on Russian Wikipedia will now add suggestions for ''<span lang="ru" dir="ltr">счастье</span>'' ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week. [https://phabricator.wikimedia.org/T408734] * Later this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will have syntax highlighting available in [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]]. This requires that the "{{int:discussiontools-preference-sourcemodetoolbar}}" preference be set. [https://phabricator.wikimedia.org/T407918] * [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|Campaign events extension]] – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known as [[m:Special:MyLanguage/CampaignEvents/Collaborative contributions|Collaborative contribution]] to help organizers and participants see the impact of activities has also been added. Join the upcoming [[m:Special:MyLanguage/Event:Connection learning session 3|learning session]] to see the new feature in action and share your feedback. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug which stopped CodeReviewBot from working, has now been fixed. [https://phabricator.wikimedia.org/T410417] '''Updates for technical contributors''' * Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill the [https://wikimediafoundation.limesurvey.net/487662 recruitment survey]. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/IREJRRWTZTGCYWQHDMSNJFTQAEPOOAE3/] * The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for <code dir=ltr>format=xml'''&xlst={stylesheet}'''</code> will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026). [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/5AX7UWAVVUNUSBOIRHMNOKWOZ5EZI3JX/] * The WDQS legacy endpoint ([https://query-legacy-full.wikidata.org/ query-legacy-full.wikidata.org]) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (<span dir=ltr><nowiki>https://query.wikidata.org/</nowiki></span> - Main graph or <span dir=ltr><nowiki>https://query-scholarly.wikidata.org/</nowiki></span> - Scholarly graph). For support with migrating use cases, please review the [[d:Special:MyLanguage/Wikidata:Data_access|Data Access]] and [[d:Wikidata:Request_a_query|Request a Query]] pages for details and assistance on alternative access methods. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.4|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:57, 24 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29702226 --> == Wikipedia translation of the week: 2025-49 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Halachic state]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The term "'''halachic state'''" (Hebrew: מְדִינַת הֲלָכָה‎ Medīnat Hălāḵā) refers to a sovereign state that endorses Judaism in an official capacity and governs by Jewish religious law. It has been a subject of discussion among Orthodox Jews, particularly with regard to modern Israel, which, although a Jewish state, is not classified as a theocracy. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 08:01, 1 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29719355 --> == Tech News: 2025-49 == <section begin="technews-2025-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/49|Translations]] are available. '''Updates for editors''' * The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's [[mw:Special:MyLanguage/Wikimedia Apps/Team/Wikipedia Year in Review/Updates|project page]]. * The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See [[phab:T396155|Phabricator]]. * [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]] will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact [[mw:user:Trizek (WMF)|Trizek (WMF)]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:34}} community-submitted {{PLURAL:34|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [https://phabricator.wikimedia.org/T399476] * Two new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q36846|Toki Pona]] ([[w:tok:|<code>w:tok:</code>]]) [https://phabricator.wikimedia.org/T404457] ** a {{int:project-localized-name-group-wikiquote}} in [[d:Q33655|Nigerian Pidgin]] ([[q:pcm:|<code>q:pcm:</code>]]) [https://phabricator.wikimedia.org/T408318] '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.5|MediaWiki]] '''In depth''' * The Wikimedia Foundation is in the early stages of exploring approaches to '''Article guidance'''. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to [[mw:Special:MyLanguage/Article guidance|learn more]] about the project, and share their thoughts on [[mw:Special:MyLanguage/Talk:Article guidance|the talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:58, 1 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29732328 --> == Wikipedia translation of the week: 2025-50 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ru:Сто лошадей]]'''<br /> <small>''([[:en:One Hundred Horses]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:A_Hundred_Steeds.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''One Hundred Horses''''' (Chinese: 百駿圖) is a Qing dynasty silk and ink painting by Giuseppe Castiglione. It was painted in 1728 for the Yongzheng emperor. The painting depicts a hundred horses in a variety of poses and activities, combining Western realism with traditional Chinese composition and brushwork. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:29, 8 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29719355 --> == Tech News: 2025-50 == <section begin="technews-2025-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/50|Translations]] are available. '''Weekly highlight''' * Anybody who wishes to secure their user account can now use [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] (2FA). This is available to all registered users of all Wikimedia projects. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] initiative. Later, 2FA will be required for all users who can take security- or privacy-sensitive actions. '''Updates for editors''' * Following last week's deployments, the [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]] feature, which allows editors to add suggested links during editing, will be available to an additional [[Phab:T410469|33 Wikipedias]] starting on 9 December. This expansion is possible thanks to the new prediction model that now supports all languages, including those that were previously not covered. While the feature has been available on most Wikipedias for some time, this rollout brings us closer to using the improved model everywhere. If you have any questions or would like more details please contact [[mw:user:Trizek (WMF)|Trizek (WMF)]]. * Last week, the [[mw:Special:MyLanguage/Wikimedia Search Platform|Search Platform team]] added [[w:en:Transliteration|transliterated]] as-you-type search suggestions to Georgian wikis. If there are only a few regular search suggestions, then queries in Latin or Cyrillic script [[phab:T127003|are now rewritten into Georgian script]] to look for more matches. For example, searching for either <bdi lang="ka-Latn" dir="ltr">''bedniereba''</bdi> or <bdi lang="ka-Cyrl" dir="ltr">''бедниереба''</bdi> will now suggest the existing article about <bdi lang="ka" dir="ltr">ბედნიერება</bdi> ("happiness"). You can recommend other languages where transliterated suggestions would be useful [[phab:T375215|on Phabricator]] for future development. * Later this week, a controlled experiment will begin for editors on the 100 largest Wikipedias who are editing a section in the mobile web visual editor. 50% of these editors will notice a new "Edit full page" button that will enable them to expand their editing session to the whole page. This feature is intended to make it easier for people on mobile web to edit any article section, regardless of which section-edit icon they tapped to begin. The experiment will last ~4 weeks. You can find [[phab:T409112|more details]] about the project. * Later this week, the [[mw:Special:MyLanguage/Readers/Reader Growth|Reader Growth team]] will launch a [[mw:Special:MyLanguage/Readers/Reader Growth/WE3.1.14 Expanded Mobile Sections|mobile web experiment]] to expand all article sections by default (currently they are collapsed by default) and pin the section header the user is currently reading to the top of the page. The experiment will affect 10% of users on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias. [https://phabricator.wikimedia.org/T409485] * The [[mw:Special:MyLanguage/Wikimedia Apps/Team/Wikipedia Year in Review/2025 Year in Review|Wikipedia Year in Review 2025]], a feature in the Wikipedia mobile apps (iOS and Android) that provides users with a personalised summary of their engagement with Wikipedia over the year, is now available on the iOS and Android apps. This edition includes expanded personalised insights, improved reading highlights, new donor messaging, and updated designs. Open the app to view your Year in Review and explore your reading journey from 2025. * A recent software bug caused edits made with VisualEditor to make unintended changes to wikitext, including removing whitespace and replacing spaces with underscores in wikilinks inside citations. This was partially fixed last week, and further fixes are in progress. Editors who used VisualEditor between November 28 and December 2 should review their edits for unexpected modifications. [https://phabricator.wikimedia.org/T411238] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the incorrect handling of URLs copied from the address bar of Microsoft Edge users, has been resolved. [https://phabricator.wikimedia.org/T341281] '''Updates for technical contributors''' * Starting this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will have [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror]] as the editor for Lua, JavaScript, CSS, JSON and Vue content models, instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]]. With this, the [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|linters]] will be upgraded. This is part of a larger effort to eventually replace CodeEditor and provide a consistent code editing experience. [https://phabricator.wikimedia.org/T373711] * Developers are encouraged to take the [https://wikimediafoundation.limesurvey.net/552643 2025 Developer Satisfaction Survey], which remains open until 5 January 2026. If you build software for the Wikimedia ecosystem and would like to share your experiences or feedback, your participation is greatly appreciated. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/W4WBKO6Q55UWWCCSFWQATKEXBEHP3QNR/] * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:46, 8 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29738112 --> == Wikipedia translation of the week: 2025-51 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:First Universal Races Congress]]'''<br /> <small>''([[:fr:Premier Congrès universel des races]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Universal Races Congress seated outside the entrance to the Imperial Institute, London, 1911.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''First Universal Races Congress''' met in 1911 for four days at the University of London as an early effort at anti-racism. Speakers from a number of countries discussed race relations and how to improve them. The congress, with 2,100 attendees, was organised by prominent humanists of that era. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 15 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29779168 --> == Tech News: 2025-51 == <section begin="technews-2025-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/51|Translations]] are available. '''Updates for editors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:18}} community-submitted {{PLURAL:18|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, one of the fixes addressed an issue for temporary accounts adding an external URL, which triggered an hCaptcha request in more cases than intended, and did not display the required popup on the first attempt to publish the edit. [https://phabricator.wikimedia.org/T411927] '''Updates for technical contributors''' * To improve database and site performance, external links to Wikimedia projects will no longer be stored in the database. This means they will not be searchable in [[{{#special:LinkSearch}}]], will not be checked by the Spam Blacklist or AbuseFilter as new links, and will not be in the <code dir=ltr>externallinks</code> table on database replicas. In the future this may be extended to other highly-linked trusted websites on a per-wiki basis, such as Creative Commons links on Wikimedia Commons. [https://phabricator.wikimedia.org/T405005] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.7|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:03, 15 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29796010 --> == Wikipedia translation of the week: 2025-52 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pin Malakul]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pin Malakul, January 1922.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pin Malakul''' (24 October 1903 – 5 October 1995) was a Thai professor, educator and writer. His contributions to education in Thailand include the establishment of various institutions of higher education, the introduction of fixed class schedules, and the implementation of teacher-training programmes. In his career he served as Director-General of the Department of General Education, later becoming Permanent Secretary, and Minister, of Education. He was also a member of the executive board of UNESCO. His writings earned him the title of National Artist in 1987, and the 100th anniversary of his birth was celebrated by the UNESCO in 2003 as recognition of his contribution to the advancement of education in Thailand and Southeast Asia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> -[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:26, 22 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29802495 --> == Tech News: 2025-52 == <section begin="technews-2025-W52"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/52|Translations]] are available. '''Updates for editors''' * From January, edit filters [[mw:Special:MyLanguage/Extension:AbuseFilter/Access flags|can be set]] to automatically suppress their details such as rules and list of attempted edits and actions. This will help oversighters use edit filters to prevent doxxing or other suppressible material. [https://phabricator.wikimedia.org/T290324] * The next issue of Tech News will be sent out on 12 January 2026 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:16}} community-submitted {{PLURAL:16|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the crash that occurred when tapping "First Steps" in the Wikipedia Android Year in Review has now been fixed, and the feature opens as expected. [https://phabricator.wikimedia.org/T411546] '''Updates for technical contributors''' * Interface elements such as diffs and categories generated by MediaWiki used to have the attribute <code dir=ltr>data-mw="interface"</code> to distinguish from wiki content. The attribute has been replaced with <code dir=ltr>data-mw-interface=""</code>, to avoid potential conflicts with other <code dir=ltr>data-mw</code> attributes, which are generated by Parsoid. [https://phabricator.wikimedia.org/T409187] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] There is no new MediaWiki version this week or next week. '''Meetings and events''' * The [[mw:Wikimedia Hackathon Northwestern Europe 2026|Wikimedia Hackathon Northwestern Europe 2026]] will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications just opened mid-December and will close in mid-January or earlier if capacity is reached. With space for approximately 100 participants, early application is encouraged. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/52|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W52"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:46, 22 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29831856 --> == Wikipedia translation of the week: 2026-01 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:The Morning of the Magicians]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Le Matin des magiciens, couverture.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''The Morning of the Magicians: Introduction to Fantastic Realism''''' (French: Le Matin des magiciens: Introduction au réalisme fantastique) is a 1960 book by the journalists Louis Pauwels and Jacques Bergier. It covers topics like cryptohistory, ufology, occultism in Nazism, alchemy, spiritual philosophy. The second half of the book is entirely dedicated to the Nazi-Occult connections; the book is widely credited with the proliferation of numerous myths related to occultism in Nazism. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:20, 29 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29802495 --> == Wikipedia translation of the week: 2026-02 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Somaliland War of Independence]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Somaliland, fighters of the Somali National Movement (SNM), 1980s.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Somaliland War of Independence''' was a rebellion waged by the Somali National Movement (SNM) against the ruling military junta in Somalia led by General Siad Barre lasting from its founding on 6 April 1981 and ended on 18 May 1991 when the SNM declared what was then northern Somalia independent as the Republic of Somaliland. The conflict served as the main theater of the larger Somali Rebellion that started in 1978. The conflict was in response to the harsh policies enacted by the Barre regime against the main clan family in Somaliland, the Isaaq, including a declaration of economic warfare on the clan-family. These harsh policies were put into effect shortly after the conclusion of the disastrous Ogaden War in 1978. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:00, 5 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29871911 --> == Wikipedia translation of the week: 2026-03 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Pietro Lauro]]'''<br /> <small>''([[:en:Pietro Lauro]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Master I.A.V.F., Pietro Lauro, born 1508, Modenese Poet and Scholar (obverse), 1555, NGA 45072.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pietro Lauro''', conosciuto anche come Pietro Lauro Modonese o Pietro Lauro da Modona (Modena o dintorni, 1510 circa – Venezia, 1568 circa) è stato un traduttore, scrittore e divulgatore scientifico italiano. Nonostante non si conosca gran parte della sua biografia, fu uno dei poligrafi italiani più conosciuti del Cinquecento. La sua produzione raccoglie traduzioni dal latino, dal greco e dallo spagnolo e riguardano opere di autori classici, stranieri e protestanti. Lauro si dimostrò abile nel trattare testi con temi molto diversi, come la filosofia, l'architettura, la medicina, il giardinaggio, l'agronomia, le scienze biologiche, la storia, la teologia e l'astronomia. Si cimentò anche nella scrittura di un poema cavalleresco sullo stile di quelli spagnoli, il Polendo, sua magnum opus in questo senso. Aderente alla Riforma protestante, sebbene le sue trasposizioni siano state oggetto di critiche già degli autori a lui contemporanei, che le giudicarono troppo letterali, rozze e imparziali, a Lauro si deve il merito di aver ultimato la traduzione in lingua volgare di numerosi testi sia classici, sia scientifici, sia epistolari. I suoi lavori ebbero una notevole diffusione, non solo tra i letterati veneziani della sua epoca, ma in tutta Italia, tanto che alcune sue traduzioni vengono ancora oggi ristampate in nuove edizioni. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:45, 12 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29894468 --> == Tech News: 2026-03 == <section begin="technews-2026-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/03|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2026-2027/Product & Technology OKRs|Meta]] and ''[[diffblog:2025/12/10/shaping-wikimedia-foundations-2026-2027-annual-goals-key-questions-for-the-wikimedia-movement/|Diff]]''. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. '''Updates for editors''' * As part of the current work of Community Tech team on the [[m:Special:MyLanguage/Community Wishlist/W372|Multiple watchlists]] project, the display of [[Special:EditWatchlist|EditWatchlist]] will be updated as a first step towards multiple watchlists. Additionally, the pagination on [[Special:Search|Search]] will be updated too, as a part of the work on the [[m:Special:MyLanguage/Community Wishlist/W186|Revamp pagination / page navigation]] wish. [https://phabricator.wikimedia.org/T411596] * [[m:Special:GlobalWatchlist|The Global Watchlist]] is a MediaWiki [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] that lets you see your watchlists from different wikis on the same page. It was recently updated to look more like the regular [[Special:Watchlist|Watchlist]], such as preparing it for temporary accounts in IP masking (including rerouting user links to contributions pages), making page titles bold, and opening links in edit summaries and tags in new browser tabs. [https://phabricator.wikimedia.org/T398361][https://phabricator.wikimedia.org/T298919][https://phabricator.wikimedia.org/T273526][https://phabricator.wikimedia.org/T286309] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where global blocks did not have the option to disable sending emails, has now been fixed, and will be available for use in the week of January 13. [https://phabricator.wikimedia.org/T401293] '''Updates for technical contributors''' * The [[mw:Special:MyLanguage/VisualEditor/Citation tool|VisualEditor citation tool]] and [[mw:Special:MyLanguage/Help:Reference Previews|Reference Previews]] now support "map" as a reference type. [https://phabricator.wikimedia.org/T411083] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.10|MediaWiki]]/[[mw:MediaWiki 1.46/wmf.11|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:34, 12 January 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29907192 --> == Wikipedia translation of the week: 2026-04 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Volto di Palazzo Vecchio]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Piazza della signoria angolo via della ninna, palazzo vecchio, cantonata con testa scolpita 02.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''volto di Palazzo Vecchio''' (conosciuto anche come L'importuno o L'inopportuno) è un incisione su pietraforte attibuita a Michelangelo Buonarroti, scolpita in una delle pietre di Palazzo Vecchio a Firenze. Secondo le varie leggende, il profilo sarebbe stato realizzato come graffito dall'artista toscano, con soggetto un suo importunatore, un debitore, un condannato a morte o se stesso. Nel 2020, gli studiosi hanno ipotizzato possa invece trattarsi di un ritratto di Francesco Granacci, pittore amico di Michelangelo. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:14, 19 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-04 == <section begin="technews-2026-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/04|Translations]] are available. '''Updates for editors''' * The tray shown on [[Special:Diff|Special:Diff]] in mobile view has been redesigned. It is now collapsed by default, and incorporates a link to undo the edit being viewed, making it easier for mobile editors and reviewers to take action while keeping the interface uncluttered. [https://phabricator.wikimedia.org/T402297] * [[m:Special:GlobalWatchlist|The Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] continues to improve — it now automatically determines the text direction (ensuring correct display of sites with unusual domain names) and shows detailed descriptions for log actions. Later this week, a new permanent link for page creations and CSS classes for each entry element will be added. [https://phabricator.wikimedia.org/T412505][https://phabricator.wikimedia.org/T287929][https://phabricator.wikimedia.org/T262768][https://phabricator.wikimedia.org/T414135] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the previously observed issue in Vector 2022, where anchor link targets were obscured by the sticky header, has now been addressed. [https://phabricator.wikimedia.org/T406114] '''Updates for technical contributors''' * As mentioned in the [[m:Special:MyLanguage/Tech/News/2025/44|October 2025 deprecation announcement]], MediaWiki Interfaces team will begin sunsetting all transform endpoints containing a trailing slash from the MediaWiki REST API the week of January 26. Changes are expected to roll out to all wikis on or before January 30th. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found, compared, and tested using the [https://test.wikipedia.org/wiki/Special:RestSandbox REST Sandbox]. If you have questions or encounter any problems, please file a ticket in Phabricator to the [https://phabricator.wikimedia.org/project/view/6931/ #MW-Interfaces-Team board]. * Interactive reference documentation for the [[mw:Special:MyLanguage/Wikimedia REST API|Wikimedia REST API]] has moved. Requests to API docs previously hosted through [[mw:Special:MyLanguage/RESTBase|RESTBase]] (e.g.: <code dir=ltr>https://en.wikipedia.org/api/rest_v1/</code>) are now redirected to the [[w:en:Special:RestSandbox|REST Sandbox]]. * The [[mw:Special:MyLanguage/Wikidata Platform|WMF Wikidata Platform team]] (WDP) has published its [[d:Special:MyLanguage/Wikidata:Wikidata Platform team/Newsletter|January 2026 newsletter]]. It includes updates on the legacy full-graph endpoint decommissioning, the User-Agent policy change, the monthly Blazegraph migration office hours, and efforts to reduce regressions caused by the legacy endpoint shutdown. As a reminder, you can [[m:Special:MyLanguage/Global message delivery/Targets/WDP team updates|subscribe to the WDP newsletter]]! * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.12|MediaWiki]] '''Meetings and events''' * The [[mw:Wikimedia Hackathon Northwestern Europe 2026|Wikimedia Hackathon Northwestern Europe 2026]] will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications opened mid-December and will close soon or when capacity is reached. It's a two-day, technically oriented hackathon bringing together Wikimedians from the region. Hope to see you there! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:30, 19 January 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29943403 --> == Wikipedia translation of the week: 2026-05 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Raffaello Kobayashi]]'''<br /> <small>''([[:en:Raffaello Kobayashi]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Raffaello Kobayashi''', nato Raffaele Sanzio (Bari, 14 gennaio 1917 – Yokohama, 1 aprile 2011), è stato un militare italiano naturalizzato giapponese. Sommergibilista durante la Seconda guerra mondiale, prestò servizio per tutte e tre le principali Potenze dell'Asse: Regno d'Italia, Germania nazista e Impero giapponese. Alla fine della guerra si nascose in Giappone per evitare di subire l'internamento in un campo di prigionia, divenendo poi cittadino nipponico e cambiando il proprio nome. Prese parte all'affondamento della HMS Calypso nel 1940, primo successo italiano in campo navale nel corso del conflitto mondiale. Con l'abbattimento di un bombardiere statunitense il 22 agosto 1945, otto giorni dopo il discorso di resa del Giappone alle potenze alleate della seconda guerra mondiale, a bordo del Comandante Cappellini, sarebbe stata l'ultima persona in assoluto a mettere fuori combattimento un velivolo degli Alleati nella stessa guerra. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 26 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-05 == <section begin="technews-2026-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/05|Translations]] are available. '''Updates for editors''' * Wikimedia Foundation invites comments on [[m:Special:MyLanguage/Product and Technology Advisory Council/Year1 Reflections and Proposed Way Forward 2026 Update|proposed future]] of the [[:m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] until 28 February. * All users with registered accounts can now use passkeys for [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] (2FA). Passkeys are a simple way to log in without using a second device. They verify the user's identity using a fingerprint, face scan, or a PIN code. To set up a passkey, first set up a regular 2FA method. Currently, to log in with a passkey, users must also use a password. Later this quarter, passwordless login will allow users to log in with a single click and a passkey. Users with advanced rights will also be required to have 2FA enabled. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project. * Unregistered contributors on blocked IPs or blocked IP ranges can now interact on-wiki to appeal a block by creating a temporary account to appeal a block on the user talk page, unless the "prevent this user from editing their own talk page" is enabled. This solves the problem of logged-out users unable to use the default unblock process via user talk page. [https://phabricator.wikimedia.org/T398673] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Two-Factor Authentication (2FA) methods description on the management page has been updated. It is now clearer and easier for users to understand and make use of. [https://phabricator.wikimedia.org/T332385] '''Updates for technical contributors''' * A new AbuseFilter variable, <code>account_type</code>, has been added to provide a reliable way to determine the account type being created in the <code>createaccount</code> and <code>autocreateaccount</code> actions. As part of this change, the variable <code>accountname</code> has been renamed to <code>account_name</code>, and <code>accountname</code> is now deprecated. Edit filter managers should update any filters that use hardcoded account type checks or the deprecated variable. [https://phabricator.wikimedia.org/T414049] * Image thumbnails that are requested in non-standard sizes, and using non-standard methods such as direct requests to <code dir=ltr><nowiki>upload.wikimedia.org/…</nowiki></code> will stop working in the near future. This change is to prevent ongoing external abuse by web-scrapers and bots. Some users with custom CSS/JS, Interface Admins who can fix gadgets and local skins, and Tool-authors, will need to update their code to use standard thumbnail sizes. [[phab:T414805|Details, search-links, and examples of how to fix them, are available in the task]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.13|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:18, 26 January 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29969530 --> == Wikipedia translation of the week: 2026-06 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Censorship in the Czech Republic]]'''<br /> <small>''([[:cs:Cenzura v Česku]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Censorship in the Czech Republic''' had been highly active until 17 November 1989 and the fall of Communism in the former Czechoslovakia. Czech Republic was ranked as the 13th most free country in the World Press Freedom Index in 2014. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:32, 2 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-06 == <section begin="technews-2026-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/06|Translations]] are available. '''Updates for editors''' * The "{{int:pageinfo-toolboxlink}}" feature, which gives validating information about a page ([{{fullurl:{{FULLPAGENAME}}|action=info}} example]), now automatically includes a table of contents. If there is a local [[{{ns:8}}:Pageinfo-header]] page created by individual users, it can now be removed. [https://phabricator.wikimedia.org/T363726] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, VisualEditor previously added bold or italic formatting inside link descriptions, making the wikicode complex. This has now been fixed. [https://phabricator.wikimedia.org/T409669] '''Updates for technical contributors''' * There was no XML dump on 20 January. Additionally, from now on, dumps will be generated once per month only. [https://phabricator.wikimedia.org/T414389] * The MediaWiki Interfaces team removed support for all transform endpoints containing a trailing slash from the [https://www.mediawiki.org/wiki/Special:MyLanguage/API:REST%20API MediaWiki REST API]. All API users currently calling those endpoints are encouraged to transition to the non-trailing slash versions. If you have questions or encounter any problems, please file a ticket in phabricator to the [https://phabricator.wikimedia.org/project/view/6931/ #MW-Interfaces-Team board]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.14|MediaWiki]] '''Weekly highlight''' * Users are reminded that the Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2026-2027/Product & Technology OKRs|Meta]] and ''[[diffblog:2025/12/10/shaping-wikimedia-foundations-2026-2027-annual-goals-key-questions-for-the-wikimedia-movement/|Diff]]''. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:44, 2 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30000986 --> == Wikipedia translation of the week: 2026-07 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Petites Heures of Jean de France, Duc de Berry]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Jacquemart de Hesdin 002.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Petites Heures of Jean de France, Duc de Berry''' is an illuminated book of hours commissioned by John, Duke of Berry between 1375 and 1385–90. It is known for its ornate miniature leaves and border decorations. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:59, 9 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-07 == <section begin="technews-2026-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/07|Translations]] are available. '''Updates for editors''' * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] Logged-in contributors who manage large or complex watchlists can now organise and filter watched pages in ways that improve their workflows with the new [[mw:Special:MyLanguage/Help:Watchlist labels|Watchlist labels]] feature. By adding custom labels (for example: pages you created, pages being monitored for vandalism, or discussion pages) users can more quickly identify what needs attention, reduce cognitive load, and respond more efficiently. This improves watchlist usability, especially for highly active editors. * A new feature available on [[Special:Contributions|Special:Contributions]] shows [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] that are likely operated by the same person, and so makes patrolling less time-consuming. Upon checking contributions of a temporary account, users with access to temporary account IP addresses can now see a view of contributions from the related temporary accounts. The feature looks up all the IPs associated with a given temporary account within the data retention period and shows all the contributions of all temporary accounts that have used these IPs. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts#February 2026: Improvements to the patroller tooling|Learn more]]. [https://phabricator.wikimedia.org/T415674] * When editors preview a wikitext edit, the reminder box that they are only seeing a preview (which is shown at the top), now has a grey/neutral background instead of a yellow/warning background. This makes it easier to distinguish preview notes from actual warnings (for example, edit conflicts or problematic redirect targets), which will now be shown in separate warning or error boxes. [https://phabricator.wikimedia.org/T414742] * The [[m:Special:GlobalWatchlist|Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] continues to improve — it now properly supports more than one Wikibase site, for example both [[d:|Wikidata]] and [[testwikidata:|testwikidata]]. In addition, issues regarding text direction have been fixed for users who prefer Wikidata or other Wikibase sites in right-to-left (RTL) languages. [https://phabricator.wikimedia.org/T415440][https://phabricator.wikimedia.org/T415458] * The automatic "magic links" for ISBN, RFC, and PMID numbers have been [[mw:Special:MyLanguage/Help:Magic links|deprecated in wikitext since 2021]] due to inflexibility and difficulties with localization. Several wikis have successfully replaced RFC and PMID magic links with equivalent external links, but a template was often required to replace the functionality of the ISBN magic link. There is now a new [[mw:Special:MyLanguage/Help:Magic words#isbn|built-in parser function]] <code dir=ltr><nowiki>{{#isbn}}</nowiki></code> available to replace the basic functionality of the ISBN magic link. This makes it easier for wikis who wish to migrate off of the deprecated magic link functionality to do so. [https://phabricator.wikimedia.org/T145604] * Two new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35401|Jju]] ([[w:kaj:|<code>w:kaj:</code>]]) [https://phabricator.wikimedia.org/T413283] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q1186896|Nawat]] ([[w:ppl:|<code>w:ppl:</code>]]) [https://phabricator.wikimedia.org/T413273] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * A new global user group has been created: [[{{int:grouppage-local-bot}}|{{int:group-local-bot}}]]. It will be used internally by the software to allow community bots to bypass rate limits that are applied to abusive [[w:en:Web scraping|web scrapers]]. Accounts that are approved as bots on at least one Wikimedia wiki will be automatically added to this group. It will not change what user permissions the bot has. [https://phabricator.wikimedia.org/T415588] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.15|MediaWiki]] '''Meetings and events''' * The [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Spring 2026|MediaWiki Users and Developers Conference, Spring 2026]] will be held March 25–27 in Salt Lake City, USA. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/AZBWVI46SDEB65PGR5J6E4TYOQQEZXM7/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:31, 9 February 2026 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30026671 --> == Wikipedia translation of the week: 2026-08 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lysmata grabhami]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lysmata grabhami1.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Lysmata grabhami''''' is a species of saltwater shrimp in the family Hippolytidae. It was first described by Gordon in 1935. It occurs in the tropical and subtropical Atlantic Ocean and is a cleaner shrimp, operating a cleaning station to which fish come to have parasites removed. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:45, 16 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-08 == <section begin="technews-2026-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/08|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Wikimedia Site Reliability Engineering|SRE Team]] will be performing a cleanup of Wikimedia's [[m:Special:MyLanguage/Etherpad|Etherpad]] instance, the web-based editor for real-time collaborative document editing. All pads will be permanently deleted after 30 April, 2026 – if there are still migration projects in progress at that point the team can revisit the date on a case by case basis. Please create local backups of any content you wish to keep, as deleted data cannot be recovered. This cleanup helps reduce database size and minimize infrastructure footprint. Etherpad will continue to support real-time collaboration, but long-term storage should not be expected. Additional cleanups may occur in the future without prior notice. [https://phabricator.wikimedia.org/T415237] '''Updates for editors''' * The Information Retrieval team will be launching an [[mw:Special:MyLanguage/Readers/Information Retrieval/Phase 1|Android mobile app experiment]] that tests hybrid search capabilities which can handle both semantic and keyword queries. The improvement of on-platform search will enable readers to find what they’re looking for directly on Wikipedia more easily. The experiment will first be launched on Greek Wikipedia in late February, followed by English, French, and Portuguese in March. [https://diff.wikimedia.org/2026/01/08/semantic-search-making-it-easier-to-find-the-information-readers-want/ Read more] on Diff blog. [https://www.mediawiki.org/wiki/Readers/Information_Retrieval] * The Reader Growth team will run [[mw:Special:MyLanguage/Readers/Reader Growth/WE3.10.2 Mobile Table of Contents|an experiment]] for mobile web users, that adds a table of contents and automatically expands all article sections, to learn more about navigation issues they face. The test will be available on Arabic, Chinese, English, French, Indonesian, and Vietnamese Wikipedias. * Previously, site notices ([[{{ns:8}}:Sitenotice]] and [[{{ns:8}}:Anonnotice]]) would only render on the desktop site. Now, they will render on all platforms. Users on mobile web will now see these notices and be informed. Site administrators should be prepared to test and fix notices on mobile devices to avoid interference with articles. To opt out, interface admins can add <code dir="ltr">#siteNotice { display: none; }</code> to [[{{ns:8}}:Minerva.css]]. [https://phabricator.wikimedia.org/T138572][https://phabricator.wikimedia.org/T416644] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue on [[Special:RecentChanges|Special:RecentChanges]] has been fixed. Previously, clicking hide in the active filters caused the "view new changes since…" button to disappear, though it should have remained visible. The button now behaves as expected. [https://phabricator.wikimedia.org/T406339] '''Updates for technical contributors''' * New documentation is now available to help editors debug on-site search features. It supports troubleshooting when pages do not appear in results, when ranking seems unexpected, and when you need to inspect what content is being indexed, helping make search behavior easier to understand and analyze. [[mw:Help:CirrusSearch/Debug|Learn more]]. [https://phabricator.wikimedia.org/T411169] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.16|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:17, 16 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30086330 --> == Wikipedia translation of the week: 2026-09 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Elefante di Cremona]]'''<br /> <small>''([[:de:Elefant von Cremona]])&#32;([[:eo:Elefanto de Cremona]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Matthew Paris Elephant from Parker MS 16 fol 151v.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> L''''elefante di Cremona''' (Asia, prima del 1228 - Parma, gennaio 1248) fu un esemplare di elefante donato nel 1228 a Federico II di Svevia da parte del sultano ayyubide al-Malik al-Kamil durante gli incontri che porteranno alla Pace di Giaffa. Usato principalmente per le manifestazioni trionfali del sovrano, l'elefante è citato da numerosi cronachisti e testimoni dell'epoca ed è noto per aver trainato il Carroccio dopo la grande vittoria delle armate di Federico II nella battaglia di Cortenuova del 1237. Rimasto a lungo nell'immaginario popolare collettivo, l'animale venne ucciso durante alcuni scontri occorsi nelle settimane immediatamente precedenti alla battaglia di Parma. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 11:43, 23 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-09 == <section begin="technews-2026-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/09|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Edit check/Reference Check|Reference Check]] has been deployed to English Wikipedia, completing its rollout across all Wikipedias. The feature prompts newcomers to add a citation before publishing new content, helping reduce common citation-related reverts and improve verifiability. In A/B testing, the impact was substantial: newcomers shown Reference Check were approximately 2.2 times more likely to include a reference on desktop and about 17.5 times more likely on mobile web. [https://analytics.wikimedia.org/published/reports/editing/reference_check_ab_test_report_final_2025.html] '''Updates for editors''' * The [[mw:Special:MyLanguage/Extension:InterwikiSorting|InterwikiSorting extension]], which allowed for the [[m:Special:MyLanguage/Interwiki sorting order|sorting of interwiki links]], has been undeployed from Wikipedia. As a result, editors who had enabled interwiki link sorting in non-compact mode (full list format) will now see links reordered. The links moving forward will be listed in the alphabetical order of language code. [https://phabricator.wikimedia.org/T253764] * Later this week, people who are editing a page-section using the mobile visual editor, will notice a new "Edit full page" button. When tapped, you will be able to edit the entire article. This helps when the change you want to make is outside the section you initially opened. [https://phabricator.wikimedia.org/T387175][https://phabricator.wikimedia.org/T409112] * [[mw:Special:MyLanguage/Readers/Reader Experience|The Reader Experience team]] is inviting editors to assess whether dark mode should still be considered "beta" on their wiki, based on their experience of how well it functions on desktop and mobile. If the feature is deemed mature, editors can update the interface messages in <code dir=ltr>MediaWiki:skin-theme-description</code> and <code dir=ltr>MediaWiki:Vector-night-mode-beta-tag</code> to indicate that dark mode is ready and no longer considered beta. * The improved [[mw:Wikimedia_Apps/Team/iOS/Activity_Tab|Activity tab]] which displays user-insights is now available to all users of the Wikipedia iOS app (version 7.9.0 and later). Following earlier A/B testing that showed higher account creation among users with access to the feature, it has been rolled out to 100% of users along with some updates. The Activity tab now shows your edited articles in the timeline, offers editing impact insights like contribution counts and article view trends, and customization options to improve in-app experience for users. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug that prevented [[mw:Special:MyLanguage/Extension:DiscussionTools|DiscussionTools]] from working on mobile has now been fixed, restoring full functionality. [https://phabricator.wikimedia.org/T415303] '''Updates for technical contributors''' * The [[m:Special:GlobalWatchlist|Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] that makes this possible continues to improve. The latest upgrade is the inclusion of a [[mw:Extension:GlobalWatchlist#hook|new hook]], <code dir=ltr>ext.globalwatchlist.rebuild</code>, which fires after each watchlist rebuild. This allows you to run gadgets and user scripts for the Special page. [https://phabricator.wikimedia.org/T275159] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.17|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:04, 23 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30119102 --> == Wikipedia translation of the week: 2026-10 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Treaty of the Danish West Indies]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:The Virgin islands of the United States of America; historical and descriptive, commercial and industrial facts, figures, and resources (1918) (14596880870).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Treaty of the Danish West Indies''' (Danish: Vestindiens traktat), officially the Convention between the United States and Denmark for cession of the Danish West Indies (Danish: Konventionen mellem USA og Danmark), was a 1916 treaty transferring sovereignty of the Danish West Indies from Denmark to the United States in exchange for a sum of US$25,000,000 in gold ($722 million in 2024) and a declaration from the United States that it would "not object to the Danish Government extending their political and economic interests to the whole of Greenland". It is one of the most recent permanent expansions of United States territory. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 2 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-10 == <section begin="technews-2026-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/10|Translations]] are available. '''Weekly highlight''' * Wikipedia 25 [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments|Birthday mode]] is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments/article configuration|~2,500 articles]], waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments#Community Configuration Demo|community configuration]] on the local wiki. '''Updates for editors''' * [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new feature to re-use references with different details has been released to Swedish Wikipedia, Polish Wikipedia and [[:phab:T418209|a couple of other wikis]]. You can [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#test|try the feature]] on these projects or on testwiki and [https://en.wikipedia.beta.wmcloud.org/wiki/Sub-referencing betawiki]. Learnings from the first pilot wiki German Wikipedia have been [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing/Learnings|published in a report]]. Reach out to the Wikimedia Deutschland team if you are [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Pilot wikis|interested in becoming a pilot wiki]]. * [[mw:Special:MyLanguage/Help:Edit check#Paste check|Paste Check]] will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check [[mw:Special:MyLanguage/Edit check/Tags|tags]] all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via [[{{#special:EditChecks}}]]. [[mw:Special:MyLanguage/Edit check/Paste Check#A/B Experiment|Research]] across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can [https://translatewiki.net/w/i.php?title=Special%3ATranslate&group=ext-visualeditor-ve-mw-editcheck&filter=&optional=1&action=translate help to localize] this and related features. * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface. [https://phabricator.wikimedia.org/T413912] * Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one. [https://phabricator.wikimedia.org/T410807] * Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon. [https://phabricator.wikimedia.org/T383948] * The [[m:Special:GlobalWatchlist|Global Watchlist]] which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] now allows activating the [[mw:Special:MyLanguage/Manual:Language#Fallback languages|language fallback system]] for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no <code dir=ltr>uselang=</code> URL parameter is provided. [https://phabricator.wikimedia.org/T373686][https://phabricator.wikimedia.org/T416111] * The Wikipedia Android team has started a beta test of [[mw:Special:MyLanguage/Readers/Information Retrieval/Phase 1|hybrid search]] on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily. * For security reasons, members of certain user groups are [[m:Special:MyLanguage/Mandatory two-factor authentication for users with some extended rights|required to have two-factor authentication]] (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will [[phab:T418580|gradually change in March]]. Members of these groups will be unable to disable last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule. [https://phabricator.wikimedia.org/T418580] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue preventing users from creating an instance in [https://www.wikibase.cloud/ Wikibase.cloud] has now been fixed. [https://phabricator.wikimedia.org/T416807] '''Updates for technical contributors''' * To help ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]], over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]]. * The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts. [https://phabricator.wikimedia.org/T415696] * The new Parsoid parser [[mw:Special:MyLanguage/Parsoid/Parser Unification/Updates|continues to be deployed to additional wikis]], improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views. * The process and criteria for [[Special:MyLanguage/Wikimedia Enterprise#Access|requesting exceptional access]] to the high volume feed of the ''Wikimedia Enterprise'' APIs (at no cost for mission-aligned usecases), [[m:Talk:Wikimedia Enterprise#Exceptional access criteria|have now been published]]. This is to provide more thorough and clearer documentation for users. * [https://techblog.wikimedia.org/ Tech Blog], the blog dedicated to the Wikimedia technical community [https://techblog.wikimedia.org/2026/02/24/a-tech-blog-diff/ will be migrating] to [[diffblog:|Diff]], the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at https://diff.wikimedia.org/techblog. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.18|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:52, 2 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30137798 --> == Wikipedia translation of the week: 2026-11 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Steens Mountain]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Steens Mountain near Andrews, Oregon.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Steens Mountain''' is a large fault-block mountain in the northwest United States, located in Harney County, Oregon. Stretching some fifty miles (80 km) north to south, on its east side it rises from the Alvord Desert at an elevation of about 4,200 feet (1,280 m) to 9,738 feet (2,968 m) at the summit. Steens Mountain is not part of a mountain range but is properly a single mountain, the largest of Oregon's fault-block mountains. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 07:30, 9 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-11 == <section begin="technews-2026-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/11|Translations]] are available. '''Weekly highlight''' * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 25 March 2026 at [https://zonestamp.toolforge.org/1774450800 15:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. * Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the [[m:Steward's noticeboard#Statement on Meta about today's user script security incident|post on the Stewards' noticeboard]] ([[m:Special:MyLanguage/Wikimedia Foundation/Product and Technology/Product Safety and Integrity/March 2026 User Script Incident|translations]]). '''Updates for editors''' * Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as [[Special:MyLanguage/Apple iCloud Private Relay|iCloud Private Relay]]) will receive clearer guidance on what they need to do to start editing again. [https://phabricator.wikimedia.org/T357118] * Later this week, [[mw:Special:MyLanguage/VisualEditor/Suggestion Mode|Suggestion Mode]] will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at [[Special:EditChecks]] and there are [[mw:Special:MyLanguage/Help:Suggestion mode#For administrators %E2%80%93 local customization|instructions for how administrators can customize]] the links to point to local guidelines. The feature is connected to [[mw:Special:MyLanguage/Help:Edit check|Edit check]] which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment. [https://phabricator.wikimedia.org/T404600] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools. [https://phabricator.wikimedia.org/T418793] '''Updates for technical contributors''' * API rate limiting update: To help ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]], global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]]. * The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and [[d:Wikidata:Wikibase GraphQL#Feedback and development|give feedback]]. You can also [https://greatquestion.co/wikimediadeutschland/GraphQLAPI/apply sign up for usability tests]. * The [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|PTAC Unsupported Tools Working Group]] continued improvements to [[commons:Special:MyLanguage/Commons:Video2commons#|Video2Commons]] in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group#February 2026|this update]] to learn more. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.19|MediaWiki]] '''In depth''' * The Article Guidance team invites experienced Wikipedia editors from selected [[mw:Special:MyLanguage/Article guidance/Pilot wikis and collaborators#Collaborators|pilot wikis]] and interested contributors from other Wikipedias to fill out this questionnaire which is available in [https://docs.google.com/forms/d/e/1FAIpQLSfmLeVWnxmsCbPoI_UF2jyRcn73WRGWCVPHzerXb4Cz97X_Ag/viewform English], [https://docs.google.com/forms/d/e/1FAIpQLSd6rzr4XXQw8r4024fE3geTPFe13M_6w7Mitj-YJi0sOlWTAw/viewform?usp=header Arabic], [https://docs.google.com/forms/d/e/1FAIpQLSdok3-RfB18lcugYTUMGkpwmqG_8p760Wv4dCXitOXOszjUDw/viewform?usp=header Bengali], [https://docs.google.com/forms/d/e/1FAIpQLSfjTfYp4jEo0akA4B1e-Nfg3QZPCudUjhJzHzzDi6AHyAaMGA/viewform?usp=header Japanese], [https://docs.google.com/forms/d/e/1FAIpQLScteVoI29Aue4xc72dekk-6RYtvmMgQxzMI900UOawrFrSTWg/viewform?usp=header Portuguese], [https://docs.google.com/forms/d/e/1FAIpQLSetdxnYwL3ub2vqA7awCg5hJZPMIYcDPaiTe12rY9h0GYnVlw/viewform?usp=header Persian], and [https://docs.google.com/forms/d/e/1FAIpQLScNvfJF-Ot-4pzA4qAN771_0QDJ4Li19YcUsaTgSKW8Nc7U_Q/viewform?usp=header Turkish]. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more [[mw:Special:MyLanguage/Article guidance|on the project page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 9 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30213008 --> == Wikipedia translation of the week: 2026-12 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Casque (anatomy)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Great hornbill (Buceros bicornis) Photograph by Shantanu Kuveskar.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''casque''' is an anatomical feature found in some species of birds, reptiles, and amphibians. In birds, it is an enlargement of the bones of the upper mandible or the skull, either on the front of the face, the top of the head, or both. The casque has been hypothesized to serve as a visual cue to a bird's sex, state of maturity, or social status; as reinforcement to the beak's structure; or as a resonance chamber, enhancing calls. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 16 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30245038 --> == Tech News: 2026-12 == <section begin="technews-2026-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/12|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature, also known as [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror 6]], has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Features|features]] to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror|please share]]. [https://phabricator.wikimedia.org/T259059] * Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks. [https://phabricator.wikimedia.org/T6055] * On wikis using [[m:Special:MyLanguage/Flagged Revisions|Flagged Revisions]], the number of pending changes shown on [[{{#Special:PendingChanges}}]] previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself. [https://phabricator.wikimedia.org/T413016] * Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about [[f:Special:MyLanguage/Wikifunctions:Status updates/2026-03-11|the changes]]. * Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'. [https://phabricator.wikimedia.org/T403775] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed. [https://phabricator.wikimedia.org/T419263] '''Updates for technical contributors''' * A new special page, [[{{#special:LintTemplateErrors}}]], has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example: [[{{#special:LintTemplateErrors}}/night-mode-unaware-background-color]]. [https://phabricator.wikimedia.org/T170874] * Users of the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature have been using [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror|Feedback or concerns are welcome]]. [https://phabricator.wikimedia.org/T419332] * The [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the <code dir=ltr>ext.CodeMirror</code> or <code dir=ltr>ext.CodeMirror.lib</code> modules from gadgets and user scripts was deprecated in July 2025. The use of the <code dir=ltr>ext.CodeMirror.switch</code> hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the [[mw:Special:MyLanguage/Extension:CodeMirror#Gadgets and user scripts|migration guide]] for more information. [https://phabricator.wikimedia.org/T373720] * The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include [[mw:Special:MyLanguage/API:REST API/Extensions|extension APIs]]. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for [https://phabricator.wikimedia.org/T414470 GrowthExperiments] and [https://phabricator.wikimedia.org/T419053 Wikifunctions] APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the [https://test.wikipedia.org/wiki/Special:RestSandbox REST Sandbox] (i.e., [[{{#Special:RestSandbox}}]], available on all wiki projects). * The [[mw:Special:MyLanguage/Extension:Scribunto|Scribunto]] extension provides different pieces of information about the wiki where the module is being used via the [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual|mw.site]] library. Starting last week, the library also provides a [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#mw.site.wikiId|way]] of accessing the [[mw:Special:MyLanguage/Manual:Wiki ID|wiki ID]] that can be used to facilitate cross-wiki module maintenance. [https://phabricator.wikimedia.org/T146616] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.20|MediaWiki]] '''In depth''' * The [[m:Special:MyLanguage/Coolest Tool Award|2026 Coolest Tool Award]] celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the [https://wikimediafoundation.limesurvey.net/435684?lang=en nomination survey] form by 23 March 2026. For more information on privacy and data handling, please see the [[foundation:Special:MyLanguage/Legal:Coolest_Tool_Award_2026_Survey_Privacy_Statement|survey privacy statement]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:36, 16 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30260505 --> == Wikipedia translation of the week: 2026-13 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Etruscan sculpture]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Frontone A del grande tempio di luni con concilio degli dei, 175-150 ac. ca. 01.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> '''Etruscan sculpture''' was one of the most important artistic expressions of the Etruscan people, who inhabited the regions of Northern Italy and Central Italy between about the 9th century BC and the 1st century BC. Etruscan art was largely a derivation of Greek art, although developed with many characteristics of its own. Given the almost total lack of Etruscan written documents, a problem compounded by the paucity of information on their language—still largely undeciphered—it is in their art that the keys to the reconstruction of their history are to be found, although Greek and Roman chronicles are also of great help. Like its culture in general, Etruscan sculpture has many obscure aspects for scholars, being the subject of controversy and forcing them to propose their interpretations always tentatively, but the consensus is that it was part of the most important and original legacy of Italian art and even contributed significantly to the initial formation of the artistic traditions of ancient Rome. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:07, 23 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30245038 --> == Tech News: 2026-13 == <section begin="technews-2026-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/13|Translations]] are available. '''Weekly highlight''' * Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional [[phab:T417120|"Log in with passkey" button]] will soon be available for users who have already registered a passkey. This update will improve security and user experience. The [[c:File:Passwordless_login_screencast.webm|screen recording]] demonstrates the passwordless login process step by step. * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 25 March 2026 at [https://zonestamp.toolforge.org/1774450800 15:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. '''Updates for editors''' * Wikimedia site users can now export their notifications older than 5 years using a [[toolforge:echo-chamber|new Toolforge tool]]. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced. [https://phabricator.wikimedia.org/T383948] * Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an [[mw:Special:MyLanguage/Moderator Tools/Dashboard|early version of an experience]] that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project. [https://phabricator.wikimedia.org/T402647] * The [[Special:Block]] now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: [[MediaWiki:Ipbreason-indef-dropdown]]. [https://phabricator.wikimedia.org/T401823] * Mobile editors [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#Logged-out|at several wikis]] can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance [[mw:Special:MyLanguage/Contributors/Account Creation Experiments|account creation experience on mobile]] and then increase participation. [https://phabricator.wikimedia.org/T408484] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:36}} community-submitted {{PLURAL:36|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia. '''Updates for technical contributors''' * Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent [https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/EMYTA32EV2V5SQ2JIEOD2CL66YFIZEKV/ cloud-announce email] and update your build configuration as necessary to ensure your tools are compatible. [https://wikitech.wikimedia.org/w/index.php?title=Help:Toolforge/Building_container_images&oldid=2392097#Buildpack_environment_upgrade_process][https://phabricator.wikimedia.org/T380127] * The [https://api.wikimedia.org/wiki/Main_Page API Portal] documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to [[mw:Wikimedia APIs|mediawiki.org]]. Learn more on the [[wikitech:API Portal/Deprecation|project page]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.21|MediaWiki]] '''In depth''' * [[m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]] is considering improvements to [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names|automatically generated reference names in VisualEditor]]. Please check out the [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names#Proposed solutions|proposed solutions]] and participate in the [[m:Talk:WMDE Technical Wishes/References/VisualEditor automatic reference names#Request for comment|request for comment]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:51, 23 March 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30268305 --> == Wikipedia translation of the week: 2026-14 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pulse (nightclub)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Orlando FL Pulse Nightclub01.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pulse''' was a gay bar, dance club, and nightclub in Orlando, Florida, founded in 2004 by Barbara Poma and Ron Legler. On June 12, 2016, the club was the scene of the second-deadliest mass shooting by a single gunman in U.S. history, and the second-deadliest terrorist attack on U.S. soil since the September 11 attacks. Forty-nine people were killed and 58 other people were injured. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:37, 30 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-14 == <section begin="technews-2026-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/14|Translations]] are available. '''Weekly highlight''' * The Beta version of [[abstract:|Abstract Wikipedia]] a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-03-26|Read more]]. '''Updates for editors''' * The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#2. Improve logged-out warning message (T415160)|Read more]]. * The Wikimedia Apps team is inviting feedback on [[mw:Special:MyLanguage/Wikimedia Apps/Team/Future of Editing on the Mobile Apps|how editing should work on the Wikipedia mobile apps]]. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:45}} community-submitted {{PLURAL:45|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where citation fetching from the large newspaper archive [https://www.newspapers.com Newspapers.com] was no longer working, due to a block in [[mw:Special:MyLanguage/Citoid|Citoid]] requests, has now been fixed. [https://phabricator.wikimedia.org/T419903] '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:26, 30 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30329462 --> == Wikipedia translation of the week: 2026-15 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Tofana di Rozes]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Tofana di Rozes 04.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Tofana di Rozes''' (3,225 metres (10,581 ft)) is a mountain of the Dolomites in the Province of Belluno, Veneto, Italy. Located west of the resort of Cortina d'Ampezzo, the mountain's giant three-edged pyramid shape and its vertical south face, above the Falzarego Pass, makes it the most popular peak in the Tofane group, and one of the most popular in the Dolomites. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:27, 6 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-15 == <section begin="technews-2026-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/15|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in [[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Collaborative contributions#Goal setting|the documentation]]. * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] The new [[mw:Special:MyLanguage/Help:Watchlist labels|watchlist labels]] feature (announced in [[m:Special:MyLanguage/Tech/News/2026/07|Tech News 2026-07]]) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via [[Special:EditWatchlist|EditWatchlist]]. In all three places it is a new field following the expiry field. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed. [https://phabricator.wikimedia.org/T419171] '''Updates for technical contributors''' * The [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|sub-referencing feature]], which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to [[phab:T414094|more wikis]] later this year. Wikis using the [[mw:Special:MyLanguage/Reference Tooltips|Reference Tooltips]] gadget are encouraged to update their version (typically at [[m:MediaWiki:Gadget-ReferenceTooltips.js|MediaWiki:Gadget-ReferenceTooltips.js]] as shown [https://en.wikipedia.org/w/index.php?diff=1344408362 here]) to ensure compatibility. Other reference-related gadgets may also be affected. [https://phabricator.wikimedia.org/T416304] * All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. [[m:Wikimedia Foundation Board noticeboard#Board of Trustees Approves Closure of Wikinews|Read more]]. * The [[:mw:Special:MyLanguage/API:Action API|Action API]] has had several formats for requested output. One of them, <bdi lang="zxx" dir="ltr"><code><nowiki>format=php</nowiki></code></bdi>, is being removed soon. Please ensure your scripts or bots use the [[mw:Special:MyLanguage/API:Data formats#Output|JSON format]]. This removal should affect very few scripts and bots. [https://phabricator.wikimedia.org/T118538] * The [[Special:NamespaceInfo|Special:NamespaceInfo]] page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia. [https://phabricator.wikimedia.org/T381455] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.23|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:19, 6 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30362761 --> == Wikipedia translation of the week: 2026-16 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Very-low-calorie diet]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Green smoothie (8222465502).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''very-low-calorie diet''' (VLCD), also known as semistarvation diet and crash diet, is a type of diet with very or extremely low daily food energy consumption. VLCDs are defined as a diet of 800 kilocalories (3,300 kJ) per day or less. Modern medically supervised VLCDs use total meal replacements, with regulated formulations in Europe and Canada which contain the recommended daily requirements for vitamins, minerals, trace elements, fatty acids, protein and electrolyte balance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:56, 13 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-16 == <section begin="technews-2026-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/16|Translations]] are available. '''Weekly highlight''' * Experienced editors are invited to [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Main_Page test] the [[mw:Special:MyLanguage/Article guidance|Article guidance]] feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are [[mw:Special:MyLanguage/Article guidance/Test feature guide|available]]. Also, after reviewing [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Category:Pages_using_article_guidance the outlines], please provide feedback on the [[mw:Talk:Article guidance|project talk page]]. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out [[c:File:Article Guidance workflow demo - April 2026.webm|the video]] explaining the feature. '''Updates for editors''' * On most wikis, all autoconfirmed users can now use [[Special:ChangeContentModel|Special:ChangeContentModel]] page to [[mw:Special:MyLanguage/Help:ChangeContentModel|create new pages with custom content models]], such as mass message lists, making custom page formats more accessible. Check [[Special:ListGroupRights|Special:ListGroupRights]] for the status of your wiki. [https://phabricator.wikimedia.org/T248294] * The Growth team has launched an [[mw:Special:MyLanguage/Contributors/Account_Creation_Experiments|account creation experiment]] to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed. [https://phabricator.wikimedia.org/T382856] '''Updates for technical contributors''' * Starting later this week, {{int:group-abusefilter}} who have the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature enabled will have [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] as the editor at [[Special:AbuseFilter|Special:AbuseFilter]]. This is part of the broader effort to make the user experience more consistent across all editors. [https://phabricator.wikimedia.org/T399673][https://phabricator.wikimedia.org/T419332] * Tools and bots that access the [[mw:Special:MyLanguage/Notifications/API|Notifications API]] (<bdi lang="zxx" dir="ltr"><code><nowiki>action=query&meta=notifications</nowiki></code></bdi>) will need to update their OAuth or BotPassword grants to also include access to private notifications. [https://phabricator.wikimedia.org/T421991] * Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia). [https://phabricator.wikimedia.org/T422544] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.24|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:19, 13 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30380527 --> == Wikipedia translation of the week: 2026-17 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Chromodoris willani]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Babosa de mar (Chromodoris willani), Anilao, Filipinas, 2023-08-24, DD 34.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Chromodoris willani''''', commonly known as Willan's chromodoris, is a species of sea slug, a dorid nudibranch, a shell-less marine gastropod mollusk in the family Chromodorididae. The species is named for the renowned nudibranch taxonomist Dr. Richard C. Willan. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:34, 20 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30430366 --> == Tech News: 2026-17 == <section begin="technews-2026-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/17|Translations]] are available. '''Weekly highlight''' * After two years of development, [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]], also known as [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror 6]], is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other [[mw:Special:MyLanguage/Help:Extension:CodeMirror|benefits]] to all users of the standard syntax highlighter. A huge thank you to volunteer [https://phabricator.wikimedia.org/p/Bhsd/ Bhsd] who developed many of the new features, including [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Code folding|code folding]], [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Autocompletion|autocompletion]], and [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|linting]]. [https://phabricator.wikimedia.org/T259059] * A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design. [https://apps.apple.com/us/app/wikipedia/id324715238 Download the latest version] and explore the update. '''Updates for editors''' * [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|Reading lists]] is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias. * An experiment which explores extending [[mw:Special:MyLanguage/Readers/Reader Growth/Mobile page previews|Page Previews to mobile web]] will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps. [[m:Special:MyLanguage/List of experiments in Product and Technology#Template|Read more about this experiment and others]]. * On several wikis, logged-in editors who haven't [[mw:Special:MyLanguage/Help:Email confirmation|confirmed their email addresses]] can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it. [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security#Encouraging users to confirm their email addresses|Learn more]]. [https://phabricator.wikimedia.org/T421366] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:15}} community-submitted {{PLURAL:15|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed. [https://phabricator.wikimedia.org/T184857] '''Updates for technical contributors''' * As part of the promotion of [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror]] from a beta feature, all users will use [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages. [https://phabricator.wikimedia.org/T419332] * The <code>mirrors.wikimedia.org</code> service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/LJYRIS4WB66HIRCAO4GIDTXCMDVZRBMA/ You can read more]. [https://phabricator.wikimedia.org/T416707] * The <bdi lang="zxx" dir="ltr"><code><nowiki>image</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>oldimage</nowiki></code></bdi> table will be removed from [[wikitech:Help:Wiki Replicas|wikireplicas]]. If your tools or queries access <bdi lang="zxx" dir="ltr"><code><nowiki>image</nowiki></code></bdi> or <bdi lang="zxx" dir="ltr"><code><nowiki>oldimage</nowiki></code></bdi> directly, please update them to use the <bdi lang="zxx" dir="ltr"><code><nowiki>file</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>filerevision</nowiki></code></bdi> table before 28 May. [https://phabricator.wikimedia.org/T28741] * Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]] by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]] and [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits/FAQ|Frequently Asked Questions]]. * The [[mw:Special:MyLanguage/Attribution API|Attribution API]] is now available as a [[mw:Special:MyLanguage/Wikimedia APIs/Stability policy|beta]]. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the [https://en.wikipedia.org/w/index.php?api=attribution.v0-beta&title=Special%3ARestSandbox REST sandbox on English Wikipedia]). Share your feedback on the [[mw:Talk:Attribution API|project talk page]]. * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:01, 20 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30432763 --> == Wikipedia translation of the week: 2026-18 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Platypus venom]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Platypus spur.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> The platypus is one of the few living mammals to produce venom. The venom is made in venom glands that are connected to hollow spurs on their hind legs; it is primarily made during the mating season.[1] While the venom's effects are described as extremely painful, it is not lethal to humans. Many archaic mammal groups possess similar tarsal spurs, so it is thought that, rather than having developed this characteristic uniquely, the platypus simply inherited this characteristic from its ancestors. Rather than being a unique outlier, the platypus is the last demonstration of what was once a common mammalian characteristic, and it can be used as a model for non-therian mammals and their venom delivery and properties. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 27 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30449041 --> == Tech News: 2026-18 == <section begin="technews-2026-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/18|Translations]] are available. '''Updates for editors''' * There is a change in how new users are autoconfirmed that will improve anti-vandalism protection. Currently, users who have had an account for a few days and made a few edits are automatically added to the [[{{int:grouppage-autoconfirmed/{{CONTENTLANGUAGE}}}}|{{int:group-autoconfirmed}}]] group. This configuration tends to be exploited by some vandals, who create accounts and start to use them only after some time. To mitigate this, the configuration will be updated next week so that – for the purpose of becoming autoconfirmed – the account age will be counted from their first edit, instead of registration date. The numeric value of the age threshold will remain the same. This change will be deployed only to wikis which require at least one edit as part of the autoconfirmation conditions. [https://phabricator.wikimedia.org/T418484] * All Wikipedia users with new accounts and those who activated the "automatically enable most beta features" option in their preference can now use the [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|reading lists]] beta feature to save articles for later reading. This helps organize reading interests in one place for convenient access. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where infobox images have huge padding in Firefox, has been fixed. [https://phabricator.wikimedia.org/T423676] '''Updates for technical contributors''' * As a reminder, the global API rate limits will be applied this week to identified API traffic. This is to help ensure [[mw:MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]]. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, including the actual rate limits, see [[mw:Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]] and [[mw:Wikimedia APIs/Rate limits/FAQ|Frequently Asked Questions]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.26|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:06, 27 April 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30458046 --> == Wikipedia translation of the week: 2026-19 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kuwait National Assembly Building]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Kuwait City Arabian Gulf Street 10.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Kuwait National Assembly Building''' is the building that housed the National Assembly of Kuwait. Designed by Danish architect Jørn Utzon in 1972, it was completed in 1982 under the direction of his son Jan. The structural design was by Max Walt. The building was seriously damaged in February 1991 when retreating Iraqi troops set it on fire but has since been restored. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:16, 4 May 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30464799 --> == Tech News: 2026-19 == <section begin="technews-2026-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/19|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Article guidance|Article guidance]] team invites experienced editors of [[mw:Special:MyLanguage/Article guidance/Pilot wikis and collaborators|pilot Wikipedias]]—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Category:Pages_using_article_guidance sample outlines]. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Special:NewArticle the feature] once it is launched in May 2026. [[mw:Special:MyLanguage/Article guidance#Adapting a sample outline in a Wikipedia|Simple instructions]] on how to translate and adapt the outlines are available. '''Updates for editors''' * The [[:m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] has published [[:m:Special:MyLanguage/Product and Technology Advisory Council/May 2026 draft PTAC recommendation for feedback|draft recommendations]] on a model that affiliates can follow when contributing to the technical space. Community members are invited to provide feedback on the recommendation until May 8th [[:m:Talk:Product and Technology Advisory Council/May 2026 draft PTAC recommendation for feedback|on the talk page]]. * The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so. [https://phabricator.wikimedia.org/T424909] * From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and [[m:Special:MyLanguage/Global reminder bot|Global reminder bot]] in that the latter reminds users a week ''before'' the rights are due to expire, so that they can renew the rights. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the problem where the ULS language selector in [[m:Special:Translate|Special:Translate]] would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages. [https://phabricator.wikimedia.org/T358864] * The [[m:Special:GlobalWatchlist|Global Watchlist]], which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as [[:d:|Wikidata]] now support [[mw:Special:MyLanguage/Extension:EntitySchema|EntitySchema]] elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|global API rate limits]] for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed. [https://phabricator.wikimedia.org/T415450][https://phabricator.wikimedia.org/T424422][https://phabricator.wikimedia.org/T418091] '''Updates for technical contributors''' * The second phase of [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|global API rate limits]] has been rolled out to reduce the [[diffblog:2026/03/26/quo-vadis-crawlers-progress-and-whats-next-on-safeguarding-our-infrastructure/|impact of AI crawlers]] and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits#Limits|Limits]] have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.27|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:44, 4 May 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30498077 --> iqp9qiltwxbohpbmbk9iv7x35ai5dz9 3 466307 4634232 4632975 2026-05-05T08:45:07Z Dan Polansky 78491 4634232 wikitext text/x-wiki {{talk header}} {{User:MiszaBot/config |archive = User talk:Codename Noreste/Archive %(counter)d |algo = old(14d) |counter = 1 |maxarchivesize = 100K |archiveheader = {{Automatic archive navigator}} |minthreadstoarchive = 1 |minthreadsleft = 1 }} == Future of game coverage on Wikimedia wikis == Hi, what's the future of video game coverage on Wikimedia wikis? I'm a major proponent of in-depth gaming coverage, even though I'm aware places like the English Wikipedia don't easy allow for its inclusion. I've also opened a question if Simple English Wikipedia can [https://simple.wikipedia.org/wiki/Wikipedia_talk:Notability#Scope loosen its scope], partly to help with the accessibility of niche topics that people who may not understand English well can read that may not be presentable as such elsewhere. Or is Wikibooks the only true Wikimedia project for in-depth game coverage, just through a textbook or instruction manual lens? [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 00:20, 17 April 2026 (UTC) : I'm afraid that I may not able to answer that, apart that you comply with Wikibooks' scope. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) == Deletion of Subpage == Hello Codename Noreste You have recently deleted a subpage in "my" Wikibook for Publications: https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia This was a page for a variety of publications which were deleted summarily about 6 months ago at a time when personal matters intervened and I was unable to respond adequately. Would you please undelete this subpage as I will shortly be seeking to have most of the publications restored (they are in the public domain). Thanks Sam Dellit [[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:46, 26 April 2026 (UTC) : Hi, which subpage would you want to be restored? Some context: @[[User:ShakespeareFan00|ShakespeareFan00]] tagged these as copyright violations which I couldn’t tell if they are, and they said they were. I deleted them, until you notified me here. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:51, 26 April 2026 (UTC) ::Hello Codename Noreste ::The primary page is here: ::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::If you could undelete the subpages also, that would be great (sorry, I have no record of what they were). ::Then I could start including proof of public domain for as many as possible (I am now again active on Wikibooks). ::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:57, 26 April 2026 (UTC) ::: @[[User:Samuel.dellit|Samuel.dellit]] They are now undeleted, so you can make the necessary changes. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) ::::Thank you, I can now see: ::::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::::But I still can't see any of the subpages ::::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 03:03, 27 April 2026 (UTC) ::::: Try restoring [[Special:Permalink/4019477|this version]], thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:10, 27 April 2026 (UTC) :{{ping|Samuel.dellit}} Reverted the tags, you should see the articles, I suggest you look into the authors of articles of transcribed articles and confirm they ALL died before 1946 ( Australia at the date of the Issues concerned was 50 pma, making it (disapointinhly that anything still in copyright in Australia in 1996, got a full US term due to URAA, NOT a 28 year and renewal as might be expected.). If you don't provide further biographical detail for the authors, these publication transcriptions will be considered copyvio, and retagged. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:01, 27 April 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Markdown == Can you clarify why you deleted [[Markdown]]? The deletion summary says "Mass deletion of abandoned/orphaned/out of scope pages with minimal or no content. (sysop action)". It did not seem to fail a RFD and from what I remeber, it was a short instructional page I made on Markdown. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 08:45, 5 May 2026 (UTC) nehzi2q5bxenzwag9eq7fn4umjdze58 4634233 4634232 2026-05-05T08:46:35Z Dan Polansky 78491 /* Markdown */ 4634233 wikitext text/x-wiki {{talk header}} {{User:MiszaBot/config |archive = User talk:Codename Noreste/Archive %(counter)d |algo = old(14d) |counter = 1 |maxarchivesize = 100K |archiveheader = {{Automatic archive navigator}} |minthreadstoarchive = 1 |minthreadsleft = 1 }} == Future of game coverage on Wikimedia wikis == Hi, what's the future of video game coverage on Wikimedia wikis? I'm a major proponent of in-depth gaming coverage, even though I'm aware places like the English Wikipedia don't easy allow for its inclusion. I've also opened a question if Simple English Wikipedia can [https://simple.wikipedia.org/wiki/Wikipedia_talk:Notability#Scope loosen its scope], partly to help with the accessibility of niche topics that people who may not understand English well can read that may not be presentable as such elsewhere. Or is Wikibooks the only true Wikimedia project for in-depth game coverage, just through a textbook or instruction manual lens? [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 00:20, 17 April 2026 (UTC) : I'm afraid that I may not able to answer that, apart that you comply with Wikibooks' scope. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) == Deletion of Subpage == Hello Codename Noreste You have recently deleted a subpage in "my" Wikibook for Publications: https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia This was a page for a variety of publications which were deleted summarily about 6 months ago at a time when personal matters intervened and I was unable to respond adequately. Would you please undelete this subpage as I will shortly be seeking to have most of the publications restored (they are in the public domain). Thanks Sam Dellit [[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:46, 26 April 2026 (UTC) : Hi, which subpage would you want to be restored? Some context: @[[User:ShakespeareFan00|ShakespeareFan00]] tagged these as copyright violations which I couldn’t tell if they are, and they said they were. I deleted them, until you notified me here. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:51, 26 April 2026 (UTC) ::Hello Codename Noreste ::The primary page is here: ::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::If you could undelete the subpages also, that would be great (sorry, I have no record of what they were). ::Then I could start including proof of public domain for as many as possible (I am now again active on Wikibooks). ::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:57, 26 April 2026 (UTC) ::: @[[User:Samuel.dellit|Samuel.dellit]] They are now undeleted, so you can make the necessary changes. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) ::::Thank you, I can now see: ::::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::::But I still can't see any of the subpages ::::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 03:03, 27 April 2026 (UTC) ::::: Try restoring [[Special:Permalink/4019477|this version]], thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:10, 27 April 2026 (UTC) :{{ping|Samuel.dellit}} Reverted the tags, you should see the articles, I suggest you look into the authors of articles of transcribed articles and confirm they ALL died before 1946 ( Australia at the date of the Issues concerned was 50 pma, making it (disapointinhly that anything still in copyright in Australia in 1996, got a full US term due to URAA, NOT a 28 year and renewal as might be expected.). If you don't provide further biographical detail for the authors, these publication transcriptions will be considered copyvio, and retagged. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:01, 27 April 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Markdown == Can you clarify why you deleted [[Markdown]]? The deletion summary says "Mass deletion of abandoned/orphaned/out of scope pages with minimal or no content. (sysop action)". It did not seem to fail a RFD and from what I remeber, it was a short instructional page I made on Markdown. The page is in [https://web.archive.org/web/20250427011600/https://en.wikibooks.org/wiki/Markdown Wayback Machine]. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 08:46, 5 May 2026 (UTC) fb8oxsalt0lpocu01x1aj6vxl20ul53 4634236 4634233 2026-05-05T08:53:46Z Dan Polansky 78491 /* Markdown */ 4634236 wikitext text/x-wiki {{talk header}} {{User:MiszaBot/config |archive = User talk:Codename Noreste/Archive %(counter)d |algo = old(14d) |counter = 1 |maxarchivesize = 100K |archiveheader = {{Automatic archive navigator}} |minthreadstoarchive = 1 |minthreadsleft = 1 }} == Future of game coverage on Wikimedia wikis == Hi, what's the future of video game coverage on Wikimedia wikis? I'm a major proponent of in-depth gaming coverage, even though I'm aware places like the English Wikipedia don't easy allow for its inclusion. I've also opened a question if Simple English Wikipedia can [https://simple.wikipedia.org/wiki/Wikipedia_talk:Notability#Scope loosen its scope], partly to help with the accessibility of niche topics that people who may not understand English well can read that may not be presentable as such elsewhere. Or is Wikibooks the only true Wikimedia project for in-depth game coverage, just through a textbook or instruction manual lens? [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 00:20, 17 April 2026 (UTC) : I'm afraid that I may not able to answer that, apart that you comply with Wikibooks' scope. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) == Deletion of Subpage == Hello Codename Noreste You have recently deleted a subpage in "my" Wikibook for Publications: https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia This was a page for a variety of publications which were deleted summarily about 6 months ago at a time when personal matters intervened and I was unable to respond adequately. Would you please undelete this subpage as I will shortly be seeking to have most of the publications restored (they are in the public domain). Thanks Sam Dellit [[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:46, 26 April 2026 (UTC) : Hi, which subpage would you want to be restored? Some context: @[[User:ShakespeareFan00|ShakespeareFan00]] tagged these as copyright violations which I couldn’t tell if they are, and they said they were. I deleted them, until you notified me here. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:51, 26 April 2026 (UTC) ::Hello Codename Noreste ::The primary page is here: ::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::If you could undelete the subpages also, that would be great (sorry, I have no record of what they were). ::Then I could start including proof of public domain for as many as possible (I am now again active on Wikibooks). ::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:57, 26 April 2026 (UTC) ::: @[[User:Samuel.dellit|Samuel.dellit]] They are now undeleted, so you can make the necessary changes. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) ::::Thank you, I can now see: ::::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::::But I still can't see any of the subpages ::::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 03:03, 27 April 2026 (UTC) ::::: Try restoring [[Special:Permalink/4019477|this version]], thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:10, 27 April 2026 (UTC) :{{ping|Samuel.dellit}} Reverted the tags, you should see the articles, I suggest you look into the authors of articles of transcribed articles and confirm they ALL died before 1946 ( Australia at the date of the Issues concerned was 50 pma, making it (disapointinhly that anything still in copyright in Australia in 1996, got a full US term due to URAA, NOT a 28 year and renewal as might be expected.). If you don't provide further biographical detail for the authors, these publication transcriptions will be considered copyvio, and retagged. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:01, 27 April 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Markdown == Can you clarify why you deleted [[Markdown]]? The deletion summary says "Mass deletion of abandoned/orphaned/out of scope pages with minimal or no content. (sysop action)". It did not seem to fail a RFD and from what I remeber, it was a short instructional page I made on Markdown. The page is in [https://web.archive.org/web/20250427011600/https://en.wikibooks.org/wiki/Markdown Wayback Machine]. Actually, can you please undelete the page, send it to RFD if you are still convinced it should be deleted, and ping me? I think it is a neat little page providing minimum useful artifact and can be expanded later. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 08:53, 5 May 2026 (UTC) 2mz22zvonjd49048z8lpakjc1tsfzwf 0 470777 4634088 4451700 2026-05-04T15:17:40Z Humzarubel 3581183 Beginning of introduction of section on AI usage in the gaming industry, and minor revisions throughout document scope to broaden article. 4634088 wikitext text/x-wiki == Overview == === Introduction === Artificial intelligence (AI) is revolutionizing creative industries, such as the music industry, by redefining how creative works are composed, performed, and consumed. What began as theoretical musings by pioneers like Alan Turing has grown into a field with sophisticated neural networks capable of composing full-length songs, for example. However, this evolution raises pressing questions about originality, ownership, and the future of human creativity. === History of AI and Music === ====== Theoretical Foundations: 1950s-1960s ====== The concept of AI-generated music originated with Alan Turing, who theorized in the 1950s that machines could emulate human cognitive processes, including music composition. His ideas laid the groundwork for computational creativity.<ref>{{Citation |last=Copeland |first=B. Jack |title=Turing and the History of Computer Music |date=2017 |url=https://link.springer.com/chapter/10.1007/978-3-319-53280-6_8 |work=Philosophical Explorations of the Legacy of Alan Turing: Turing 100 |pages=189–218 |editor-last=Floyd |editor-first=Juliet |access-date=2024-12-02 |place=Cham |publisher=Springer International Publishing |language=en |doi=10.1007/978-3-319-53280-6_8 |isbn=978-3-319-53280-6 |last2=Long |first2=Jason |editor2-last=Bokulich |editor2-first=Alisa}}</ref> In 1957, Lejaren Hiller and Leonard Isaacson at the University of Illinois created the Illiac Suite<ref>{{Cite web |title=ILLIAC Suite – Illinois Distributed Museum |url=https://distributedmuseum.illinois.edu/exhibit/illiac-suite/ |access-date=2024-12-02 |website=distributedmuseum.illinois.edu}}</ref>. Using the ILLIAC I computer, they developed an algorithmic process to compose a string quartet, marking one of the first successful instances of computer-generated music. It demonstrated the potential of computers to collaborate in creative endeavors, sparking decades of research into AI's role in music. ====== Rule-Based Systems: 1970s-1980s ====== During the 1970s and 1980s, AI systems advanced with rule-based algorithms that mimicked specific musical styles. David Cope’s Experiments in Musical Intelligence<ref>{{Cite web |last=tluong |date=2015-04-29 |title=Algorithmic Music – David Cope and EMI |url=https://computerhistory.org/blog/algorithmic-music-david-cope-and-emi/ |access-date=2024-12-02 |website=CHM |language=en}}</ref> (EMI) exemplified this approach by analyzing existing compositions and generating new ones in the style of Bach and Mozart. However, EMI heavily relied on predefined human rules, highlighting the imitative, rather than generative, nature of early AI. A significant technological leap came in 1983 with the introduction of MIDI<ref>{{Citation |title=MIDI |date=2024-11-25 |url=https://en.wikipedia.org/wiki/MIDI |work=Wikipedia |access-date=2024-12-02 |language=en}}</ref> (Musical Instrument Digital Interface). MIDI standardized communication between computers and electronic instruments, enabling precise control of musical elements and facilitating data collection for future AI systems. ====== Machine Learning: 1990s-2000s ====== AI music systems transitioned from rule-based models to data-driven techniques in the 1990s. Machine learning algorithms enabled pattern recognition and predictive modeling, allowing AI to generate more complex and varied compositions. Projects like Accenture’s Symphonologie<ref>{{Cite web |title=Accenture {{!}} Symphonologie |url=https://www.oneclub.org/awards/theoneshow/-award/25489/symphonologie/ |access-date=2024-12-02 |website=www.oneclub.org |language=en}}</ref> showcased AI as a collaborative tool, blending human and machine creativity. ====== Neural Networks: 2010s-Present ====== The rise of deep learning revolutionized AI in music. Neural networks, trained on vast datasets, now compose intricate, multi-instrumental pieces in seconds. Tools like OpenAI’s MuseNet<ref>{{Cite web |title=MuseNet |url=https://openai.com/index/musenet/ |access-date=2024-12-02 |website=openai.com |language=en-US}}</ref> and AIVA<ref>{{Cite web |title=AIVA, the AI Music Generation Assistant |url=https://www.aiva.ai/ |access-date=2024-12-02 |website=www.aiva.ai |language=en}}</ref> exemplify how AI has expanded its creative capabilities across genres, challenging the boundaries of human artistry. == Relevant Legal Disputes == === Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884) === [[File:Oscar Wilde 1882.jpg|thumb|Oscar Wilde No.18 by Napoleon Sarony (1882)]] [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithography Co v. Sarony]] was submitted on December 13, 1883 when Sarony filed a copyright suit against Burrow-Giles when the company had marketed lithographs of Sarony's photograph, Oscar Wilde No.18, without Sarony's permission. Burrow-Giles argued that photographs were neither writings nor a production of an author, and thus did not possess copyright protection. The court determined that even though creating a photograph is "merely mechanical, with no place for novelty, invention, or originality", the photograph Sarony created was his "own original mental conception, to which he gave visible form by posing the said Oscar Wilde in front of the camera, selecting and arranging the costume, draperies, . . . suggesting and evoking the desired expression, and from such . . . representation, made entirely by plaintiff, he produced the picture in suit.'" On March 17, 1884, the court established that photography is a copyrightable medium. Furthermore, this case reinforced that an author of a work is "he to whom anything owes its origin."<ref>Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884)</ref> === Naruto v. Slater, No. 16-15469 (9th Cir. 2018) === [[File:Macaca nigra self-portrait large.jpg|left|thumb|One of the monkey selfies]] Naruto v. Slater, more commonly known as the [[wikipedia:Artificial_intelligence_and_copyright|Monkey Selfie copyright dispute]], began on September 22, 2015. PETA, representing the crested macaque Naruto, sued Slater claiming that because the monkey took its own picture, it was entitled to the copyright. David J. Slater, the photographer, argued that he held the copyright as he engineered the situation that led to the monkey taking its selfie. On April 23, 2018, the court determined that "this monkey - and all animals, since they are not human – [lack] statutory standing under the Copyright Act", reinforcing that non-humans cannot own copyright.<ref>Naruto v. Slater, No. 16-15469 (9th Cir. 2018)</ref> === Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023) === [[File:A Recent Entrance to Paradise.jpg|thumb|A Recent Entrance to Paradise]] Thaler v. Perlmutter emerged after the U.S. Copyright Office denied Dr. Stephen Thaler's copyright application for an AI generated work, "A Recent Entrance to Paradise". The court focused on answering "whether a work generated autonomously by a computer falls under the protection of copyright law upon its creation". Thaler filed a lawsuit, arguing that the copyright of the AI generated work belonged to him as the AI model's creator. He stated that "AI should be ‘acknowledge[d] . . . as an author where it otherwise meets authorship criteria, with any copyright ownership vesting in the AI’s owner.’" The court reviewed the decision of [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithographic Co. v. Sarony]], finding that the author of any AI generated work would be the AI. However, following the decision of [[wikipedia:Artificial_intelligence_and_copyright|Naruto v. Slater]], since AIs are not human, they cannot hold copyright. The case was decided on August 18, 2023, confirming that AIs cannot hold copyright. As such, the work fell under public domain. However, the court explicitly stated that they were not making any decisions on "how much human input is necessary to qualify the user of an AI system as an 'author' of a generated work".<ref>Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023)</ref> === Zarya of the Dawn === [[File:Zarya of the Dawn cover.webp|thumb|Zarya of the Dawn by Kristina Kashtanova]] [[wikipedia:Zarya_of_the_Dawn|Zarya of the Dawn]], a comic book authored by Kristina Kashtanova and illustrated using the AI generator Midjourney sparked a significant copyright dispute in 2022. When Kashtanova applied for copyright of the comic in September 2022, she failed to disclose that the images were generated by Midjourney. The comic was originally granted copyright by the Copyright Office, but after discovering Midjourney's involvement in illustrating the comic, they reviewed their decision. While the Copyright Office agreed that the text and compilation (the arrangement of images and text) were copyrightable, the art was not, as the "process is not controlled by the user because it is not possible to predict what Midjourney will create ahead of time." Although, Kashtanova claimed "she personally edited some of the images created by Midjourney", the Copyright office could not determine "what expression in the image was contributed through her use of Photoshop as opposed to generated by Midjourney" and thus revoked the copyright. <ref>{{Cite web |last=Kasunic |first=Robert J. |date=February 21, 2023 |title=2023.02.21 Zarya of the Dawn Letter |url=https://www.copyright.gov/docs/zarya-of-the-dawn.pdf |url-status=live |access-date=December 9, 2024 |website=Copyright Office (.gov)}}</ref> == Relevant Copyright Chapters == === Chapter 308: The Originality Requirement<ref name=":0">U.S. Copyright Office, Compendium of U.S. Copyright Office Practices § 101 (3d ed. 2021).</ref> === The Originality Requirement has two primary requirements: "The work must be ‘independently created by the author’ and it must possess ‘at least some minimal degree of creativity’" ==== Chapter 308.1 ==== The Copyright Act defines "independent creation" as a work created "without copying from other works." However, "a work may satisfy the independent creation requirement ‘even though it closely resembles other works so long as the similarity is fortuitous, not the result of copying.’" ==== Chapter 308.2 ==== In terms of creativity, the Copyright Act states that "‘the requisite level of creativity is extremely low.’ Even a ‘slight amount’ of creative expression will suffice.’" ==== Works That Do Not Satisfy the Originality Requirement ==== 313.4(A): Mere Copies 313.4(K): Mere Variations of Colorings === Chapter 306: The Human Authorship Requirement<ref name=":0" /> === The Human Authorship Requirement states that only humans may own a copyright. "The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being." ==== Chapter 313.2 ==== The chapter states that "the U.S. Copyright Office will not register works produced by nature, animals, or plants." Furthermore, "the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author." ==== Works That Lack Human Authorship ==== * A photograph taken by a monkey. * A mural painted by an elephant. * A claim based on the appearance of actual animal skin. * A claim based on driftwood that has been shaped and smoothed by the ocean. * A claim based on cut marks, defects, and other qualities found in natural stone. * An application for a song naming the Holy Spirit as the author of the work. === Chapter 507.1: Derivate Works<ref name=":0" /> === As AI generated works are considered to be authored by the AI, and thus public domain, attempts to edit and then copyright the works would most likely fall under derivative works. The Copyright Act defines a derivative work as "a work based upon one or more preexisting works, such as a . . . art reproduction . . . or any other form in which a work may be recast, transformed, or adapted." ==== Chapter 311.2 ==== Derivative works follow the same originality requirements as original works. Derivative works may only receive copyright protection "provided that [the work] contains a sufficient amount of original expression, meaning that the derivative work must be independently created and it must possess more than a modicum of creativity" The Copyright Act does reiterate that "[m]iniscule variations do not satisfy this requirement, such as merely changing the size of the preexisting work." == Present Issues == === AI Music === ==== Lack of Creativity ==== In 2023, an anonymous creator known as "Ghostwriter" released Heart on My Sleeve, featuring AI-generated vocals mimicking Drake and The Weeknd. The song went viral, drawing millions of streams before being removed for copyright infringement. Universal Music Group argued that the AI-generated track exploited the artists’ likenesses without consent, raising ethical and legal concerns<ref>{{Cite web |last=Reed |first=Rachel |title=AI created a song mimicking the work of Drake and The Weeknd. What does that mean for copyright law? |url=https://hls.harvard.edu/today/ai-created-a-song-mimicking-the-work-of-drake-and-the-weeknd-what-does-that-mean-for-copyright-law/ |access-date=2024-12-02 |website=Harvard Law School |language=en-us}}</ref>. This case highlights AI’s ability to imitate human creativity so convincingly that it blurs the line between originality and replication. Although the creator faced no legal repercussions, the controversy underscored the need for clearer regulations on AI-generated content. * AI doesn’t create entirely new works; it amplifies patterns derived from training data. While it can replicate styles, it lacks the emotional depth and intentionality of human artistry. * Tools like MuseNet and Suno allow anyone to compose music in minutes, potentially devaluing human creativity by making artistic production instantaneous and impersonal. ==== Suno and Udio ==== The most current case reflecting the debate regarding the originality of AI music is in the RIAA vs. Suno and RIAA vs. Udio. The RIAA, or the Recording Industry Association of America, is a trade organization that represents many record labels, including Sony Music Group, Universal Music Group, and Warner Music Group (colloquially known as "the big Three" in the industry as they own up to 85% of market share). In June 2024, the RIAA placed a copyright infringement lawsuit on Suno and Udio (two generative AI music startup companies). They had three main goals with this lawsuit: <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html#:~:text=The%20lawsuits%20make%20three%20specific,to%20nine%20figures%20or%20more. |access-date=2024-12-10 |website=Vulture |language=en}}</ref> # To have these companies admit their models use copyrighted music. # Immediately stop training their AI models using this copyrighted music. # Seek damages up to $150,000 per song used in the models. When first discussing the lawsuit with the press, Chairman and CEO of RIAA, Mitch Glazier, stated: "The music community has embraced AI and we are already partnering and collaborating with responsible developers to build sustainable AI tools centered on human creativity '''that put artists and songwriters in charge''', but we can only succeed if developers are willing to work together with us. Unlicensed services like Suno and Udio that '''claim it's 'fair' to copy an artist's life's work and exploit it for their own profit without consent or pay''' set back the promise of genuinely innovative AI for us all."<ref>{{Cite web |last=Connelly |first=Rose |date=2024-06-24 |title=Record Companies Bring Landmark Cases for Responsible AI Against Suno and Udio in Boston and New York Federal Courts, Respectively |url=https://www.riaa.com/record-companies-bring-landmark-cases-for-responsible-ai-againstsuno-and-udio-in-boston-and-new-york-federal-courts-respectively/ |access-date=2024-12-10 |website=RIAA |language=en-US}}</ref> The RIAA hopes to reflect that the inherent moral value of this statement for pursuing this lawsuit is protecting artists' work and fair pay. However, in any of RIAA's arguments, the percentage of and how the money collected from damages will be distributed to the artists of each respective record label must be clarified. Suno responded to the copyright lawsuit, "What the major record labels really don't want is competition." While this calls to question the actual motive of the lawsuit and whether the benefactors will include artists, the results of this lawsuit are pertinent as they will set further precedents in how copyright pertains to AI overall. Initially, in response to the lawsuit, Udio claimed "fair use," which is primarily used for academic or journalistic purposes. However, lawyers dismissed this claim because their training is not used for human-created content. <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html |access-date=2024-12-10 |website=Vulture |language=en}}</ref> As the lawsuit proceeded, both companies admitted to using copyrighted music only as "intermediate copies." They sighted a copyright case from 2021 regarding an AI algorithm's use of copyrighted images to create a search algorithm. In that case, using these "intermediate copies was lawful" because these lower-resolution copies did not satisfy the user's desire to see the full images. However, in Suno and Udio's context, their AI models are not search algorithms but are generative.  ==== Other AI Music Lawsuits ==== Following this case, different record labels (primarily Universal) have filed a copyright on issues regarding AI music. On October 18, 2023, several record labels, namely Universal, filed a lawsuit alleging that Anthropic's AI chatbot, "Claude," unlawfully copied and disseminated copyrighted works, including lyrics "owned or controlled by the Publishers. On January 31, 2024, the copyright license agreement between Universal Music Group (UMG), the world's largest music company, and TikTok owner ByteDance Ltd. expired without a renewal agreement. TikTok was forced to turn off the reproduction of all audio content from artists belonging to UMG's catalog, including Taylor Swift, Billie Eilish, Romeo Santos, J Balvin, and Imagine Dragons, among many others. During these negotiations, UMG made AI-generated music a sticking point in their TikTok negotiations, and a group of musicians spoke out against AI-generated music. Groups, including the Recording Academy, the Music Workers Alliance, the National Association of Music Publishers, the American Association of Independent Music, and even SAG-AFTRA, have all made statements supporting the lawsuits. ==== Ethical Implications of AI in the Music Industry ==== As is apparent with the growing number of lawsuits directed at AI music companies, advancements in AI bring new possibilities for creativity and efficiency along with critical ethical concerns regarding economic impact, bias, and data harvesting. AI’s role in the music industry is a double-edged sword, offering both opportunities and challenges. On the one hand, AI automates many aspects of music creation and production. Tasks like composition, audio mastering, and even lyric writing can now be performed by AI tools. However, this automation has led to concerns about job displacement. Traditional roles in the industry, such as sound engineers and live musicians, face increasing obsolescence as AI tools become more sophisticated and accessible. However, AI also democratizes music production, enabling independent artists and smaller labels to create high-quality music without needing expensive equipment or studio time. So, while jobs are being lost, new roles are emerging, such as AI music curators and prompt engineers. This demonstrates how technological advancements can create fresh opportunities even as they disrupt existing systems. Another critical issue in the use of AI in music is the presence of bias in the models used to generate content. AI systems are only as good as the data they are trained on, and this dependency can result in significant imbalances. For instance, if an AI model’s training data predominantly features Western music, the system may struggle to generate accurate representations of non-Western genres or cultural styles. Along with racial bias, gender bias in datasets used for AI training can perpetuate existing inequalities in the music industry. If female and non-binary artists are underrepresented in the data, AI-generated music may disproportionately reflect the styles and contributions of male artists. Such biases highlight the need for diverse and inclusive training datasets. Developers must address these issues to ensure that AI tools reflect a broader and more equitable spectrum of musical expression. As discussed previously, the question of how AI systems source their training data has sparked widespread ethical debates. Many AI models, most notably Suno and Udio, are trained using copyrighted music, often without the consent or compensation of the original artists and have received backlash. This practice raises significant concerns about exploitation. Artists invest considerable time and effort into creating music, yet their work can be appropriated by AI systems without acknowledgment or financial remuneration. This mirrors controversies in other areas of AI, such as the exploitation of the unpaid labor of associated with Remotask workers. If creators cannot safeguard their work against unauthorized use by AI systems, the industry risks devaluing artistic contributions in favor of technological efficiency. The music industry is at a crossroads–do we protect the rights of creators, or do we embrace AI-drive efficiency without clear ethical guidelines? === AI in the Video Game Industry === The intersection of visual art, music, voice, and code make the gaming industry a hot spot for AI usage within creative works. AI has existed within gaming for some time in the form of non-playable characters (NPCs), but the modern implementation of AI within gaming specifically sees increased usage of generative tools for creative purposes. === Nvidia DLSS 5.0 === Nvidia is a prolific graphics card producer with extensive ties to the gaming industry. Originally founded for the purpose of innovating computer gaming<ref>{{Cite web |title=NVIDIA Corporation: History |url=https://www.nvidia.com/en-us/about-nvidia/corporate-timeline/ |access-date=2026-05-04 |website=NVIDIA |language=en-us}}</ref>, they have since leveraged their graphics processing unit (GPU) technology for AI usage extensively, while also seeking to implement AI within their gaming technologies. Deep Learning Super Sampling (DLSS) is a technology developed by Nvidia to use real-time deep learning AI to upscale video game rendering. The initial versions of DLSS were employed by running games at a lower native resolution, then using AI to upscale to a higher resolution based on the picture generated by the GPU<ref>{{Cite web |last=Martindale |first=Jon |date=2020-02-14 |title=Nvidia RTX DLSS: everything you need to know |url=https://www.digitaltrends.com/computing/everything-you-need-to-know-about-nvidias-rtx-dlss-technology/ |access-date=2026-05-04 |website=Digital Trends |language=en-us}}</ref>; this implementation did not use AI to directly modify any of the actual contents of games themselves. DLSS 5.0, however, made use of generative AI to attempt to directly enhance the visual content of games. While the exact details of the implementation have yet to be released as of May 2026, the technology appears to generate new frames from prior training data, using the existing content of a game as the base. This introduces elements of the rendering which may not have been present in the original developer's vision. == Reception == === Music === ==== Students ==== While students seem to find AI music fascinating, they emphasize that AI music lacks the emotional depth found in human compositions. They explain that human compositions are capable of conveying authentic human experiences and feelings, which AI cannot replicate. ''Quotes are pulled directly from a New York Times article''<ref>{{Cite web |last=The Learning Network |first= |date=May 11, 2023 |title=What Students Are Saying About A.I.-Generated Music |url=https://www.nytimes.com/2023/05/11/learning/what-students-are-saying-about-ai-generated-music.html |url-status=live |access-date=December 9, 2024 |website=The New York Times}}</ref>: "Human singers have the ability to convey a wide range of emotions and add their own unique style to their music. They have the creativity and experience to interpret lyrics and to give them their own style. Music made with A.I. may be good, but it will never be the same as music sung by a good pop star. While A.I. can be a helpful tool for composers and producers to experiment with new sounds and styles, it will never replace the raw talent and artistry of human vocalists." - ''Sergi, Sant Gregori'' "In my personal opinion, the main allure of music lies in the emotional connection that it establishes with the listener. It’s not only about the melody or the lyrics, but also the sentiments and reminiscences that the music evokes. If I became aware that a song was completely generated by an artificial intelligence system, I would feel intrigued to listen to it, driven by my fascination with the underlying technology. Nevertheless, I might not feel as connected to the song on an emotional level as I would if it was composed by a human artist." - ''Aleena, Julia R. Masterman, Philadelphia, PA'' "Even if the lyrics emulate a real pop star’s lyrics, whether it talks about heartbreak, love, or family, it would never have the same impact like one created by a real pop star because the listeners know it is all just to sound good and appeal to the listeners. It would have nothing to do with the artist themselves … Music is supposed to be relatable. When I listen to music, I like to listen to artists I know have gone through similar things or have the same feelings as me." - ''Sophia, Hinsdale Central High School'' ==== Composers ==== The evolution of composers attitudes towards AI music is reflected in [https://www.youtube.com/channel/UCelK8dBKY0Xs5oRI6sJf7aA Daniel James], a composer on YouTube, perspective over time. While he acknowledged that AI generated music was inevitable, it would never allow a total newbie to suddenly become a professional.<ref>{{Citation |last=Daniel James |title=TADay #4 - Composer Talk Radio - Is AI a threat or is it the future of composition. |date=2019-06-29 |url=https://www.youtube.com/watch?v=cqJWI4HF1CY |access-date=2024-12-09}}</ref> He suggested if AI became proficient in replicating professionals, composers would need to come up with their own style away from the AI. James had a positive view on AIs potential as a tool, comparing it to a ghost composer that could handle much of the monotonous work that an assistant might do. He predicted that AI would primarily impact the lower-skilled composers, widening the gap between low and high skilled composers. By 2023, James' perspective has become more nuanced.<ref>{{Citation |last=Daniel James |title=AI In The Music Industry - Tool Or Threat - A Professional Composers View. |date=2022-12-11 |url=https://www.youtube.com/watch?v=fOL32kRuUI0 |access-date=2024-12-09}}</ref> He discussed the limitations of AI, explaining that it can't really create something new, and can only make variations. While acknowledging AIs capability to blend styles, like reimagining Beethoven as hip-hop, he emphasizes that music exists within the context of the time it is created. James considers that although AI can accurately replicate music, it still struggles with emotional nuance. He also notes that skilled AI use would still require musical expertise to properly guide the AI. James also discusses the significant impacts AI might have. Formulaic music like EDM and trailer music seem particularly vulnerable to AI as there is a "correct" way to write those styles of music. He also believes that AI music will severely damage the lower end of the creative field. He worries that if newer generations of artists are trained to use AI, they may forget how to develop their own original styles, stunting their growth. The broader composer community has similar views. On Reddit, many composers advocate for limiting AI's role to reference and placeholder work that bridge the gap between the client and the composer.<ref>{{Cite web |last=ArgamaWitch |date=2024-04-15 |title=Composers that take commissions, what's your thoughts on AI music being used as reference? |url=https://www.reddit.com/r/composer/comments/1c4vrvr/composers_that_take_commissions_whats_your/?rdt=57624 |access-date=2024-12-09 |website=r/composer}}</ref> The consensus among professional composers, including James, is that AI needs much better regulation. They argue for protecting artists' unique, copyrightable styles from unauthorized AI replication and advocate that AI companies should compensate the artists whos works train the AI models. These composers are working to convince the Copyright Office that training AI on artists' work without compensation devalues artists. == References == <references /> {{BookCat}} obi5xvqr4caad23kxplm7gysfbeoqad 4634090 4634088 2026-05-04T15:20:10Z ~2026-26946-20 3581199 Appended Thaler v Perlmutter to be up-to-date. Noted tha the case has been denied by supreme court and has concluded. The results are finished: IP created by AI cannot hold copyright 4634090 wikitext text/x-wiki == Overview == === Introduction === Artificial intelligence (AI) is revolutionizing creative industries, such as the music industry, by redefining how creative works are composed, performed, and consumed. What began as theoretical musings by pioneers like Alan Turing has grown into a field with sophisticated neural networks capable of composing full-length songs, for example. However, this evolution raises pressing questions about originality, ownership, and the future of human creativity. === History of AI and Music === ====== Theoretical Foundations: 1950s-1960s ====== The concept of AI-generated music originated with Alan Turing, who theorized in the 1950s that machines could emulate human cognitive processes, including music composition. His ideas laid the groundwork for computational creativity.<ref>{{Citation |last=Copeland |first=B. Jack |title=Turing and the History of Computer Music |date=2017 |url=https://link.springer.com/chapter/10.1007/978-3-319-53280-6_8 |work=Philosophical Explorations of the Legacy of Alan Turing: Turing 100 |pages=189–218 |editor-last=Floyd |editor-first=Juliet |access-date=2024-12-02 |place=Cham |publisher=Springer International Publishing |language=en |doi=10.1007/978-3-319-53280-6_8 |isbn=978-3-319-53280-6 |last2=Long |first2=Jason |editor2-last=Bokulich |editor2-first=Alisa}}</ref> In 1957, Lejaren Hiller and Leonard Isaacson at the University of Illinois created the Illiac Suite<ref>{{Cite web |title=ILLIAC Suite – Illinois Distributed Museum |url=https://distributedmuseum.illinois.edu/exhibit/illiac-suite/ |access-date=2024-12-02 |website=distributedmuseum.illinois.edu}}</ref>. Using the ILLIAC I computer, they developed an algorithmic process to compose a string quartet, marking one of the first successful instances of computer-generated music. It demonstrated the potential of computers to collaborate in creative endeavors, sparking decades of research into AI's role in music. ====== Rule-Based Systems: 1970s-1980s ====== During the 1970s and 1980s, AI systems advanced with rule-based algorithms that mimicked specific musical styles. David Cope’s Experiments in Musical Intelligence<ref>{{Cite web |last=tluong |date=2015-04-29 |title=Algorithmic Music – David Cope and EMI |url=https://computerhistory.org/blog/algorithmic-music-david-cope-and-emi/ |access-date=2024-12-02 |website=CHM |language=en}}</ref> (EMI) exemplified this approach by analyzing existing compositions and generating new ones in the style of Bach and Mozart. However, EMI heavily relied on predefined human rules, highlighting the imitative, rather than generative, nature of early AI. A significant technological leap came in 1983 with the introduction of MIDI<ref>{{Citation |title=MIDI |date=2024-11-25 |url=https://en.wikipedia.org/wiki/MIDI |work=Wikipedia |access-date=2024-12-02 |language=en}}</ref> (Musical Instrument Digital Interface). MIDI standardized communication between computers and electronic instruments, enabling precise control of musical elements and facilitating data collection for future AI systems. ====== Machine Learning: 1990s-2000s ====== AI music systems transitioned from rule-based models to data-driven techniques in the 1990s. Machine learning algorithms enabled pattern recognition and predictive modeling, allowing AI to generate more complex and varied compositions. Projects like Accenture’s Symphonologie<ref>{{Cite web |title=Accenture {{!}} Symphonologie |url=https://www.oneclub.org/awards/theoneshow/-award/25489/symphonologie/ |access-date=2024-12-02 |website=www.oneclub.org |language=en}}</ref> showcased AI as a collaborative tool, blending human and machine creativity. ====== Neural Networks: 2010s-Present ====== The rise of deep learning revolutionized AI in music. Neural networks, trained on vast datasets, now compose intricate, multi-instrumental pieces in seconds. Tools like OpenAI’s MuseNet<ref>{{Cite web |title=MuseNet |url=https://openai.com/index/musenet/ |access-date=2024-12-02 |website=openai.com |language=en-US}}</ref> and AIVA<ref>{{Cite web |title=AIVA, the AI Music Generation Assistant |url=https://www.aiva.ai/ |access-date=2024-12-02 |website=www.aiva.ai |language=en}}</ref> exemplify how AI has expanded its creative capabilities across genres, challenging the boundaries of human artistry. == Relevant Legal Disputes == === Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884) === [[File:Oscar Wilde 1882.jpg|thumb|Oscar Wilde No.18 by Napoleon Sarony (1882)]] [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithography Co v. Sarony]] was submitted on December 13, 1883 when Sarony filed a copyright suit against Burrow-Giles when the company had marketed lithographs of Sarony's photograph, Oscar Wilde No.18, without Sarony's permission. Burrow-Giles argued that photographs were neither writings nor a production of an author, and thus did not possess copyright protection. The court determined that even though creating a photograph is "merely mechanical, with no place for novelty, invention, or originality", the photograph Sarony created was his "own original mental conception, to which he gave visible form by posing the said Oscar Wilde in front of the camera, selecting and arranging the costume, draperies, . . . suggesting and evoking the desired expression, and from such . . . representation, made entirely by plaintiff, he produced the picture in suit.'" On March 17, 1884, the court established that photography is a copyrightable medium. Furthermore, this case reinforced that an author of a work is "he to whom anything owes its origin."<ref>Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884)</ref> === Naruto v. Slater, No. 16-15469 (9th Cir. 2018) === [[File:Macaca nigra self-portrait large.jpg|left|thumb|One of the monkey selfies]] Naruto v. Slater, more commonly known as the [[wikipedia:Artificial_intelligence_and_copyright|Monkey Selfie copyright dispute]], began on September 22, 2015. PETA, representing the crested macaque Naruto, sued Slater claiming that because the monkey took its own picture, it was entitled to the copyright. David J. Slater, the photographer, argued that he held the copyright as he engineered the situation that led to the monkey taking its selfie. On April 23, 2018, the court determined that "this monkey - and all animals, since they are not human – [lack] statutory standing under the Copyright Act", reinforcing that non-humans cannot own copyright.<ref>Naruto v. Slater, No. 16-15469 (9th Cir. 2018)</ref> === Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023) === [[File:A Recent Entrance to Paradise.jpg|thumb|A Recent Entrance to Paradise]] Thaler v. Perlmutter emerged after the U.S. Copyright Office denied Dr. Stephen Thaler's copyright application for an AI generated work, "A Recent Entrance to Paradise". The court focused on answering "whether a work generated autonomously by a computer falls under the protection of copyright law upon its creation". Thaler filed a lawsuit, arguing that the copyright of the AI generated work belonged to him as the AI model's creator. He stated that "AI should be ‘acknowledge[d] . . . as an author where it otherwise meets authorship criteria, with any copyright ownership vesting in the AI’s owner.’" The court reviewed the decision of [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithographic Co. v. Sarony]], finding that the author of any AI generated work would be the AI. However, following the decision of [[wikipedia:Artificial_intelligence_and_copyright|Naruto v. Slater]], since AIs are not human, they cannot hold copyright. The case was decided on August 18, 2023, confirming that AIs cannot hold copyright. As such, the work fell under public domain. However, the court explicitly stated that they were not making any decisions on "how much human input is necessary to qualify the user of an AI system as an 'author' of a generated work".<ref>Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023)</ref> The D.C. Circuit unanimously affirmed in March 2025. On March 2, 2026, the Supreme Court denied certiorari, making the ruling final and exhausting Thaler's appeals. ''Thaler'' now stands as binding precedent that AI systems cannot themselves be authors under U.S. copyright law, and that works generated entirely without human creative contribution are ineligible for registration. === Zarya of the Dawn === [[File:Zarya of the Dawn cover.webp|thumb|Zarya of the Dawn by Kristina Kashtanova]] [[wikipedia:Zarya_of_the_Dawn|Zarya of the Dawn]], a comic book authored by Kristina Kashtanova and illustrated using the AI generator Midjourney sparked a significant copyright dispute in 2022. When Kashtanova applied for copyright of the comic in September 2022, she failed to disclose that the images were generated by Midjourney. The comic was originally granted copyright by the Copyright Office, but after discovering Midjourney's involvement in illustrating the comic, they reviewed their decision. While the Copyright Office agreed that the text and compilation (the arrangement of images and text) were copyrightable, the art was not, as the "process is not controlled by the user because it is not possible to predict what Midjourney will create ahead of time." Although, Kashtanova claimed "she personally edited some of the images created by Midjourney", the Copyright office could not determine "what expression in the image was contributed through her use of Photoshop as opposed to generated by Midjourney" and thus revoked the copyright. <ref>{{Cite web |last=Kasunic |first=Robert J. |date=February 21, 2023 |title=2023.02.21 Zarya of the Dawn Letter |url=https://www.copyright.gov/docs/zarya-of-the-dawn.pdf |url-status=live |access-date=December 9, 2024 |website=Copyright Office (.gov)}}</ref> == Relevant Copyright Chapters == === Chapter 308: The Originality Requirement<ref name=":0">U.S. Copyright Office, Compendium of U.S. Copyright Office Practices § 101 (3d ed. 2021).</ref> === The Originality Requirement has two primary requirements: "The work must be ‘independently created by the author’ and it must possess ‘at least some minimal degree of creativity’" ==== Chapter 308.1 ==== The Copyright Act defines "independent creation" as a work created "without copying from other works." However, "a work may satisfy the independent creation requirement ‘even though it closely resembles other works so long as the similarity is fortuitous, not the result of copying.’" ==== Chapter 308.2 ==== In terms of creativity, the Copyright Act states that "‘the requisite level of creativity is extremely low.’ Even a ‘slight amount’ of creative expression will suffice.’" ==== Works That Do Not Satisfy the Originality Requirement ==== 313.4(A): Mere Copies 313.4(K): Mere Variations of Colorings === Chapter 306: The Human Authorship Requirement<ref name=":0" /> === The Human Authorship Requirement states that only humans may own a copyright. "The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being." ==== Chapter 313.2 ==== The chapter states that "the U.S. Copyright Office will not register works produced by nature, animals, or plants." Furthermore, "the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author." ==== Works That Lack Human Authorship ==== * A photograph taken by a monkey. * A mural painted by an elephant. * A claim based on the appearance of actual animal skin. * A claim based on driftwood that has been shaped and smoothed by the ocean. * A claim based on cut marks, defects, and other qualities found in natural stone. * An application for a song naming the Holy Spirit as the author of the work. === Chapter 507.1: Derivate Works<ref name=":0" /> === As AI generated works are considered to be authored by the AI, and thus public domain, attempts to edit and then copyright the works would most likely fall under derivative works. The Copyright Act defines a derivative work as "a work based upon one or more preexisting works, such as a . . . art reproduction . . . or any other form in which a work may be recast, transformed, or adapted." ==== Chapter 311.2 ==== Derivative works follow the same originality requirements as original works. Derivative works may only receive copyright protection "provided that [the work] contains a sufficient amount of original expression, meaning that the derivative work must be independently created and it must possess more than a modicum of creativity" The Copyright Act does reiterate that "[m]iniscule variations do not satisfy this requirement, such as merely changing the size of the preexisting work." == Present Issues == === AI Music === ==== Lack of Creativity ==== In 2023, an anonymous creator known as "Ghostwriter" released Heart on My Sleeve, featuring AI-generated vocals mimicking Drake and The Weeknd. The song went viral, drawing millions of streams before being removed for copyright infringement. Universal Music Group argued that the AI-generated track exploited the artists’ likenesses without consent, raising ethical and legal concerns<ref>{{Cite web |last=Reed |first=Rachel |title=AI created a song mimicking the work of Drake and The Weeknd. What does that mean for copyright law? |url=https://hls.harvard.edu/today/ai-created-a-song-mimicking-the-work-of-drake-and-the-weeknd-what-does-that-mean-for-copyright-law/ |access-date=2024-12-02 |website=Harvard Law School |language=en-us}}</ref>. This case highlights AI’s ability to imitate human creativity so convincingly that it blurs the line between originality and replication. Although the creator faced no legal repercussions, the controversy underscored the need for clearer regulations on AI-generated content. * AI doesn’t create entirely new works; it amplifies patterns derived from training data. While it can replicate styles, it lacks the emotional depth and intentionality of human artistry. * Tools like MuseNet and Suno allow anyone to compose music in minutes, potentially devaluing human creativity by making artistic production instantaneous and impersonal. ==== Suno and Udio ==== The most current case reflecting the debate regarding the originality of AI music is in the RIAA vs. Suno and RIAA vs. Udio. The RIAA, or the Recording Industry Association of America, is a trade organization that represents many record labels, including Sony Music Group, Universal Music Group, and Warner Music Group (colloquially known as "the big Three" in the industry as they own up to 85% of market share). In June 2024, the RIAA placed a copyright infringement lawsuit on Suno and Udio (two generative AI music startup companies). They had three main goals with this lawsuit: <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html#:~:text=The%20lawsuits%20make%20three%20specific,to%20nine%20figures%20or%20more. |access-date=2024-12-10 |website=Vulture |language=en}}</ref> # To have these companies admit their models use copyrighted music. # Immediately stop training their AI models using this copyrighted music. # Seek damages up to $150,000 per song used in the models. When first discussing the lawsuit with the press, Chairman and CEO of RIAA, Mitch Glazier, stated: "The music community has embraced AI and we are already partnering and collaborating with responsible developers to build sustainable AI tools centered on human creativity '''that put artists and songwriters in charge''', but we can only succeed if developers are willing to work together with us. Unlicensed services like Suno and Udio that '''claim it's 'fair' to copy an artist's life's work and exploit it for their own profit without consent or pay''' set back the promise of genuinely innovative AI for us all."<ref>{{Cite web |last=Connelly |first=Rose |date=2024-06-24 |title=Record Companies Bring Landmark Cases for Responsible AI Against Suno and Udio in Boston and New York Federal Courts, Respectively |url=https://www.riaa.com/record-companies-bring-landmark-cases-for-responsible-ai-againstsuno-and-udio-in-boston-and-new-york-federal-courts-respectively/ |access-date=2024-12-10 |website=RIAA |language=en-US}}</ref> The RIAA hopes to reflect that the inherent moral value of this statement for pursuing this lawsuit is protecting artists' work and fair pay. However, in any of RIAA's arguments, the percentage of and how the money collected from damages will be distributed to the artists of each respective record label must be clarified. Suno responded to the copyright lawsuit, "What the major record labels really don't want is competition." While this calls to question the actual motive of the lawsuit and whether the benefactors will include artists, the results of this lawsuit are pertinent as they will set further precedents in how copyright pertains to AI overall. Initially, in response to the lawsuit, Udio claimed "fair use," which is primarily used for academic or journalistic purposes. However, lawyers dismissed this claim because their training is not used for human-created content. <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html |access-date=2024-12-10 |website=Vulture |language=en}}</ref> As the lawsuit proceeded, both companies admitted to using copyrighted music only as "intermediate copies." They sighted a copyright case from 2021 regarding an AI algorithm's use of copyrighted images to create a search algorithm. In that case, using these "intermediate copies was lawful" because these lower-resolution copies did not satisfy the user's desire to see the full images. However, in Suno and Udio's context, their AI models are not search algorithms but are generative.  ==== Other AI Music Lawsuits ==== Following this case, different record labels (primarily Universal) have filed a copyright on issues regarding AI music. On October 18, 2023, several record labels, namely Universal, filed a lawsuit alleging that Anthropic's AI chatbot, "Claude," unlawfully copied and disseminated copyrighted works, including lyrics "owned or controlled by the Publishers. On January 31, 2024, the copyright license agreement between Universal Music Group (UMG), the world's largest music company, and TikTok owner ByteDance Ltd. expired without a renewal agreement. TikTok was forced to turn off the reproduction of all audio content from artists belonging to UMG's catalog, including Taylor Swift, Billie Eilish, Romeo Santos, J Balvin, and Imagine Dragons, among many others. During these negotiations, UMG made AI-generated music a sticking point in their TikTok negotiations, and a group of musicians spoke out against AI-generated music. Groups, including the Recording Academy, the Music Workers Alliance, the National Association of Music Publishers, the American Association of Independent Music, and even SAG-AFTRA, have all made statements supporting the lawsuits. ==== Ethical Implications of AI in the Music Industry ==== As is apparent with the growing number of lawsuits directed at AI music companies, advancements in AI bring new possibilities for creativity and efficiency along with critical ethical concerns regarding economic impact, bias, and data harvesting. AI’s role in the music industry is a double-edged sword, offering both opportunities and challenges. On the one hand, AI automates many aspects of music creation and production. Tasks like composition, audio mastering, and even lyric writing can now be performed by AI tools. However, this automation has led to concerns about job displacement. Traditional roles in the industry, such as sound engineers and live musicians, face increasing obsolescence as AI tools become more sophisticated and accessible. However, AI also democratizes music production, enabling independent artists and smaller labels to create high-quality music without needing expensive equipment or studio time. So, while jobs are being lost, new roles are emerging, such as AI music curators and prompt engineers. This demonstrates how technological advancements can create fresh opportunities even as they disrupt existing systems. Another critical issue in the use of AI in music is the presence of bias in the models used to generate content. AI systems are only as good as the data they are trained on, and this dependency can result in significant imbalances. For instance, if an AI model’s training data predominantly features Western music, the system may struggle to generate accurate representations of non-Western genres or cultural styles. Along with racial bias, gender bias in datasets used for AI training can perpetuate existing inequalities in the music industry. If female and non-binary artists are underrepresented in the data, AI-generated music may disproportionately reflect the styles and contributions of male artists. Such biases highlight the need for diverse and inclusive training datasets. Developers must address these issues to ensure that AI tools reflect a broader and more equitable spectrum of musical expression. As discussed previously, the question of how AI systems source their training data has sparked widespread ethical debates. Many AI models, most notably Suno and Udio, are trained using copyrighted music, often without the consent or compensation of the original artists and have received backlash. This practice raises significant concerns about exploitation. Artists invest considerable time and effort into creating music, yet their work can be appropriated by AI systems without acknowledgment or financial remuneration. This mirrors controversies in other areas of AI, such as the exploitation of the unpaid labor of associated with Remotask workers. If creators cannot safeguard their work against unauthorized use by AI systems, the industry risks devaluing artistic contributions in favor of technological efficiency. The music industry is at a crossroads–do we protect the rights of creators, or do we embrace AI-drive efficiency without clear ethical guidelines? === AI in the Video Game Industry === The intersection of visual art, music, voice, and code make the gaming industry a hot spot for AI usage within creative works. AI has existed within gaming for some time in the form of non-playable characters (NPCs), but the modern implementation of AI within gaming specifically sees increased usage of generative tools for creative purposes. === Nvidia DLSS 5.0 === Nvidia is a prolific graphics card producer with extensive ties to the gaming industry. Originally founded for the purpose of innovating computer gaming<ref>{{Cite web |title=NVIDIA Corporation: History |url=https://www.nvidia.com/en-us/about-nvidia/corporate-timeline/ |access-date=2026-05-04 |website=NVIDIA |language=en-us}}</ref>, they have since leveraged their graphics processing unit (GPU) technology for AI usage extensively, while also seeking to implement AI within their gaming technologies. Deep Learning Super Sampling (DLSS) is a technology developed by Nvidia to use real-time deep learning AI to upscale video game rendering. The initial versions of DLSS were employed by running games at a lower native resolution, then using AI to upscale to a higher resolution based on the picture generated by the GPU<ref>{{Cite web |last=Martindale |first=Jon |date=2020-02-14 |title=Nvidia RTX DLSS: everything you need to know |url=https://www.digitaltrends.com/computing/everything-you-need-to-know-about-nvidias-rtx-dlss-technology/ |access-date=2026-05-04 |website=Digital Trends |language=en-us}}</ref>; this implementation did not use AI to directly modify any of the actual contents of games themselves. DLSS 5.0, however, made use of generative AI to attempt to directly enhance the visual content of games. While the exact details of the implementation have yet to be released as of May 2026, the technology appears to generate new frames from prior training data, using the existing content of a game as the base. This introduces elements of the rendering which may not have been present in the original developer's vision. == Reception == === Music === ==== Students ==== While students seem to find AI music fascinating, they emphasize that AI music lacks the emotional depth found in human compositions. They explain that human compositions are capable of conveying authentic human experiences and feelings, which AI cannot replicate. ''Quotes are pulled directly from a New York Times article''<ref>{{Cite web |last=The Learning Network |first= |date=May 11, 2023 |title=What Students Are Saying About A.I.-Generated Music |url=https://www.nytimes.com/2023/05/11/learning/what-students-are-saying-about-ai-generated-music.html |url-status=live |access-date=December 9, 2024 |website=The New York Times}}</ref>: "Human singers have the ability to convey a wide range of emotions and add their own unique style to their music. They have the creativity and experience to interpret lyrics and to give them their own style. Music made with A.I. may be good, but it will never be the same as music sung by a good pop star. While A.I. can be a helpful tool for composers and producers to experiment with new sounds and styles, it will never replace the raw talent and artistry of human vocalists." - ''Sergi, Sant Gregori'' "In my personal opinion, the main allure of music lies in the emotional connection that it establishes with the listener. It’s not only about the melody or the lyrics, but also the sentiments and reminiscences that the music evokes. If I became aware that a song was completely generated by an artificial intelligence system, I would feel intrigued to listen to it, driven by my fascination with the underlying technology. Nevertheless, I might not feel as connected to the song on an emotional level as I would if it was composed by a human artist." - ''Aleena, Julia R. Masterman, Philadelphia, PA'' "Even if the lyrics emulate a real pop star’s lyrics, whether it talks about heartbreak, love, or family, it would never have the same impact like one created by a real pop star because the listeners know it is all just to sound good and appeal to the listeners. It would have nothing to do with the artist themselves … Music is supposed to be relatable. When I listen to music, I like to listen to artists I know have gone through similar things or have the same feelings as me." - ''Sophia, Hinsdale Central High School'' ==== Composers ==== The evolution of composers attitudes towards AI music is reflected in [https://www.youtube.com/channel/UCelK8dBKY0Xs5oRI6sJf7aA Daniel James], a composer on YouTube, perspective over time. While he acknowledged that AI generated music was inevitable, it would never allow a total newbie to suddenly become a professional.<ref>{{Citation |last=Daniel James |title=TADay #4 - Composer Talk Radio - Is AI a threat or is it the future of composition. |date=2019-06-29 |url=https://www.youtube.com/watch?v=cqJWI4HF1CY |access-date=2024-12-09}}</ref> He suggested if AI became proficient in replicating professionals, composers would need to come up with their own style away from the AI. James had a positive view on AIs potential as a tool, comparing it to a ghost composer that could handle much of the monotonous work that an assistant might do. He predicted that AI would primarily impact the lower-skilled composers, widening the gap between low and high skilled composers. By 2023, James' perspective has become more nuanced.<ref>{{Citation |last=Daniel James |title=AI In The Music Industry - Tool Or Threat - A Professional Composers View. |date=2022-12-11 |url=https://www.youtube.com/watch?v=fOL32kRuUI0 |access-date=2024-12-09}}</ref> He discussed the limitations of AI, explaining that it can't really create something new, and can only make variations. While acknowledging AIs capability to blend styles, like reimagining Beethoven as hip-hop, he emphasizes that music exists within the context of the time it is created. James considers that although AI can accurately replicate music, it still struggles with emotional nuance. He also notes that skilled AI use would still require musical expertise to properly guide the AI. James also discusses the significant impacts AI might have. Formulaic music like EDM and trailer music seem particularly vulnerable to AI as there is a "correct" way to write those styles of music. He also believes that AI music will severely damage the lower end of the creative field. He worries that if newer generations of artists are trained to use AI, they may forget how to develop their own original styles, stunting their growth. The broader composer community has similar views. On Reddit, many composers advocate for limiting AI's role to reference and placeholder work that bridge the gap between the client and the composer.<ref>{{Cite web |last=ArgamaWitch |date=2024-04-15 |title=Composers that take commissions, what's your thoughts on AI music being used as reference? |url=https://www.reddit.com/r/composer/comments/1c4vrvr/composers_that_take_commissions_whats_your/?rdt=57624 |access-date=2024-12-09 |website=r/composer}}</ref> The consensus among professional composers, including James, is that AI needs much better regulation. They argue for protecting artists' unique, copyrightable styles from unauthorized AI replication and advocate that AI companies should compensate the artists whos works train the AI models. These composers are working to convince the Copyright Office that training AI on artists' work without compensation devalues artists. == References == <references /> {{BookCat}} 4v2w74ajiq43h5lrzw1zos4qk87ieqj 4634092 4634090 2026-05-04T15:27:36Z ~2026-26946-20 3581199 Added most currently relevant AI IP case: Alllen v Perlmutter 4634092 wikitext text/x-wiki == Overview == === Introduction === Artificial intelligence (AI) is revolutionizing creative industries, such as the music industry, by redefining how creative works are composed, performed, and consumed. What began as theoretical musings by pioneers like Alan Turing has grown into a field with sophisticated neural networks capable of composing full-length songs, for example. However, this evolution raises pressing questions about originality, ownership, and the future of human creativity. === History of AI and Music === ====== Theoretical Foundations: 1950s-1960s ====== The concept of AI-generated music originated with Alan Turing, who theorized in the 1950s that machines could emulate human cognitive processes, including music composition. His ideas laid the groundwork for computational creativity.<ref>{{Citation |last=Copeland |first=B. Jack |title=Turing and the History of Computer Music |date=2017 |url=https://link.springer.com/chapter/10.1007/978-3-319-53280-6_8 |work=Philosophical Explorations of the Legacy of Alan Turing: Turing 100 |pages=189–218 |editor-last=Floyd |editor-first=Juliet |access-date=2024-12-02 |place=Cham |publisher=Springer International Publishing |language=en |doi=10.1007/978-3-319-53280-6_8 |isbn=978-3-319-53280-6 |last2=Long |first2=Jason |editor2-last=Bokulich |editor2-first=Alisa}}</ref> In 1957, Lejaren Hiller and Leonard Isaacson at the University of Illinois created the Illiac Suite<ref>{{Cite web |title=ILLIAC Suite – Illinois Distributed Museum |url=https://distributedmuseum.illinois.edu/exhibit/illiac-suite/ |access-date=2024-12-02 |website=distributedmuseum.illinois.edu}}</ref>. Using the ILLIAC I computer, they developed an algorithmic process to compose a string quartet, marking one of the first successful instances of computer-generated music. It demonstrated the potential of computers to collaborate in creative endeavors, sparking decades of research into AI's role in music. ====== Rule-Based Systems: 1970s-1980s ====== During the 1970s and 1980s, AI systems advanced with rule-based algorithms that mimicked specific musical styles. David Cope’s Experiments in Musical Intelligence<ref>{{Cite web |last=tluong |date=2015-04-29 |title=Algorithmic Music – David Cope and EMI |url=https://computerhistory.org/blog/algorithmic-music-david-cope-and-emi/ |access-date=2024-12-02 |website=CHM |language=en}}</ref> (EMI) exemplified this approach by analyzing existing compositions and generating new ones in the style of Bach and Mozart. However, EMI heavily relied on predefined human rules, highlighting the imitative, rather than generative, nature of early AI. A significant technological leap came in 1983 with the introduction of MIDI<ref>{{Citation |title=MIDI |date=2024-11-25 |url=https://en.wikipedia.org/wiki/MIDI |work=Wikipedia |access-date=2024-12-02 |language=en}}</ref> (Musical Instrument Digital Interface). MIDI standardized communication between computers and electronic instruments, enabling precise control of musical elements and facilitating data collection for future AI systems. ====== Machine Learning: 1990s-2000s ====== AI music systems transitioned from rule-based models to data-driven techniques in the 1990s. Machine learning algorithms enabled pattern recognition and predictive modeling, allowing AI to generate more complex and varied compositions. Projects like Accenture’s Symphonologie<ref>{{Cite web |title=Accenture {{!}} Symphonologie |url=https://www.oneclub.org/awards/theoneshow/-award/25489/symphonologie/ |access-date=2024-12-02 |website=www.oneclub.org |language=en}}</ref> showcased AI as a collaborative tool, blending human and machine creativity. ====== Neural Networks: 2010s-Present ====== The rise of deep learning revolutionized AI in music. Neural networks, trained on vast datasets, now compose intricate, multi-instrumental pieces in seconds. Tools like OpenAI’s MuseNet<ref>{{Cite web |title=MuseNet |url=https://openai.com/index/musenet/ |access-date=2024-12-02 |website=openai.com |language=en-US}}</ref> and AIVA<ref>{{Cite web |title=AIVA, the AI Music Generation Assistant |url=https://www.aiva.ai/ |access-date=2024-12-02 |website=www.aiva.ai |language=en}}</ref> exemplify how AI has expanded its creative capabilities across genres, challenging the boundaries of human artistry. == Relevant Legal Disputes == === Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884) === [[File:Oscar Wilde 1882.jpg|thumb|Oscar Wilde No.18 by Napoleon Sarony (1882)]] [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithography Co v. Sarony]] was submitted on December 13, 1883 when Sarony filed a copyright suit against Burrow-Giles when the company had marketed lithographs of Sarony's photograph, Oscar Wilde No.18, without Sarony's permission. Burrow-Giles argued that photographs were neither writings nor a production of an author, and thus did not possess copyright protection. The court determined that even though creating a photograph is "merely mechanical, with no place for novelty, invention, or originality", the photograph Sarony created was his "own original mental conception, to which he gave visible form by posing the said Oscar Wilde in front of the camera, selecting and arranging the costume, draperies, . . . suggesting and evoking the desired expression, and from such . . . representation, made entirely by plaintiff, he produced the picture in suit.'" On March 17, 1884, the court established that photography is a copyrightable medium. Furthermore, this case reinforced that an author of a work is "he to whom anything owes its origin."<ref>Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884)</ref> === Naruto v. Slater, No. 16-15469 (9th Cir. 2018) === [[File:Macaca nigra self-portrait large.jpg|left|thumb|One of the monkey selfies]] Naruto v. Slater, more commonly known as the [[wikipedia:Artificial_intelligence_and_copyright|Monkey Selfie copyright dispute]], began on September 22, 2015. PETA, representing the crested macaque Naruto, sued Slater claiming that because the monkey took its own picture, it was entitled to the copyright. David J. Slater, the photographer, argued that he held the copyright as he engineered the situation that led to the monkey taking its selfie. On April 23, 2018, the court determined that "this monkey - and all animals, since they are not human – [lack] statutory standing under the Copyright Act", reinforcing that non-humans cannot own copyright.<ref>Naruto v. Slater, No. 16-15469 (9th Cir. 2018)</ref> === Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023) === [[File:A Recent Entrance to Paradise.jpg|thumb|A Recent Entrance to Paradise]] Thaler v. Perlmutter emerged after the U.S. Copyright Office denied Dr. Stephen Thaler's copyright application for an AI generated work, "A Recent Entrance to Paradise". The court focused on answering "whether a work generated autonomously by a computer falls under the protection of copyright law upon its creation". Thaler filed a lawsuit, arguing that the copyright of the AI generated work belonged to him as the AI model's creator. He stated that "AI should be ‘acknowledge[d] . . . as an author where it otherwise meets authorship criteria, with any copyright ownership vesting in the AI’s owner.’" The court reviewed the decision of [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithographic Co. v. Sarony]], finding that the author of any AI generated work would be the AI. However, following the decision of [[wikipedia:Artificial_intelligence_and_copyright|Naruto v. Slater]], since AIs are not human, they cannot hold copyright. The case was decided on August 18, 2023, confirming that AIs cannot hold copyright. As such, the work fell under public domain. However, the court explicitly stated that they were not making any decisions on "how much human input is necessary to qualify the user of an AI system as an 'author' of a generated work".<ref>Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023)</ref> The D.C. Circuit unanimously affirmed in March 2025. On March 2, 2026, the Supreme Court denied certiorari, making the ruling final and exhausting Thaler's appeals. ''Thaler'' now stands as binding precedent that AI systems cannot themselves be authors under U.S. copyright law, and that works generated entirely without human creative contribution are ineligible for registration. '''''Allen v. Perlmutter'', No. 24-2665 (WJM) (D. Colo. 2026)''' [[File:Théâtre D’opéra Spatial.png|thumb|''Théâtre D'opéra Spatial'', created by Jason M. Allen using Midjourney, Photoshop, and Gigapixel AI]] ''Allen v. Perlmutter'' picks up where ''Thaler'' left off. In August 2022, Colorado artist Jason Allen used Midjourney to create ''Théâtre D'opéra Spatial'', entering text prompts at least 624 times to specify genre, tone, composition, and style, then refining the chosen output in Photoshop and Gigapixel AI. The image won first place at the Colorado State Fair in September 2022. When Allen applied for copyright registration as the sole human author, the Office offered to register only the portions reflecting his own contributions if he disclaimed the AI-generated material. Allen refused, and after the Review Board issued its final refusal in June 2023, he filed suit in the U.S. District Court for the District of Colorado on September 26, 2024. He moved for summary judgment in August 2025, the Copyright Office cross-moved in January 2026, and Allen filed his reply in February 2026. Allen argues that his iterative prompting and creative selection constitute authorship analogous to the photographer's creative choices that made photography copyrightable under ''Burrow-Giles''. The Copyright Office counters that prompts are ideas, not expression, because Midjourney determines the actual visual output regardless of how detailed the instructions are. The case is now fully briefed before Judge William J. Martínez, with a ruling expected in 2026 that will produce the first judicial standard answering the question ''Thaler'' left open: when does human input in AI-assisted work rise to the level of copyright authorship? === Zarya of the Dawn === [[File:Zarya of the Dawn cover.webp|thumb|Zarya of the Dawn by Kristina Kashtanova]] [[wikipedia:Zarya_of_the_Dawn|Zarya of the Dawn]], a comic book authored by Kristina Kashtanova and illustrated using the AI generator Midjourney sparked a significant copyright dispute in 2022. When Kashtanova applied for copyright of the comic in September 2022, she failed to disclose that the images were generated by Midjourney. The comic was originally granted copyright by the Copyright Office, but after discovering Midjourney's involvement in illustrating the comic, they reviewed their decision. While the Copyright Office agreed that the text and compilation (the arrangement of images and text) were copyrightable, the art was not, as the "process is not controlled by the user because it is not possible to predict what Midjourney will create ahead of time." Although, Kashtanova claimed "she personally edited some of the images created by Midjourney", the Copyright office could not determine "what expression in the image was contributed through her use of Photoshop as opposed to generated by Midjourney" and thus revoked the copyright. <ref>{{Cite web |last=Kasunic |first=Robert J. |date=February 21, 2023 |title=2023.02.21 Zarya of the Dawn Letter |url=https://www.copyright.gov/docs/zarya-of-the-dawn.pdf |url-status=live |access-date=December 9, 2024 |website=Copyright Office (.gov)}}</ref> == Relevant Copyright Chapters == === Chapter 308: The Originality Requirement<ref name=":0">U.S. Copyright Office, Compendium of U.S. Copyright Office Practices § 101 (3d ed. 2021).</ref> === The Originality Requirement has two primary requirements: "The work must be ‘independently created by the author’ and it must possess ‘at least some minimal degree of creativity’" ==== Chapter 308.1 ==== The Copyright Act defines "independent creation" as a work created "without copying from other works." However, "a work may satisfy the independent creation requirement ‘even though it closely resembles other works so long as the similarity is fortuitous, not the result of copying.’" ==== Chapter 308.2 ==== In terms of creativity, the Copyright Act states that "‘the requisite level of creativity is extremely low.’ Even a ‘slight amount’ of creative expression will suffice.’" ==== Works That Do Not Satisfy the Originality Requirement ==== 313.4(A): Mere Copies 313.4(K): Mere Variations of Colorings === Chapter 306: The Human Authorship Requirement<ref name=":0" /> === The Human Authorship Requirement states that only humans may own a copyright. "The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being." ==== Chapter 313.2 ==== The chapter states that "the U.S. Copyright Office will not register works produced by nature, animals, or plants." Furthermore, "the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author." ==== Works That Lack Human Authorship ==== * A photograph taken by a monkey. * A mural painted by an elephant. * A claim based on the appearance of actual animal skin. * A claim based on driftwood that has been shaped and smoothed by the ocean. * A claim based on cut marks, defects, and other qualities found in natural stone. * An application for a song naming the Holy Spirit as the author of the work. === Chapter 507.1: Derivate Works<ref name=":0" /> === As AI generated works are considered to be authored by the AI, and thus public domain, attempts to edit and then copyright the works would most likely fall under derivative works. The Copyright Act defines a derivative work as "a work based upon one or more preexisting works, such as a . . . art reproduction . . . or any other form in which a work may be recast, transformed, or adapted." ==== Chapter 311.2 ==== Derivative works follow the same originality requirements as original works. Derivative works may only receive copyright protection "provided that [the work] contains a sufficient amount of original expression, meaning that the derivative work must be independently created and it must possess more than a modicum of creativity" The Copyright Act does reiterate that "[m]iniscule variations do not satisfy this requirement, such as merely changing the size of the preexisting work." == Present Issues == === AI Music === ==== Lack of Creativity ==== In 2023, an anonymous creator known as "Ghostwriter" released Heart on My Sleeve, featuring AI-generated vocals mimicking Drake and The Weeknd. The song went viral, drawing millions of streams before being removed for copyright infringement. Universal Music Group argued that the AI-generated track exploited the artists’ likenesses without consent, raising ethical and legal concerns<ref>{{Cite web |last=Reed |first=Rachel |title=AI created a song mimicking the work of Drake and The Weeknd. What does that mean for copyright law? |url=https://hls.harvard.edu/today/ai-created-a-song-mimicking-the-work-of-drake-and-the-weeknd-what-does-that-mean-for-copyright-law/ |access-date=2024-12-02 |website=Harvard Law School |language=en-us}}</ref>. This case highlights AI’s ability to imitate human creativity so convincingly that it blurs the line between originality and replication. Although the creator faced no legal repercussions, the controversy underscored the need for clearer regulations on AI-generated content. * AI doesn’t create entirely new works; it amplifies patterns derived from training data. While it can replicate styles, it lacks the emotional depth and intentionality of human artistry. * Tools like MuseNet and Suno allow anyone to compose music in minutes, potentially devaluing human creativity by making artistic production instantaneous and impersonal. ==== Suno and Udio ==== The most current case reflecting the debate regarding the originality of AI music is in the RIAA vs. Suno and RIAA vs. Udio. The RIAA, or the Recording Industry Association of America, is a trade organization that represents many record labels, including Sony Music Group, Universal Music Group, and Warner Music Group (colloquially known as "the big Three" in the industry as they own up to 85% of market share). In June 2024, the RIAA placed a copyright infringement lawsuit on Suno and Udio (two generative AI music startup companies). They had three main goals with this lawsuit: <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html#:~:text=The%20lawsuits%20make%20three%20specific,to%20nine%20figures%20or%20more. |access-date=2024-12-10 |website=Vulture |language=en}}</ref> # To have these companies admit their models use copyrighted music. # Immediately stop training their AI models using this copyrighted music. # Seek damages up to $150,000 per song used in the models. When first discussing the lawsuit with the press, Chairman and CEO of RIAA, Mitch Glazier, stated: "The music community has embraced AI and we are already partnering and collaborating with responsible developers to build sustainable AI tools centered on human creativity '''that put artists and songwriters in charge''', but we can only succeed if developers are willing to work together with us. Unlicensed services like Suno and Udio that '''claim it's 'fair' to copy an artist's life's work and exploit it for their own profit without consent or pay''' set back the promise of genuinely innovative AI for us all."<ref>{{Cite web |last=Connelly |first=Rose |date=2024-06-24 |title=Record Companies Bring Landmark Cases for Responsible AI Against Suno and Udio in Boston and New York Federal Courts, Respectively |url=https://www.riaa.com/record-companies-bring-landmark-cases-for-responsible-ai-againstsuno-and-udio-in-boston-and-new-york-federal-courts-respectively/ |access-date=2024-12-10 |website=RIAA |language=en-US}}</ref> The RIAA hopes to reflect that the inherent moral value of this statement for pursuing this lawsuit is protecting artists' work and fair pay. However, in any of RIAA's arguments, the percentage of and how the money collected from damages will be distributed to the artists of each respective record label must be clarified. Suno responded to the copyright lawsuit, "What the major record labels really don't want is competition." While this calls to question the actual motive of the lawsuit and whether the benefactors will include artists, the results of this lawsuit are pertinent as they will set further precedents in how copyright pertains to AI overall. Initially, in response to the lawsuit, Udio claimed "fair use," which is primarily used for academic or journalistic purposes. However, lawyers dismissed this claim because their training is not used for human-created content. <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html |access-date=2024-12-10 |website=Vulture |language=en}}</ref> As the lawsuit proceeded, both companies admitted to using copyrighted music only as "intermediate copies." They sighted a copyright case from 2021 regarding an AI algorithm's use of copyrighted images to create a search algorithm. In that case, using these "intermediate copies was lawful" because these lower-resolution copies did not satisfy the user's desire to see the full images. However, in Suno and Udio's context, their AI models are not search algorithms but are generative.  ==== Other AI Music Lawsuits ==== Following this case, different record labels (primarily Universal) have filed a copyright on issues regarding AI music. On October 18, 2023, several record labels, namely Universal, filed a lawsuit alleging that Anthropic's AI chatbot, "Claude," unlawfully copied and disseminated copyrighted works, including lyrics "owned or controlled by the Publishers. On January 31, 2024, the copyright license agreement between Universal Music Group (UMG), the world's largest music company, and TikTok owner ByteDance Ltd. expired without a renewal agreement. TikTok was forced to turn off the reproduction of all audio content from artists belonging to UMG's catalog, including Taylor Swift, Billie Eilish, Romeo Santos, J Balvin, and Imagine Dragons, among many others. During these negotiations, UMG made AI-generated music a sticking point in their TikTok negotiations, and a group of musicians spoke out against AI-generated music. Groups, including the Recording Academy, the Music Workers Alliance, the National Association of Music Publishers, the American Association of Independent Music, and even SAG-AFTRA, have all made statements supporting the lawsuits. ==== Ethical Implications of AI in the Music Industry ==== As is apparent with the growing number of lawsuits directed at AI music companies, advancements in AI bring new possibilities for creativity and efficiency along with critical ethical concerns regarding economic impact, bias, and data harvesting. AI’s role in the music industry is a double-edged sword, offering both opportunities and challenges. On the one hand, AI automates many aspects of music creation and production. Tasks like composition, audio mastering, and even lyric writing can now be performed by AI tools. However, this automation has led to concerns about job displacement. Traditional roles in the industry, such as sound engineers and live musicians, face increasing obsolescence as AI tools become more sophisticated and accessible. However, AI also democratizes music production, enabling independent artists and smaller labels to create high-quality music without needing expensive equipment or studio time. So, while jobs are being lost, new roles are emerging, such as AI music curators and prompt engineers. This demonstrates how technological advancements can create fresh opportunities even as they disrupt existing systems. Another critical issue in the use of AI in music is the presence of bias in the models used to generate content. AI systems are only as good as the data they are trained on, and this dependency can result in significant imbalances. For instance, if an AI model’s training data predominantly features Western music, the system may struggle to generate accurate representations of non-Western genres or cultural styles. Along with racial bias, gender bias in datasets used for AI training can perpetuate existing inequalities in the music industry. If female and non-binary artists are underrepresented in the data, AI-generated music may disproportionately reflect the styles and contributions of male artists. Such biases highlight the need for diverse and inclusive training datasets. Developers must address these issues to ensure that AI tools reflect a broader and more equitable spectrum of musical expression. As discussed previously, the question of how AI systems source their training data has sparked widespread ethical debates. Many AI models, most notably Suno and Udio, are trained using copyrighted music, often without the consent or compensation of the original artists and have received backlash. This practice raises significant concerns about exploitation. Artists invest considerable time and effort into creating music, yet their work can be appropriated by AI systems without acknowledgment or financial remuneration. This mirrors controversies in other areas of AI, such as the exploitation of the unpaid labor of associated with Remotask workers. If creators cannot safeguard their work against unauthorized use by AI systems, the industry risks devaluing artistic contributions in favor of technological efficiency. The music industry is at a crossroads–do we protect the rights of creators, or do we embrace AI-drive efficiency without clear ethical guidelines? === AI in the Video Game Industry === The intersection of visual art, music, voice, and code make the gaming industry a hot spot for AI usage within creative works. AI has existed within gaming for some time in the form of non-playable characters (NPCs), but the modern implementation of AI within gaming specifically sees increased usage of generative tools for creative purposes. === Nvidia DLSS 5.0 === Nvidia is a prolific graphics card producer with extensive ties to the gaming industry. Originally founded for the purpose of innovating computer gaming<ref>{{Cite web |title=NVIDIA Corporation: History |url=https://www.nvidia.com/en-us/about-nvidia/corporate-timeline/ |access-date=2026-05-04 |website=NVIDIA |language=en-us}}</ref>, they have since leveraged their graphics processing unit (GPU) technology for AI usage extensively, while also seeking to implement AI within their gaming technologies. Deep Learning Super Sampling (DLSS) is a technology developed by Nvidia to use real-time deep learning AI to upscale video game rendering. The initial versions of DLSS were employed by running games at a lower native resolution, then using AI to upscale to a higher resolution based on the picture generated by the GPU<ref>{{Cite web |last=Martindale |first=Jon |date=2020-02-14 |title=Nvidia RTX DLSS: everything you need to know |url=https://www.digitaltrends.com/computing/everything-you-need-to-know-about-nvidias-rtx-dlss-technology/ |access-date=2026-05-04 |website=Digital Trends |language=en-us}}</ref>; this implementation did not use AI to directly modify any of the actual contents of games themselves. DLSS 5.0, however, made use of generative AI to attempt to directly enhance the visual content of games. While the exact details of the implementation have yet to be released as of May 2026, the technology appears to generate new frames from prior training data, using the existing content of a game as the base. This introduces elements of the rendering which may not have been present in the original developer's vision. == Reception == === Music === ==== Students ==== While students seem to find AI music fascinating, they emphasize that AI music lacks the emotional depth found in human compositions. They explain that human compositions are capable of conveying authentic human experiences and feelings, which AI cannot replicate. ''Quotes are pulled directly from a New York Times article''<ref>{{Cite web |last=The Learning Network |first= |date=May 11, 2023 |title=What Students Are Saying About A.I.-Generated Music |url=https://www.nytimes.com/2023/05/11/learning/what-students-are-saying-about-ai-generated-music.html |url-status=live |access-date=December 9, 2024 |website=The New York Times}}</ref>: "Human singers have the ability to convey a wide range of emotions and add their own unique style to their music. They have the creativity and experience to interpret lyrics and to give them their own style. Music made with A.I. may be good, but it will never be the same as music sung by a good pop star. While A.I. can be a helpful tool for composers and producers to experiment with new sounds and styles, it will never replace the raw talent and artistry of human vocalists." - ''Sergi, Sant Gregori'' "In my personal opinion, the main allure of music lies in the emotional connection that it establishes with the listener. It’s not only about the melody or the lyrics, but also the sentiments and reminiscences that the music evokes. If I became aware that a song was completely generated by an artificial intelligence system, I would feel intrigued to listen to it, driven by my fascination with the underlying technology. Nevertheless, I might not feel as connected to the song on an emotional level as I would if it was composed by a human artist." - ''Aleena, Julia R. Masterman, Philadelphia, PA'' "Even if the lyrics emulate a real pop star’s lyrics, whether it talks about heartbreak, love, or family, it would never have the same impact like one created by a real pop star because the listeners know it is all just to sound good and appeal to the listeners. It would have nothing to do with the artist themselves … Music is supposed to be relatable. When I listen to music, I like to listen to artists I know have gone through similar things or have the same feelings as me." - ''Sophia, Hinsdale Central High School'' ==== Composers ==== The evolution of composers attitudes towards AI music is reflected in [https://www.youtube.com/channel/UCelK8dBKY0Xs5oRI6sJf7aA Daniel James], a composer on YouTube, perspective over time. While he acknowledged that AI generated music was inevitable, it would never allow a total newbie to suddenly become a professional.<ref>{{Citation |last=Daniel James |title=TADay #4 - Composer Talk Radio - Is AI a threat or is it the future of composition. |date=2019-06-29 |url=https://www.youtube.com/watch?v=cqJWI4HF1CY |access-date=2024-12-09}}</ref> He suggested if AI became proficient in replicating professionals, composers would need to come up with their own style away from the AI. James had a positive view on AIs potential as a tool, comparing it to a ghost composer that could handle much of the monotonous work that an assistant might do. He predicted that AI would primarily impact the lower-skilled composers, widening the gap between low and high skilled composers. By 2023, James' perspective has become more nuanced.<ref>{{Citation |last=Daniel James |title=AI In The Music Industry - Tool Or Threat - A Professional Composers View. |date=2022-12-11 |url=https://www.youtube.com/watch?v=fOL32kRuUI0 |access-date=2024-12-09}}</ref> He discussed the limitations of AI, explaining that it can't really create something new, and can only make variations. While acknowledging AIs capability to blend styles, like reimagining Beethoven as hip-hop, he emphasizes that music exists within the context of the time it is created. James considers that although AI can accurately replicate music, it still struggles with emotional nuance. He also notes that skilled AI use would still require musical expertise to properly guide the AI. James also discusses the significant impacts AI might have. Formulaic music like EDM and trailer music seem particularly vulnerable to AI as there is a "correct" way to write those styles of music. He also believes that AI music will severely damage the lower end of the creative field. He worries that if newer generations of artists are trained to use AI, they may forget how to develop their own original styles, stunting their growth. The broader composer community has similar views. On Reddit, many composers advocate for limiting AI's role to reference and placeholder work that bridge the gap between the client and the composer.<ref>{{Cite web |last=ArgamaWitch |date=2024-04-15 |title=Composers that take commissions, what's your thoughts on AI music being used as reference? |url=https://www.reddit.com/r/composer/comments/1c4vrvr/composers_that_take_commissions_whats_your/?rdt=57624 |access-date=2024-12-09 |website=r/composer}}</ref> The consensus among professional composers, including James, is that AI needs much better regulation. They argue for protecting artists' unique, copyrightable styles from unauthorized AI replication and advocate that AI companies should compensate the artists whos works train the AI models. These composers are working to convince the Copyright Office that training AI on artists' work without compensation devalues artists. == References == <references /> {{BookCat}} 5bccggeij69s2c5g72lf7yiqsc8d0b1 4634094 4634092 2026-05-04T15:34:28Z Humzarubel 3581183 Expansion of section on NVIDIA DLSS 5.0 and AI use in gaming, addition of gaming reception in reception section 4634094 wikitext text/x-wiki == Overview == === Introduction === Artificial intelligence (AI) is revolutionizing creative industries, such as the music industry, by redefining how creative works are composed, performed, and consumed. What began as theoretical musings by pioneers like Alan Turing has grown into a field with sophisticated neural networks capable of composing full-length songs, for example. However, this evolution raises pressing questions about originality, ownership, and the future of human creativity. === History of AI and Music === ====== Theoretical Foundations: 1950s-1960s ====== The concept of AI-generated music originated with Alan Turing, who theorized in the 1950s that machines could emulate human cognitive processes, including music composition. His ideas laid the groundwork for computational creativity.<ref>{{Citation |last=Copeland |first=B. Jack |title=Turing and the History of Computer Music |date=2017 |url=https://link.springer.com/chapter/10.1007/978-3-319-53280-6_8 |work=Philosophical Explorations of the Legacy of Alan Turing: Turing 100 |pages=189–218 |editor-last=Floyd |editor-first=Juliet |access-date=2024-12-02 |place=Cham |publisher=Springer International Publishing |language=en |doi=10.1007/978-3-319-53280-6_8 |isbn=978-3-319-53280-6 |last2=Long |first2=Jason |editor2-last=Bokulich |editor2-first=Alisa}}</ref> In 1957, Lejaren Hiller and Leonard Isaacson at the University of Illinois created the Illiac Suite<ref>{{Cite web |title=ILLIAC Suite – Illinois Distributed Museum |url=https://distributedmuseum.illinois.edu/exhibit/illiac-suite/ |access-date=2024-12-02 |website=distributedmuseum.illinois.edu}}</ref>. Using the ILLIAC I computer, they developed an algorithmic process to compose a string quartet, marking one of the first successful instances of computer-generated music. It demonstrated the potential of computers to collaborate in creative endeavors, sparking decades of research into AI's role in music. ====== Rule-Based Systems: 1970s-1980s ====== During the 1970s and 1980s, AI systems advanced with rule-based algorithms that mimicked specific musical styles. David Cope’s Experiments in Musical Intelligence<ref>{{Cite web |last=tluong |date=2015-04-29 |title=Algorithmic Music – David Cope and EMI |url=https://computerhistory.org/blog/algorithmic-music-david-cope-and-emi/ |access-date=2024-12-02 |website=CHM |language=en}}</ref> (EMI) exemplified this approach by analyzing existing compositions and generating new ones in the style of Bach and Mozart. However, EMI heavily relied on predefined human rules, highlighting the imitative, rather than generative, nature of early AI. A significant technological leap came in 1983 with the introduction of MIDI<ref>{{Citation |title=MIDI |date=2024-11-25 |url=https://en.wikipedia.org/wiki/MIDI |work=Wikipedia |access-date=2024-12-02 |language=en}}</ref> (Musical Instrument Digital Interface). MIDI standardized communication between computers and electronic instruments, enabling precise control of musical elements and facilitating data collection for future AI systems. ====== Machine Learning: 1990s-2000s ====== AI music systems transitioned from rule-based models to data-driven techniques in the 1990s. Machine learning algorithms enabled pattern recognition and predictive modeling, allowing AI to generate more complex and varied compositions. Projects like Accenture’s Symphonologie<ref>{{Cite web |title=Accenture {{!}} Symphonologie |url=https://www.oneclub.org/awards/theoneshow/-award/25489/symphonologie/ |access-date=2024-12-02 |website=www.oneclub.org |language=en}}</ref> showcased AI as a collaborative tool, blending human and machine creativity. ====== Neural Networks: 2010s-Present ====== The rise of deep learning revolutionized AI in music. Neural networks, trained on vast datasets, now compose intricate, multi-instrumental pieces in seconds. Tools like OpenAI’s MuseNet<ref>{{Cite web |title=MuseNet |url=https://openai.com/index/musenet/ |access-date=2024-12-02 |website=openai.com |language=en-US}}</ref> and AIVA<ref>{{Cite web |title=AIVA, the AI Music Generation Assistant |url=https://www.aiva.ai/ |access-date=2024-12-02 |website=www.aiva.ai |language=en}}</ref> exemplify how AI has expanded its creative capabilities across genres, challenging the boundaries of human artistry. == Relevant Legal Disputes == === Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884) === [[File:Oscar Wilde 1882.jpg|thumb|Oscar Wilde No.18 by Napoleon Sarony (1882)]] [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithography Co v. Sarony]] was submitted on December 13, 1883 when Sarony filed a copyright suit against Burrow-Giles when the company had marketed lithographs of Sarony's photograph, Oscar Wilde No.18, without Sarony's permission. Burrow-Giles argued that photographs were neither writings nor a production of an author, and thus did not possess copyright protection. The court determined that even though creating a photograph is "merely mechanical, with no place for novelty, invention, or originality", the photograph Sarony created was his "own original mental conception, to which he gave visible form by posing the said Oscar Wilde in front of the camera, selecting and arranging the costume, draperies, . . . suggesting and evoking the desired expression, and from such . . . representation, made entirely by plaintiff, he produced the picture in suit.'" On March 17, 1884, the court established that photography is a copyrightable medium. Furthermore, this case reinforced that an author of a work is "he to whom anything owes its origin."<ref>Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884)</ref> === Naruto v. Slater, No. 16-15469 (9th Cir. 2018) === [[File:Macaca nigra self-portrait large.jpg|left|thumb|One of the monkey selfies]] Naruto v. Slater, more commonly known as the [[wikipedia:Artificial_intelligence_and_copyright|Monkey Selfie copyright dispute]], began on September 22, 2015. PETA, representing the crested macaque Naruto, sued Slater claiming that because the monkey took its own picture, it was entitled to the copyright. David J. Slater, the photographer, argued that he held the copyright as he engineered the situation that led to the monkey taking its selfie. On April 23, 2018, the court determined that "this monkey - and all animals, since they are not human – [lack] statutory standing under the Copyright Act", reinforcing that non-humans cannot own copyright.<ref>Naruto v. Slater, No. 16-15469 (9th Cir. 2018)</ref> === Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023) === [[File:A Recent Entrance to Paradise.jpg|thumb|A Recent Entrance to Paradise]] Thaler v. Perlmutter emerged after the U.S. Copyright Office denied Dr. Stephen Thaler's copyright application for an AI generated work, "A Recent Entrance to Paradise". The court focused on answering "whether a work generated autonomously by a computer falls under the protection of copyright law upon its creation". Thaler filed a lawsuit, arguing that the copyright of the AI generated work belonged to him as the AI model's creator. He stated that "AI should be ‘acknowledge[d] . . . as an author where it otherwise meets authorship criteria, with any copyright ownership vesting in the AI’s owner.’" The court reviewed the decision of [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithographic Co. v. Sarony]], finding that the author of any AI generated work would be the AI. However, following the decision of [[wikipedia:Artificial_intelligence_and_copyright|Naruto v. Slater]], since AIs are not human, they cannot hold copyright. The case was decided on August 18, 2023, confirming that AIs cannot hold copyright. As such, the work fell under public domain. However, the court explicitly stated that they were not making any decisions on "how much human input is necessary to qualify the user of an AI system as an 'author' of a generated work".<ref>Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023)</ref> The D.C. Circuit unanimously affirmed in March 2025. On March 2, 2026, the Supreme Court denied certiorari, making the ruling final and exhausting Thaler's appeals. ''Thaler'' now stands as binding precedent that AI systems cannot themselves be authors under U.S. copyright law, and that works generated entirely without human creative contribution are ineligible for registration. '''''Allen v. Perlmutter'', No. 24-2665 (WJM) (D. Colo. 2026)''' [[File:Théâtre D’opéra Spatial.png|thumb|''Théâtre D'opéra Spatial'', created by Jason M. Allen using Midjourney, Photoshop, and Gigapixel AI]] ''Allen v. Perlmutter'' picks up where ''Thaler'' left off. In August 2022, Colorado artist Jason Allen used Midjourney to create ''Théâtre D'opéra Spatial'', entering text prompts at least 624 times to specify genre, tone, composition, and style, then refining the chosen output in Photoshop and Gigapixel AI. The image won first place at the Colorado State Fair in September 2022. When Allen applied for copyright registration as the sole human author, the Office offered to register only the portions reflecting his own contributions if he disclaimed the AI-generated material. Allen refused, and after the Review Board issued its final refusal in June 2023, he filed suit in the U.S. District Court for the District of Colorado on September 26, 2024. He moved for summary judgment in August 2025, the Copyright Office cross-moved in January 2026, and Allen filed his reply in February 2026. Allen argues that his iterative prompting and creative selection constitute authorship analogous to the photographer's creative choices that made photography copyrightable under ''Burrow-Giles''. The Copyright Office counters that prompts are ideas, not expression, because Midjourney determines the actual visual output regardless of how detailed the instructions are. The case is now fully briefed before Judge William J. Martínez, with a ruling expected in 2026 that will produce the first judicial standard answering the question ''Thaler'' left open: when does human input in AI-assisted work rise to the level of copyright authorship? === Zarya of the Dawn === [[File:Zarya of the Dawn cover.webp|thumb|Zarya of the Dawn by Kristina Kashtanova]] [[wikipedia:Zarya_of_the_Dawn|Zarya of the Dawn]], a comic book authored by Kristina Kashtanova and illustrated using the AI generator Midjourney sparked a significant copyright dispute in 2022. When Kashtanova applied for copyright of the comic in September 2022, she failed to disclose that the images were generated by Midjourney. The comic was originally granted copyright by the Copyright Office, but after discovering Midjourney's involvement in illustrating the comic, they reviewed their decision. While the Copyright Office agreed that the text and compilation (the arrangement of images and text) were copyrightable, the art was not, as the "process is not controlled by the user because it is not possible to predict what Midjourney will create ahead of time." Although, Kashtanova claimed "she personally edited some of the images created by Midjourney", the Copyright office could not determine "what expression in the image was contributed through her use of Photoshop as opposed to generated by Midjourney" and thus revoked the copyright. <ref>{{Cite web |last=Kasunic |first=Robert J. |date=February 21, 2023 |title=2023.02.21 Zarya of the Dawn Letter |url=https://www.copyright.gov/docs/zarya-of-the-dawn.pdf |url-status=live |access-date=December 9, 2024 |website=Copyright Office (.gov)}}</ref> == Relevant Copyright Chapters == === Chapter 308: The Originality Requirement<ref name=":0">U.S. Copyright Office, Compendium of U.S. Copyright Office Practices § 101 (3d ed. 2021).</ref> === The Originality Requirement has two primary requirements: "The work must be ‘independently created by the author’ and it must possess ‘at least some minimal degree of creativity’" ==== Chapter 308.1 ==== The Copyright Act defines "independent creation" as a work created "without copying from other works." However, "a work may satisfy the independent creation requirement ‘even though it closely resembles other works so long as the similarity is fortuitous, not the result of copying.’" ==== Chapter 308.2 ==== In terms of creativity, the Copyright Act states that "‘the requisite level of creativity is extremely low.’ Even a ‘slight amount’ of creative expression will suffice.’" ==== Works That Do Not Satisfy the Originality Requirement ==== 313.4(A): Mere Copies 313.4(K): Mere Variations of Colorings === Chapter 306: The Human Authorship Requirement<ref name=":0" /> === The Human Authorship Requirement states that only humans may own a copyright. "The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being." ==== Chapter 313.2 ==== The chapter states that "the U.S. Copyright Office will not register works produced by nature, animals, or plants." Furthermore, "the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author." ==== Works That Lack Human Authorship ==== * A photograph taken by a monkey. * A mural painted by an elephant. * A claim based on the appearance of actual animal skin. * A claim based on driftwood that has been shaped and smoothed by the ocean. * A claim based on cut marks, defects, and other qualities found in natural stone. * An application for a song naming the Holy Spirit as the author of the work. === Chapter 507.1: Derivate Works<ref name=":0" /> === As AI generated works are considered to be authored by the AI, and thus public domain, attempts to edit and then copyright the works would most likely fall under derivative works. The Copyright Act defines a derivative work as "a work based upon one or more preexisting works, such as a . . . art reproduction . . . or any other form in which a work may be recast, transformed, or adapted." ==== Chapter 311.2 ==== Derivative works follow the same originality requirements as original works. Derivative works may only receive copyright protection "provided that [the work] contains a sufficient amount of original expression, meaning that the derivative work must be independently created and it must possess more than a modicum of creativity" The Copyright Act does reiterate that "[m]iniscule variations do not satisfy this requirement, such as merely changing the size of the preexisting work." == Present Issues == === AI Music === ==== Lack of Creativity ==== In 2023, an anonymous creator known as "Ghostwriter" released Heart on My Sleeve, featuring AI-generated vocals mimicking Drake and The Weeknd. The song went viral, drawing millions of streams before being removed for copyright infringement. Universal Music Group argued that the AI-generated track exploited the artists’ likenesses without consent, raising ethical and legal concerns<ref>{{Cite web |last=Reed |first=Rachel |title=AI created a song mimicking the work of Drake and The Weeknd. What does that mean for copyright law? |url=https://hls.harvard.edu/today/ai-created-a-song-mimicking-the-work-of-drake-and-the-weeknd-what-does-that-mean-for-copyright-law/ |access-date=2024-12-02 |website=Harvard Law School |language=en-us}}</ref>. This case highlights AI’s ability to imitate human creativity so convincingly that it blurs the line between originality and replication. Although the creator faced no legal repercussions, the controversy underscored the need for clearer regulations on AI-generated content. * AI doesn’t create entirely new works; it amplifies patterns derived from training data. While it can replicate styles, it lacks the emotional depth and intentionality of human artistry. * Tools like MuseNet and Suno allow anyone to compose music in minutes, potentially devaluing human creativity by making artistic production instantaneous and impersonal. ==== Suno and Udio ==== The most current case reflecting the debate regarding the originality of AI music is in the RIAA vs. Suno and RIAA vs. Udio. The RIAA, or the Recording Industry Association of America, is a trade organization that represents many record labels, including Sony Music Group, Universal Music Group, and Warner Music Group (colloquially known as "the big Three" in the industry as they own up to 85% of market share). In June 2024, the RIAA placed a copyright infringement lawsuit on Suno and Udio (two generative AI music startup companies). They had three main goals with this lawsuit: <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html#:~:text=The%20lawsuits%20make%20three%20specific,to%20nine%20figures%20or%20more. |access-date=2024-12-10 |website=Vulture |language=en}}</ref> # To have these companies admit their models use copyrighted music. # Immediately stop training their AI models using this copyrighted music. # Seek damages up to $150,000 per song used in the models. When first discussing the lawsuit with the press, Chairman and CEO of RIAA, Mitch Glazier, stated: "The music community has embraced AI and we are already partnering and collaborating with responsible developers to build sustainable AI tools centered on human creativity '''that put artists and songwriters in charge''', but we can only succeed if developers are willing to work together with us. Unlicensed services like Suno and Udio that '''claim it's 'fair' to copy an artist's life's work and exploit it for their own profit without consent or pay''' set back the promise of genuinely innovative AI for us all."<ref>{{Cite web |last=Connelly |first=Rose |date=2024-06-24 |title=Record Companies Bring Landmark Cases for Responsible AI Against Suno and Udio in Boston and New York Federal Courts, Respectively |url=https://www.riaa.com/record-companies-bring-landmark-cases-for-responsible-ai-againstsuno-and-udio-in-boston-and-new-york-federal-courts-respectively/ |access-date=2024-12-10 |website=RIAA |language=en-US}}</ref> The RIAA hopes to reflect that the inherent moral value of this statement for pursuing this lawsuit is protecting artists' work and fair pay. However, in any of RIAA's arguments, the percentage of and how the money collected from damages will be distributed to the artists of each respective record label must be clarified. Suno responded to the copyright lawsuit, "What the major record labels really don't want is competition." While this calls to question the actual motive of the lawsuit and whether the benefactors will include artists, the results of this lawsuit are pertinent as they will set further precedents in how copyright pertains to AI overall. Initially, in response to the lawsuit, Udio claimed "fair use," which is primarily used for academic or journalistic purposes. However, lawyers dismissed this claim because their training is not used for human-created content. <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html |access-date=2024-12-10 |website=Vulture |language=en}}</ref> As the lawsuit proceeded, both companies admitted to using copyrighted music only as "intermediate copies." They sighted a copyright case from 2021 regarding an AI algorithm's use of copyrighted images to create a search algorithm. In that case, using these "intermediate copies was lawful" because these lower-resolution copies did not satisfy the user's desire to see the full images. However, in Suno and Udio's context, their AI models are not search algorithms but are generative.  ==== Other AI Music Lawsuits ==== Following this case, different record labels (primarily Universal) have filed a copyright on issues regarding AI music. On October 18, 2023, several record labels, namely Universal, filed a lawsuit alleging that Anthropic's AI chatbot, "Claude," unlawfully copied and disseminated copyrighted works, including lyrics "owned or controlled by the Publishers. On January 31, 2024, the copyright license agreement between Universal Music Group (UMG), the world's largest music company, and TikTok owner ByteDance Ltd. expired without a renewal agreement. TikTok was forced to turn off the reproduction of all audio content from artists belonging to UMG's catalog, including Taylor Swift, Billie Eilish, Romeo Santos, J Balvin, and Imagine Dragons, among many others. During these negotiations, UMG made AI-generated music a sticking point in their TikTok negotiations, and a group of musicians spoke out against AI-generated music. Groups, including the Recording Academy, the Music Workers Alliance, the National Association of Music Publishers, the American Association of Independent Music, and even SAG-AFTRA, have all made statements supporting the lawsuits. ==== Ethical Implications of AI in the Music Industry ==== As is apparent with the growing number of lawsuits directed at AI music companies, advancements in AI bring new possibilities for creativity and efficiency along with critical ethical concerns regarding economic impact, bias, and data harvesting. AI’s role in the music industry is a double-edged sword, offering both opportunities and challenges. On the one hand, AI automates many aspects of music creation and production. Tasks like composition, audio mastering, and even lyric writing can now be performed by AI tools. However, this automation has led to concerns about job displacement. Traditional roles in the industry, such as sound engineers and live musicians, face increasing obsolescence as AI tools become more sophisticated and accessible. However, AI also democratizes music production, enabling independent artists and smaller labels to create high-quality music without needing expensive equipment or studio time. So, while jobs are being lost, new roles are emerging, such as AI music curators and prompt engineers. This demonstrates how technological advancements can create fresh opportunities even as they disrupt existing systems. Another critical issue in the use of AI in music is the presence of bias in the models used to generate content. AI systems are only as good as the data they are trained on, and this dependency can result in significant imbalances. For instance, if an AI model’s training data predominantly features Western music, the system may struggle to generate accurate representations of non-Western genres or cultural styles. Along with racial bias, gender bias in datasets used for AI training can perpetuate existing inequalities in the music industry. If female and non-binary artists are underrepresented in the data, AI-generated music may disproportionately reflect the styles and contributions of male artists. Such biases highlight the need for diverse and inclusive training datasets. Developers must address these issues to ensure that AI tools reflect a broader and more equitable spectrum of musical expression. As discussed previously, the question of how AI systems source their training data has sparked widespread ethical debates. Many AI models, most notably Suno and Udio, are trained using copyrighted music, often without the consent or compensation of the original artists and have received backlash. This practice raises significant concerns about exploitation. Artists invest considerable time and effort into creating music, yet their work can be appropriated by AI systems without acknowledgment or financial remuneration. This mirrors controversies in other areas of AI, such as the exploitation of the unpaid labor of associated with Remotask workers. If creators cannot safeguard their work against unauthorized use by AI systems, the industry risks devaluing artistic contributions in favor of technological efficiency. The music industry is at a crossroads–do we protect the rights of creators, or do we embrace AI-drive efficiency without clear ethical guidelines? === AI in the Video Game Industry === The intersection of visual art, music, voice, and code make the gaming industry a hot spot for AI usage within creative works. AI has existed within gaming for some time in the form of non-playable characters (NPCs), but the modern implementation of AI within gaming specifically sees increased usage of generative tools for creative purposes. ==== Nvidia DLSS 5.0 ==== Nvidia is a prolific graphics card producer with extensive ties to the gaming industry. Originally founded for the purpose of innovating computer gaming<ref>{{Cite web |title=NVIDIA Corporation: History |url=https://www.nvidia.com/en-us/about-nvidia/corporate-timeline/ |access-date=2026-05-04 |website=NVIDIA |language=en-us}}</ref>, they have since leveraged their graphics processing unit (GPU) technology for AI usage extensively, while also seeking to implement AI within their gaming technologies. Deep Learning Super Sampling (DLSS) is a technology developed by Nvidia to use real-time deep learning AI to upscale video game rendering. The initial versions of DLSS were employed by running games at a lower native resolution, then using AI to upscale to a higher resolution based on the picture generated by the GPU<ref>{{Cite web |last=Martindale |first=Jon |date=2020-02-14 |title=Nvidia RTX DLSS: everything you need to know |url=https://www.digitaltrends.com/computing/everything-you-need-to-know-about-nvidias-rtx-dlss-technology/ |access-date=2026-05-04 |website=Digital Trends |language=en-us}}</ref>; this implementation did not use AI to directly modify any of the actual contents of games themselves. DLSS 5.0, however, made use of generative AI to attempt to directly enhance the visual content of games. While the exact details of the implementation have yet to be released as of May 2026, the technology appears to generate new frames from prior training data, using the existing content of a game as the base. This introduces elements of the rendering which may not have been present in the original developer's vision, and poses issues related to artistic vision: Since the AI is able to directly add new content and textures, concerns are raised about whether a game is still the same piece of art/media. ==== AI Voice Acting and Other Content ==== AI usage in gaming development can be difficult to discern, leading to the spread of many rumors and allegations of use in voice acting, dialogue generation, textures, among others. Games such as The Finals and Arc Raiders have been accused of using AI tools to generate voice lines, which many perceive to be of lower quality than those generated by human counterparts. For The Finals in particular, the developers at Embark Studios stated that they used AI to extend voice lines created by real voice actors<ref>{{Cite web |last=Notis |first=Ari |date=2025-10-31 |title=Arc Raiders' use of AI voices is The Finals controversy all over again |url=https://www.polygon.com/arc-raiders-ai-voices-the-finals-embark-studios/ |access-date=2026-05-04 |website=Polygon.com |language=en}}</ref>. This can be problematic with respect to intellectual property rights, say for instance a development studio, unbeknown to a voice actor, is using said actor's voice as a baseline for AI generated quips and content. == Reception == === Music === ==== Students ==== While students seem to find AI music fascinating, they emphasize that AI music lacks the emotional depth found in human compositions. They explain that human compositions are capable of conveying authentic human experiences and feelings, which AI cannot replicate. ''Quotes are pulled directly from a New York Times article''<ref>{{Cite web |last=The Learning Network |first= |date=May 11, 2023 |title=What Students Are Saying About A.I.-Generated Music |url=https://www.nytimes.com/2023/05/11/learning/what-students-are-saying-about-ai-generated-music.html |url-status=live |access-date=December 9, 2024 |website=The New York Times}}</ref>: "Human singers have the ability to convey a wide range of emotions and add their own unique style to their music. They have the creativity and experience to interpret lyrics and to give them their own style. Music made with A.I. may be good, but it will never be the same as music sung by a good pop star. While A.I. can be a helpful tool for composers and producers to experiment with new sounds and styles, it will never replace the raw talent and artistry of human vocalists." - ''Sergi, Sant Gregori'' "In my personal opinion, the main allure of music lies in the emotional connection that it establishes with the listener. It’s not only about the melody or the lyrics, but also the sentiments and reminiscences that the music evokes. If I became aware that a song was completely generated by an artificial intelligence system, I would feel intrigued to listen to it, driven by my fascination with the underlying technology. Nevertheless, I might not feel as connected to the song on an emotional level as I would if it was composed by a human artist." - ''Aleena, Julia R. Masterman, Philadelphia, PA'' "Even if the lyrics emulate a real pop star’s lyrics, whether it talks about heartbreak, love, or family, it would never have the same impact like one created by a real pop star because the listeners know it is all just to sound good and appeal to the listeners. It would have nothing to do with the artist themselves … Music is supposed to be relatable. When I listen to music, I like to listen to artists I know have gone through similar things or have the same feelings as me." - ''Sophia, Hinsdale Central High School'' ==== Composers ==== The evolution of composers attitudes towards AI music is reflected in [https://www.youtube.com/channel/UCelK8dBKY0Xs5oRI6sJf7aA Daniel James], a composer on YouTube, perspective over time. While he acknowledged that AI generated music was inevitable, it would never allow a total newbie to suddenly become a professional.<ref>{{Citation |last=Daniel James |title=TADay #4 - Composer Talk Radio - Is AI a threat or is it the future of composition. |date=2019-06-29 |url=https://www.youtube.com/watch?v=cqJWI4HF1CY |access-date=2024-12-09}}</ref> He suggested if AI became proficient in replicating professionals, composers would need to come up with their own style away from the AI. James had a positive view on AIs potential as a tool, comparing it to a ghost composer that could handle much of the monotonous work that an assistant might do. He predicted that AI would primarily impact the lower-skilled composers, widening the gap between low and high skilled composers. By 2023, James' perspective has become more nuanced.<ref>{{Citation |last=Daniel James |title=AI In The Music Industry - Tool Or Threat - A Professional Composers View. |date=2022-12-11 |url=https://www.youtube.com/watch?v=fOL32kRuUI0 |access-date=2024-12-09}}</ref> He discussed the limitations of AI, explaining that it can't really create something new, and can only make variations. While acknowledging AIs capability to blend styles, like reimagining Beethoven as hip-hop, he emphasizes that music exists within the context of the time it is created. James considers that although AI can accurately replicate music, it still struggles with emotional nuance. He also notes that skilled AI use would still require musical expertise to properly guide the AI. James also discusses the significant impacts AI might have. Formulaic music like EDM and trailer music seem particularly vulnerable to AI as there is a "correct" way to write those styles of music. He also believes that AI music will severely damage the lower end of the creative field. He worries that if newer generations of artists are trained to use AI, they may forget how to develop their own original styles, stunting their growth. The broader composer community has similar views. On Reddit, many composers advocate for limiting AI's role to reference and placeholder work that bridge the gap between the client and the composer.<ref>{{Cite web |last=ArgamaWitch |date=2024-04-15 |title=Composers that take commissions, what's your thoughts on AI music being used as reference? |url=https://www.reddit.com/r/composer/comments/1c4vrvr/composers_that_take_commissions_whats_your/?rdt=57624 |access-date=2024-12-09 |website=r/composer}}</ref> The consensus among professional composers, including James, is that AI needs much better regulation. They argue for protecting artists' unique, copyrightable styles from unauthorized AI replication and advocate that AI companies should compensate the artists whos works train the AI models. These composers are working to convince the Copyright Office that training AI on artists' work without compensation devalues artists. === Gaming === ==== Players ==== Players of video games tend towards a negative reception of generative AI usage in game development. Games will often receive negative reviews or discussions on forum pages when AI use is apparent: for instance, Steam (a platform used to distribute and discuss games) has entire community-driven pages dedicated towards identifying and shaming AI employment in games<ref>{{Cite web |title=Steam Curator: Games That Use AI Generation |url=https://store.steampowered.com/curator/45944619-Games-That-Use-AI-Generation/ |access-date=2026-05-04 |website=store.steampowered.com |language=en}}</ref>. == References == <references /> {{BookCat}} cx6benvrtercrae1cw4x9z8zh8vzt4h 4634122 4634094 2026-05-04T17:23:04Z ~2026-27050-27 3581225 Updated Suno and Udio section 4634122 wikitext text/x-wiki == Overview == === Introduction === Artificial intelligence (AI) is revolutionizing creative industries, such as the music industry, by redefining how creative works are composed, performed, and consumed. What began as theoretical musings by pioneers like Alan Turing has grown into a field with sophisticated neural networks capable of composing full-length songs, for example. However, this evolution raises pressing questions about originality, ownership, and the future of human creativity. === History of AI and Music === ====== Theoretical Foundations: 1950s-1960s ====== The concept of AI-generated music originated with Alan Turing, who theorized in the 1950s that machines could emulate human cognitive processes, including music composition. His ideas laid the groundwork for computational creativity.<ref>{{Citation |last=Copeland |first=B. Jack |title=Turing and the History of Computer Music |date=2017 |url=https://link.springer.com/chapter/10.1007/978-3-319-53280-6_8 |work=Philosophical Explorations of the Legacy of Alan Turing: Turing 100 |pages=189–218 |editor-last=Floyd |editor-first=Juliet |access-date=2024-12-02 |place=Cham |publisher=Springer International Publishing |language=en |doi=10.1007/978-3-319-53280-6_8 |isbn=978-3-319-53280-6 |last2=Long |first2=Jason |editor2-last=Bokulich |editor2-first=Alisa}}</ref> In 1957, Lejaren Hiller and Leonard Isaacson at the University of Illinois created the Illiac Suite<ref>{{Cite web |title=ILLIAC Suite – Illinois Distributed Museum |url=https://distributedmuseum.illinois.edu/exhibit/illiac-suite/ |access-date=2024-12-02 |website=distributedmuseum.illinois.edu}}</ref>. Using the ILLIAC I computer, they developed an algorithmic process to compose a string quartet, marking one of the first successful instances of computer-generated music. It demonstrated the potential of computers to collaborate in creative endeavors, sparking decades of research into AI's role in music. ====== Rule-Based Systems: 1970s-1980s ====== During the 1970s and 1980s, AI systems advanced with rule-based algorithms that mimicked specific musical styles. David Cope’s Experiments in Musical Intelligence<ref>{{Cite web |last=tluong |date=2015-04-29 |title=Algorithmic Music – David Cope and EMI |url=https://computerhistory.org/blog/algorithmic-music-david-cope-and-emi/ |access-date=2024-12-02 |website=CHM |language=en}}</ref> (EMI) exemplified this approach by analyzing existing compositions and generating new ones in the style of Bach and Mozart. However, EMI heavily relied on predefined human rules, highlighting the imitative, rather than generative, nature of early AI. A significant technological leap came in 1983 with the introduction of MIDI<ref>{{Citation |title=MIDI |date=2024-11-25 |url=https://en.wikipedia.org/wiki/MIDI |work=Wikipedia |access-date=2024-12-02 |language=en}}</ref> (Musical Instrument Digital Interface). MIDI standardized communication between computers and electronic instruments, enabling precise control of musical elements and facilitating data collection for future AI systems. ====== Machine Learning: 1990s-2000s ====== AI music systems transitioned from rule-based models to data-driven techniques in the 1990s. Machine learning algorithms enabled pattern recognition and predictive modeling, allowing AI to generate more complex and varied compositions. Projects like Accenture’s Symphonologie<ref>{{Cite web |title=Accenture {{!}} Symphonologie |url=https://www.oneclub.org/awards/theoneshow/-award/25489/symphonologie/ |access-date=2024-12-02 |website=www.oneclub.org |language=en}}</ref> showcased AI as a collaborative tool, blending human and machine creativity. ====== Neural Networks: 2010s-Present ====== The rise of deep learning revolutionized AI in music. Neural networks, trained on vast datasets, now compose intricate, multi-instrumental pieces in seconds. Tools like OpenAI’s MuseNet<ref>{{Cite web |title=MuseNet |url=https://openai.com/index/musenet/ |access-date=2024-12-02 |website=openai.com |language=en-US}}</ref> and AIVA<ref>{{Cite web |title=AIVA, the AI Music Generation Assistant |url=https://www.aiva.ai/ |access-date=2024-12-02 |website=www.aiva.ai |language=en}}</ref> exemplify how AI has expanded its creative capabilities across genres, challenging the boundaries of human artistry. == Relevant Legal Disputes == === Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884) === [[File:Oscar Wilde 1882.jpg|thumb|Oscar Wilde No.18 by Napoleon Sarony (1882)]] [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithography Co v. Sarony]] was submitted on December 13, 1883 when Sarony filed a copyright suit against Burrow-Giles when the company had marketed lithographs of Sarony's photograph, Oscar Wilde No.18, without Sarony's permission. Burrow-Giles argued that photographs were neither writings nor a production of an author, and thus did not possess copyright protection. The court determined that even though creating a photograph is "merely mechanical, with no place for novelty, invention, or originality", the photograph Sarony created was his "own original mental conception, to which he gave visible form by posing the said Oscar Wilde in front of the camera, selecting and arranging the costume, draperies, . . . suggesting and evoking the desired expression, and from such . . . representation, made entirely by plaintiff, he produced the picture in suit.'" On March 17, 1884, the court established that photography is a copyrightable medium. Furthermore, this case reinforced that an author of a work is "he to whom anything owes its origin."<ref>Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884)</ref> === Naruto v. Slater, No. 16-15469 (9th Cir. 2018) === [[File:Macaca nigra self-portrait large.jpg|left|thumb|One of the monkey selfies]] Naruto v. Slater, more commonly known as the [[wikipedia:Artificial_intelligence_and_copyright|Monkey Selfie copyright dispute]], began on September 22, 2015. PETA, representing the crested macaque Naruto, sued Slater claiming that because the monkey took its own picture, it was entitled to the copyright. David J. Slater, the photographer, argued that he held the copyright as he engineered the situation that led to the monkey taking its selfie. On April 23, 2018, the court determined that "this monkey - and all animals, since they are not human – [lack] statutory standing under the Copyright Act", reinforcing that non-humans cannot own copyright.<ref>Naruto v. Slater, No. 16-15469 (9th Cir. 2018)</ref> === Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023) === [[File:A Recent Entrance to Paradise.jpg|thumb|A Recent Entrance to Paradise]] Thaler v. Perlmutter emerged after the U.S. Copyright Office denied Dr. Stephen Thaler's copyright application for an AI generated work, "A Recent Entrance to Paradise". The court focused on answering "whether a work generated autonomously by a computer falls under the protection of copyright law upon its creation". Thaler filed a lawsuit, arguing that the copyright of the AI generated work belonged to him as the AI model's creator. He stated that "AI should be ‘acknowledge[d] . . . as an author where it otherwise meets authorship criteria, with any copyright ownership vesting in the AI’s owner.’" The court reviewed the decision of [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithographic Co. v. Sarony]], finding that the author of any AI generated work would be the AI. However, following the decision of [[wikipedia:Artificial_intelligence_and_copyright|Naruto v. Slater]], since AIs are not human, they cannot hold copyright. The case was decided on August 18, 2023, confirming that AIs cannot hold copyright. As such, the work fell under public domain. However, the court explicitly stated that they were not making any decisions on "how much human input is necessary to qualify the user of an AI system as an 'author' of a generated work".<ref>Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023)</ref> The D.C. Circuit unanimously affirmed in March 2025. On March 2, 2026, the Supreme Court denied certiorari, making the ruling final and exhausting Thaler's appeals. ''Thaler'' now stands as binding precedent that AI systems cannot themselves be authors under U.S. copyright law, and that works generated entirely without human creative contribution are ineligible for registration. '''''Allen v. Perlmutter'', No. 24-2665 (WJM) (D. Colo. 2026)''' [[File:Théâtre D’opéra Spatial.png|thumb|''Théâtre D'opéra Spatial'', created by Jason M. Allen using Midjourney, Photoshop, and Gigapixel AI]] ''Allen v. Perlmutter'' picks up where ''Thaler'' left off. In August 2022, Colorado artist Jason Allen used Midjourney to create ''Théâtre D'opéra Spatial'', entering text prompts at least 624 times to specify genre, tone, composition, and style, then refining the chosen output in Photoshop and Gigapixel AI. The image won first place at the Colorado State Fair in September 2022. When Allen applied for copyright registration as the sole human author, the Office offered to register only the portions reflecting his own contributions if he disclaimed the AI-generated material. Allen refused, and after the Review Board issued its final refusal in June 2023, he filed suit in the U.S. District Court for the District of Colorado on September 26, 2024. He moved for summary judgment in August 2025, the Copyright Office cross-moved in January 2026, and Allen filed his reply in February 2026. Allen argues that his iterative prompting and creative selection constitute authorship analogous to the photographer's creative choices that made photography copyrightable under ''Burrow-Giles''. The Copyright Office counters that prompts are ideas, not expression, because Midjourney determines the actual visual output regardless of how detailed the instructions are. The case is now fully briefed before Judge William J. Martínez, with a ruling expected in 2026 that will produce the first judicial standard answering the question ''Thaler'' left open: when does human input in AI-assisted work rise to the level of copyright authorship? === Zarya of the Dawn === [[File:Zarya of the Dawn cover.webp|thumb|Zarya of the Dawn by Kristina Kashtanova]] [[wikipedia:Zarya_of_the_Dawn|Zarya of the Dawn]], a comic book authored by Kristina Kashtanova and illustrated using the AI generator Midjourney sparked a significant copyright dispute in 2022. When Kashtanova applied for copyright of the comic in September 2022, she failed to disclose that the images were generated by Midjourney. The comic was originally granted copyright by the Copyright Office, but after discovering Midjourney's involvement in illustrating the comic, they reviewed their decision. While the Copyright Office agreed that the text and compilation (the arrangement of images and text) were copyrightable, the art was not, as the "process is not controlled by the user because it is not possible to predict what Midjourney will create ahead of time." Although, Kashtanova claimed "she personally edited some of the images created by Midjourney", the Copyright office could not determine "what expression in the image was contributed through her use of Photoshop as opposed to generated by Midjourney" and thus revoked the copyright. <ref>{{Cite web |last=Kasunic |first=Robert J. |date=February 21, 2023 |title=2023.02.21 Zarya of the Dawn Letter |url=https://www.copyright.gov/docs/zarya-of-the-dawn.pdf |url-status=live |access-date=December 9, 2024 |website=Copyright Office (.gov)}}</ref> == Relevant Copyright Chapters == === Chapter 308: The Originality Requirement<ref name=":0">U.S. Copyright Office, Compendium of U.S. Copyright Office Practices § 101 (3d ed. 2021).</ref> === The Originality Requirement has two primary requirements: "The work must be ‘independently created by the author’ and it must possess ‘at least some minimal degree of creativity’" ==== Chapter 308.1 ==== The Copyright Act defines "independent creation" as a work created "without copying from other works." However, "a work may satisfy the independent creation requirement ‘even though it closely resembles other works so long as the similarity is fortuitous, not the result of copying.’" ==== Chapter 308.2 ==== In terms of creativity, the Copyright Act states that "‘the requisite level of creativity is extremely low.’ Even a ‘slight amount’ of creative expression will suffice.’" ==== Works That Do Not Satisfy the Originality Requirement ==== 313.4(A): Mere Copies 313.4(K): Mere Variations of Colorings === Chapter 306: The Human Authorship Requirement<ref name=":0" /> === The Human Authorship Requirement states that only humans may own a copyright. "The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being." ==== Chapter 313.2 ==== The chapter states that "the U.S. Copyright Office will not register works produced by nature, animals, or plants." Furthermore, "the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author." ==== Works That Lack Human Authorship ==== * A photograph taken by a monkey. * A mural painted by an elephant. * A claim based on the appearance of actual animal skin. * A claim based on driftwood that has been shaped and smoothed by the ocean. * A claim based on cut marks, defects, and other qualities found in natural stone. * An application for a song naming the Holy Spirit as the author of the work. === Chapter 507.1: Derivate Works<ref name=":0" /> === As AI generated works are considered to be authored by the AI, and thus public domain, attempts to edit and then copyright the works would most likely fall under derivative works. The Copyright Act defines a derivative work as "a work based upon one or more preexisting works, such as a . . . art reproduction . . . or any other form in which a work may be recast, transformed, or adapted." ==== Chapter 311.2 ==== Derivative works follow the same originality requirements as original works. Derivative works may only receive copyright protection "provided that [the work] contains a sufficient amount of original expression, meaning that the derivative work must be independently created and it must possess more than a modicum of creativity" The Copyright Act does reiterate that "[m]iniscule variations do not satisfy this requirement, such as merely changing the size of the preexisting work." == Present Issues == === AI Music === ==== Lack of Creativity ==== In 2023, an anonymous creator known as "Ghostwriter" released Heart on My Sleeve, featuring AI-generated vocals mimicking Drake and The Weeknd. The song went viral, drawing millions of streams before being removed for copyright infringement. Universal Music Group argued that the AI-generated track exploited the artists’ likenesses without consent, raising ethical and legal concerns<ref>{{Cite web |last=Reed |first=Rachel |title=AI created a song mimicking the work of Drake and The Weeknd. What does that mean for copyright law? |url=https://hls.harvard.edu/today/ai-created-a-song-mimicking-the-work-of-drake-and-the-weeknd-what-does-that-mean-for-copyright-law/ |access-date=2024-12-02 |website=Harvard Law School |language=en-us}}</ref>. This case highlights AI’s ability to imitate human creativity so convincingly that it blurs the line between originality and replication. Although the creator faced no legal repercussions, the controversy underscored the need for clearer regulations on AI-generated content. * AI doesn’t create entirely new works; it amplifies patterns derived from training data. While it can replicate styles, it lacks the emotional depth and intentionality of human artistry. * Tools like MuseNet and Suno allow anyone to compose music in minutes, potentially devaluing human creativity by making artistic production instantaneous and impersonal. ==== Suno and Udio ==== The most current case reflecting the debate regarding the originality of AI music is in the RIAA vs. Suno and RIAA vs. Udio. The RIAA, or the Recording Industry Association of America, is a trade organization that represents many record labels, including Sony Music Group, Universal Music Group, and Warner Music Group (colloquially known as "the big Three" in the industry as they own up to 85% of market share). In June 2024, the RIAA placed a copyright infringement lawsuit on Suno and Udio (two generative AI music startup companies). They had three main goals with this lawsuit: <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html#:~:text=The%20lawsuits%20make%20three%20specific,to%20nine%20figures%20or%20more. |access-date=2024-12-10 |website=Vulture |language=en}}</ref> # To have these companies admit their models use copyrighted music. # Immediately stop training their AI models using this copyrighted music. # Seek damages up to $150,000 per song used in the models. When first discussing the lawsuit with the press, Chairman and CEO of RIAA, Mitch Glazier, stated: "The music community has embraced AI and we are already partnering and collaborating with responsible developers to build sustainable AI tools centered on human creativity '''that put artists and songwriters in charge''', but we can only succeed if developers are willing to work together with us. Unlicensed services like Suno and Udio that '''claim it's 'fair' to copy an artist's life's work and exploit it for their own profit without consent or pay''' set back the promise of genuinely innovative AI for us all."<ref>{{Cite web |last=Connelly |first=Rose |date=2024-06-24 |title=Record Companies Bring Landmark Cases for Responsible AI Against Suno and Udio in Boston and New York Federal Courts, Respectively |url=https://www.riaa.com/record-companies-bring-landmark-cases-for-responsible-ai-againstsuno-and-udio-in-boston-and-new-york-federal-courts-respectively/ |access-date=2024-12-10 |website=RIAA |language=en-US}}</ref> The RIAA hopes to reflect that the inherent moral value of this statement for pursuing this lawsuit is protecting artists' work and fair pay. However, in any of RIAA's arguments, the percentage of and how the money collected from damages will be distributed to the artists of each respective record label must be clarified. Suno responded to the copyright lawsuit, "What the major record labels really don't want is competition." While this calls to question the actual motive of the lawsuit and whether the benefactors will include artists, the results of this lawsuit are pertinent as they will set further precedents in how copyright pertains to AI overall. Initially, in response to the lawsuit, Udio claimed "fair use," which is primarily used for academic or journalistic purposes. However, lawyers dismissed this claim because their training is not used for human-created content. <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html |access-date=2024-12-10 |website=Vulture |language=en}}</ref> As the lawsuit proceeded, both companies admitted to using copyrighted music only as "intermediate copies." They sighted a copyright case from 2021 regarding an AI algorithm's use of copyrighted images to create a search algorithm. In that case, using these "intermediate copies was lawful" because these lower-resolution copies did not satisfy the user's desire to see the full images. However, in Suno and Udio's context, their AI models are not search algorithms but are generative. As the lawsuits progressed into late 2025, the landscape began to shift from purely adversarial to partially collaborative. Major record labels, including Universal Music Group and Warner Music Group, reached settlements with AI companies like Udio and Suno. These agreements introduced a new model centered on licensing and artist consent, allowing musicians to “opt in” to have their work used in training datasets. This marks a significant shift toward a hybrid system where AI developers and record labels may coexist through formal partnerships rather than litigation alone. However, not all disputes have been resolved, as some companies—particularly Sony Music Group—continue to pursue legal action, signaling that consensus across the industry remains incomplete. As of 2026 the progress of the three goals of the lawsuit is as follows: * To have these companies admit their models use copyrighted music. ** The Sudo and Udio never outright admitted they were using copyrighted material, but instead shifted the focus of the lawsuit to whether or not using copyrighted material was legal in the first place. * Immediately stop training their AI models using this copyrighted music. ** The AI models are no longer being trained on the music illegally but this is due to the record labels making deals so that the Sudo and Udio could continue what they were doing but now legally.<ref>{{Cite web |date=2026-02-26 |title=AI song generator startups Suno and Udio angered the music industry. Now they're hoping to join it |url=https://www.latimes.com/business/story/2026-02-26/ai-song-generator-startups-suno-udio-angered-music-industry-now-theyre-hoping-to-join-it |access-date=2026-05-04 |website=Los Angeles Times |language=en-US}}</ref> * Seek damages up to $150,000 per song used in the models. ** The settlements and partnership deals were never made public so we can't be sure what exactly happened.  The case is less about a definitive win or loss and more about setting an early precedent for how generative AI and intellectual property will coexist. Moving forward, these outcomes will likely influence future cases involving AI training data, reinforcing the importance of consent, compensation, and human authorship in creative industries. ==== Other AI Music Lawsuits ==== Following this case, different record labels (primarily Universal) have filed a copyright on issues regarding AI music. On October 18, 2023, several record labels, namely Universal, filed a lawsuit alleging that Anthropic's AI chatbot, "Claude," unlawfully copied and disseminated copyrighted works, including lyrics "owned or controlled by the Publishers. On January 31, 2024, the copyright license agreement between Universal Music Group (UMG), the world's largest music company, and TikTok owner ByteDance Ltd. expired without a renewal agreement. TikTok was forced to turn off the reproduction of all audio content from artists belonging to UMG's catalog, including Taylor Swift, Billie Eilish, Romeo Santos, J Balvin, and Imagine Dragons, among many others. During these negotiations, UMG made AI-generated music a sticking point in their TikTok negotiations, and a group of musicians spoke out against AI-generated music. Groups, including the Recording Academy, the Music Workers Alliance, the National Association of Music Publishers, the American Association of Independent Music, and even SAG-AFTRA, have all made statements supporting the lawsuits. ==== Ethical Implications of AI in the Music Industry ==== As is apparent with the growing number of lawsuits directed at AI music companies, advancements in AI bring new possibilities for creativity and efficiency along with critical ethical concerns regarding economic impact, bias, and data harvesting. AI’s role in the music industry is a double-edged sword, offering both opportunities and challenges. On the one hand, AI automates many aspects of music creation and production. Tasks like composition, audio mastering, and even lyric writing can now be performed by AI tools. However, this automation has led to concerns about job displacement. Traditional roles in the industry, such as sound engineers and live musicians, face increasing obsolescence as AI tools become more sophisticated and accessible. However, AI also democratizes music production, enabling independent artists and smaller labels to create high-quality music without needing expensive equipment or studio time. So, while jobs are being lost, new roles are emerging, such as AI music curators and prompt engineers. This demonstrates how technological advancements can create fresh opportunities even as they disrupt existing systems. Another critical issue in the use of AI in music is the presence of bias in the models used to generate content. AI systems are only as good as the data they are trained on, and this dependency can result in significant imbalances. For instance, if an AI model’s training data predominantly features Western music, the system may struggle to generate accurate representations of non-Western genres or cultural styles. Along with racial bias, gender bias in datasets used for AI training can perpetuate existing inequalities in the music industry. If female and non-binary artists are underrepresented in the data, AI-generated music may disproportionately reflect the styles and contributions of male artists. Such biases highlight the need for diverse and inclusive training datasets. Developers must address these issues to ensure that AI tools reflect a broader and more equitable spectrum of musical expression. As discussed previously, the question of how AI systems source their training data has sparked widespread ethical debates. Many AI models, most notably Suno and Udio, are trained using copyrighted music, often without the consent or compensation of the original artists and have received backlash. This practice raises significant concerns about exploitation. Artists invest considerable time and effort into creating music, yet their work can be appropriated by AI systems without acknowledgment or financial remuneration. This mirrors controversies in other areas of AI, such as the exploitation of the unpaid labor of associated with Remotask workers. If creators cannot safeguard their work against unauthorized use by AI systems, the industry risks devaluing artistic contributions in favor of technological efficiency. The music industry is at a crossroads–do we protect the rights of creators, or do we embrace AI-drive efficiency without clear ethical guidelines? === AI in the Video Game Industry === The intersection of visual art, music, voice, and code make the gaming industry a hot spot for AI usage within creative works. AI has existed within gaming for some time in the form of non-playable characters (NPCs), but the modern implementation of AI within gaming specifically sees increased usage of generative tools for creative purposes. ==== Nvidia DLSS 5.0 ==== Nvidia is a prolific graphics card producer with extensive ties to the gaming industry. Originally founded for the purpose of innovating computer gaming<ref>{{Cite web |title=NVIDIA Corporation: History |url=https://www.nvidia.com/en-us/about-nvidia/corporate-timeline/ |access-date=2026-05-04 |website=NVIDIA |language=en-us}}</ref>, they have since leveraged their graphics processing unit (GPU) technology for AI usage extensively, while also seeking to implement AI within their gaming technologies. Deep Learning Super Sampling (DLSS) is a technology developed by Nvidia to use real-time deep learning AI to upscale video game rendering. The initial versions of DLSS were employed by running games at a lower native resolution, then using AI to upscale to a higher resolution based on the picture generated by the GPU<ref>{{Cite web |last=Martindale |first=Jon |date=2020-02-14 |title=Nvidia RTX DLSS: everything you need to know |url=https://www.digitaltrends.com/computing/everything-you-need-to-know-about-nvidias-rtx-dlss-technology/ |access-date=2026-05-04 |website=Digital Trends |language=en-us}}</ref>; this implementation did not use AI to directly modify any of the actual contents of games themselves. DLSS 5.0, however, made use of generative AI to attempt to directly enhance the visual content of games. While the exact details of the implementation have yet to be released as of May 2026, the technology appears to generate new frames from prior training data, using the existing content of a game as the base. This introduces elements of the rendering which may not have been present in the original developer's vision, and poses issues related to artistic vision: Since the AI is able to directly add new content and textures, concerns are raised about whether a game is still the same piece of art/media. ==== AI Voice Acting and Other Content ==== AI usage in gaming development can be difficult to discern, leading to the spread of many rumors and allegations of use in voice acting, dialogue generation, textures, among others. Games such as The Finals and Arc Raiders have been accused of using AI tools to generate voice lines, which many perceive to be of lower quality than those generated by human counterparts. For The Finals in particular, the developers at Embark Studios stated that they used AI to extend voice lines created by real voice actors<ref>{{Cite web |last=Notis |first=Ari |date=2025-10-31 |title=Arc Raiders' use of AI voices is The Finals controversy all over again |url=https://www.polygon.com/arc-raiders-ai-voices-the-finals-embark-studios/ |access-date=2026-05-04 |website=Polygon.com |language=en}}</ref>. This can be problematic with respect to intellectual property rights, say for instance a development studio, unbeknown to a voice actor, is using said actor's voice as a baseline for AI generated quips and content. == Reception == === Music === ==== Students ==== While students seem to find AI music fascinating, they emphasize that AI music lacks the emotional depth found in human compositions. They explain that human compositions are capable of conveying authentic human experiences and feelings, which AI cannot replicate. ''Quotes are pulled directly from a New York Times article''<ref>{{Cite web |last=The Learning Network |first= |date=May 11, 2023 |title=What Students Are Saying About A.I.-Generated Music |url=https://www.nytimes.com/2023/05/11/learning/what-students-are-saying-about-ai-generated-music.html |url-status=live |access-date=December 9, 2024 |website=The New York Times}}</ref>: "Human singers have the ability to convey a wide range of emotions and add their own unique style to their music. They have the creativity and experience to interpret lyrics and to give them their own style. Music made with A.I. may be good, but it will never be the same as music sung by a good pop star. While A.I. can be a helpful tool for composers and producers to experiment with new sounds and styles, it will never replace the raw talent and artistry of human vocalists." - ''Sergi, Sant Gregori'' "In my personal opinion, the main allure of music lies in the emotional connection that it establishes with the listener. It’s not only about the melody or the lyrics, but also the sentiments and reminiscences that the music evokes. If I became aware that a song was completely generated by an artificial intelligence system, I would feel intrigued to listen to it, driven by my fascination with the underlying technology. Nevertheless, I might not feel as connected to the song on an emotional level as I would if it was composed by a human artist." - ''Aleena, Julia R. Masterman, Philadelphia, PA'' "Even if the lyrics emulate a real pop star’s lyrics, whether it talks about heartbreak, love, or family, it would never have the same impact like one created by a real pop star because the listeners know it is all just to sound good and appeal to the listeners. It would have nothing to do with the artist themselves … Music is supposed to be relatable. When I listen to music, I like to listen to artists I know have gone through similar things or have the same feelings as me." - ''Sophia, Hinsdale Central High School'' ==== Composers ==== The evolution of composers attitudes towards AI music is reflected in [https://www.youtube.com/channel/UCelK8dBKY0Xs5oRI6sJf7aA Daniel James], a composer on YouTube, perspective over time. While he acknowledged that AI generated music was inevitable, it would never allow a total newbie to suddenly become a professional.<ref>{{Citation |last=Daniel James |title=TADay #4 - Composer Talk Radio - Is AI a threat or is it the future of composition. |date=2019-06-29 |url=https://www.youtube.com/watch?v=cqJWI4HF1CY |access-date=2024-12-09}}</ref> He suggested if AI became proficient in replicating professionals, composers would need to come up with their own style away from the AI. James had a positive view on AIs potential as a tool, comparing it to a ghost composer that could handle much of the monotonous work that an assistant might do. He predicted that AI would primarily impact the lower-skilled composers, widening the gap between low and high skilled composers. By 2023, James' perspective has become more nuanced.<ref>{{Citation |last=Daniel James |title=AI In The Music Industry - Tool Or Threat - A Professional Composers View. |date=2022-12-11 |url=https://www.youtube.com/watch?v=fOL32kRuUI0 |access-date=2024-12-09}}</ref> He discussed the limitations of AI, explaining that it can't really create something new, and can only make variations. While acknowledging AIs capability to blend styles, like reimagining Beethoven as hip-hop, he emphasizes that music exists within the context of the time it is created. James considers that although AI can accurately replicate music, it still struggles with emotional nuance. He also notes that skilled AI use would still require musical expertise to properly guide the AI. James also discusses the significant impacts AI might have. Formulaic music like EDM and trailer music seem particularly vulnerable to AI as there is a "correct" way to write those styles of music. He also believes that AI music will severely damage the lower end of the creative field. He worries that if newer generations of artists are trained to use AI, they may forget how to develop their own original styles, stunting their growth. The broader composer community has similar views. On Reddit, many composers advocate for limiting AI's role to reference and placeholder work that bridge the gap between the client and the composer.<ref>{{Cite web |last=ArgamaWitch |date=2024-04-15 |title=Composers that take commissions, what's your thoughts on AI music being used as reference? |url=https://www.reddit.com/r/composer/comments/1c4vrvr/composers_that_take_commissions_whats_your/?rdt=57624 |access-date=2024-12-09 |website=r/composer}}</ref> The consensus among professional composers, including James, is that AI needs much better regulation. They argue for protecting artists' unique, copyrightable styles from unauthorized AI replication and advocate that AI companies should compensate the artists whos works train the AI models. These composers are working to convince the Copyright Office that training AI on artists' work without compensation devalues artists. === Gaming === ==== Players ==== Players of video games tend towards a negative reception of generative AI usage in game development. Games will often receive negative reviews or discussions on forum pages when AI use is apparent: for instance, Steam (a platform used to distribute and discuss games) has entire community-driven pages dedicated towards identifying and shaming AI employment in games<ref>{{Cite web |title=Steam Curator: Games That Use AI Generation |url=https://store.steampowered.com/curator/45944619-Games-That-Use-AI-Generation/ |access-date=2026-05-04 |website=store.steampowered.com |language=en}}</ref>. == References == <references /> {{BookCat}} rfg6zkmmpxqnj133h4x7shtafut44il 4634153 4634122 2026-05-04T18:42:01Z PhilipNaveen 3578471 Added a description on AI video animation and how it's used in adverts and production movies. 4634153 wikitext text/x-wiki == Overview == === Introduction === Artificial intelligence (AI) is revolutionizing creative industries, such as the music industry, by redefining how creative works are composed, performed, and consumed. What began as theoretical musings by pioneers like Alan Turing has grown into a field with sophisticated neural networks capable of composing full-length songs, for example. However, this evolution raises pressing questions about originality, ownership, and the future of human creativity. === History of AI and Music === ====== Theoretical Foundations: 1950s-1960s ====== The concept of AI-generated music originated with Alan Turing, who theorized in the 1950s that machines could emulate human cognitive processes, including music composition. His ideas laid the groundwork for computational creativity.<ref>{{Citation |last=Copeland |first=B. Jack |title=Turing and the History of Computer Music |date=2017 |url=https://link.springer.com/chapter/10.1007/978-3-319-53280-6_8 |work=Philosophical Explorations of the Legacy of Alan Turing: Turing 100 |pages=189–218 |editor-last=Floyd |editor-first=Juliet |access-date=2024-12-02 |place=Cham |publisher=Springer International Publishing |language=en |doi=10.1007/978-3-319-53280-6_8 |isbn=978-3-319-53280-6 |last2=Long |first2=Jason |editor2-last=Bokulich |editor2-first=Alisa}}</ref> In 1957, Lejaren Hiller and Leonard Isaacson at the University of Illinois created the Illiac Suite<ref>{{Cite web |title=ILLIAC Suite – Illinois Distributed Museum |url=https://distributedmuseum.illinois.edu/exhibit/illiac-suite/ |access-date=2024-12-02 |website=distributedmuseum.illinois.edu}}</ref>. Using the ILLIAC I computer, they developed an algorithmic process to compose a string quartet, marking one of the first successful instances of computer-generated music. It demonstrated the potential of computers to collaborate in creative endeavors, sparking decades of research into AI's role in music. ====== Rule-Based Systems: 1970s-1980s ====== During the 1970s and 1980s, AI systems advanced with rule-based algorithms that mimicked specific musical styles. David Cope’s Experiments in Musical Intelligence<ref>{{Cite web |last=tluong |date=2015-04-29 |title=Algorithmic Music – David Cope and EMI |url=https://computerhistory.org/blog/algorithmic-music-david-cope-and-emi/ |access-date=2024-12-02 |website=CHM |language=en}}</ref> (EMI) exemplified this approach by analyzing existing compositions and generating new ones in the style of Bach and Mozart. However, EMI heavily relied on predefined human rules, highlighting the imitative, rather than generative, nature of early AI. A significant technological leap came in 1983 with the introduction of MIDI<ref>{{Citation |title=MIDI |date=2024-11-25 |url=https://en.wikipedia.org/wiki/MIDI |work=Wikipedia |access-date=2024-12-02 |language=en}}</ref> (Musical Instrument Digital Interface). MIDI standardized communication between computers and electronic instruments, enabling precise control of musical elements and facilitating data collection for future AI systems. ====== Machine Learning: 1990s-2000s ====== AI music systems transitioned from rule-based models to data-driven techniques in the 1990s. Machine learning algorithms enabled pattern recognition and predictive modeling, allowing AI to generate more complex and varied compositions. Projects like Accenture’s Symphonologie<ref>{{Cite web |title=Accenture {{!}} Symphonologie |url=https://www.oneclub.org/awards/theoneshow/-award/25489/symphonologie/ |access-date=2024-12-02 |website=www.oneclub.org |language=en}}</ref> showcased AI as a collaborative tool, blending human and machine creativity. ====== Neural Networks: 2010s-Present ====== The rise of deep learning revolutionized AI in music. Neural networks, trained on vast datasets, now compose intricate, multi-instrumental pieces in seconds. Tools like OpenAI’s MuseNet<ref>{{Cite web |title=MuseNet |url=https://openai.com/index/musenet/ |access-date=2024-12-02 |website=openai.com |language=en-US}}</ref> and AIVA<ref>{{Cite web |title=AIVA, the AI Music Generation Assistant |url=https://www.aiva.ai/ |access-date=2024-12-02 |website=www.aiva.ai |language=en}}</ref> exemplify how AI has expanded its creative capabilities across genres, challenging the boundaries of human artistry. == Relevant Legal Disputes == === Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884) === [[File:Oscar Wilde 1882.jpg|thumb|Oscar Wilde No.18 by Napoleon Sarony (1882)]] [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithography Co v. Sarony]] was submitted on December 13, 1883 when Sarony filed a copyright suit against Burrow-Giles when the company had marketed lithographs of Sarony's photograph, Oscar Wilde No.18, without Sarony's permission. Burrow-Giles argued that photographs were neither writings nor a production of an author, and thus did not possess copyright protection. The court determined that even though creating a photograph is "merely mechanical, with no place for novelty, invention, or originality", the photograph Sarony created was his "own original mental conception, to which he gave visible form by posing the said Oscar Wilde in front of the camera, selecting and arranging the costume, draperies, . . . suggesting and evoking the desired expression, and from such . . . representation, made entirely by plaintiff, he produced the picture in suit.'" On March 17, 1884, the court established that photography is a copyrightable medium. Furthermore, this case reinforced that an author of a work is "he to whom anything owes its origin."<ref>Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884)</ref> === Naruto v. Slater, No. 16-15469 (9th Cir. 2018) === [[File:Macaca nigra self-portrait large.jpg|left|thumb|One of the monkey selfies]] Naruto v. Slater, more commonly known as the [[wikipedia:Artificial_intelligence_and_copyright|Monkey Selfie copyright dispute]], began on September 22, 2015. PETA, representing the crested macaque Naruto, sued Slater claiming that because the monkey took its own picture, it was entitled to the copyright. David J. Slater, the photographer, argued that he held the copyright as he engineered the situation that led to the monkey taking its selfie. On April 23, 2018, the court determined that "this monkey - and all animals, since they are not human – [lack] statutory standing under the Copyright Act", reinforcing that non-humans cannot own copyright.<ref>Naruto v. Slater, No. 16-15469 (9th Cir. 2018)</ref> === Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023) === [[File:A Recent Entrance to Paradise.jpg|thumb|A Recent Entrance to Paradise]] Thaler v. Perlmutter emerged after the U.S. Copyright Office denied Dr. Stephen Thaler's copyright application for an AI generated work, "A Recent Entrance to Paradise". The court focused on answering "whether a work generated autonomously by a computer falls under the protection of copyright law upon its creation". Thaler filed a lawsuit, arguing that the copyright of the AI generated work belonged to him as the AI model's creator. He stated that "AI should be ‘acknowledge[d] . . . as an author where it otherwise meets authorship criteria, with any copyright ownership vesting in the AI’s owner.’" The court reviewed the decision of [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithographic Co. v. Sarony]], finding that the author of any AI generated work would be the AI. However, following the decision of [[wikipedia:Artificial_intelligence_and_copyright|Naruto v. Slater]], since AIs are not human, they cannot hold copyright. The case was decided on August 18, 2023, confirming that AIs cannot hold copyright. As such, the work fell under public domain. However, the court explicitly stated that they were not making any decisions on "how much human input is necessary to qualify the user of an AI system as an 'author' of a generated work".<ref>Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023)</ref> The D.C. Circuit unanimously affirmed in March 2025. On March 2, 2026, the Supreme Court denied certiorari, making the ruling final and exhausting Thaler's appeals. ''Thaler'' now stands as binding precedent that AI systems cannot themselves be authors under U.S. copyright law, and that works generated entirely without human creative contribution are ineligible for registration. '''''Allen v. Perlmutter'', No. 24-2665 (WJM) (D. Colo. 2026)''' [[File:Théâtre D’opéra Spatial.png|thumb|''Théâtre D'opéra Spatial'', created by Jason M. Allen using Midjourney, Photoshop, and Gigapixel AI]] ''Allen v. Perlmutter'' picks up where ''Thaler'' left off. In August 2022, Colorado artist Jason Allen used Midjourney to create ''Théâtre D'opéra Spatial'', entering text prompts at least 624 times to specify genre, tone, composition, and style, then refining the chosen output in Photoshop and Gigapixel AI. The image won first place at the Colorado State Fair in September 2022. When Allen applied for copyright registration as the sole human author, the Office offered to register only the portions reflecting his own contributions if he disclaimed the AI-generated material. Allen refused, and after the Review Board issued its final refusal in June 2023, he filed suit in the U.S. District Court for the District of Colorado on September 26, 2024. He moved for summary judgment in August 2025, the Copyright Office cross-moved in January 2026, and Allen filed his reply in February 2026. Allen argues that his iterative prompting and creative selection constitute authorship analogous to the photographer's creative choices that made photography copyrightable under ''Burrow-Giles''. The Copyright Office counters that prompts are ideas, not expression, because Midjourney determines the actual visual output regardless of how detailed the instructions are. The case is now fully briefed before Judge William J. Martínez, with a ruling expected in 2026 that will produce the first judicial standard answering the question ''Thaler'' left open: when does human input in AI-assisted work rise to the level of copyright authorship? === Zarya of the Dawn === [[File:Zarya of the Dawn cover.webp|thumb|Zarya of the Dawn by Kristina Kashtanova]] [[wikipedia:Zarya_of_the_Dawn|Zarya of the Dawn]], a comic book authored by Kristina Kashtanova and illustrated using the AI generator Midjourney sparked a significant copyright dispute in 2022. When Kashtanova applied for copyright of the comic in September 2022, she failed to disclose that the images were generated by Midjourney. The comic was originally granted copyright by the Copyright Office, but after discovering Midjourney's involvement in illustrating the comic, they reviewed their decision. While the Copyright Office agreed that the text and compilation (the arrangement of images and text) were copyrightable, the art was not, as the "process is not controlled by the user because it is not possible to predict what Midjourney will create ahead of time." Although, Kashtanova claimed "she personally edited some of the images created by Midjourney", the Copyright office could not determine "what expression in the image was contributed through her use of Photoshop as opposed to generated by Midjourney" and thus revoked the copyright. <ref>{{Cite web |last=Kasunic |first=Robert J. |date=February 21, 2023 |title=2023.02.21 Zarya of the Dawn Letter |url=https://www.copyright.gov/docs/zarya-of-the-dawn.pdf |url-status=live |access-date=December 9, 2024 |website=Copyright Office (.gov)}}</ref> == Relevant Copyright Chapters == === Chapter 308: The Originality Requirement<ref name=":0">U.S. Copyright Office, Compendium of U.S. Copyright Office Practices § 101 (3d ed. 2021).</ref> === The Originality Requirement has two primary requirements: "The work must be ‘independently created by the author’ and it must possess ‘at least some minimal degree of creativity’" ==== Chapter 308.1 ==== The Copyright Act defines "independent creation" as a work created "without copying from other works." However, "a work may satisfy the independent creation requirement ‘even though it closely resembles other works so long as the similarity is fortuitous, not the result of copying.’" ==== Chapter 308.2 ==== In terms of creativity, the Copyright Act states that "‘the requisite level of creativity is extremely low.’ Even a ‘slight amount’ of creative expression will suffice.’" ==== Works That Do Not Satisfy the Originality Requirement ==== 313.4(A): Mere Copies 313.4(K): Mere Variations of Colorings === Chapter 306: The Human Authorship Requirement<ref name=":0" /> === The Human Authorship Requirement states that only humans may own a copyright. "The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being." ==== Chapter 313.2 ==== The chapter states that "the U.S. Copyright Office will not register works produced by nature, animals, or plants." Furthermore, "the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author." ==== Works That Lack Human Authorship ==== * A photograph taken by a monkey. * A mural painted by an elephant. * A claim based on the appearance of actual animal skin. * A claim based on driftwood that has been shaped and smoothed by the ocean. * A claim based on cut marks, defects, and other qualities found in natural stone. * An application for a song naming the Holy Spirit as the author of the work. === Chapter 507.1: Derivate Works<ref name=":0" /> === As AI generated works are considered to be authored by the AI, and thus public domain, attempts to edit and then copyright the works would most likely fall under derivative works. The Copyright Act defines a derivative work as "a work based upon one or more preexisting works, such as a . . . art reproduction . . . or any other form in which a work may be recast, transformed, or adapted." ==== Chapter 311.2 ==== Derivative works follow the same originality requirements as original works. Derivative works may only receive copyright protection "provided that [the work] contains a sufficient amount of original expression, meaning that the derivative work must be independently created and it must possess more than a modicum of creativity" The Copyright Act does reiterate that "[m]iniscule variations do not satisfy this requirement, such as merely changing the size of the preexisting work." == Present Issues == === AI Music === ==== Lack of Creativity ==== In 2023, an anonymous creator known as "Ghostwriter" released Heart on My Sleeve, featuring AI-generated vocals mimicking Drake and The Weeknd. The song went viral, drawing millions of streams before being removed for copyright infringement. Universal Music Group argued that the AI-generated track exploited the artists’ likenesses without consent, raising ethical and legal concerns<ref>{{Cite web |last=Reed |first=Rachel |title=AI created a song mimicking the work of Drake and The Weeknd. What does that mean for copyright law? |url=https://hls.harvard.edu/today/ai-created-a-song-mimicking-the-work-of-drake-and-the-weeknd-what-does-that-mean-for-copyright-law/ |access-date=2024-12-02 |website=Harvard Law School |language=en-us}}</ref>. This case highlights AI’s ability to imitate human creativity so convincingly that it blurs the line between originality and replication. Although the creator faced no legal repercussions, the controversy underscored the need for clearer regulations on AI-generated content. * AI doesn’t create entirely new works; it amplifies patterns derived from training data. While it can replicate styles, it lacks the emotional depth and intentionality of human artistry. * Tools like MuseNet and Suno allow anyone to compose music in minutes, potentially devaluing human creativity by making artistic production instantaneous and impersonal. ==== Suno and Udio ==== The most current case reflecting the debate regarding the originality of AI music is in the RIAA vs. Suno and RIAA vs. Udio. The RIAA, or the Recording Industry Association of America, is a trade organization that represents many record labels, including Sony Music Group, Universal Music Group, and Warner Music Group (colloquially known as "the big Three" in the industry as they own up to 85% of market share). In June 2024, the RIAA placed a copyright infringement lawsuit on Suno and Udio (two generative AI music startup companies). They had three main goals with this lawsuit: <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html#:~:text=The%20lawsuits%20make%20three%20specific,to%20nine%20figures%20or%20more. |access-date=2024-12-10 |website=Vulture |language=en}}</ref> # To have these companies admit their models use copyrighted music. # Immediately stop training their AI models using this copyrighted music. # Seek damages up to $150,000 per song used in the models. When first discussing the lawsuit with the press, Chairman and CEO of RIAA, Mitch Glazier, stated: "The music community has embraced AI and we are already partnering and collaborating with responsible developers to build sustainable AI tools centered on human creativity '''that put artists and songwriters in charge''', but we can only succeed if developers are willing to work together with us. Unlicensed services like Suno and Udio that '''claim it's 'fair' to copy an artist's life's work and exploit it for their own profit without consent or pay''' set back the promise of genuinely innovative AI for us all."<ref>{{Cite web |last=Connelly |first=Rose |date=2024-06-24 |title=Record Companies Bring Landmark Cases for Responsible AI Against Suno and Udio in Boston and New York Federal Courts, Respectively |url=https://www.riaa.com/record-companies-bring-landmark-cases-for-responsible-ai-againstsuno-and-udio-in-boston-and-new-york-federal-courts-respectively/ |access-date=2024-12-10 |website=RIAA |language=en-US}}</ref> The RIAA hopes to reflect that the inherent moral value of this statement for pursuing this lawsuit is protecting artists' work and fair pay. However, in any of RIAA's arguments, the percentage of and how the money collected from damages will be distributed to the artists of each respective record label must be clarified. Suno responded to the copyright lawsuit, "What the major record labels really don't want is competition." While this calls to question the actual motive of the lawsuit and whether the benefactors will include artists, the results of this lawsuit are pertinent as they will set further precedents in how copyright pertains to AI overall. Initially, in response to the lawsuit, Udio claimed "fair use," which is primarily used for academic or journalistic purposes. However, lawyers dismissed this claim because their training is not used for human-created content. <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html |access-date=2024-12-10 |website=Vulture |language=en}}</ref> As the lawsuit proceeded, both companies admitted to using copyrighted music only as "intermediate copies." They sighted a copyright case from 2021 regarding an AI algorithm's use of copyrighted images to create a search algorithm. In that case, using these "intermediate copies was lawful" because these lower-resolution copies did not satisfy the user's desire to see the full images. However, in Suno and Udio's context, their AI models are not search algorithms but are generative. As the lawsuits progressed into late 2025, the landscape began to shift from purely adversarial to partially collaborative. Major record labels, including Universal Music Group and Warner Music Group, reached settlements with AI companies like Udio and Suno. These agreements introduced a new model centered on licensing and artist consent, allowing musicians to “opt in” to have their work used in training datasets. This marks a significant shift toward a hybrid system where AI developers and record labels may coexist through formal partnerships rather than litigation alone. However, not all disputes have been resolved, as some companies—particularly Sony Music Group—continue to pursue legal action, signaling that consensus across the industry remains incomplete. As of 2026 the progress of the three goals of the lawsuit is as follows: * To have these companies admit their models use copyrighted music. ** The Sudo and Udio never outright admitted they were using copyrighted material, but instead shifted the focus of the lawsuit to whether or not using copyrighted material was legal in the first place. * Immediately stop training their AI models using this copyrighted music. ** The AI models are no longer being trained on the music illegally but this is due to the record labels making deals so that the Sudo and Udio could continue what they were doing but now legally.<ref>{{Cite web |date=2026-02-26 |title=AI song generator startups Suno and Udio angered the music industry. Now they're hoping to join it |url=https://www.latimes.com/business/story/2026-02-26/ai-song-generator-startups-suno-udio-angered-music-industry-now-theyre-hoping-to-join-it |access-date=2026-05-04 |website=Los Angeles Times |language=en-US}}</ref> * Seek damages up to $150,000 per song used in the models. ** The settlements and partnership deals were never made public so we can't be sure what exactly happened.  The case is less about a definitive win or loss and more about setting an early precedent for how generative AI and intellectual property will coexist. Moving forward, these outcomes will likely influence future cases involving AI training data, reinforcing the importance of consent, compensation, and human authorship in creative industries. === AI Video Animation === AI video generation, though more accurately video animation, became visible to the public during the 2026 Super Bowl, when many brands used and advertised generative AI to create visuals rather than VFX. Svedka actually used generative AI to create their entire ad. The general reception to Svedka's ad, as well as ones created by Kalshi and Coca Cola was generally negative, stating they were cheap and uncanny <ref>{{Cite web |last=Monllos |first=ByKristina |title=About that AI Bowl: Reception of AI ads ‘sharply negative’ as brand beefs, misinformation brewed |url=https://www.marketingbrew.com/stories/2026/02/11/ai-bowl-ad-reception-openai-anthropic-feud |access-date=2026-05-04 |website=Marketing Brew |language=en-us}}</ref>. In Hollywood, the usage of AI video animation is more subtle, but it has existed for longer. Movies will not have entirely AI generated scenes by in large. However, studios use AI video tools for previsualization, which means generating rough versions of scenes before shooting them in real life. Another use is concept iteration. Instead of waiting days for artists, teams can generate dozens of variations of a scene in minutes. AI is mostly used for background generation, de-aging real actors, and filling minor gaps in VFX shots. Systems like Sora showed the ability to generate clips up to about a half minute long with simulated camera motion, depth, and basic physics. But these clips often break under further constraints and scrutiny. Objects drift, characters change appearance mid shot, and motion is not physically consistent, which makes it largely impractical to produce any meaningfully long scenes. However, companies such as Netflix and Amazon have started partnering with Runway to trained specialized franchise video animation models on their proprietary content. <ref>{{Cite web |last=Metz |first=Rachel |date=2025-07-22 |title=Netflix using startup Runway AI’s video tools for production |url=https://www.latimes.com/business/story/2025-07-22/netflix-using-startup-runway-ais-video-tools-for-production |access-date=2026-05-04 |website=Los Angeles Times |language=en-US}}</ref> Steven Spielberg accepts the use of AI, but drew a hard line in that it cannot replace a human creative. He said AI can help with planning and visual development but should not replace real actors and artists <ref>{{Cite web |last=Perez |first=Sarah |date=2026-03-13 |title=Steven Spielberg says he's 'never used AI' in any of his films |url=https://techcrunch.com/2026/03/13/steven-spielberg-says-hes-never-used-ai-in-any-of-his-films/ |access-date=2026-05-04 |website=TechCrunch |language=en-US}}</ref>. George Lucas has argued that tools like this are inevitable and will lower costs for independent creators. AI was used to create a deep faked face of a young Mark Hamill as Luke Skywalker in the Boba Fett series, meaning Lucasfilm under Disney had been using AI as early as 2021 <ref>{{Cite web |last=King |first=Jack |date=2022-02-10 |title=Deepfake Luke Skywalker is another step down a ghoulish CGI path |url=https://www.gq-magazine.co.uk/culture/article/boba-fett-luke-skywalker |access-date=2026-05-04 |website=British GQ |language=en-GB}}</ref>. Paul Schrader warned that full AI-generated films are close and could remove the need for many creative roles. His concern is not just quality but control over authorship and credit, which in part is shared by his audience. Sora itself ran into some concrete problems. It was expensive to run because each generated video required expensive GPU clusters for diffusion sampling across hundreds of frames. Companies like The Walt Disney Company were cautious about allowing their content or likenesses to be replicated by such systems. Walt Disney entered into a contract with OpenAI that allowed them to generate their characters in Sora clips. Newer systems like Veo improved temporal consistency by modeling motion across frames instead of generating each frame independently. Veo also added better camera controls, longer clip generation, and tighter integration with editing workflows <ref>{{Cite web |last=Abitbul |first=Hanna |date=2025-06-25 |title=Veo 3 vs. Sora by OpenAI: 2026 Comparison |url=https://www.powtoon.com/blog/veo-3-vs-sora/ |access-date=2026-05-04 |website=Powtoon Blog |language=en-US}}</ref>. As of April 26th 2026, Sora was discontinued by OpenAI despite Disney already being involved <ref>{{Cite web |title=What to know about the Sora discontinuation |url=https://help.openai.com/en/articles/20001152-what-to-know-about-the-sora-discontinuation |access-date=2026-05-04 |website=OpenAI Help Center |language=en-US}}</ref>. ==== Other AI Music Lawsuits ==== Following this case, different record labels (primarily Universal) have filed a copyright on issues regarding AI music. On October 18, 2023, several record labels, namely Universal, filed a lawsuit alleging that Anthropic's AI chatbot, "Claude," unlawfully copied and disseminated copyrighted works, including lyrics "owned or controlled by the Publishers. On January 31, 2024, the copyright license agreement between Universal Music Group (UMG), the world's largest music company, and TikTok owner ByteDance Ltd. expired without a renewal agreement. TikTok was forced to turn off the reproduction of all audio content from artists belonging to UMG's catalog, including Taylor Swift, Billie Eilish, Romeo Santos, J Balvin, and Imagine Dragons, among many others. During these negotiations, UMG made AI-generated music a sticking point in their TikTok negotiations, and a group of musicians spoke out against AI-generated music. Groups, including the Recording Academy, the Music Workers Alliance, the National Association of Music Publishers, the American Association of Independent Music, and even SAG-AFTRA, have all made statements supporting the lawsuits. ==== Ethical Implications of AI in the Music Industry ==== As is apparent with the growing number of lawsuits directed at AI music companies, advancements in AI bring new possibilities for creativity and efficiency along with critical ethical concerns regarding economic impact, bias, and data harvesting. AI’s role in the music industry is a double-edged sword, offering both opportunities and challenges. On the one hand, AI automates many aspects of music creation and production. Tasks like composition, audio mastering, and even lyric writing can now be performed by AI tools. However, this automation has led to concerns about job displacement. Traditional roles in the industry, such as sound engineers and live musicians, face increasing obsolescence as AI tools become more sophisticated and accessible. However, AI also democratizes music production, enabling independent artists and smaller labels to create high-quality music without needing expensive equipment or studio time. So, while jobs are being lost, new roles are emerging, such as AI music curators and prompt engineers. This demonstrates how technological advancements can create fresh opportunities even as they disrupt existing systems. Another critical issue in the use of AI in music is the presence of bias in the models used to generate content. AI systems are only as good as the data they are trained on, and this dependency can result in significant imbalances. For instance, if an AI model’s training data predominantly features Western music, the system may struggle to generate accurate representations of non-Western genres or cultural styles. Along with racial bias, gender bias in datasets used for AI training can perpetuate existing inequalities in the music industry. If female and non-binary artists are underrepresented in the data, AI-generated music may disproportionately reflect the styles and contributions of male artists. Such biases highlight the need for diverse and inclusive training datasets. Developers must address these issues to ensure that AI tools reflect a broader and more equitable spectrum of musical expression. As discussed previously, the question of how AI systems source their training data has sparked widespread ethical debates. Many AI models, most notably Suno and Udio, are trained using copyrighted music, often without the consent or compensation of the original artists and have received backlash. This practice raises significant concerns about exploitation. Artists invest considerable time and effort into creating music, yet their work can be appropriated by AI systems without acknowledgment or financial remuneration. This mirrors controversies in other areas of AI, such as the exploitation of the unpaid labor of associated with Remotask workers. If creators cannot safeguard their work against unauthorized use by AI systems, the industry risks devaluing artistic contributions in favor of technological efficiency. The music industry is at a crossroads–do we protect the rights of creators, or do we embrace AI-drive efficiency without clear ethical guidelines? === AI in the Video Game Industry === The intersection of visual art, music, voice, and code make the gaming industry a hot spot for AI usage within creative works. AI has existed within gaming for some time in the form of non-playable characters (NPCs), but the modern implementation of AI within gaming specifically sees increased usage of generative tools for creative purposes. ==== Nvidia DLSS 5.0 ==== Nvidia is a prolific graphics card producer with extensive ties to the gaming industry. Originally founded for the purpose of innovating computer gaming<ref>{{Cite web |title=NVIDIA Corporation: History |url=https://www.nvidia.com/en-us/about-nvidia/corporate-timeline/ |access-date=2026-05-04 |website=NVIDIA |language=en-us}}</ref>, they have since leveraged their graphics processing unit (GPU) technology for AI usage extensively, while also seeking to implement AI within their gaming technologies. Deep Learning Super Sampling (DLSS) is a technology developed by Nvidia to use real-time deep learning AI to upscale video game rendering. The initial versions of DLSS were employed by running games at a lower native resolution, then using AI to upscale to a higher resolution based on the picture generated by the GPU<ref>{{Cite web |last=Martindale |first=Jon |date=2020-02-14 |title=Nvidia RTX DLSS: everything you need to know |url=https://www.digitaltrends.com/computing/everything-you-need-to-know-about-nvidias-rtx-dlss-technology/ |access-date=2026-05-04 |website=Digital Trends |language=en-us}}</ref>; this implementation did not use AI to directly modify any of the actual contents of games themselves. DLSS 5.0, however, made use of generative AI to attempt to directly enhance the visual content of games. While the exact details of the implementation have yet to be released as of May 2026, the technology appears to generate new frames from prior training data, using the existing content of a game as the base. This introduces elements of the rendering which may not have been present in the original developer's vision, and poses issues related to artistic vision: Since the AI is able to directly add new content and textures, concerns are raised about whether a game is still the same piece of art/media. ==== AI Voice Acting and Other Content ==== AI usage in gaming development can be difficult to discern, leading to the spread of many rumors and allegations of use in voice acting, dialogue generation, textures, among others. Games such as The Finals and Arc Raiders have been accused of using AI tools to generate voice lines, which many perceive to be of lower quality than those generated by human counterparts. For The Finals in particular, the developers at Embark Studios stated that they used AI to extend voice lines created by real voice actors<ref>{{Cite web |last=Notis |first=Ari |date=2025-10-31 |title=Arc Raiders' use of AI voices is The Finals controversy all over again |url=https://www.polygon.com/arc-raiders-ai-voices-the-finals-embark-studios/ |access-date=2026-05-04 |website=Polygon.com |language=en}}</ref>. This can be problematic with respect to intellectual property rights, say for instance a development studio, unbeknown to a voice actor, is using said actor's voice as a baseline for AI generated quips and content. == Reception == === Music === ==== Students ==== While students seem to find AI music fascinating, they emphasize that AI music lacks the emotional depth found in human compositions. They explain that human compositions are capable of conveying authentic human experiences and feelings, which AI cannot replicate. ''Quotes are pulled directly from a New York Times article''<ref>{{Cite web |last=The Learning Network |first= |date=May 11, 2023 |title=What Students Are Saying About A.I.-Generated Music |url=https://www.nytimes.com/2023/05/11/learning/what-students-are-saying-about-ai-generated-music.html |url-status=live |access-date=December 9, 2024 |website=The New York Times}}</ref>: "Human singers have the ability to convey a wide range of emotions and add their own unique style to their music. They have the creativity and experience to interpret lyrics and to give them their own style. Music made with A.I. may be good, but it will never be the same as music sung by a good pop star. While A.I. can be a helpful tool for composers and producers to experiment with new sounds and styles, it will never replace the raw talent and artistry of human vocalists." - ''Sergi, Sant Gregori'' "In my personal opinion, the main allure of music lies in the emotional connection that it establishes with the listener. It’s not only about the melody or the lyrics, but also the sentiments and reminiscences that the music evokes. If I became aware that a song was completely generated by an artificial intelligence system, I would feel intrigued to listen to it, driven by my fascination with the underlying technology. Nevertheless, I might not feel as connected to the song on an emotional level as I would if it was composed by a human artist." - ''Aleena, Julia R. Masterman, Philadelphia, PA'' "Even if the lyrics emulate a real pop star’s lyrics, whether it talks about heartbreak, love, or family, it would never have the same impact like one created by a real pop star because the listeners know it is all just to sound good and appeal to the listeners. It would have nothing to do with the artist themselves … Music is supposed to be relatable. When I listen to music, I like to listen to artists I know have gone through similar things or have the same feelings as me." - ''Sophia, Hinsdale Central High School'' ==== Composers ==== The evolution of composers attitudes towards AI music is reflected in [https://www.youtube.com/channel/UCelK8dBKY0Xs5oRI6sJf7aA Daniel James], a composer on YouTube, perspective over time. While he acknowledged that AI generated music was inevitable, it would never allow a total newbie to suddenly become a professional.<ref>{{Citation |last=Daniel James |title=TADay #4 - Composer Talk Radio - Is AI a threat or is it the future of composition. |date=2019-06-29 |url=https://www.youtube.com/watch?v=cqJWI4HF1CY |access-date=2024-12-09}}</ref> He suggested if AI became proficient in replicating professionals, composers would need to come up with their own style away from the AI. James had a positive view on AIs potential as a tool, comparing it to a ghost composer that could handle much of the monotonous work that an assistant might do. He predicted that AI would primarily impact the lower-skilled composers, widening the gap between low and high skilled composers. By 2023, James' perspective has become more nuanced.<ref>{{Citation |last=Daniel James |title=AI In The Music Industry - Tool Or Threat - A Professional Composers View. |date=2022-12-11 |url=https://www.youtube.com/watch?v=fOL32kRuUI0 |access-date=2024-12-09}}</ref> He discussed the limitations of AI, explaining that it can't really create something new, and can only make variations. While acknowledging AIs capability to blend styles, like reimagining Beethoven as hip-hop, he emphasizes that music exists within the context of the time it is created. James considers that although AI can accurately replicate music, it still struggles with emotional nuance. He also notes that skilled AI use would still require musical expertise to properly guide the AI. James also discusses the significant impacts AI might have. Formulaic music like EDM and trailer music seem particularly vulnerable to AI as there is a "correct" way to write those styles of music. He also believes that AI music will severely damage the lower end of the creative field. He worries that if newer generations of artists are trained to use AI, they may forget how to develop their own original styles, stunting their growth. The broader composer community has similar views. On Reddit, many composers advocate for limiting AI's role to reference and placeholder work that bridge the gap between the client and the composer.<ref>{{Cite web |last=ArgamaWitch |date=2024-04-15 |title=Composers that take commissions, what's your thoughts on AI music being used as reference? |url=https://www.reddit.com/r/composer/comments/1c4vrvr/composers_that_take_commissions_whats_your/?rdt=57624 |access-date=2024-12-09 |website=r/composer}}</ref> The consensus among professional composers, including James, is that AI needs much better regulation. They argue for protecting artists' unique, copyrightable styles from unauthorized AI replication and advocate that AI companies should compensate the artists whos works train the AI models. These composers are working to convince the Copyright Office that training AI on artists' work without compensation devalues artists. === Gaming === ==== Players ==== Players of video games tend towards a negative reception of generative AI usage in game development. Games will often receive negative reviews or discussions on forum pages when AI use is apparent: for instance, Steam (a platform used to distribute and discuss games) has entire community-driven pages dedicated towards identifying and shaming AI employment in games<ref>{{Cite web |title=Steam Curator: Games That Use AI Generation |url=https://store.steampowered.com/curator/45944619-Games-That-Use-AI-Generation/ |access-date=2026-05-04 |website=store.steampowered.com |language=en}}</ref>. == References == <references /> {{BookCat}} pv07ju2q5yl43n1xv88ulq25gd0lqiu 4634180 4634153 2026-05-04T19:28:54Z Humzarubel 3581183 Addition of a small section in Reception/Gaming discussing executive response to AI and backlash 4634180 wikitext text/x-wiki == Overview == === Introduction === Artificial intelligence (AI) is revolutionizing creative industries, such as the music industry, by redefining how creative works are composed, performed, and consumed. What began as theoretical musings by pioneers like Alan Turing has grown into a field with sophisticated neural networks capable of composing full-length songs, for example. However, this evolution raises pressing questions about originality, ownership, and the future of human creativity. === History of AI and Music === ====== Theoretical Foundations: 1950s-1960s ====== The concept of AI-generated music originated with Alan Turing, who theorized in the 1950s that machines could emulate human cognitive processes, including music composition. His ideas laid the groundwork for computational creativity.<ref>{{Citation |last=Copeland |first=B. Jack |title=Turing and the History of Computer Music |date=2017 |url=https://link.springer.com/chapter/10.1007/978-3-319-53280-6_8 |work=Philosophical Explorations of the Legacy of Alan Turing: Turing 100 |pages=189–218 |editor-last=Floyd |editor-first=Juliet |access-date=2024-12-02 |place=Cham |publisher=Springer International Publishing |language=en |doi=10.1007/978-3-319-53280-6_8 |isbn=978-3-319-53280-6 |last2=Long |first2=Jason |editor2-last=Bokulich |editor2-first=Alisa}}</ref> In 1957, Lejaren Hiller and Leonard Isaacson at the University of Illinois created the Illiac Suite<ref>{{Cite web |title=ILLIAC Suite – Illinois Distributed Museum |url=https://distributedmuseum.illinois.edu/exhibit/illiac-suite/ |access-date=2024-12-02 |website=distributedmuseum.illinois.edu}}</ref>. Using the ILLIAC I computer, they developed an algorithmic process to compose a string quartet, marking one of the first successful instances of computer-generated music. It demonstrated the potential of computers to collaborate in creative endeavors, sparking decades of research into AI's role in music. ====== Rule-Based Systems: 1970s-1980s ====== During the 1970s and 1980s, AI systems advanced with rule-based algorithms that mimicked specific musical styles. David Cope’s Experiments in Musical Intelligence<ref>{{Cite web |last=tluong |date=2015-04-29 |title=Algorithmic Music – David Cope and EMI |url=https://computerhistory.org/blog/algorithmic-music-david-cope-and-emi/ |access-date=2024-12-02 |website=CHM |language=en}}</ref> (EMI) exemplified this approach by analyzing existing compositions and generating new ones in the style of Bach and Mozart. However, EMI heavily relied on predefined human rules, highlighting the imitative, rather than generative, nature of early AI. A significant technological leap came in 1983 with the introduction of MIDI<ref>{{Citation |title=MIDI |date=2024-11-25 |url=https://en.wikipedia.org/wiki/MIDI |work=Wikipedia |access-date=2024-12-02 |language=en}}</ref> (Musical Instrument Digital Interface). MIDI standardized communication between computers and electronic instruments, enabling precise control of musical elements and facilitating data collection for future AI systems. ====== Machine Learning: 1990s-2000s ====== AI music systems transitioned from rule-based models to data-driven techniques in the 1990s. Machine learning algorithms enabled pattern recognition and predictive modeling, allowing AI to generate more complex and varied compositions. Projects like Accenture’s Symphonologie<ref>{{Cite web |title=Accenture {{!}} Symphonologie |url=https://www.oneclub.org/awards/theoneshow/-award/25489/symphonologie/ |access-date=2024-12-02 |website=www.oneclub.org |language=en}}</ref> showcased AI as a collaborative tool, blending human and machine creativity. ====== Neural Networks: 2010s-Present ====== The rise of deep learning revolutionized AI in music. Neural networks, trained on vast datasets, now compose intricate, multi-instrumental pieces in seconds. Tools like OpenAI’s MuseNet<ref>{{Cite web |title=MuseNet |url=https://openai.com/index/musenet/ |access-date=2024-12-02 |website=openai.com |language=en-US}}</ref> and AIVA<ref>{{Cite web |title=AIVA, the AI Music Generation Assistant |url=https://www.aiva.ai/ |access-date=2024-12-02 |website=www.aiva.ai |language=en}}</ref> exemplify how AI has expanded its creative capabilities across genres, challenging the boundaries of human artistry. == Relevant Legal Disputes == === Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884) === [[File:Oscar Wilde 1882.jpg|thumb|Oscar Wilde No.18 by Napoleon Sarony (1882)]] [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithography Co v. Sarony]] was submitted on December 13, 1883 when Sarony filed a copyright suit against Burrow-Giles when the company had marketed lithographs of Sarony's photograph, Oscar Wilde No.18, without Sarony's permission. Burrow-Giles argued that photographs were neither writings nor a production of an author, and thus did not possess copyright protection. The court determined that even though creating a photograph is "merely mechanical, with no place for novelty, invention, or originality", the photograph Sarony created was his "own original mental conception, to which he gave visible form by posing the said Oscar Wilde in front of the camera, selecting and arranging the costume, draperies, . . . suggesting and evoking the desired expression, and from such . . . representation, made entirely by plaintiff, he produced the picture in suit.'" On March 17, 1884, the court established that photography is a copyrightable medium. Furthermore, this case reinforced that an author of a work is "he to whom anything owes its origin."<ref>Burrow-Giles Lithographic Company v. Sarony, 111 U.S. 53 (1884)</ref> === Naruto v. Slater, No. 16-15469 (9th Cir. 2018) === [[File:Macaca nigra self-portrait large.jpg|left|thumb|One of the monkey selfies]] Naruto v. Slater, more commonly known as the [[wikipedia:Artificial_intelligence_and_copyright|Monkey Selfie copyright dispute]], began on September 22, 2015. PETA, representing the crested macaque Naruto, sued Slater claiming that because the monkey took its own picture, it was entitled to the copyright. David J. Slater, the photographer, argued that he held the copyright as he engineered the situation that led to the monkey taking its selfie. On April 23, 2018, the court determined that "this monkey - and all animals, since they are not human – [lack] statutory standing under the Copyright Act", reinforcing that non-humans cannot own copyright.<ref>Naruto v. Slater, No. 16-15469 (9th Cir. 2018)</ref> === Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023) === [[File:A Recent Entrance to Paradise.jpg|thumb|A Recent Entrance to Paradise]] Thaler v. Perlmutter emerged after the U.S. Copyright Office denied Dr. Stephen Thaler's copyright application for an AI generated work, "A Recent Entrance to Paradise". The court focused on answering "whether a work generated autonomously by a computer falls under the protection of copyright law upon its creation". Thaler filed a lawsuit, arguing that the copyright of the AI generated work belonged to him as the AI model's creator. He stated that "AI should be ‘acknowledge[d] . . . as an author where it otherwise meets authorship criteria, with any copyright ownership vesting in the AI’s owner.’" The court reviewed the decision of [[wikipedia:Burrow-Giles_Lithographic_Co._v._Sarony|Burrow-Giles Lithographic Co. v. Sarony]], finding that the author of any AI generated work would be the AI. However, following the decision of [[wikipedia:Artificial_intelligence_and_copyright|Naruto v. Slater]], since AIs are not human, they cannot hold copyright. The case was decided on August 18, 2023, confirming that AIs cannot hold copyright. As such, the work fell under public domain. However, the court explicitly stated that they were not making any decisions on "how much human input is necessary to qualify the user of an AI system as an 'author' of a generated work".<ref>Thaler v. Perlmutter, No. 22-1564 (BAH)(DDC 2023)</ref> The D.C. Circuit unanimously affirmed in March 2025. On March 2, 2026, the Supreme Court denied certiorari, making the ruling final and exhausting Thaler's appeals. ''Thaler'' now stands as binding precedent that AI systems cannot themselves be authors under U.S. copyright law, and that works generated entirely without human creative contribution are ineligible for registration. '''''Allen v. Perlmutter'', No. 24-2665 (WJM) (D. Colo. 2026)''' [[File:Théâtre D’opéra Spatial.png|thumb|''Théâtre D'opéra Spatial'', created by Jason M. Allen using Midjourney, Photoshop, and Gigapixel AI]] ''Allen v. Perlmutter'' picks up where ''Thaler'' left off. In August 2022, Colorado artist Jason Allen used Midjourney to create ''Théâtre D'opéra Spatial'', entering text prompts at least 624 times to specify genre, tone, composition, and style, then refining the chosen output in Photoshop and Gigapixel AI. The image won first place at the Colorado State Fair in September 2022. When Allen applied for copyright registration as the sole human author, the Office offered to register only the portions reflecting his own contributions if he disclaimed the AI-generated material. Allen refused, and after the Review Board issued its final refusal in June 2023, he filed suit in the U.S. District Court for the District of Colorado on September 26, 2024. He moved for summary judgment in August 2025, the Copyright Office cross-moved in January 2026, and Allen filed his reply in February 2026. Allen argues that his iterative prompting and creative selection constitute authorship analogous to the photographer's creative choices that made photography copyrightable under ''Burrow-Giles''. The Copyright Office counters that prompts are ideas, not expression, because Midjourney determines the actual visual output regardless of how detailed the instructions are. The case is now fully briefed before Judge William J. Martínez, with a ruling expected in 2026 that will produce the first judicial standard answering the question ''Thaler'' left open: when does human input in AI-assisted work rise to the level of copyright authorship? === Zarya of the Dawn === [[File:Zarya of the Dawn cover.webp|thumb|Zarya of the Dawn by Kristina Kashtanova]] [[wikipedia:Zarya_of_the_Dawn|Zarya of the Dawn]], a comic book authored by Kristina Kashtanova and illustrated using the AI generator Midjourney sparked a significant copyright dispute in 2022. When Kashtanova applied for copyright of the comic in September 2022, she failed to disclose that the images were generated by Midjourney. The comic was originally granted copyright by the Copyright Office, but after discovering Midjourney's involvement in illustrating the comic, they reviewed their decision. While the Copyright Office agreed that the text and compilation (the arrangement of images and text) were copyrightable, the art was not, as the "process is not controlled by the user because it is not possible to predict what Midjourney will create ahead of time." Although, Kashtanova claimed "she personally edited some of the images created by Midjourney", the Copyright office could not determine "what expression in the image was contributed through her use of Photoshop as opposed to generated by Midjourney" and thus revoked the copyright. <ref>{{Cite web |last=Kasunic |first=Robert J. |date=February 21, 2023 |title=2023.02.21 Zarya of the Dawn Letter |url=https://www.copyright.gov/docs/zarya-of-the-dawn.pdf |url-status=live |access-date=December 9, 2024 |website=Copyright Office (.gov)}}</ref> == Relevant Copyright Chapters == === Chapter 308: The Originality Requirement<ref name=":0">U.S. Copyright Office, Compendium of U.S. Copyright Office Practices § 101 (3d ed. 2021).</ref> === The Originality Requirement has two primary requirements: "The work must be ‘independently created by the author’ and it must possess ‘at least some minimal degree of creativity’" ==== Chapter 308.1 ==== The Copyright Act defines "independent creation" as a work created "without copying from other works." However, "a work may satisfy the independent creation requirement ‘even though it closely resembles other works so long as the similarity is fortuitous, not the result of copying.’" ==== Chapter 308.2 ==== In terms of creativity, the Copyright Act states that "‘the requisite level of creativity is extremely low.’ Even a ‘slight amount’ of creative expression will suffice.’" ==== Works That Do Not Satisfy the Originality Requirement ==== 313.4(A): Mere Copies 313.4(K): Mere Variations of Colorings === Chapter 306: The Human Authorship Requirement<ref name=":0" /> === The Human Authorship Requirement states that only humans may own a copyright. "The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being." ==== Chapter 313.2 ==== The chapter states that "the U.S. Copyright Office will not register works produced by nature, animals, or plants." Furthermore, "the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author." ==== Works That Lack Human Authorship ==== * A photograph taken by a monkey. * A mural painted by an elephant. * A claim based on the appearance of actual animal skin. * A claim based on driftwood that has been shaped and smoothed by the ocean. * A claim based on cut marks, defects, and other qualities found in natural stone. * An application for a song naming the Holy Spirit as the author of the work. === Chapter 507.1: Derivate Works<ref name=":0" /> === As AI generated works are considered to be authored by the AI, and thus public domain, attempts to edit and then copyright the works would most likely fall under derivative works. The Copyright Act defines a derivative work as "a work based upon one or more preexisting works, such as a . . . art reproduction . . . or any other form in which a work may be recast, transformed, or adapted." ==== Chapter 311.2 ==== Derivative works follow the same originality requirements as original works. Derivative works may only receive copyright protection "provided that [the work] contains a sufficient amount of original expression, meaning that the derivative work must be independently created and it must possess more than a modicum of creativity" The Copyright Act does reiterate that "[m]iniscule variations do not satisfy this requirement, such as merely changing the size of the preexisting work." == Present Issues == === AI Music === ==== Lack of Creativity ==== In 2023, an anonymous creator known as "Ghostwriter" released Heart on My Sleeve, featuring AI-generated vocals mimicking Drake and The Weeknd. The song went viral, drawing millions of streams before being removed for copyright infringement. Universal Music Group argued that the AI-generated track exploited the artists’ likenesses without consent, raising ethical and legal concerns<ref>{{Cite web |last=Reed |first=Rachel |title=AI created a song mimicking the work of Drake and The Weeknd. What does that mean for copyright law? |url=https://hls.harvard.edu/today/ai-created-a-song-mimicking-the-work-of-drake-and-the-weeknd-what-does-that-mean-for-copyright-law/ |access-date=2024-12-02 |website=Harvard Law School |language=en-us}}</ref>. This case highlights AI’s ability to imitate human creativity so convincingly that it blurs the line between originality and replication. Although the creator faced no legal repercussions, the controversy underscored the need for clearer regulations on AI-generated content. * AI doesn’t create entirely new works; it amplifies patterns derived from training data. While it can replicate styles, it lacks the emotional depth and intentionality of human artistry. * Tools like MuseNet and Suno allow anyone to compose music in minutes, potentially devaluing human creativity by making artistic production instantaneous and impersonal. ==== Suno and Udio ==== The most current case reflecting the debate regarding the originality of AI music is in the RIAA vs. Suno and RIAA vs. Udio. The RIAA, or the Recording Industry Association of America, is a trade organization that represents many record labels, including Sony Music Group, Universal Music Group, and Warner Music Group (colloquially known as "the big Three" in the industry as they own up to 85% of market share). In June 2024, the RIAA placed a copyright infringement lawsuit on Suno and Udio (two generative AI music startup companies). They had three main goals with this lawsuit: <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html#:~:text=The%20lawsuits%20make%20three%20specific,to%20nine%20figures%20or%20more. |access-date=2024-12-10 |website=Vulture |language=en}}</ref> # To have these companies admit their models use copyrighted music. # Immediately stop training their AI models using this copyrighted music. # Seek damages up to $150,000 per song used in the models. When first discussing the lawsuit with the press, Chairman and CEO of RIAA, Mitch Glazier, stated: "The music community has embraced AI and we are already partnering and collaborating with responsible developers to build sustainable AI tools centered on human creativity '''that put artists and songwriters in charge''', but we can only succeed if developers are willing to work together with us. Unlicensed services like Suno and Udio that '''claim it's 'fair' to copy an artist's life's work and exploit it for their own profit without consent or pay''' set back the promise of genuinely innovative AI for us all."<ref>{{Cite web |last=Connelly |first=Rose |date=2024-06-24 |title=Record Companies Bring Landmark Cases for Responsible AI Against Suno and Udio in Boston and New York Federal Courts, Respectively |url=https://www.riaa.com/record-companies-bring-landmark-cases-for-responsible-ai-againstsuno-and-udio-in-boston-and-new-york-federal-courts-respectively/ |access-date=2024-12-10 |website=RIAA |language=en-US}}</ref> The RIAA hopes to reflect that the inherent moral value of this statement for pursuing this lawsuit is protecting artists' work and fair pay. However, in any of RIAA's arguments, the percentage of and how the money collected from damages will be distributed to the artists of each respective record label must be clarified. Suno responded to the copyright lawsuit, "What the major record labels really don't want is competition." While this calls to question the actual motive of the lawsuit and whether the benefactors will include artists, the results of this lawsuit are pertinent as they will set further precedents in how copyright pertains to AI overall. Initially, in response to the lawsuit, Udio claimed "fair use," which is primarily used for academic or journalistic purposes. However, lawyers dismissed this claim because their training is not used for human-created content. <ref>{{Cite web |last=Curto |first=Justin |date=2024-08-01 |title=All 3 Major Labels Are Suing AI Start-ups for Copyright Infringement |url=https://www.vulture.com/article/major-labels-music-ai-suno-udio-lawsuit.html |access-date=2024-12-10 |website=Vulture |language=en}}</ref> As the lawsuit proceeded, both companies admitted to using copyrighted music only as "intermediate copies." They sighted a copyright case from 2021 regarding an AI algorithm's use of copyrighted images to create a search algorithm. In that case, using these "intermediate copies was lawful" because these lower-resolution copies did not satisfy the user's desire to see the full images. However, in Suno and Udio's context, their AI models are not search algorithms but are generative. As the lawsuits progressed into late 2025, the landscape began to shift from purely adversarial to partially collaborative. Major record labels, including Universal Music Group and Warner Music Group, reached settlements with AI companies like Udio and Suno. These agreements introduced a new model centered on licensing and artist consent, allowing musicians to “opt in” to have their work used in training datasets. This marks a significant shift toward a hybrid system where AI developers and record labels may coexist through formal partnerships rather than litigation alone. However, not all disputes have been resolved, as some companies—particularly Sony Music Group—continue to pursue legal action, signaling that consensus across the industry remains incomplete. As of 2026 the progress of the three goals of the lawsuit is as follows: * To have these companies admit their models use copyrighted music. ** The Sudo and Udio never outright admitted they were using copyrighted material, but instead shifted the focus of the lawsuit to whether or not using copyrighted material was legal in the first place. * Immediately stop training their AI models using this copyrighted music. ** The AI models are no longer being trained on the music illegally but this is due to the record labels making deals so that the Sudo and Udio could continue what they were doing but now legally.<ref>{{Cite web |date=2026-02-26 |title=AI song generator startups Suno and Udio angered the music industry. Now they're hoping to join it |url=https://www.latimes.com/business/story/2026-02-26/ai-song-generator-startups-suno-udio-angered-music-industry-now-theyre-hoping-to-join-it |access-date=2026-05-04 |website=Los Angeles Times |language=en-US}}</ref> * Seek damages up to $150,000 per song used in the models. ** The settlements and partnership deals were never made public so we can't be sure what exactly happened.  The case is less about a definitive win or loss and more about setting an early precedent for how generative AI and intellectual property will coexist. Moving forward, these outcomes will likely influence future cases involving AI training data, reinforcing the importance of consent, compensation, and human authorship in creative industries. === AI Video Animation === AI video generation, though more accurately video animation, became visible to the public during the 2026 Super Bowl, when many brands used and advertised generative AI to create visuals rather than VFX. Svedka actually used generative AI to create their entire ad. The general reception to Svedka's ad, as well as ones created by Kalshi and Coca Cola was generally negative, stating they were cheap and uncanny <ref>{{Cite web |last=Monllos |first=ByKristina |title=About that AI Bowl: Reception of AI ads ‘sharply negative’ as brand beefs, misinformation brewed |url=https://www.marketingbrew.com/stories/2026/02/11/ai-bowl-ad-reception-openai-anthropic-feud |access-date=2026-05-04 |website=Marketing Brew |language=en-us}}</ref>. In Hollywood, the usage of AI video animation is more subtle, but it has existed for longer. Movies will not have entirely AI generated scenes by in large. However, studios use AI video tools for previsualization, which means generating rough versions of scenes before shooting them in real life. Another use is concept iteration. Instead of waiting days for artists, teams can generate dozens of variations of a scene in minutes. AI is mostly used for background generation, de-aging real actors, and filling minor gaps in VFX shots. Systems like Sora showed the ability to generate clips up to about a half minute long with simulated camera motion, depth, and basic physics. But these clips often break under further constraints and scrutiny. Objects drift, characters change appearance mid shot, and motion is not physically consistent, which makes it largely impractical to produce any meaningfully long scenes. However, companies such as Netflix and Amazon have started partnering with Runway to trained specialized franchise video animation models on their proprietary content. <ref>{{Cite web |last=Metz |first=Rachel |date=2025-07-22 |title=Netflix using startup Runway AI’s video tools for production |url=https://www.latimes.com/business/story/2025-07-22/netflix-using-startup-runway-ais-video-tools-for-production |access-date=2026-05-04 |website=Los Angeles Times |language=en-US}}</ref> Steven Spielberg accepts the use of AI, but drew a hard line in that it cannot replace a human creative. He said AI can help with planning and visual development but should not replace real actors and artists <ref>{{Cite web |last=Perez |first=Sarah |date=2026-03-13 |title=Steven Spielberg says he's 'never used AI' in any of his films |url=https://techcrunch.com/2026/03/13/steven-spielberg-says-hes-never-used-ai-in-any-of-his-films/ |access-date=2026-05-04 |website=TechCrunch |language=en-US}}</ref>. George Lucas has argued that tools like this are inevitable and will lower costs for independent creators. AI was used to create a deep faked face of a young Mark Hamill as Luke Skywalker in the Boba Fett series, meaning Lucasfilm under Disney had been using AI as early as 2021 <ref>{{Cite web |last=King |first=Jack |date=2022-02-10 |title=Deepfake Luke Skywalker is another step down a ghoulish CGI path |url=https://www.gq-magazine.co.uk/culture/article/boba-fett-luke-skywalker |access-date=2026-05-04 |website=British GQ |language=en-GB}}</ref>. Paul Schrader warned that full AI-generated films are close and could remove the need for many creative roles. His concern is not just quality but control over authorship and credit, which in part is shared by his audience. Sora itself ran into some concrete problems. It was expensive to run because each generated video required expensive GPU clusters for diffusion sampling across hundreds of frames. Companies like The Walt Disney Company were cautious about allowing their content or likenesses to be replicated by such systems. Walt Disney entered into a contract with OpenAI that allowed them to generate their characters in Sora clips. Newer systems like Veo improved temporal consistency by modeling motion across frames instead of generating each frame independently. Veo also added better camera controls, longer clip generation, and tighter integration with editing workflows <ref>{{Cite web |last=Abitbul |first=Hanna |date=2025-06-25 |title=Veo 3 vs. Sora by OpenAI: 2026 Comparison |url=https://www.powtoon.com/blog/veo-3-vs-sora/ |access-date=2026-05-04 |website=Powtoon Blog |language=en-US}}</ref>. As of April 26th 2026, Sora was discontinued by OpenAI despite Disney already being involved <ref>{{Cite web |title=What to know about the Sora discontinuation |url=https://help.openai.com/en/articles/20001152-what-to-know-about-the-sora-discontinuation |access-date=2026-05-04 |website=OpenAI Help Center |language=en-US}}</ref>. ==== Other AI Music Lawsuits ==== Following this case, different record labels (primarily Universal) have filed a copyright on issues regarding AI music. On October 18, 2023, several record labels, namely Universal, filed a lawsuit alleging that Anthropic's AI chatbot, "Claude," unlawfully copied and disseminated copyrighted works, including lyrics "owned or controlled by the Publishers. On January 31, 2024, the copyright license agreement between Universal Music Group (UMG), the world's largest music company, and TikTok owner ByteDance Ltd. expired without a renewal agreement. TikTok was forced to turn off the reproduction of all audio content from artists belonging to UMG's catalog, including Taylor Swift, Billie Eilish, Romeo Santos, J Balvin, and Imagine Dragons, among many others. During these negotiations, UMG made AI-generated music a sticking point in their TikTok negotiations, and a group of musicians spoke out against AI-generated music. Groups, including the Recording Academy, the Music Workers Alliance, the National Association of Music Publishers, the American Association of Independent Music, and even SAG-AFTRA, have all made statements supporting the lawsuits. ==== Ethical Implications of AI in the Music Industry ==== As is apparent with the growing number of lawsuits directed at AI music companies, advancements in AI bring new possibilities for creativity and efficiency along with critical ethical concerns regarding economic impact, bias, and data harvesting. AI’s role in the music industry is a double-edged sword, offering both opportunities and challenges. On the one hand, AI automates many aspects of music creation and production. Tasks like composition, audio mastering, and even lyric writing can now be performed by AI tools. However, this automation has led to concerns about job displacement. Traditional roles in the industry, such as sound engineers and live musicians, face increasing obsolescence as AI tools become more sophisticated and accessible. However, AI also democratizes music production, enabling independent artists and smaller labels to create high-quality music without needing expensive equipment or studio time. So, while jobs are being lost, new roles are emerging, such as AI music curators and prompt engineers. This demonstrates how technological advancements can create fresh opportunities even as they disrupt existing systems. Another critical issue in the use of AI in music is the presence of bias in the models used to generate content. AI systems are only as good as the data they are trained on, and this dependency can result in significant imbalances. For instance, if an AI model’s training data predominantly features Western music, the system may struggle to generate accurate representations of non-Western genres or cultural styles. Along with racial bias, gender bias in datasets used for AI training can perpetuate existing inequalities in the music industry. If female and non-binary artists are underrepresented in the data, AI-generated music may disproportionately reflect the styles and contributions of male artists. Such biases highlight the need for diverse and inclusive training datasets. Developers must address these issues to ensure that AI tools reflect a broader and more equitable spectrum of musical expression. As discussed previously, the question of how AI systems source their training data has sparked widespread ethical debates. Many AI models, most notably Suno and Udio, are trained using copyrighted music, often without the consent or compensation of the original artists and have received backlash. This practice raises significant concerns about exploitation. Artists invest considerable time and effort into creating music, yet their work can be appropriated by AI systems without acknowledgment or financial remuneration. This mirrors controversies in other areas of AI, such as the exploitation of the unpaid labor of associated with Remotask workers. If creators cannot safeguard their work against unauthorized use by AI systems, the industry risks devaluing artistic contributions in favor of technological efficiency. The music industry is at a crossroads–do we protect the rights of creators, or do we embrace AI-drive efficiency without clear ethical guidelines? === AI in the Video Game Industry === The intersection of visual art, music, voice, and code make the gaming industry a hot spot for AI usage within creative works. AI has existed within gaming for some time in the form of non-playable characters (NPCs), but the modern implementation of AI within gaming specifically sees increased usage of generative tools for creative purposes. ==== Nvidia DLSS 5.0 ==== Nvidia is a prolific graphics card producer with extensive ties to the gaming industry. Originally founded for the purpose of innovating computer gaming<ref>{{Cite web |title=NVIDIA Corporation: History |url=https://www.nvidia.com/en-us/about-nvidia/corporate-timeline/ |access-date=2026-05-04 |website=NVIDIA |language=en-us}}</ref>, they have since leveraged their graphics processing unit (GPU) technology for AI usage extensively, while also seeking to implement AI within their gaming technologies. Deep Learning Super Sampling (DLSS) is a technology developed by Nvidia to use real-time deep learning AI to upscale video game rendering. The initial versions of DLSS were employed by running games at a lower native resolution, then using AI to upscale to a higher resolution based on the picture generated by the GPU<ref>{{Cite web |last=Martindale |first=Jon |date=2020-02-14 |title=Nvidia RTX DLSS: everything you need to know |url=https://www.digitaltrends.com/computing/everything-you-need-to-know-about-nvidias-rtx-dlss-technology/ |access-date=2026-05-04 |website=Digital Trends |language=en-us}}</ref>; this implementation did not use AI to directly modify any of the actual contents of games themselves. DLSS 5.0, however, made use of generative AI to attempt to directly enhance the visual content of games. While the exact details of the implementation have yet to be released as of May 2026, the technology appears to generate new frames from prior training data, using the existing content of a game as the base. This introduces elements of the rendering which may not have been present in the original developer's vision, and poses issues related to artistic vision: Since the AI is able to directly add new content and textures, concerns are raised about whether a game is still the same piece of art/media. ==== AI Voice Acting and Other Content ==== AI usage in gaming development can be difficult to discern, leading to the spread of many rumors and allegations of use in voice acting, dialogue generation, textures, among others. Games such as The Finals and Arc Raiders have been accused of using AI tools to generate voice lines, which many perceive to be of lower quality than those generated by human counterparts. For The Finals in particular, the developers at Embark Studios stated that they used AI to extend voice lines created by real voice actors<ref>{{Cite web |last=Notis |first=Ari |date=2025-10-31 |title=Arc Raiders' use of AI voices is The Finals controversy all over again |url=https://www.polygon.com/arc-raiders-ai-voices-the-finals-embark-studios/ |access-date=2026-05-04 |website=Polygon.com |language=en}}</ref>. This can be problematic with respect to intellectual property rights, say for instance a development studio, unbeknown to a voice actor, is using said actor's voice as a baseline for AI generated quips and content. == Reception == === Music === ==== Students ==== While students seem to find AI music fascinating, they emphasize that AI music lacks the emotional depth found in human compositions. They explain that human compositions are capable of conveying authentic human experiences and feelings, which AI cannot replicate. ''Quotes are pulled directly from a New York Times article''<ref>{{Cite web |last=The Learning Network |first= |date=May 11, 2023 |title=What Students Are Saying About A.I.-Generated Music |url=https://www.nytimes.com/2023/05/11/learning/what-students-are-saying-about-ai-generated-music.html |url-status=live |access-date=December 9, 2024 |website=The New York Times}}</ref>: "Human singers have the ability to convey a wide range of emotions and add their own unique style to their music. They have the creativity and experience to interpret lyrics and to give them their own style. Music made with A.I. may be good, but it will never be the same as music sung by a good pop star. While A.I. can be a helpful tool for composers and producers to experiment with new sounds and styles, it will never replace the raw talent and artistry of human vocalists." - ''Sergi, Sant Gregori'' "In my personal opinion, the main allure of music lies in the emotional connection that it establishes with the listener. It’s not only about the melody or the lyrics, but also the sentiments and reminiscences that the music evokes. If I became aware that a song was completely generated by an artificial intelligence system, I would feel intrigued to listen to it, driven by my fascination with the underlying technology. Nevertheless, I might not feel as connected to the song on an emotional level as I would if it was composed by a human artist." - ''Aleena, Julia R. Masterman, Philadelphia, PA'' "Even if the lyrics emulate a real pop star’s lyrics, whether it talks about heartbreak, love, or family, it would never have the same impact like one created by a real pop star because the listeners know it is all just to sound good and appeal to the listeners. It would have nothing to do with the artist themselves … Music is supposed to be relatable. When I listen to music, I like to listen to artists I know have gone through similar things or have the same feelings as me." - ''Sophia, Hinsdale Central High School'' ==== Composers ==== The evolution of composers attitudes towards AI music is reflected in [https://www.youtube.com/channel/UCelK8dBKY0Xs5oRI6sJf7aA Daniel James], a composer on YouTube, perspective over time. While he acknowledged that AI generated music was inevitable, it would never allow a total newbie to suddenly become a professional.<ref>{{Citation |last=Daniel James |title=TADay #4 - Composer Talk Radio - Is AI a threat or is it the future of composition. |date=2019-06-29 |url=https://www.youtube.com/watch?v=cqJWI4HF1CY |access-date=2024-12-09}}</ref> He suggested if AI became proficient in replicating professionals, composers would need to come up with their own style away from the AI. James had a positive view on AIs potential as a tool, comparing it to a ghost composer that could handle much of the monotonous work that an assistant might do. He predicted that AI would primarily impact the lower-skilled composers, widening the gap between low and high skilled composers. By 2023, James' perspective has become more nuanced.<ref>{{Citation |last=Daniel James |title=AI In The Music Industry - Tool Or Threat - A Professional Composers View. |date=2022-12-11 |url=https://www.youtube.com/watch?v=fOL32kRuUI0 |access-date=2024-12-09}}</ref> He discussed the limitations of AI, explaining that it can't really create something new, and can only make variations. While acknowledging AIs capability to blend styles, like reimagining Beethoven as hip-hop, he emphasizes that music exists within the context of the time it is created. James considers that although AI can accurately replicate music, it still struggles with emotional nuance. He also notes that skilled AI use would still require musical expertise to properly guide the AI. James also discusses the significant impacts AI might have. Formulaic music like EDM and trailer music seem particularly vulnerable to AI as there is a "correct" way to write those styles of music. He also believes that AI music will severely damage the lower end of the creative field. He worries that if newer generations of artists are trained to use AI, they may forget how to develop their own original styles, stunting their growth. The broader composer community has similar views. On Reddit, many composers advocate for limiting AI's role to reference and placeholder work that bridge the gap between the client and the composer.<ref>{{Cite web |last=ArgamaWitch |date=2024-04-15 |title=Composers that take commissions, what's your thoughts on AI music being used as reference? |url=https://www.reddit.com/r/composer/comments/1c4vrvr/composers_that_take_commissions_whats_your/?rdt=57624 |access-date=2024-12-09 |website=r/composer}}</ref> The consensus among professional composers, including James, is that AI needs much better regulation. They argue for protecting artists' unique, copyrightable styles from unauthorized AI replication and advocate that AI companies should compensate the artists whos works train the AI models. These composers are working to convince the Copyright Office that training AI on artists' work without compensation devalues artists. === Gaming === ==== Players ==== Players of video games tend towards a negative reception of generative AI usage in game development. Games will often receive negative reviews or discussions on forum pages when AI use is apparent: for instance, Steam (a platform used to distribute and discuss games) has entire community-driven pages dedicated towards identifying and shaming AI employment in games<ref>{{Cite web |title=Steam Curator: Games That Use AI Generation |url=https://store.steampowered.com/curator/45944619-Games-That-Use-AI-Generation/ |access-date=2026-05-04 |website=store.steampowered.com |language=en}}</ref>. ==== Executives/Industry ==== Nvidia met extensive backlash following their announce and demonstration of DLSS 5.0. Jensen Huang, CEO of Nvidia, retorted by dismissing the critiques as ill founded: "They're completely wrong", he said, when asked about the idea that DLSS 5 may make games appear artistically altered and potentially worse.<ref>{{Cite web |last=published |first=Andrew E. Freedman Contributions from Paul Alcorn |date=2026-03-17 |title=Jensen Huang says gamers are 'completely wrong' about DLSS 5 — Nvidia CEO responds to DLSS 5 backlash |url=https://www.tomshardware.com/pc-components/gpus/jensen-huang-says-gamers-are-completely-wrong-about-dlss-5-nvidia-ceo-responds-to-dlss-5-backlash |access-date=2026-05-04 |website=Tom's Hardware |language=en}}</ref> == References == <references /> {{BookCat}} gbhtsrra8vso75bztbkgjdk0oh8pb14 2 471107 4634075 4633528 2026-05-04T13:49:13Z JJPMaster (bot) 3488561 Bot: Updating markAdmins data 4634075 json application/json { ".snoopy.": [ "global-rollbacker", "editor" ], "1234qwer1234qwer4": [ "editor", "steward" ], "157yagz5r48a5f1a1f": [ "editor" ], "1997kB": [ "global-rollbacker", "global-renamer", "editor" ], "1F616EMO": [ "global-renamer" ], "1exec1": [ "transwiki", "editor" ], "1sfoerster": [ "editor" ], "20041027 tatsu": [ "global-rollbacker" ], "2005-Fan": [ "transwiki", "editor", "uploader" ], "331dot": [ "global-renamer" ], "33rogers": [ "editor" ], "4PlayerChess": [ "autoreview" ], "4pillars": [ "editor" ], "511KeV": [ "global-rollbacker" ], "94rain": [ "global-rollbacker", "editor" ], "A R King": [ "editor" ], "A Sulaiman Z": [ "editor" ], "A.K.Karthikeyan": [ "editor" ], "A09": [ "steward" ], "AFBorchert": [ "vrt-permissions" ], "AIProf": [ "editor" ], "ALittleSlow": [ "autoreview" ], "AManWithNoPlan": [ "editor" ], "ATannedBurger": [ "global-renamer" ], "AVRS": [ "editor" ], "Aafi": [ "vrt-permissions" ], "Abenwagner": [ "editor" ], "Abigor": [ "editor" ], "Abitt002": [ "editor" ], "Abyssal": [ "editor" ], "Acagastya": [ "autoreview" ], "Acalamari": [ "global-renamer" ], "Acarologiste": [ "editor" ], "AcidBat": [ "editor" ], "Acrow005": [ "editor" ], "Actualist": [ "editor" ], "Adalvis": [ "editor" ], "Adart001": [ "editor" ], "Adavyd": [ "global-renamer" ], "Addihockey10": [ "editor" ], "Addihockey10 (automated)": [ "editor" ], "Adrignola": [ "editor" ], "AdventureWriter": [ "editor" ], "Aferg006": [ "editor" ], "Afett001": [ "editor" ], "Affe2011": [ "global-rollbacker" ], "Agnerf": [ "editor", "uploader" ], "Agpires": [ "editor" ], "Agricola": [ "editor" ], "Agusbou2015": [ "editor" ], "Ah3kal": [ "global-rollbacker", "editor" ], "Ahecht": [ "global-renamer", "vrt-permissions" ], "Ahonc": [ "global-renamer", "vrt-permissions" ], "AiClassEland": [ "editor" ], "Ainz Ooal Gown": [ "editor" ], "Airpmb": [ "editor" ], "Ajraddatz": [ "editor", "steward" ], "Aka": [ "vrt-permissions" ], "Alanah.97": [ "autoreview" ], "Albertoleoncio": [ "steward", "vrt-permissions" ], "Albmont": [ "editor" ], "Aldnonymous": [ "editor" ], "Aledownload": [ "editor" ], "Alexlatham96": [ "editor" ], "Alextejthompson": [ "editor" ], "Alison": [ "global-rollbacker" ], "AllenZh": [ "editor" ], "Alphama": [ "global-renamer" ], "AlvaroMolina": [ "editor" ], "AmandaNP": [ "steward" ], "Ambrevar": [ "editor" ], "Amcgail": [ "editor" ], "Ameisenigel": [ "global-rollbacker", "global-sysop", "ombuds", "editor", "vrt-permissions" ], "AmieKim": [ "editor" ], "Amire80": [ "global-sysop" ], "Anachronist": [ "editor", "vrt-permissions" ], "Ancient9983": [ "editor" ], "Andrei Stroe": [ "vrt-permissions" ], "Andrew janke": [ "editor" ], "Andriy.v": [ "vrt-permissions" ], "Andyross": [ "editor" ], "Anil Shaligram": [ "editor" ], "Animajosser": [ "editor" ], "Anne Correia": [ "editor" ], "Anonim Şahıs": [ "editor" ], "Anonymity": [ "editor" ], "AnotherEditor144": [ "autoreview" ], "Antanana": [ "vrt-permissions" ], "Antandrus": [ "editor" ], "Anthere": [ "editor" ], "AntiCompositeNumber": [ "steward", "vrt-permissions" ], "Antonizoon": [ "editor" ], "Antonw": [ "editor" ], "Apfelmus": [ "editor" ], "Aphoneyclimber": [ "editor" ], "Apocheir": [ "editor" ], "Aqurs1": [ "global-rollbacker", "global-renamer", "global-sysop" ], "AramilFeraxa": [ "steward" ], "Arch dude": [ "editor" ], "Archolman": [ "editor" ], "Arcticocean": [ "ombuds" ], "ArdentPerf": [ "editor", "uploader" ], "Arlen22": [ "transwiki", "editor" ], "Armchair": [ "editor" ], "Arno-nl": [ "editor" ], "Arrow303": [ "vrt-permissions" ], "Arthurvogel": [ "editor" ], "Artoria2e5": [ "editor" ], "Arturoiochoam": [ "editor" ], "Arunreginald": [ "editor" ], "AshLin": [ "editor" ], "Atcovi": [ "sysop", "global-rollbacker" ], "Athrash": [ "editor" ], "Atiedebee": [ "editor" ], "Atlas.Spheres": [ "editor" ], "Atsme": [ "vrt-permissions" ], "Auremel": [ "editor" ], "Austncorp": [ "editor" ], "AuthorsAndContributorsBot": [ "autoreview" ], "Avicennasis": [ "editor" ], "Avraham": [ "global-renamer", "editor" ], "Awesome Princess": [ "editor" ], "Axpde": [ "editor" ], "Az1568": [ "global-rollbacker" ], "Az2008": [ "editor" ], "Azotochtli": [ "editor" ], "B.Korlah": [ "editor" ], "BD2412": [ "editor" ], "BORGATO Pierandrea": [ "editor" ], "BRPever": [ "global-rollbacker", "global-sysop" ], "BRUTE": [ "editor" ], "Backfromquadrangle": [ "editor" ], "Baiji": [ "global-rollbacker" ], "Bakasakali": [ "editor" ], "Balaji.md au": [ "editor" ], "BarkingFish": [ "editor" ], "Barras": [ "steward" ], "Base": [ "steward", "vrt-permissions" ], "Bastique": [ "editor" ], "Bautsch": [ "editor" ], "BeardMD": [ "editor" ], "Beetstra": [ "global-rollbacker" ], "BenTels": [ "editor" ], "Bencemac": [ "global-rollbacker", "global-renamer", "vrt-permissions" ], "Benjamin J. Burger": [ "editor" ], "Benjamin.doe": [ "editor" ], "Benrattray": [ "editor" ], "Benson Muite": [ "editor" ], "Bentbracke": [ "editor" ], "Bequw": [ "editor" ], "Bert Niehaus": [ "autoreview" ], "BethNaught": [ "editor" ], "Beuc": [ "editor" ], "Bhardwaj Anil": [ "autoreview" ], "BiT": [ "editor" ], "Bigdelboy": [ "transwiki" ], "Bignose~enwikibooks": [ "editor" ], "Billinghurst": [ "global-rollbacker", "editor" ], "Billymac00": [ "editor" ], "Biplab Anand": [ "global-rollbacker", "global-sysop" ], "Birdofadozentides": [ "editor" ], "BitterAsianMan": [ "editor" ], "Blua lago": [ "global-renamer" ], "Bluefoxicy": [ "editor" ], "Bluerasberry": [ "vrt-permissions" ], "BobChan2": [ "editor" ], "Bodhisattwa": [ "vrt-permissions" ], "BoldLuis": [ "editor" ], "Borhan": [ "global-rollbacker", "vrt-permissions" ], "Boris1951zz": [ "editor" ], "Bpenn005": [ "editor" ], "Brewster239": [ "global-rollbacker" ], "Bridget": [ "global-rollbacker", "editor" ], "Brienna.Hall77": [ "editor" ], "Brim": [ "editor" ], "Brittanys": [ "editor" ], "Bronwynh": [ "editor" ], "Bsadowski1": [ "editor", "steward" ], "Buddpaul": [ "editor" ], "Bullercruz1": [ "editor" ], "Buncic": [ "editor" ], "BurakD53": [ "editor" ], "Burkep": [ "editor" ], "ByGrace": [ "editor" ], "Bykim2012": [ "editor" ], "C1203sc": [ "editor" ], "CJakes1": [ "editor" ], "CKWG - Ada Magica": [ "editor" ], "Cabayi": [ "global-renamer" ], "CaitlinCarbury": [ "autoreview" ], "CalciumTetraoxide": [ "editor" ], "CalendulaAsteraceae": [ "editor" ], "Caliburn": [ "editor" ], "CallumPoole": [ "editor" ], "Calvin.Andrus": [ "editor" ], "Cameron11598": [ "editor" ], "Camouflaged Mirage": [ "editor" ], "Captain-tucker": [ "vrt-permissions" ], "Carlo.milanesi": [ "editor" ], "Caro de Segeda": [ "editor" ], "CarsracBot": [ "editor" ], "Catermark": [ "editor" ], "Cecila123": [ "autoreview" ], "Cedar101": [ "editor" ], "Champion": [ "editor" ], "Chaojidage": [ "editor" ], "Chaojoker": [ "editor" ], "Chaotic Enby": [ "autoreview", "global-renamer" ], "Chapka": [ "editor" ], "Charidri": [ "editor" ], "Charleneabeana": [ "autoreview" ], "CharlesHoffman": [ "editor" ], "Chazz": [ "editor" ], "Chelseafan528": [ "editor" ], "Cheryl2012": [ "editor" ], "Chescargot": [ "vrt-permissions" ], "Chi Sigma": [ "editor" ], "Chinmayee Mishra": [ "ombuds" ], "Chongkian": [ "editor" ], "Chowbok": [ "editor" ], "ChrisHodgesUK": [ "editor" ], "ChrisWallace": [ "editor" ], "Chriswaterguy": [ "editor" ], "Chuckhoffmann": [ "editor" ], "Church of emacs": [ "global-rollbacker" ], "Cic": [ "editor" ], "Ciell": [ "vrt-permissions" ], "Cilantrohead": [ "editor" ], "Cintilo": [ "editor" ], "Circuit dreamer": [ "editor" ], "Circuit-fantasist": [ "editor" ], "Civvì": [ "global-rollbacker", "global-renamer" ], "Ckwalker": [ "editor" ], "Clairerusselll": [ "autoreview" ], "Cloidl": [ "autoreview" ], "Cmsmcq": [ "editor" ], "Cnrowley": [ "editor" ], "CocoaZen": [ "editor" ], "CoconutOctopus": [ "global-renamer" ], "Codename Noreste": [ "sysop", "global-rollbacker", "interface-admin" ], "Codename Noroeste": [ "editor" ], "Codinghead": [ "editor" ], "CommonsDelinker": [ "autoreview" ], "Comp.arch": [ "editor" ], "Conan": [ "editor" ], "Cormullion": [ "editor" ], "Count Count": [ "steward" ], "Coupe": [ "editor" ], "Courcelles": [ "global-rollbacker", "editor" ], "CptViraj": [ "global-rollbacker", "global-renamer", "global-sysop" ], "Craignewland": [ "editor" ], "Craxd1": [ "editor" ], "CrazyEddy": [ "editor" ], "Cremastra": [ "editor" ], "Cremastra (JWB)": [ "autoreview" ], "Cromium": [ "editor" ], "Cromwellt": [ "editor" ], "Crystal East": [ "editor" ], "Cttcraig": [ "editor" ], "Cultures17": [ "editor" ], "Cultures33": [ "editor" ], "Cultures4": [ "editor" ], "Cultures92": [ "editor" ], "CunninghamJohn": [ "autoreview" ], "Curtaintoad": [ "editor" ], "Cyberpower678": [ "global-rollbacker" ], "Céréales Killer": [ "global-renamer" ], "D1n05aur5 4ever": [ "editor" ], "DARIO SEVERI": [ "autoreview", "global-rollbacker", "global-sysop" ], "DC Slagel": [ "editor" ], "DCB": [ "vrt-permissions" ], "DD 8630": [ "editor" ], "DGerman": [ "editor" ], "DVD206": [ "editor" ], "DZadventiste": [ "editor" ], "DaB.": [ "vrt-permissions" ], "DaGizza": [ "editor" ], "Dagana4": [ "autoreview" ], "Dallas1278": [ "editor" ], "Dan Koehl": [ "editor" ], "Dan Polansky": [ "editor" ], "Dan-aka-jack": [ "editor" ], "DanCherek": [ "autoreview" ], "Danarwaller": [ "editor" ], "DanielWhernchend": [ "editor" ], "Danielravennest": [ "editor" ], "Danilka5469": [ "editor" ], "Daniuu": [ "steward", "vrt-permissions" ], "DannyS712": [ "editor" ], "Darklama": [ "editor" ], "Darklilac": [ "editor" ], "Darrelljon": [ "editor" ], "DarwIn": [ "vrt-permissions" ], "Dave Braunschweig": [ "editor" ], "David L Davis": [ "editor" ], "DavidCary": [ "editor" ], "DavidLevinson": [ "editor" ], "Davidbena": [ "editor" ], "Dayshade": [ "editor" ], "Dchmelik": [ "editor" ], "Dcljr": [ "editor" ], "Dcondon": [ "editor" ], "Deepfriedokra": [ "global-renamer" ], "DejaVu": [ "global-rollbacker", "global-renamer" ], "DennisDaniels": [ "editor" ], "Dennisblu": [ "uploader" ], "Denniss": [ "editor" ], "DerHexer": [ "editor", "steward", "vrt-permissions" ], "Derek Andrews": [ "editor" ], "Designermadsen": [ "editor" ], "Deu": [ "global-rollbacker" ], "Dexxor": [ "editor" ], "Dezedien": [ "vrt-permissions" ], "Diandramartin": [ "autoreview" ], "Didym": [ "vrt-permissions" ], "Dino Bronto Rex": [ "editor" ], "Dirk Hünniger": [ "editor" ], "Divinations": [ "global-rollbacker" ], "Djb": [ "editor" ], "Djbrown": [ "editor" ], "Dlrohrer2003": [ "editor" ], "Dmccreary": [ "editor" ], "Doc Taxon": [ "vrt-permissions" ], "Doctorxgc": [ "editor" ], "Dom walden": [ "editor" ], "Domdomegg": [ "editor" ], "DominikTurner": [ "autoreview" ], "DonaldKronos": [ "editor" ], "DoubleGrazing": [ "global-renamer" ], "Doubleotoo": [ "editor" ], "Downdate": [ "editor" ], "Dr-Taher": [ "global-renamer" ], "Dr.Unclear": [ "editor" ], "DreamRimmer": [ "global-renamer", "global-sysop" ], "Dreftymac": [ "editor" ], "Drpundir": [ "editor" ], "Drummingman": [ "global-rollbacker", "global-renamer", "vrt-permissions" ], "DuLithgow": [ "editor" ], "Dungodung": [ "vrt-permissions" ], "Duplode": [ "editor" ], "DustDFG": [ "editor" ], "Dyolf77": [ "vrt-permissions" ], "EDCU320RHT": [ "editor" ], "EDUC320 Sylvialiang": [ "editor" ], "EE JRW": [ "editor" ], "EMAD KAYYAM": [ "editor" ], "EPIC": [ "steward" ], "EarlGrey2005": [ "autoreview" ], "Ebe123": [ "editor" ], "Ecarew": [ "editor" ], "Edgar181": [ "editor" ], "Edit filter": [ "sysop" ], "EdoDodo": [ "editor" ], "Edornbush": [ "editor" ], "Edriiic": [ "editor" ], "Efex": [ "editor" ], "Efex3": [ "editor" ], "Effeietsanders": [ "editor", "vrt-permissions" ], "EggRoll97": [ "editor" ], "Egil": [ "editor" ], "Eihel": [ "global-rollbacker", "editor" ], "Ejs-80": [ "global-renamer" ], "Ekaroleski": [ "editor" ], "Elaurier": [ "editor" ], "Elcobbola": [ "vrt-permissions" ], "Electro": [ "editor" ], "ElfSnail123": [ "editor" ], "Eli bubo4ka": [ "editor" ], "Eliarani": [ "editor" ], "Elli": [ "global-renamer", "vrt-permissions" ], "Ellywa": [ "vrt-permissions" ], "Elmacenderesi": [ "vrt-permissions" ], "Elton": [ "editor", "steward" ], "Emha": [ "vrt-permissions" ], "EmilymDaniel": [ "autoreview" ], "Empire3131": [ "editor" ], "Emufarmers": [ "vrt-permissions" ], "Encik Tekateki": [ "editor" ], "Enzomartinelli": [ "editor" ], "Eric Evers": [ "editor" ], "Erigena": [ "editor" ], "Erik Baas": [ "editor" ], "ErinNik": [ "editor" ], "Erinamukuta": [ "editor" ], "ErrantX": [ "editor" ], "EruannoVG": [ "editor" ], "Espen180": [ "editor" ], "Eta Carinae": [ "global-renamer" ], "Ethacke1": [ "editor" ], "Eumolpo": [ "editor" ], "Euphydryas": [ "global-renamer" ], "Eurodyne": [ "editor" ], "EvDawg93": [ "editor" ], "EvanCarroll": [ "editor" ], "Ewen": [ "editor" ], "Exusiai": [ "global-renamer" ], "Ezarate": [ "global-rollbacker", "vrt-permissions" ], "Fabartus": [ "editor", "uploader" ], "Faendalimas": [ "ombuds" ], "Fasten": [ "editor" ], "Faster than Thunder": [ "editor" ], "Fathoms Below": [ "global-renamer" ], "Fcorthay": [ "editor" ], "Fdena": [ "editor" ], "Federhalter": [ "editor" ], "Fehufanga": [ "global-rollbacker", "global-sysop" ], "Fekarp": [ "editor" ], "Fephisto": [ "editor" ], "Ferien": [ "global-rollbacker" ], "Fernando2812l": [ "editor" ], "Fernly": [ "editor" ], "Ffion B Thompson": [ "autoreview" ], "Fimatic": [ "editor" ], "FischX": [ "editor" ], "Fishpi": [ "editor" ], "Flattail": [ "editor" ], "FlightTime": [ "global-renamer" ], "Flolit": [ "editor" ], "Fluffernutter": [ "vrt-permissions" ], "FlyingAce": [ "global-rollbacker" ], "Fountain Pen": [ "editor" ], "Fr33kman": [ "editor" ], "FrancisFromGaspesie": [ "editor" ], "Frantsch": [ "autoreview" ], "Fredericknortje": [ "editor" ], "Fritzlein~enwikibooks": [ "editor" ], "Frozen Wind": [ "transwiki", "editor" ], "Ftaljaard": [ "editor" ], "Ftiercel": [ "editor" ], "Furrykef": [ "editor" ], "GKFX": [ "editor" ], "Galahad": [ "global-rollbacker" ], "Gampe": [ "vrt-permissions" ], "Ganímedes": [ "vrt-permissions" ], "Gary Dorman Wiggins": [ "editor", "uploader" ], "Garygaryj": [ "editor" ], "Gat lombard": [ "editor" ], "Gc211": [ "editor" ], "Geagea": [ "vrt-permissions" ], "Geekgirl": [ "editor" ], "GemmaCampbell": [ "autoreview" ], "Geoff Plourde": [ "editor" ], "Geofferybard": [ "transwiki", "editor" ], "GerbenRienk": [ "editor" ], "Gerges": [ "global-renamer" ], "Germany Poul Ah": [ "editor" ], "Gertbuschmann": [ "editor" ], "Ggee0621": [ "editor" ], "Gifnk dlm 2020": [ "editor", "uploader" ], "Girdi": [ "editor" ], "Glaisher": [ "editor" ], "Glane23": [ "vrt-permissions" ], "Gleb713": [ "autoreview" ], "Glich": [ "editor" ], "Gllyons": [ "editor" ], "Gmasterman": [ "editor" ], "GoblinInventor": [ "editor" ], "Good afternoon": [ "editor" ], "GoreyCat": [ "editor" ], "GorgeUbuasha": [ "editor" ], "GorillaWarfare": [ "vrt-permissions" ], "Gott wisst": [ "editor" ], "Goulart": [ "editor" ], "Gpkp": [ "editor" ], "Gracebaysinger": [ "editor" ], "Graeme E. Smith": [ "editor" ], "Greatswrd": [ "editor" ], "GreenC": [ "editor" ], "Greenbreen": [ "editor" ], "Greenman": [ "editor" ], "GregXenon01": [ "editor" ], "Gretski247": [ "editor" ], "GreyCat": [ "editor" ], "Grin": [ "vrt-permissions" ], "Growl41": [ "editor" ], "Guaka": [ "editor" ], "Guanaco": [ "editor" ], "GuillermoHazebrouck": [ "editor" ], "Guus": [ "editor" ], "Guy vandegrift": [ "editor" ], "Guywan": [ "editor" ], "Gzuufy": [ "editor" ], "HLand": [ "editor" ], "HYanWong": [ "editor" ], "Ha98574": [ "editor" ], "Hagindaz": [ "editor" ], "HakanIST": [ "editor", "steward" ], "Hamish": [ "global-rollbacker", "vrt-permissions" ], "Hanay": [ "vrt-permissions" ], "Hannes Röst": [ "editor" ], "Hans Adler": [ "editor" ], "Haoreima": [ "editor" ], "Happy-melon": [ "editor" ], "Harry Wood": [ "editor" ], "Harrybrowne1986": [ "editor" ], "Harv4": [ "editor" ], "Hasley": [ "editor" ], "Hazard-SJ": [ "global-rollbacker" ], "He7d3r": [ "editor" ], "HenkvD": [ "editor" ], "Herbythyme": [ "editor" ], "Hercule": [ "editor" ], "Herman darman": [ "editor" ], "HerrHartmuth": [ "editor" ], "Hethrir": [ "editor" ], "HgDeviasse": [ "editor" ], "Hippias": [ "editor" ], "Hliow": [ "autoreview" ], "Holder": [ "global-rollbacker" ], "Holdoffhunger": [ "editor" ], "Hoo man": [ "editor", "steward" ], "HouseBlaster": [ "global-renamer" ], "Howard Beale": [ "editor" ], "Hpon": [ "editor" ], "Hrkalona": [ "autoreview" ], "Hskeet": [ "editor", "uploader" ], "Htm": [ "vrt-permissions" ], "Hugetim": [ "editor" ], "Humaira Ali": [ "editor" ], "Huntertur": [ "editor" ], "Hydriz": [ "global-rollbacker" ], "Ibidthewriter": [ "editor" ], "Ibrahim Sani Mustapha": [ "editor" ], "Ibrahim.ID": [ "vrt-permissions" ], "Icetruck": [ "editor" ], "Icodense": [ "global-rollbacker" ], "Ideasman42": [ "editor" ], "Igna": [ "editor" ], "Ijon": [ "vrt-permissions" ], "Illusional": [ "editor" ], "Iluvatar": [ "global-rollbacker", "vrt-permissions" ], "Indiana": [ "editor" ], "Inductiveload": [ "editor" ], "Inertia6084": [ "autoreview" ], "Inferno986return": [ "editor" ], "Infinite0694": [ "global-rollbacker", "global-sysop" ], "Ingenuity": [ "global-renamer" ], "Ingolemo": [ "editor" ], "Insignificantwrangler": [ "editor" ], "Internoob": [ "transwiki", "editor" ], "InverseHypercube": [ "editor" ], "Isenhand": [ "editor" ], "Ish ishwar": [ "editor" ], "Iste Praetor": [ "editor" ], "ItsNyoty": [ "vrt-permissions" ], "Itsmeyash31": [ "autoreview" ], "Itswikisam": [ "editor" ], "Itti": [ "global-renamer", "vrt-permissions" ], "Ixfd64": [ "editor" ], "J ansari": [ "global-rollbacker", "global-renamer" ], "J.palacios.jean": [ "editor" ], "J36miles": [ "editor" ], "JBW": [ "global-renamer" ], "JCrue": [ "editor" ], "JJ12880": [ "editor" ], "JJMC89": [ "vrt-permissions" ], "JJPMaster": [ "sysop", "global-rollbacker", "global-renamer", "interface-admin", "vrt-permissions" ], "JJPMaster (test 1)": [ "autoreview" ], "JJohnson": [ "editor" ], "JJohnson1701": [ "editor" ], "JPPINTO": [ "editor" ], "Jack Frost": [ "vrt-permissions" ], "JackBot": [ "editor" ], "JackPotte": [ "sysop", "interface-admin" ], "Jackhand1": [ "autoreview" ], "Jacob J. Walker": [ "editor" ], "Jafeluv": [ "global-rollbacker", "editor" ], "Jake Park": [ "global-renamer" ], "Jakec": [ "editor" ], "JamesCrook": [ "editor" ], "JamesNZ": [ "editor" ], "Jamesofur": [ "global-rollbacker" ], "Jamesssss": [ "editor" ], "Jamzze": [ "editor" ], "Jan Myšák": [ "global-rollbacker" ], "Jan.duggan": [ "autoreview" ], "Janbery": [ "global-rollbacker", "vrt-permissions" ], "Janpha": [ "editor" ], "Janschejbal": [ "editor" ], "Jason.Cozens": [ "editor" ], "Jaspalkaler": [ "editor" ], "Jasper Deng": [ "global-rollbacker" ], "JavaHurricane": [ "global-rollbacker", "editor" ], "Javier Carro": [ "editor" ], "JavierCantero": [ "editor" ], "Jay Bolero": [ "editor" ], "Jazzmanian": [ "editor" ], "Jcb": [ "editor", "vrt-permissions" ], "Jcwf": [ "editor" ], "Jeff G.": [ "global-rollbacker", "editor" ], "Jeff1138": [ "editor" ], "Jellysandwich0": [ "editor" ], "JenVan": [ "editor" ], "JenniferPalacios": [ "editor" ], "Jenniferjkidd": [ "editor" ], "Jens Østergaard Petersen": [ "editor" ], "JeremyMcCracken": [ "editor" ], "Jeroenr": [ "editor" ], "Jerome Charles Potts": [ "editor" ], "Jerry vlntn": [ "editor" ], "Jesdisciple": [ "editor" ], "Jfmantis": [ "editor" ], "Jianhui67": [ "global-rollbacker", "editor" ], "Jianhui67 public": [ "editor" ], "Jim Ashby": [ "autoreview" ], "JimKillock": [ "editor" ], "Jimbotyson": [ "editor" ], "Jimmy Xu": [ "vrt-permissions" ], "Jivee Blau": [ "vrt-permissions" ], "Jkauf007": [ "editor" ], "Jmdeschamps": [ "uploader" ], "Jnanaranjan sahu": [ "ombuds" ], "Jnewh001": [ "editor" ], "Jobin RV": [ "editor" ], "Joewiz": [ "editor" ], "Johannes Bo": [ "editor" ], "Johannnes89": [ "steward" ], "John Cross": [ "editor" ], "JohnMarcelo": [ "editor" ], "Johnkn63": [ "editor" ], "Johnwhelan": [ "editor" ], "Jokes Free4Me": [ "editor" ], "Jomegat": [ "editor" ], "Jon Harald Søby": [ "vrt-permissions" ], "Jon Kolbert": [ "steward", "vrt-permissions" ], "Jonathan Webley": [ "editor" ], "Jordan Brown": [ "editor" ], "JorisvS": [ "editor" ], "Josve05a": [ "vrt-permissions" ], "Jrincayc": [ "editor" ], "Jsnaree": [ "editor" ], "Jtneill": [ "editor" ], "JuethoBot": [ "autoreview" ], "Jugandi": [ "editor" ], "Jules*": [ "global-renamer" ], "Juliancolton": [ "global-rollbacker", "editor" ], "Jumark27": [ "editor" ], "JustTheFacts33": [ "editor" ], "Justlettersandnumbers": [ "global-renamer", "vrt-permissions" ], "K6ka": [ "global-rollbacker", "global-renamer" ], "Kadı": [ "global-renamer", "vrt-permissions" ], "Kai Burghardt": [ "editor" ], "Kaltenmeyer": [ "editor" ], "Kambai Akau": [ "editor" ], "Kanjy": [ "global-rollbacker", "editor" ], "Kapooht": [ "editor" ], "Karl Wick": [ "editor" ], "Karosent": [ "editor" ], "Kashkhan": [ "editor" ], "Kathryn Mary Nicholson": [ "autoreview" ], "Katiemgeorge": [ "editor" ], "Katyauchter": [ "editor" ], "Kaushlendratripathi": [ "editor" ], "Kaw8yh": [ "editor" ], "Kayau": [ "transwiki", "editor" ], "Kellen": [ "editor" ], "Kelti": [ "editor" ], "Kiefer.Wolfowitz": [ "editor" ], "Killarnee": [ "editor" ], "King of Hearts": [ "vrt-permissions" ], "Kingaustin07": [ "editor" ], "Kingofnuthin": [ "editor" ], "Kirito": [ "global-rollbacker", "editor" ], "Kittycataclysm": [ "sysop" ], "Kj cheetham": [ "global-renamer" ], "Kkmurray": [ "editor" ], "Kl-robertson": [ "editor" ], "Klaas van Buiten": [ "editor" ], "Knittedbees": [ "transwiki", "editor" ], "Knoppson": [ "autoreview" ], "Koantum": [ "editor" ], "Koavf": [ "global-rollbacker", "editor" ], "Kodos": [ "editor" ], "KonstantinaG07": [ "editor", "steward" ], "Kowey": [ "editor" ], "KrakatoaKatie": [ "vrt-permissions" ], "Krd": [ "vrt-permissions" ], "Krdbot": [ "vrt-permissions" ], "Kri": [ "editor" ], "Krinkle": [ "global-rollbacker" ], "Kropotkine 113": [ "vrt-permissions" ], "Kruusamägi": [ "vrt-permissions" ], "Ktucker": [ "editor" ], "Kwamikagami": [ "editor" ], "Kwhitefoot": [ "editor" ], "Kylu": [ "editor" ], "Kızıl": [ "global-renamer" ], "L10nM4st3r": [ "editor" ], "LABoyd2": [ "editor" ], "LR0725": [ "global-rollbacker", "global-sysop" ], "Ladislav": [ "editor" ], "Ladsgroup": [ "global-renamer" ], "Ladybug62": [ "editor" ], "Lagoset": [ "editor" ], "Larsnooden": [ "editor" ], "Laurianedani": [ "editor" ], "Lcraw005": [ "editor" ], "Ldo": [ "editor" ], "Leaderboard": [ "sysop", "global-renamer", "interface-admin" ], "Learnerktm": [ "editor" ], "Lechatjaune": [ "vrt-permissions" ], "Leighblackall": [ "editor" ], "Lengel46": [ "editor" ], "Lentokonefani": [ "global-renamer" ], "LeoChiukl": [ "editor" ], "Leonard64": [ "uploader" ], "Leonidlednev": [ "autoreview", "global-rollbacker" ], "Leovanderven": [ "editor" ], "Lesless": [ "vrt-permissions" ], "Leyo": [ "global-rollbacker" ], "Lgriot": [ "editor" ], "Liam987": [ "editor" ], "Liao": [ "editor" ], "Libperry": [ "editor" ], "Limiza": [ "editor" ], "Lionel Cristiano": [ "editor" ], "Litlok": [ "global-renamer" ], "Little Sunshine": [ "global-renamer" ], "Llakew": [ "editor" ], "LlamaAl": [ "editor" ], "Lobsteroh": [ "editor" ], "LodestarChariot2": [ "editor" ], "Lofty abyss": [ "global-rollbacker", "editor", "vrt-permissions" ], "Logictheo": [ "editor" ], "Lomita": [ "vrt-permissions" ], "Londonjackbooks": [ "editor" ], "Lovepeacejoy404": [ "editor" ], "Lp0 on fire": [ "autoreview" ], "Lubaochuan": [ "editor" ], "Luckas Blade": [ "editor" ], "Lucystewpid": [ "autoreview" ], "Ludovic Brenta": [ "editor" ], "Ludovicocaldara": [ "editor", "uploader" ], "Lukas²³": [ "editor" ], "LukeCEL": [ "editor" ], "Lvova": [ "vrt-permissions" ], "Lwill031": [ "editor" ], "M7": [ "steward" ], "MARKELLOS": [ "vrt-permissions" ], "MBq": [ "global-renamer" ], "MF-Warburg": [ "global-rollbacker", "global-sysop", "editor" ], "MGA73": [ "vrt-permissions" ], "MIacono": [ "editor" ], "MNeuschaefer": [ "editor" ], "MS Sakib": [ "global-renamer", "vrt-permissions" ], "Mabdul": [ "transwiki", "editor", "uploader" ], "Madisonhen": [ "autoreview" ], "Magda.dagda": [ "editor" ], "Magnus Manske": [ "editor" ], "Mahagaja": [ "editor" ], "MaikoM93": [ "editor" ], "Maire": [ "global-renamer" ], "Malarz pl": [ "global-renamer" ], "Manchiu": [ "global-renamer" ], "MandoRachovitsa": [ "autoreview" ], "Mandy Hopkins": [ "editor" ], "ManuelGR": [ "editor" ], "MarcGarver": [ "sysop", "checkuser", "steward" ], "Marco Klunder": [ "editor" ], "MarcoAurelio": [ "editor" ], "Marcus Cyron": [ "vrt-permissions" ], "Mardus": [ "editor" ], "MarkJFernandes": [ "editor" ], "MarkTraceur": [ "editor" ], "Markcwm": [ "editor" ], "Markhobley": [ "editor" ], "MarsRover": [ "editor" ], "Marshman~enwikibooks": [ "editor" ], "Martin Kraus": [ "editor" ], "Martin Sauter": [ "editor" ], "Martin Urbanec": [ "editor", "steward", "vrt-permissions" ], "MartinPoulter": [ "editor" ], "Martinwguy2": [ "editor" ], "MarygoldRules": [ "editor" ], "Master tongue": [ "editor" ], "Masti": [ "steward", "vrt-permissions" ], "Math buff": [ "editor" ], "MathXplore": [ "global-rollbacker", "editor" ], "Mathildem16": [ "autoreview" ], "Mathmensch": [ "editor" ], "Mathmensch-Smalledits": [ "editor" ], "Mathmogeek": [ "editor" ], "Maths314": [ "editor" ], "Matiia": [ "editor" ], "Matrix": [ "autoreview", "vrt-permissions" ], "Matsievsky": [ "editor" ], "Mattb112885": [ "editor" ], "Mattbarton.exe": [ "editor" ], "Matthewrb": [ "vrt-permissions" ], "Matttest": [ "autoreview" ], "Max Milas": [ "editor" ], "Maxim": [ "editor" ], "Maximillion Pegasus": [ "global-rollbacker", "editor" ], "Maxint2": [ "editor" ], "Mazbel": [ "global-rollbacker" ], "Mbch331": [ "vrt-permissions" ], "Mbrickn": [ "transwiki", "editor" ], "Mcdonnkm": [ "editor" ], "Mcld": [ "editor" ], "Mdkoch84": [ "editor" ], "Mdmckenzie": [ "editor" ], "MdsShakil": [ "steward", "vrt-permissions" ], "Mdupont": [ "editor" ], "Me Lendroz": [ "editor" ], "Meanmicio": [ "editor" ], "Mecanismo": [ "editor" ], "MediaKyle": [ "editor" ], "Meditation": [ "editor" ], "Meev0": [ "editor" ], "Mehman": [ "ombuds", "vrt-permissions" ], "Melos": [ "steward", "vrt-permissions" ], "MemicznyJanusz": [ "global-renamer" ], "Mendelivia~enwikibooks": [ "editor" ], "Meniktah": [ "editor" ], "Mercy": [ "global-rollbacker", "editor" ], "MerlLinkBot": [ "editor" ], "Mfield": [ "global-renamer" ], "Mh7kJ": [ "editor" ], "Michael Romanov": [ "editor" ], "MichaelFrey": [ "editor" ], "Michaelbluett": [ "editor", "uploader" ], "Mido": [ "vrt-permissions" ], "MihalOrela": [ "editor" ], "MiiCii": [ "editor" ], "Mike Hayes": [ "editor" ], "Mike.lifeguard": [ "editor" ], "Mild Bill Hiccup": [ "editor" ], "Mill3315": [ "editor" ], "Millbart": [ "vrt-permissions" ], "Mimarx": [ "editor" ], "Min1996": [ "autoreview" ], "Minorax": [ "global-rollbacker", "global-sysop", "editor" ], "Mirinano": [ "global-rollbacker" ], "Mithridates": [ "editor" ], "Mjbt": [ "editor" ], "Mjchael": [ "editor" ], "Mjkaye": [ "editor" ], "Mkline": [ "autoreview" ], "Mlipl001": [ "editor" ], "Moby-Dick4000": [ "editor" ], "Mohean": [ "editor" ], "Money-lover-12345": [ "editor" ], "Moonriddengirl": [ "autoreview", "vrt-permissions" ], "Mortense": [ "editor" ], "Mpfau": [ "editor" ], "Mr. Stradivarius": [ "editor" ], "MrAlanKoh": [ "editor" ], "MrJaroslavik": [ "global-rollbacker", "ombuds" ], "Mrajcok": [ "editor" ], "Mrjulesd": [ "editor" ], "Mrwojo": [ "editor" ], "Mschrag": [ "editor" ], "Msmithma": [ "editor" ], "MtPenguinMonster": [ "editor" ], "Mtarch11": [ "global-rollbacker", "global-sysop", "editor" ], "Musical Inquisit": [ "editor" ], "Mussklprozz": [ "vrt-permissions" ], "Mvolz": [ "editor" ], "Mwtoews": [ "editor" ], "Mxn": [ "editor" ], "Myklaw": [ "editor" ], "Mykola7": [ "steward" ], "Mys 721tx": [ "global-renamer", "vrt-permissions" ], "NDG": [ "global-rollbacker" ], "Nadzik": [ "global-rollbacker", "global-renamer" ], "NahidSultan": [ "vrt-permissions" ], "Nangkhan Magar": [ "editor" ], "Natuur12": [ "vrt-permissions" ], "Nbarth": [ "editor" ], "Nbro": [ "editor" ], "Nehaoua": [ "ombuds" ], "Neils51": [ "editor" ], "Nemoralis": [ "vrt-permissions" ], "Neojacob": [ "editor" ], "Neriah": [ "global-rollbacker", "global-renamer" ], "Nesbit": [ "editor" ], "Newlisp": [ "editor" ], "Nfgdayton": [ "editor" ], "NguoiDungKhongDinhDanh": [ "global-rollbacker", "editor" ], "NhacNy2412": [ "global-renamer" ], "Nick.anderegg": [ "editor" ], "NickPenguin": [ "editor" ], "NicoScribe": [ "editor" ], "Nicole Sharp": [ "editor" ], "Nieuwsgierige Gebruiker": [ "editor" ], "Nigos": [ "autoreview" ], "Nihonjoe": [ "global-renamer" ], "Nikai": [ "editor" ], "Ninjastrikers": [ "vrt-permissions" ], "NipplesMeCool": [ "editor" ], "Njardarlogar": [ "editor" ], "Nobody60": [ "editor" ], "Nolispanmo": [ "vrt-permissions" ], "Nomstuff": [ "autoreview" ], "Nonenmac": [ "editor" ], "Norton": [ "editor" ], "Npettiaux": [ "editor" ], "Nsaa": [ "vrt-permissions" ], "Nthep": [ "vrt-permissions" ], "NuclearWarfare": [ "global-rollbacker", "editor" ], "OMSMike": [ "editor" ], "Officer781": [ "editor" ], "OhanaUnited": [ "vrt-permissions" ], "Oleander": [ "editor" ], "Oliviacatherall": [ "autoreview" ], "Omphalographer": [ "editor" ], "OnBeyondZebrax": [ "editor" ], "Onsen": [ "editor" ], "Ontzak": [ "global-renamer" ], "Orderud": [ "editor" ], "OrenBochman": [ "editor" ], "Oshwah": [ "global-renamer" ], "Ottawahitech": [ "editor" ], "Owain.davies": [ "editor" ], "PAC": [ "editor" ], "PAC2": [ "editor" ], "PK 97": [ "editor" ], "PNW Raven": [ "editor" ], "Pac8612": [ "editor" ], "Paloi Sciurala": [ "global-rollbacker" ], "Panic2k4": [ "transwiki", "editor" ], "Pascal Pignard": [ "editor" ], "Pastbury": [ "editor" ], "Pathfinders": [ "editor" ], "Pathoschild": [ "editor" ], "Patrik": [ "editor" ], "PauSix": [ "editor" ], "Paul James": [ "editor" ], "Pavroo": [ "editor" ], "PbakerODU": [ "editor" ], "Pbrower2a": [ "editor" ], "Peacearth": [ "global-renamer" ], "Pearts": [ "editor" ], "Peeragogia": [ "editor" ], "Peri Coleman": [ "editor" ], "Perl~enwikibooks": [ "editor" ], "Peter1180": [ "editor" ], "PeterEasthope": [ "editor" ], "Peyton09": [ "editor" ], "Phan M. Nhat": [ "autoreview" ], "PhilKnight": [ "global-renamer" ], "Phoebe": [ "editor" ], "Phosgram": [ "editor" ], "Pi zero": [ "editor" ], "PieWriter": [ "editor" ], "Piotrus": [ "editor" ], "Pithikos": [ "editor" ], "Pittsburgh Poet": [ "editor" ], "Pjpearce": [ "editor" ], "Pkkao": [ "editor" ], "Planotse": [ "editor" ], "Platonides": [ "vrt-permissions" ], "Pluke": [ "editor" ], "PlyrStar93": [ "global-rollbacker", "editor" ], "Pminh141": [ "global-renamer" ], "Pmlineditor": [ "editor" ], "Pmw57": [ "editor" ], "Poetcsw": [ "editor" ], "PoizonMyst": [ "editor" ], "Pola 2607": [ "autoreview" ], "Polimerek": [ "vrt-permissions" ], "Polluks": [ "editor" ], "Pookiyama": [ "editor" ], "Popski": [ "editor" ], "Povigna": [ "editor" ], "Ppolar bear": [ "global-rollbacker", "global-renamer" ], "Pppery": [ "autoreview" ], "Prahlad balaji": [ "editor" ], "Pratyeka": [ "editor" ], "Praxidicae": [ "global-rollbacker", "global-sysop", "editor" ], "Primefac": [ "vrt-permissions" ], "Prince Kassad~enwikibooks": [ "editor" ], "Pronesto": [ "editor" ], "Prototyperspective": [ "autoreview" ], "Psoup": [ "editor" ], "Psr1909": [ "editor" ], "PullUpYourSocks": [ "editor" ], "PurpleBuffalo": [ "global-renamer" ], "PurplePieman": [ "editor" ], "Purplebackpack89": [ "editor" ], "Putukas01": [ "editor" ], "Qenalcu": [ "autoreview" ], "Quebecguy": [ "global-rollbacker" ], "QueerEcofeminist": [ "global-rollbacker", "global-renamer", "editor" ], "Quinlan83": [ "global-rollbacker", "editor" ], "Quintucket": [ "editor" ], "Qwerty number1": [ "editor" ], "Qwertyus": [ "editor" ], "Qədir": [ "global-rollbacker", "global-renamer", "vrt-permissions" ], "R. Henrik Nilsson": [ "editor" ], "RAdimer-WMF": [ "global-rollbacker" ], "RDBury": [ "editor" ], "RJHall": [ "editor" ], "Ra'ike": [ "vrt-permissions" ], "Rachboots": [ "editor" ], "Rachel": [ "editor" ], "Rachmat04": [ "global-renamer", "vrt-permissions" ], "RadiX": [ "editor", "steward", "vrt-permissions" ], "Raffaela Kunz": [ "editor" ], "Rahulkepapa": [ "editor" ], "Ramac": [ "editor" ], "Rambam rashi": [ "editor" ], "Randykitty": [ "autoreview", "global-rollbacker" ], "RatónMístico176": [ "editor" ], "Ravichandar84": [ "editor" ], "Rawheatley": [ "editor" ], "Ray Trygstad": [ "editor" ], "RayeChellMahela": [ "editor" ], "Raymond": [ "vrt-permissions" ], "Razr Nation": [ "editor" ], "Rchaswms01": [ "editor" ], "Rcragun": [ "editor", "uploader" ], "Readyokaygo": [ "editor" ], "Recent Runes": [ "editor" ], "Redlentil": [ "editor" ], "Refcanimm": [ "editor" ], "Regasterios": [ "vrt-permissions" ], "Reinhard Kraasch": [ "vrt-permissions" ], "RenaissanceMan2144": [ "autoreview" ], "Renamed user 242094acfb1a5b2f08e9e78f2e021a40": [ "editor" ], "Renamed user 5f91ca71739b07cfce8397eed758fe13": [ "editor", "uploader" ], "Renamed user f26394dcb19bd7bdad78f0d752896653": [ "editor" ], "Renvoy": [ "global-rollbacker", "global-sysop" ], "Reseletti": [ "editor" ], "Retropunk": [ "editor" ], "Reuben1508": [ "autoreview" ], "Revi C.": [ "global-rollbacker", "global-renamer", "ombuds", "editor", "vrt-permissions" ], "Reyk": [ "editor" ], "Rfc1394": [ "editor" ], "Rgdboer": [ "editor" ], "Rgreenone": [ "editor" ], "Rhole2001": [ "autoreview" ], "Rich Farmbrough": [ "editor" ], "Rickstambaugh": [ "editor" ], "Riggwelter": [ "vrt-permissions" ], "Risk": [ "editor" ], "Risteall": [ "editor" ], "Ritjesman": [ "editor" ], "RoMancer": [ "editor" ], "Robbiemorrison": [ "editor" ], "Robert Huber~enwikibooks": [ "editor" ], "Roberto Mura": [ "editor" ], "Robertsky": [ "global-renamer", "vrt-permissions" ], "RobinH": [ "editor" ], "Rodasmith": [ "editor" ], "Rodrigo": [ "editor" ], "Rodrigo.Argenton": [ "vrt-permissions" ], "Rogerborrell": [ "editor" ], "Rogerdpack": [ "editor" ], "RogueScholar": [ "editor" ], "Romainbehar": [ "editor" ], "RomaineBot": [ "vrt-permissions" ], "RonaldB": [ "vrt-permissions" ], "Rosser1954": [ "editor" ], "Rotlink": [ "editor" ], "RoySmith": [ "ombuds" ], "Rozzychan": [ "editor" ], "Rplano": [ "editor" ], "Rreagan007": [ "autoreview" ], "Rrgreen": [ "editor" ], "Rschen7754": [ "global-rollbacker", "editor" ], "RshieldsVA": [ "editor" ], "Rsjaffe": [ "global-renamer" ], "Rtaisis": [ "editor" ], "Ruakh": [ "editor" ], "Rudolpho~enwikibooks": [ "editor" ], "Runfellow": [ "editor" ], "Runner4lyfe": [ "editor" ], "RunningBlind": [ "editor" ], "Ruthven": [ "vrt-permissions" ], "Ruud Koot": [ "transwiki", "editor" ], "Rzuwig": [ "autoreview", "global-rollbacker" ], "S8321414": [ "global-renamer" ], "SB Johnny": [ "editor" ], "SCP-2000": [ "global-rollbacker", "vrt-permissions" ], "SHB2000": [ "sysop", "steward" ], "SPM": [ "editor" ], "Sae1962": [ "editor" ], "Safuan12616": [ "editor" ], "SahniM": [ "editor" ], "Sakretsu": [ "steward" ], "Sakura emad": [ "global-rollbacker" ], "Salil Kumar Mukherjee": [ "editor" ], "Samat": [ "vrt-permissions" ], "Sammy2012": [ "editor" ], "Samuel.dellit": [ "editor" ], "Samuele2002": [ "global-rollbacker", "editor" ], "Samwilson": [ "editor" ], "SanBonne": [ "global-renamer", "vrt-permissions" ], "Sandbergja": [ "editor" ], "Sannita": [ "vrt-permissions" ], "Sante Caserio~enwikibooks": [ "editor" ], "SarahFatimaK": [ "editor" ], "Sargoth": [ "vrt-permissions" ], "Saroj": [ "global-rollbacker" ], "Sascha Lill 95": [ "editor" ], "Satdeep Gill": [ "vrt-permissions" ], "Savh": [ "global-rollbacker", "editor" ], "Sbb1413": [ "editor" ], "Scention": [ "editor" ], "Schniggendiller": [ "steward" ], "SchreiberBike": [ "editor" ], "Scott.beckman": [ "editor" ], "Sebastian Wallroth": [ "vrt-permissions" ], "Seewolf": [ "global-rollbacker", "vrt-permissions" ], "Selden": [ "editor" ], "Sennecaster": [ "vrt-permissions" ], "Serinap": [ "editor" ], "Seth Miller": [ "editor" ], "SevenSpheres": [ "editor" ], "Sfan00 IMG": [ "editor" ], "Sfoerster": [ "editor" ], "Sgarrigan": [ "editor" ], "Sgowal": [ "editor" ], "Shaitand": [ "editor" ], "ShakespeareFan00": [ "editor" ], "SharingNotes": [ "editor" ], "Shawntanchinyang": [ "editor" ], "Shdwninja8": [ "editor" ], "ShelleyAdams": [ "autoreview" ], "ShifaYT": [ "global-rollbacker" ], "Shii": [ "editor" ], "Shira the Mogul": [ "editor" ], "Shlomif": [ "editor" ], "ShuBraque": [ "editor" ], "Sidelight12": [ "editor" ], "Sidorkin": [ "editor" ], "Sidpatil": [ "editor" ], "Siebengang": [ "editor" ], "Sigma 7": [ "editor" ], "Simon Peter Hughes": [ "editor" ], "Sinus46": [ "editor" ], "Sir Beluga": [ "editor" ], "Sir Lestaty de Lioncourt": [ "vrt-permissions" ], "SixWingedSeraph": [ "editor" ], "Sj": [ "editor" ], "Sjc~enwikibooks": [ "editor" ], "Sjlegg": [ "editor" ], "Sjone101": [ "editor" ], "Sjö": [ "global-rollbacker" ], "Skymath": [ "editor" ], "Slava Ukraini Heroyam Slava 123": [ "editor", "uploader" ], "Slava Ukrajini Heroyam Slava": [ "editor" ], "Sluffs": [ "editor" ], "Smjg": [ "editor" ], "SnappyDragonPennyroyal": [ "editor" ], "SocialKnowledge": [ "editor" ], "SoftwareEngineerMoose": [ "autoreview" ], "Sonia": [ "editor" ], "Sophie Cheng": [ "editor" ], "Sotiale": [ "steward" ], "Soul windsurfer": [ "editor" ], "SouthParkFan65": [ "editor" ], "SoylentGreen": [ "editor" ], "Spamduck": [ "editor" ], "Spaynton": [ "editor" ], "Spender2001": [ "editor" ], "Speregrination": [ "editor" ], "Spiderworm": [ "editor" ], "Spoon!": [ "editor" ], "Squasher": [ "global-renamer" ], "Srhat": [ "editor" ], "Stang": [ "global-rollbacker", "editor", "vrt-permissions" ], "Stanglavine": [ "editor" ], "Steinsplitter": [ "global-renamer", "vrt-permissions" ], "StephT0704": [ "autoreview" ], "Stepheng3": [ "editor" ], "Stepro": [ "vrt-permissions" ], "Steve M": [ "editor" ], "Stilfehler": [ "editor" ], "Stockywood": [ "editor" ], "Storeye": [ "editor" ], "Strainu": [ "vrt-permissions" ], "Strange quark": [ "editor" ], "Stryn": [ "global-rollbacker", "editor" ], "Stïnger": [ "global-rollbacker", "editor" ], "Suchenwi": [ "editor" ], "Sumone10154": [ "editor" ], "SunCreator": [ "editor" ], "Sunny Cryolite": [ "global-rollbacker" ], "Sunshineconnelly": [ "editor" ], "SuperTyphoonNoru": [ "editor" ], "Superbass": [ "vrt-permissions" ], "Superpes15": [ "global-rollbacker", "global-renamer", "global-sysop", "vrt-permissions" ], "Supertoff": [ "vrt-permissions" ], "Superzerocool": [ "vrt-permissions" ], "SupremeUmanu": [ "editor" ], "Suruena": [ "editor" ], "Sutambe": [ "editor" ], "Sutton Publishing": [ "editor" ], "Sué González Hauck": [ "editor" ], "Svartava": [ "global-rollbacker", "global-renamer", "global-sysop", "editor" ], "SweetCanadianMullet": [ "editor" ], "Swift": [ "editor" ], "SyG": [ "editor" ], "Sylvesterchukwu04": [ "editor" ], "Sylvialim": [ "editor" ], "Sylviaread": [ "editor" ], "Synoman Barris": [ "global-rollbacker", "transwiki", "editor" ], "Syum90": [ "global-rollbacker", "editor" ], "Syunsyunminmin": [ "global-rollbacker", "global-renamer", "global-sysop", "editor" ], "T.seppelt": [ "editor" ], "TDang": [ "editor" ], "TTWIDEE": [ "editor" ], "Tahmid": [ "editor" ], "Taiwania Justo": [ "vrt-permissions" ], "Taketa": [ "global-renamer" ], "Takipoint123": [ "vrt-permissions" ], "TakuyaMurata": [ "editor" ], "Tamzin": [ "global-renamer" ], "Tanbiruzzaman": [ "global-rollbacker", "global-renamer", "global-sysop", "editor", "vrt-permissions" ], "Tannertsf": [ "editor" ], "Taoheedah": [ "editor" ], "Tapsevarg": [ "editor" ], "TaronjaSatsuma": [ "vrt-permissions" ], "Taxman": [ "editor" ], "Tchoř": [ "global-renamer" ], "Tdkehoe": [ "editor" ], "Tdvorak": [ "editor" ], "Techman224": [ "editor" ], "Tegel": [ "editor", "steward" ], "Teles": [ "ombuds", "steward", "vrt-permissions" ], "Tem5psu": [ "editor" ], "Tempodivalse": [ "editor" ], "TenWhile6": [ "global-rollbacker", "global-renamer", "global-sysop", "editor" ], "Terence Kearey": [ "editor" ], "Ternarius": [ "global-renamer" ], "Ternera": [ "global-rollbacker", "global-renamer", "global-sysop", "editor" ], "Tesleemah": [ "editor" ], "Tevfik AKTUĞLU": [ "editor" ], "Tgregtregretgtr": [ "editor" ], "ThatBPengineer": [ "autoreview" ], "Thatonewikiguy": [ "editor" ], "The Squirrel Conspiracy": [ "vrt-permissions" ], "The labs": [ "editor" ], "TheGoodEndedHappily": [ "vrt-permissions" ], "ThePCKid": [ "editor" ], "TheSandDoctor": [ "global-renamer", "vrt-permissions" ], "Theknightwho": [ "editor" ], "Thenub314": [ "editor" ], "Theo Hughes": [ "editor" ], "Theornamentalist": [ "editor" ], "Thereen": [ "editor" ], "Thewinster": [ "editor" ], "Thierry Dugnolle": [ "editor" ], "Thinkglobalnow": [ "editor" ], "Thirunavukkarasye-Raveendran": [ "editor" ], "Thomas Simpson": [ "editor" ], "Thomas.haslwanter": [ "editor" ], "Thomas.lochmatter": [ "editor" ], "Tibetologist": [ "editor" ], "Tigerzeng": [ "global-rollbacker" ], "Tiled": [ "editor" ], "TimBorgNetzWerk": [ "editor" ], "Timothy Gu": [ "editor" ], "Timpo": [ "editor" ], "Tiptoety": [ "editor" ], "Tjyang": [ "editor" ], "Tlustulimu": [ "editor" ], "Tmvogel": [ "editor" ], "Tom Morris": [ "editor" ], "Tomato86": [ "editor" ], "Tomt87": [ "editor" ], "Tomybrz": [ "editor" ], "Tonyvall": [ "autoreview" ], "Tp42": [ "editor" ], "Tracklayingninja": [ "editor" ], "Tradimus": [ "editor" ], "Tropicalkitty": [ "global-rollbacker", "editor" ], "TrulyShruti": [ "editor" ], "Ts12rAc": [ "global-rollbacker" ], "Tsarina CatarinaToo": [ "autoreview" ], "TunnelESON": [ "sysop" ], "Turbojet": [ "vrt-permissions" ], "Turkmen": [ "editor" ], "TwoThirty": [ "editor" ], "Tyoyafud": [ "editor" ], "Túrelio": [ "autoreview" ], "U$3rname008": [ "editor" ], "Uf.hun2201": [ "editor" ], "Ulubatli Hasan": [ "global-renamer" ], "Uncitoyen": [ "global-rollbacker", "global-renamer" ], "Uncle G": [ "editor" ], "Unixxx": [ "editor" ], "User01938": [ "editor" ], "Username222": [ "editor" ], "Utcursch": [ "vrt-permissions" ], "Uziel302": [ "editor" ], "Uzume": [ "editor" ], "VIGNERON": [ "steward" ], "Valery Starikov": [ "editor" ], "Van der Hoorn": [ "editor" ], "Varnent": [ "vrt-permissions" ], "Vdolar": [ "autoreview" ], "VectorVoyager": [ "editor" ], "Venzz": [ "vrt-permissions" ], "Verfassungsfreund": [ "editor" ], "Veritas Sapientiae": [ "global-rollbacker", "global-renamer", "vrt-permissions" ], "Vermont": [ "editor", "steward", "vrt-permissions" ], "Victor Stefan Stoica": [ "autoreview" ], "Victor Trevor": [ "autoreview" ], "Victoria.sandeman": [ "autoreview" ], "Vincent Vega": [ "global-renamer" ], "Vito Genovese": [ "editor" ], "Vituzzu": [ "editor" ], "Vladimir Solovjev": [ "global-renamer", "vrt-permissions" ], "Vogone": [ "global-rollbacker", "editor" ], "Vossman": [ "editor" ], "Vrinda": [ "editor" ], "VulcanWikiEdit": [ "editor" ], "Vwanweb": [ "editor" ], "WOSlinker": [ "autoreview" ], "Waihorace": [ "global-rollbacker" ], "Waldyrious": [ "editor" ], "WalshDay": [ "editor" ], "Wargo": [ "editor" ], "Wbjimmyd": [ "editor" ], "Wcoole": [ "editor" ], "WeelkyWikiReader": [ "editor" ], "Wekeepwhatwekill": [ "autoreview" ], "WereSpielChequers": [ "editor" ], "What no2000": [ "editor" ], "WhatamIdoing": [ "editor" ], "WhitePhosphorus": [ "global-rollbacker", "global-sysop" ], "Whiteknight": [ "editor" ], "Whoop whoop pull up": [ "editor" ], "Whym": [ "editor", "vrt-permissions" ], "Wiki13": [ "editor" ], "WikiBayer": [ "global-rollbacker", "global-sysop", "editor" ], "WikiFer": [ "global-renamer", "vrt-permissions" ], "Wikimi-dhiann": [ "editor" ], "Wikiotics": [ "editor" ], "Wikiwau": [ "autoreview", "editor" ], "WillNess": [ "editor" ], "Willscrlt": [ "editor" ], "Wim b": [ "global-rollbacker", "global-sysop", "editor" ], "Wisden": [ "editor" ], "Withinfocus": [ "editor" ], "Wj32": [ "editor" ], "Wkee4ager": [ "editor" ], "Wobbit": [ "editor" ], "Wong128hk": [ "global-renamer" ], "Wundermacht": [ "editor" ], "Wutsje": [ "global-rollbacker", "editor" ], "Ww2censor": [ "vrt-permissions" ], "Wüstenspringmaus": [ "global-rollbacker", "global-renamer" ], "XXBlackburnXx": [ "editor", "steward" ], "Xandradi": [ "editor" ], "Xania": [ "sysop", "checkuser" ], "Xaosflux": [ "editor", "steward" ], "XenonX3": [ "vrt-permissions" ], "Xerol": [ "editor" ], "Xeverything11": [ "editor", "uploader" ], "Xhungab": [ "editor" ], "Xinkai Wu": [ "editor" ], "Xixtas": [ "editor" ], "Xqt": [ "global-rollbacker" ], "Xxagile": [ "editor" ], "Xypron": [ "editor" ], "Xz64": [ "editor" ], "Y-S.Ko": [ "editor" ], "YMS": [ "editor" ], "Yahya": [ "steward", "vrt-permissions" ], "Yamla": [ "global-renamer" ], "Yann": [ "editor" ], "Yerpo": [ "global-renamer", "vrt-permissions" ], "Yikrazuul": [ "editor" ], "Ymblanter": [ "global-rollbacker" ], "Yndesai": [ "editor" ], "Youssefsan": [ "editor" ], "Ysangkok": [ "editor" ], "Yvelik": [ "uploader" ], "Yzmo": [ "editor" ], "ZI Jony": [ "editor" ], "Zabe": [ "global-rollbacker" ], "Zafer": [ "ombuds" ], "Zedshort": [ "editor" ], "ZeroOne": [ "editor" ], "Zetud": [ "global-rollbacker", "vrt-permissions" ], "Ziv": [ "editor" ], "Zoeannl": [ "editor" ], "Zollerriia": [ "editor" ], "Zoohouse": [ "editor" ], "Zoot": [ "editor" ], "Zsohl": [ "autoreview", "editor" ], "Zvsmith": [ "editor" ], "Zweighaft": [ "editor" ], "ZxxZxxZ": [ "editor" ], "~riley": [ "global-rollbacker", "editor" ], "Érico": [ "global-renamer" ], "Виктор Пинчук": [ "editor" ], "Воображение": [ "editor" ], "Всевидящий": [ "global-rollbacker" ], "Д.Ильин": [ "editor" ], "Л.П. Джепко": [ "editor" ], "יהודה שמחה ולדמן": [ "editor" ], "מקף": [ "global-rollbacker", "global-renamer" ], "د. فارس الجويلي": [ "global-renamer" ], "علاء": [ "steward", "vrt-permissions" ], "فيصل": [ "global-renamer", "vrt-permissions" ], "सीमा1": [ "editor" ], "タチコマ robot": [ "editor" ], "ネイ": [ "global-renamer" ], "人间百态": [ "global-rollbacker" ], "臺灣象象": [ "autoreview" ], "范": [ "vrt-permissions" ], "青子守歌": [ "vrt-permissions" ], "魔琴": [ "global-rollbacker" ], "ꠢꠣꠍꠘ ꠞꠣꠎꠣ": [ "editor" ], "기나ㅏㄴ": [ "global-rollbacker", "global-renamer" ] } qcx22tzazgzs66rnphx8wxlj9thr75i 102 474496 4634113 4614591 2026-05-04T16:17:21Z SHE-LOVES-BRIAN 3581157 added a wiki link 4634113 wikitext text/x-wiki {{Incomplete recipe|reason=missing categories; What does it mean to "extract the juice using warm water"?}}__NOTOC__ {{Recipe summary | Category = Soup recipes | Yield = 4 servings | Difficulty = 2 | Image = [[File:Banga Soup.jpg|300px]] }} {{Recipe}} '''Banga soup''' is a traditional Nigerian soup made from palm nut extract, typically enjoyed by the Urhobo and Itsekiri people of the Niger Delta. It is rich, flavorful, and often served with [[Cookbook:Nigerian starch|starch]] or other swallow foods. == Ingredients == * 4 cups raw [[Cookbook: Oil Palm Fruit|palm nuts]] or 800 ml canned palm nut extract * 500 g assorted [[Cookbook:Meat|meat]] (beef, goat meat, tripe) * 1–2 pieces [[Cookbook:Dryfish|dried fish]] (washed and deboned) * 1 [[Cookbook: Dehydrated Broth|stock cube]] (Maggi or Knorr) * [[Cookbook:Salt|Salt]] to taste * 1 tablespoon [[Cookbook: Ground Crayfish|ground crayfish]] * 1 small [[Cookbook: Onion|onion]] (chopped) * 1 teaspoon Banga spice mix (optional but traditional) * [[Cookbook:Scent Leaf|Scent leaves]] (or substitute with basil) * [[Cookbook: Water|Water]] (as needed) == Procedure == # If using raw palm nuts, boil until soft, then pound lightly and extract the juice using warm water. Strain to remove the chaff. If using canned extract, skip this step. # Place the assorted meat and dried fish in a pot. Add chopped onions, stock cube, and salt. Add a small amount of water and boil until the meat is tender. # Pour in the palm nut extract. Add more water if too thick. Stir well and bring to a boil. # Add ground crayfish and Banga spice mix. Allow to cook uncovered on medium heat for 15–20 minutes, or until the oil begins to rise to the top. # Add scent leaves (or basil) and cook for another 5 minutes. # Remove from heat and serve hot with starch, fufu, pounded yam, or rice. == Notes, tips, and variations == * Canned palm nut concentrate saves time and is commonly available in African stores. * Banga spice mix can be homemade or store-bought. A typical mix includes oburunbebe stick, aidan fruit, rohoje, and beletientien. * You can substitute scent leaves with basil or bitterleaf, depending on availability and taste preference. * Add fresh pepper if you like it spicy. * For a richer flavor, include smoked catfish or periwinkle. * Banga soup is traditionally eaten with starch in Delta state, but pounded yam or eba is common in other regions. [[Category:Nigerian recipes]] [[Category:Recipes for soup]] [[Category:Recipes using meat]] gfaf0r09tjedqfk60vcw24nvm40gn3h 10 481575 4634139 4618239 2026-05-04T18:03:03Z Kittycataclysm 3371989 4634139 wikitext text/x-wiki {{ {{{|safesubst:}}}ifsubst |<includeonly>{{subst:Unsubst|How much| name|{{{name|¬}}}|reason|{{{reason|¬}}}| date|{{{date|{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}}}} }}</includeonly>| {{Fix |name={{{name|How much}}} |link=Cookbook:Policy/Recipe template#Ingredients |text=how much? |class=Template-Fact |title=The cook needs more guidance on the quantity |date={{{date|}}} |cat= }} }}<noinclude>{{Documentation}}</noinclude> bnjxskkim1waq8im9o5uoz0gcpt1hl9 4634140 4634139 2026-05-04T18:04:11Z Kittycataclysm 3371989 Kittycataclysm moved page [[User:Kittycataclysm/sandbox]] to [[Template:How much]] without leaving a redirect: updating template based on [[Template:citation needed]] 4634139 wikitext text/x-wiki {{ {{{|safesubst:}}}ifsubst |<includeonly>{{subst:Unsubst|How much| name|{{{name|¬}}}|reason|{{{reason|¬}}}| date|{{{date|{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}}}} }}</includeonly>| {{Fix |name={{{name|How much}}} |link=Cookbook:Policy/Recipe template#Ingredients |text=how much? |class=Template-Fact |title=The cook needs more guidance on the quantity |date={{{date|}}} |cat= }} }}<noinclude>{{Documentation}}</noinclude> bnjxskkim1waq8im9o5uoz0gcpt1hl9 0 481710 4634072 4632705 2026-05-04T13:35:43Z Shira the Mogul 3560559 /* Unit 20: Qing-RoC Literature */ Two good ones 4634072 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== <!--- 日本書記, etc. ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} 35ie6u0lamnkme95yb919nmk3cov457 4634073 4634072 2026-05-04T13:42:20Z Shira the Mogul 3560559 /* Unit 18: Buddhist Literature */ I'm working on a translation with someone here and the wording is super simple, perfect for this. 4634073 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== <!--- 日本書記, etc. ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} f8jqd7punvf9zucbkux214kmc1f89g2 4634076 4634073 2026-05-04T13:50:23Z Shira the Mogul 3560559 /* Unit 6: Nation Focus - Japan */ Sword and stele 4634076 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== # [[/The Inariyama Sword/]] <!--- short and sweet! ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/The Oldest Inscription in Japan/]] <!--- 宇治橋断碑 ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> # [[/Reading the History of Japan with Prince Toneri/]] <!--- 日本書記, etc. ---> <!--- # [[/Occupying Taiwan/]] ---> <!--- I have some colonial literature on me that can be used here. ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} m00neyjrtrrjyidru1u7aq0b2qhp1iq 4634077 4634076 2026-05-04T13:52:30Z Shira the Mogul 3560559 /* Unit 6: Nation Focus - Japan */ Diary 4634077 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== # [[/The Inariyama Sword/]] <!--- short and sweet! ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/The Oldest Inscription in Japan/]] <!--- 宇治橋断碑 ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> # [[/The Diary of Fujiwara no Teika/]] <!--- 明月記 ---> # [[/Reading the History of Japan with Prince Toneri/]] <!--- 日本書記, etc. ---> <!--- # [[/Occupying Taiwan/]] ---> <!--- I have some colonial literature on me that can be used here. ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} j9wb8rum2n7w54uilwgui9m5kb2fyz5 4634078 4634077 2026-05-04T13:55:31Z Shira the Mogul 3560559 /* Unit 12: Literary Chinese in Medicine */ Extremely early Dutch translation 4634078 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== # [[/The Inariyama Sword/]] <!--- short and sweet! ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/The Oldest Inscription in Japan/]] <!--- 宇治橋断碑 ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> # [[/The Diary of Fujiwara no Teika/]] <!--- 明月記 ---> # [[/Reading the History of Japan with Prince Toneri/]] <!--- 日本書記, etc. ---> <!--- # [[/Occupying Taiwan/]] ---> <!--- I have some colonial literature on me that can be used here. ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> # [[/Anatomy with Sugita Genpaku/]] <!--- 解体新書 ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} 5gjyt18b4es5t2waahsmilhqne6tmr4 4634079 4634078 2026-05-04T13:57:15Z Shira the Mogul 3560559 4634079 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== # [[/The Inariyama Sword/]] <!--- short and sweet! ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/The Oldest Inscription in Japan/]] <!--- 宇治橋断碑 ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> # [[/The Diary of Fujiwara no Teika/]] <!--- 明月記 ---> # [[/Reading the History of Japan with Prince Toneri/]] <!--- 日本書記, etc. ---> <!--- # [[/Occupying Taiwan/]] ---> <!--- I have some colonial literature on me that can be used here. ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> # [[/Anatomy with Sugita Genpaku/]] <!--- 解体新書 ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. Look at Japan's 五山文学 ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} ts5ckbxpfn1d34w9hy2z9s4p6fgmgxh 4634080 4634079 2026-05-04T14:01:34Z Shira the Mogul 3560559 /* Unit 6: Nation Focus - Japan */ Shintoism! 4634080 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== # [[/The Inariyama Sword/]] <!--- short and sweet! ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/The Oldest Inscription in Japan/]] <!--- 宇治橋断碑 ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> # [[/Shinto Teachings with Honda Chikaatsu/]] <!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---> # [[/The Diary of Fujiwara no Teika/]] <!--- 明月記 ---> # [[/Reading the History of Japan with Prince Toneri/]] <!--- 日本書記, etc. ---> <!--- # [[/Occupying Taiwan/]] ---> <!--- I have some colonial literature on me that can be used here. ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> # [[/Anatomy with Sugita Genpaku/]] <!--- 解体新書 ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. Look at Japan's 五山文学 ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} g5nbjciopaoj8ftlclc8bmcfpaius57 4634082 4634080 2026-05-04T14:04:12Z Shira the Mogul 3560559 /* Unit 1: Basic Skills */ This is amazing wtf 4634082 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武，大/小，厚/薄，橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象，三靈…… ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 30 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/What are Chinese characters, anyway?/]] <!--- deploy several single-radical texts---> # [[/How do we write Chinese?/]] # [[/Tilling the Fields with 有/]] # [[/The Sun and the Moon/]] # [[/Weapons and Metals/]] # [[/Recognizing Phonetics/]] <!--- time to deploy my one-syllable articles! ---> # [[/Cangjie Created Characters/]] ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] <!--- It is hard to find authentic materials for this ---> # [[/One, Two, Left, and Right with Gongsun Long/]] <!--- 曰：「二有一乎？」 曰：「二無一。」 曰：「二有右乎？」 曰：「二無右。」 曰：「二有左乎？」 曰：「二無左。」 曰：「右可謂二乎？」 曰：「不可。」 曰：「左可謂二乎？」 曰：「不可。」 曰：「左與右可謂二乎？」 曰：「可。」 ---> # [[/The Heavenly Stems/]] <!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---> # [[/Tell the Time with Earthly Branches/]] <!--- Introduce verbs and timekeeping ---> # [[/Lunar Dates with the Spring and Autumn Annals/]] <!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---> # [[/Skimming for Major Events in Historical Annals/]] <!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701 Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! ---> # [[/Dinner with the Daimyo/]] <!-- 侍宴·大友皇子 皇明光日月，帝徳載天地。 三才併秦昌，万国表臣義。 --> # [[/In Discourse with Jibong/]] <!-- 芝峰類說 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 --> # [[/Shinto FAQ with Honda Chikaatsu/]] <!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 問 天帝無始無終乎。 對 天帝無始無終也。 旣以無始無終之力 與無始無終之體 造無始無終之萬物。 其功亦無始無終也。 問 天地大原在道乎。 對 天地大原實在道。 鬼神依道而立。 人民依道而活。 萬物依道而息。 This is great! ---> <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to explain how Sinitic Poetry rhymes and the themes it contains. * Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- 春江花月夜·楊廣 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 This is really simple and can elucidate Ping-Ze easily. ---> # [[/To Study the Odes/]] <!-- 蟋蟀·姬旦 國風·唐風 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。 --> <!-- 黃鳥 小雅·鴻鴈之什 黃鳥黃鳥，無集于穀，無啄我粟。 此邦之人，不我肯穀。言旋言歸，復我邦族。 黃鳥黃鳥，無集于桑，無啄我粱。 此邦之人，不可與明。言旋言歸，復我諸兄。 黃鳥黃鳥，無集于栩，無啄我黍。 此邦之人，不可與處。言旋言歸，復我諸父。 --> # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] <!--- 西湖竹枝詞·布哈特穆爾 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 宫词·布哈特穆爾 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 Mongol writer from the Uyghur Kingdom of Gaochang Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC) ---> # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！ Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火，元火復還生。 若為木無火，鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞，垂陰動百尋。 李膺真烈烈，和嶠自森森。 桃李何堪較，雪霜安得侵。 萬年身不老，種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草，班蘭最有名。 深根將綠茁，長葉亦叢生。 取味迎賓合，入厨任水烹。 可憐經一用，擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/On a Journey with Sa Dula/]] <!--- 無題·薩都剌 為客三年海上洲，故鄉何處瘴雲稠。 數千里外蠻人域，十八灘頭過客舟。 時有山禽呼姓字，或從海鳥作朋儔。 故人珂珮周旋處，紫殿風清十二樓。 https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C) A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone. ---> <!--- 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋，詩興與秋高。 千古風流人物，一時多少雄豪。 霜清玉塞，雲飛隴首，風落江皋。 夢到鳳凰台上，山圍故國周遭。 北郊晚步 陂水荷凋晚，茅檐燕去涼。 遠林明落景，平麓淡秋光。 群牧歸村巷，孤禽立野航。 自諳閑散樂，園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! By the end of this unit, students should be able to: * Recognise around 200+ characters. * Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably. * Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. ** 於 and 于 should be distinguishable. * Survive a text of at least 250 characters and read for gist. Lessons: # [[/A Brief Overview of Confucianism/]] # [[/The Mountains with Yelü Tuyu/]] <!--- 立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華 小山壓大山，大山全無力。 羞見故鄉人，從此投外國。 ---> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杏杏重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚，十載風塵貫耳鈴。 已是臨枰知敵手，莫須敲月苦殫精。 為輪為彈隨遭遇，誰鳳誰鶯任賦生。 造物於人何苟惜，明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気，月色興無窮 群犬吠山径，百蟲啼野風 悲秋秋夜永，感古古今同 自是孤窓下，凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴，歷歷銀鈎指下生。 自恨羅衣掩詩句，擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！ 子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！ 柏舟 彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。 汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。 行露 厭浥行露，豈不夙夜，謂行多露。 誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。 誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄，董卓亂天常。 志欲圖篡弒，先害諸賢良。 逼迫遷舊邦，擁主以自強。 海內興義師，欲共討不祥。 卓眾來東下，金甲耀日光。 平土人脆弱，來兵皆胡羌。 獵野圍城邑，所向悉破亡。 斬截無孑遺，屍骸相撐拒。 馬邊懸男頭，馬後載婦女。 長驅西入關，迥路險且阻。 還顧邈冥冥，肝脾為爛腐。 所略有萬計，不得令屯聚。 或有骨肉俱，欲言不敢語。 失意幾微間，輒言斃降虜。 要當以亭刃，我曹不活汝。 豈復惜性命，不堪其詈罵。 或便加棰杖，毒痛參並下。 旦則號泣行，夜則悲吟坐。 欲死不能得，欲生無一可。 彼蒼者何辜，乃遭此厄禍。 邊荒與華異，人俗少義理。 處所多霜雪，胡風春夏起。 翩翩吹我衣，肅肅入我耳。 感時念父母，哀嘆無窮已。 有客從外來，聞之常歡喜。 迎問其消息，輒復非鄉里。 邂逅徼時願，骨肉來迎己。 己得自解免，當復棄兒子。 天屬綴人心，念別無會期。 存亡永乖隔，不忍與之辭。 兒前抱我頸，問母欲何之。 人言母當去，豈復有還時。 阿母常仁惻，今何更不慈。 我尚未成人，奈何不顧思。 見此崩五內，恍惚生狂痴。 號泣手撫摩，當發復回疑。 兼有同時輩，相送告離別。 慕我獨得歸，哀叫聲摧裂。 馬為立踟躕，車為不轉轍。 觀者皆噓唏，行路亦嗚咽。 去去割情戀，遄征日遐邁。 悠悠三千里，何時復交會。 念我出腹子，匈臆為摧敗。 既至家人盡，又復無中外。 城廓為山林，庭宇生荊艾。 白骨不知誰，縱橫莫覆蓋。 出門無人聲，豺狼號且吠。 煢煢對孤景，怛吒糜肝肺。 登高遠眺望，魂神忽飛逝。 奄若壽命盡，旁人相寬大。 為復強視息，雖生何聊賴。 託命於新人，竭心自勖勵。 流離成鄙賤，常恐復捐廢。 人生幾何時，懷憂終年歲。 ---> ===Unit 5: Myths and Legends of East Asia=== <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] <!--- Even here, the odes can be studied! ---> # [[/Ultimate Justice with Xiezhi/]] # [[/The Virtue of the Fenghuang/]] # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 6: Nation Focus - Japan=== # [[/The Inariyama Sword/]] <!--- short and sweet! ---> # [[/Entering Japan with Takeda Shingen/]] <!--- 便面蘆間有漁·武田信玄 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船 便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440 似 is a really useful thing to teach early on. ---> # [[/The Oldest Inscription in Japan/]] <!--- 宇治橋断碑 ---> # [[/Remembering Conflict with Nakajima Noburu/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/6faa4d3e57a24e542db0375894f0ead5503218bb ---> # [[/Shinto Teachings with Honda Chikaatsu/]] <!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---> # [[/The Diary of Fujiwara no Teika/]] <!--- 明月記 ---> # [[/Reading the History of Japan with Prince Toneri/]] <!--- 日本書記, etc. ---> <!--- # [[/Occupying Taiwan/]] ---> <!--- I have some colonial literature on me that can be used here. ---> ===Unit 7: Nation Focus - Korea=== <!--- 三國史記 for sure! ---> <!--- 放蟬賦 by Yi Kyubo ---> <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋（최자） 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> ===Unit 8: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 9: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] <!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---> # [[/Qingtan with Xie Daoyun/]] <!--- 謝道韞; mentioned in the sanzijing. could be good! 《泰山吟·謝道韞》 峩峩東嶽高，秀極衝青天。 巖中間虛宇，寂寞幽以玄。 非工復非匠，雲構發自然。 器象爾何物，遂令我屢遷。 逝將宅斯宇，可以盡天年。 《拟嵇中散咏松诗·謝道韞》 遙望山上松，隆冬不能凋。 願想遊不憩，瞻彼萬仞條。 騰躍未能升，頓足俟王喬。 時哉不我與，大運所飄遙。 ---> # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 10: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] <!--- 康熙二十二年封王尚貞敕 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。 Teach imperial edicts. Consider seeing if there's a letter of acceptance from Shō Tei. Recorded in 琉球國志略 https://ctext.org/wiki.pl?if=en&chapter=966326 ---> # [[/The Twilight of Ryukyu with Shō Ten/]] <!--- 神田酒樓街燈 尚典 酒樓今秋設芳筵， 一望街燈燦燦連。 烟氣引來通柱上， 光爭星月照神田。 ---> # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 11: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> ===Unit 12: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> # [[/Anatomy with Sugita Genpaku/]] <!--- 解体新書 ---> ===Unit 13: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Zhang Honghe/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云： 去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。 诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> <!--- Possible Jurchen/Khitan focus? 耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. ---> ===Unit 14: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 15: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史 　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。 　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。 　　過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。 　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。 ---> # [[/An Edict from the Xianbei/]] <!--- 教義詔 楊廣 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 ---> # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] <!--- 順治帝 告示 逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。 大清順治二年五月二十四日 恩詔 今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。 永昌二年新正初一 There's probably better choices here. Review. ---> ===Unit 16: Nation Focus - Vietnam=== <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---> # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 17: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> ===Unit 18: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. Look at Japan's 五山文学 ---> # [[/A Buddhist Temple in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言，教外別傳意已圓。 只履攜將蔥嶺去，不妨來上月明船。 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> ===Unit 19: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] <!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---> # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> ===Unit 20: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰，東寧國 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} kwttgke0jwf2fvk8ckumdh94lzw29nm 0 481968 4634181 4633998 2026-05-04T19:32:08Z JustTheFacts33 3434282 /* Position 5, Engine: */ 4634181 wikitext text/x-wiki ===Positions 1–3, World Manufacturer Identifier:=== * WP0 - Porsche passenger car * WP1 - Porsche SUV ===Position 4, Body Style:=== '''924:''' * A = Coupe '''944:''' * A = Coupe * B = Cabriolet (1989 only) * C = Cabriolet (1990-1991) '''968/Boxster/Cayman/718:''' * A = Coupe * C = Cabriolet '''928:''' * J = Coupe (1981-1990) * A = Coupe (1991-1995) '''911:''' * A = Coupe (Except Type 930 Turbo coupe) * B = Targa (911 - Type 964/996/997/991/992) * C = Cabriolet (911 - Type 964/993/996/997/991/992) or Speedster (Type 964/997/991) or Roadster (Type 964) * D = Targa (911 - Type 993) * E = Targa or Cabriolet (911 [1981-1989] or 911 Turbo - Type 930 [1987-1989]) or Speedster (911 - 1989) * J = Turbo Coupe (911 - Type 930 [US: 1986-1989, Canada: 1981-1989]) '''Carrera GT / 918 Spyder:''' * C = Cabriolet '''Panamera / Taycan:''' * A = sedan (SWB) * B = LWB sedan (Panamera Executive) or Cross Turismo (Taycan) * C = Sport Turismo '''Macan / Cayenne:''' * A = SUV (wagon) * B = Coupe-styled SUV (Cayenne Coupe) ===Position 5, Engine:=== '''944:''' *B = 3.0L DOHC 16-valve Porsche M44 I4, 208 hp (944 S2 '90-'91) *B = 2.5L turbo SOHC 8-valve Porsche M44 I4, 247 hp (944 Turbo '8-'90) '''968:''' *A = 3.0L DOHC 16-valve Porsche M44 I4, 236 hp ('92-'95) '''928:''' *B = 5.0L DOHC 32-valve Porsche M28 V8, 316 hp (928 S4 '87-'90) *B = 5.0L DOHC 32-valve Porsche M28 V8, 326 hp (928 GT '89-'90) *A = 5.0L DOHC 32-valve Porsche M28 V8, 316 hp (928 S4 '91) *A = 5.0L DOHC 32-valve Porsche M28 V8, 326 hp (928 GT '91) *A = 5.4L DOHC 32-valve Porsche M28 V8, 345 hp (928 GTS '93-'95) '''Boxster/Cayman:''' Type 986: *A = 2.5L flat-6, 201 hp (Boxster '97-'99) *A = 2.7L flat-6, 217 hp (Boxster '00-'02) *A = 2.7L flat-6, 225 hp (Boxster '03-'04) *B = 3.2L flat-6, 250 hp (Boxster S '00-'02) *B = 3.2L flat-6, 258 hp (Boxster S '03-'04) *B = 3.2L flat-6, 264 hp (Boxster S 50 Years of the 550 Spyder Anniversary Edition '04) Type 987: *A = 2.7L flat-6, 240 hp (Boxster '05-'06) *A = 2.7L flat-6, 245 hp (Boxster '07-'08, Limited Edition '08), 245 hp (Cayman '07-'08) *A = 2.9L flat-6, 255 hp (Boxster '09-'12), 265 hp (Cayman '09-'12) *B = 3.2L flat-6, 280 hp (Boxster S '05-'06) *B = 3.4L flat-6, 295 hp (Boxster S '07-'08, S Limited Edition '08), 295 hp (Cayman S '06-'08) *B = 3.4L flat-6, 310 hp (Boxster S '09-'12), 320 hp (Cayman S '09-'12) *B = 3.4L flat-6, 303 hp (Boxster S Porsche Design Edition 2 '08, RS 60 Spyder '08), 303 hp (Cayman S Sport '08) *B = 3.4L flat-6, 320 hp (Boxster S Black Edition '12, Spyder '11-'12), 330 hp (Cayman S Black Edition '12, Cayman R '12) Type 981: *A = 2.7L flat-6, 265 hp (Boxster '13-'16, Boxster Black Edition '16), 275 hp (Cayman '14-'16) *B = 3.4L flat-6, 315 hp (Boxster S '13-'16), 325 hp (Cayman S '14-'16) *B = 3.4L flat-6, 330 hp (Boxster GTS '15-'16), 340 hp (Cayman GTS '15-'16) *C = 3.8L flat-6, 375 hp (Boxster Spyder '16), 385 hp (Cayman GT4 '16) '''718 Boxster/Cayman:''' Type 982: *A = 2.0L turbo flat-4, 300 hp <br> (718 Boxster '17-'25, 718 Boxster T '20-'23, 718 Boxster Style Edition '24-'25, 718 Cayman '17-'25, 718 Cayman T '20-'23, 718 Cayman Style Edition '24-'25) *B = 2.5L turbo flat-4, 350 hp (718 Boxster S, 718 Cayman S '17-'25) *B = 2.5L turbo flat-4, 365 hp (718 Boxster GTS, 718 Cayman GTS '18-'19) *D = 4.0L flat-6, 394 hp (718 Boxster GTS 4.0 '21-'25, 718 Boxster 25 Years '21, 718 Cayman GTS 4.0 '21-'25) *C = 4.0L flat-6, 414 hp (718 Spyder, 718 Cayman GT4 '20-'23) *E = 4.0L flat-6, 493 hp (718 Spyder RS '24-'25, 718 Cayman GT4 RS '23-'25) '''911:''' Type 964: *B = 3.6L SOHC 12-valve air-cooled flat-6, 247 hp (911 Carrera 2 '90-'94, Targa '90-'94, 911 America Roadster '92-'93, RS America '93-'94, Speedster '94,<br> Carrera 4 '89-'94, Carrera 4 Widebody Coupe '94, Carrera 4 Targa '90-'93) *B = 3.6L SOHC 12-valve air-cooled flat-6, 256 hp (911 Carrera Cup USA Edition '92) *A = 3.3L turbo SOHC 12-valve air-cooled flat-6, 315 hp (911 Turbo '91-'92) *C = 3.6L turbo SOHC 12-valve air-cooled flat-6, 355 hp (911 Turbo 3.6 '94) *C = 3.6L turbo SOHC 12-valve air-cooled flat-6, 380 hp (911 Turbo S 3.6 '94) Type 993: *A = 3.6L SOHC 12-valve air-cooled flat-6, 270 hp (911 Carrera '95, Carrera 4 '95) *A = 3.6L SOHC 12-valve air-cooled flat-6, 282 hp (911 Carrera '96-'98, Targa '96-'98, Carrera S '98, Carrera 4 '96-'98, Carrera 4S '96-'98) *C = 3.6L twin-turbo SOHC 12-valve air-cooled flat-6, 400 hp (911 Turbo '96-'97) *C = 3.6L twin-turbo SOHC 12-valve air-cooled flat-6, 424 hp (911 Turbo S '97) Type 996: *A = 3.4L DOHC 24-valve water-cooled flat-6, 296 hp (911 Carrera '99, Carrera 4 '99) *A = 3.4L flat-6, 300 hp (911 Carrera '00-'01, Carrera 4 '00-'01) *A = 3.6L flat-6, 320 hp (911 Carrera '02-'04, Carrera Cabriolet '05, Targa '02-'05, Carrera 4 '02-'04, Carrera 4S '03-'05) *A = 3.6L flat-6, 345 hp (911 Carrera 40th Anniversary Edition -'04) *B = 3.6L twin-turbo flat-6, 415 hp (911 Turbo '01-'05) *B = 3.6L twin-turbo flat-6, 444 hp (911 Turbo S '05) *C = 3.6L flat-6, 381 hp (911 GT3 '04-'05) *B = 3.6L twin-turbo flat-6, 456 hp (911 GT2 '02-'03) *B = 3.6L twin-turbo flat-6, 477 hp (911 GT2 '04) Type 997: *A = 3.6L flat-6, 325 hp (911 Carrera '05-'08, Carrera 4 '06-'08, Targa 4 '07-'08) *A = 3.6L flat-6, 345 hp (911 Carrera '09-'12, Carrera Black Edition '12, Carrera 4 '09-'12, Targa 4 '09-'12) *B = 3.8L flat-6, 355 hp (911 Carrera S '05-'08, Carrera 4S '06-'08, Targa 4S '07-'08) *B = 3.8L flat-6, 385 hp (911 Carrera S '09-'12, Carrera 4S '09-'12, Targa 4S '09-'12) *B = 3.8L flat-6, 381 hp (911 Carrera S Club Coupe '06) *B = 3.8L flat-6, 408 hp (911 Carrera GTS '11-'12, Carrera 4 GTS '12, Speedster '11) *D = 3.6L twin-turbo flat-6, 480 hp (911 Turbo '07-'09) *D = 3.8L twin-turbo flat-6, 500 hp (911 Turbo '10-'13) *D = 3.8L twin-turbo flat-6, 530 hp (911 Turbo S '11-'13) *C = 3.6L flat-6, 415 hp (911 GT3 '07-'08) *C = 3.8L flat-6, 435 hp (911 GT3 '10-'11) *C = 3.6L flat-6, 415 hp (911 GT3 RS '07-'08) *C = 3.8L flat-6, 450 hp (911 GT3 RS '10-'11) *F = 4.0L flat-6, 500 hp (911 GT3 RS 4.0 '11) *D = 3.6L twin-turbo flat-6, 530 hp (911 GT2 '08-'09) *E = 3.8L twin-turbo flat-6, 620 hp (911 GT2 RS '11) Type 991.1: *A = 3.4L flat-6, 350 hp (911 Carrera '12-'16, Carrera 4 '13-'16, Targa 4 '14-'16) *B = 3.8L flat-6, 400 hp (911 Carrera S '12-'16, Carrera 4S '13-'16, Targa 4S '14-'16, 911 50th Anniversary Edition '14) *B = 3.8L flat-6, 430 hp (911 Carrera GTS '15-'16, Carrera 4 GTS '15-'16, Targa 4 GTS '16) *D = 3.8L twin-turbo flat-6, 520 hp (911 Turbo '14-'16) *D = 3.8L twin-turbo flat-6, 560 hp (911 Turbo S '14-'16) *C = 3.8L flat-6, 475 hp (911 GT3 '14-'15) *F = 4.0L flat-6, 500 hp (911 GT3 RS '16, 911 R '16) Type 991.2: *A = 3.0L twin-turbo flat-6, 370 hp (911 Carrera '17-'19, Carrera T '18-'19, Carrera 4 '17-'19, Targa 4 '17-'19) *B = 3.0L twin-turbo flat-6, 420 hp (911 Carrera S '17-'19, Carrera 4S '17-'19, Targa 4S '17-'19) *B = 3.0L twin-turbo flat-6, 450 hp (911 Carrera GTS '17-'19, Carrera 4 GTS '17-'19, Targa 4 GTS '17-'19) *D = 3.8L twin-turbo flat-6, 540 hp (911 Turbo '17-'19) *D = 3.8L twin-turbo flat-6, 580 hp (911 Turbo S '17-'19) *D = 3.8L twin-turbo flat-6, 607 hp (911 Turbo S Exclusive Series '18-'19) *C = 4.0L flat-6, 500 hp (911 GT3, GT3 Touring '18-'19) *F = 4.0L flat-6, 502 hp (911 Speedster '19) *F = 4.0L flat-6, 520 hp (911 GT3 RS '19) *E = 3.8L twin-turbo flat-6, 690 hp (911 GT2 RS '18-'19) Type 992: *A = 3.0L twin-turbo flat-6, 379 hp (911 Carrera '20-'24, Carrera T '23-'24, Carrera 4 '20-'24, Targa 4 '21-'24) *A = 3.0L twin-turbo flat-6, 388 hp (911 Carrera, Carrera T '25-, Carrera T Club Coupe '26) *B = 3.0L twin-turbo flat-6, 443 hp (911 Carrera S '20-'24, Carrera 4S '20-'24, Targa 4S '21-'24) *H = 3.0L twin-turbo flat-6, 473 hp (911 Carrera S '26-, Carrera 4S '26-, Targa 4S '26-) *B = 3.0L twin-turbo flat-6, 473 hp (911 Carrera GTS '22-'24, Carrera 4 GTS '22-'24, Targa 4 GTS '22-'24, Dakar '23-'24) *B = Hybrid: 3.6L turbo flat-6 + electric motor, Lithium-ion battery, 532 hp (911 Carrera GTS, Carrera 4 GTS, Targa 4 GTS '25-, 911 Spirit 70 '26) *G = 3.7L twin-turbo flat-6, 543 hp (911 Sport Classic '23) *D = 3.7L twin-turbo flat-6, 572 hp (911 Turbo '21-'25) *D = 3.7L twin-turbo flat-6, 640 hp (911 Turbo S '21-'25) *D = Hybrid: 3.6L twin-turbo flat-6 + electric motor, Lithium-ion battery, 701 hp (911 Turbo S '26-) *C = 4.0L flat-6, 502 hp (911 GT3, GT3 Touring '22-'26) *F = 4.0L flat-6, 518 hp (911 GT3 RS '23-'25, 911 S/T '24) '''Carrera GT:''' *A = 5.7L Porsche M80.01 68° V10, 605 hp (Carrera GT '04-'05) '''918 Spyder:''' *A = PHEV: 4.6L Porsche M18 flat-plane crank V8 + 2 electric motors (1 front, 1 rear), Lithium-ion battery, 887 total system hp (918 Spyder '15) '''Panamera:''' Type 970: *A = 3.6L Porsche M46.20 (2wd)/M46.40 (4wd) 90° V6, 300 hp (Panamera, Panamera 4 '11-'13) *A = 3.6L Porsche M46.20 (2wd)/M46.40 (4wd) 90° V6, 310 hp (Panamera, Panamera 4 '14-'16) *D = HEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Nickel-metal hydride battery, 380 hp (Panamera S Hybrid '12-'13) *D = PHEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Lithium-ion battery, 416 hp (Panamera S E-Hybrid '14-'16) *B = 4.8L Porsche M48 V8, 400 hp (Panamera S, 4S '10-'13) *B = 3.0L twin-turbo Porsche M46.60 90° V6, 420 hp (Panamera S, 4S '14-'16) *F = 4.8L Porsche M48 V8, 430 hp (Panamera GTS '13) *F = 4.8L Porsche M48 V8, 440 hp (Panamera GTS '14-'16) *C = 4.8L twin-turbo Porsche M48 V8, 500 hp (Panamera Turbo '10-'13) *C = 4.8L twin-turbo Porsche M48 V8, 520 hp (Panamera Turbo '14-'16) *C = 4.8L twin-turbo Porsche M48 V8, 550 hp (Panamera Turbo S '12-'13) *C = 4.8L twin-turbo Porsche M48 V8, 570 hp (Panamera Turbo S '15-'16) Type 971 & 976: *A = 3.0L turbo Audi-Porsche EA839T 90° V6, 330 hp (Panamera, Panamera 4 '17-'20) *J = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 325 hp (Panamera, Panamera 4 '21-'23) *A = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 348 hp (Panamera, Panamera 4 '24-) *E = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 455 hp (Panamera 4 E-Hybrid '18-'23) *E = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 463 hp (Panamera 4 E-Hybrid '25-) *B = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 440 hp (Panamera 4S '17-'20) *B = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 443 hp (Panamera 4S '21-'23) *K = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 552 hp (Panamera 4S E-Hybrid '21-'23) *C = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 536 hp (Panamera 4S E-Hybrid '25-) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 453 hp (Panamera GTS '19-'20) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 473 hp (Panamera GTS '21-'23) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 493 hp (Panamera GTS '25-) *F = 4.0L twin-turbo Porsche-Audi EA825TT V8, 550 hp (Panamera Turbo '17-'20) *F = 4.0L twin-turbo Porsche-Audi EA825TT V8, 620 hp (Panamera Turbo S '21-'23) *F = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 670 hp (Panamera Turbo E-Hybrid '25-) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 680 hp (Panamera Turbo S E-Hybrid '18-'20) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 690 hp (Panamera Turbo S E-Hybrid '21-'23) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 771 hp (Panamera Turbo S E-Hybrid '25-) '''Taycan:''' *A = battery-electric, 1 rear motor, Rwd, 402 hp (71 Kwh battery) or 469 hp (83.7 Kwh battery) (Taycan '21-'24) *A = battery-electric, 1 rear motor, Rwd, 402 hp (82.3 Kwh battery) or 429 hp (97 Kwh battery) (Taycan '25-) *A = battery-electric, 2 motors, 4wd, 402 hp (82.3 Kwh battery) or 429 hp (97 Kwh battery) (Taycan 4 '25-) *B = battery-electric, 2 motors, 4wd, 522 hp (71 Kwh battery) or 562 hp (83.7 Kwh battery) (Taycan 4S '20-'24) *B = battery-electric, 2 motors, 4wd, 536 hp (82.3 Kwh battery) or 590 hp (97 Kwh battery) (Taycan 4S '25-) *D = battery-electric, 2 motors, 4wd, 590 hp (83.7 Kwh battery) (Taycan GTS '22-'24) *D = battery-electric, 2 motors, 4wd, 690 hp (97 Kwh battery) (Taycan GTS '25-) *C = battery-electric, 2 motors, 4wd, 670 hp (83.7 Kwh battery) (Taycan Turbo '20-'24) *C = battery-electric, 2 motors, 4wd, 750 hp (83.7 Kwh battery) (Taycan Turbo S '20-'24) *C = battery-electric, 2 motors, 4wd, 871 hp (97 Kwh battery) (Taycan Turbo '25-) *C = battery-electric, 2 motors, 4wd, 938 hp (97 Kwh battery) (Taycan Turbo S '25-) *E = battery-electric, 2 motors, 4wd, 1019 hp (97 Kwh battery) (Taycan Turbo GT '25-) '''Macan:''' *A = 2.0L turbo Audi EA888T I4, 248 hp (Macan '17-'21) *A = 2.0L turbo Audi EA888T I4, 261 hp (Macan '22-, Macan T '23-) *B = 3.0L turbo Porsche M46.30 90° V6, 340 hp (Macan S '15-'18) *B = 3.0L turbo Audi-Porsche EA839T 90° V6, 348 hp (Macan S '19-'21) *G = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 375 hp (Macan S '22-) *G = 3.0L twin-turbo Porsche M46.30 90° V6, 360 hp (Macan GTS '17-'18) *G = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 375 hp (Macan GTS '20-'21) *F = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 434 hp (Macan GTS '22-) *F = 3.6L twin-turbo Porsche M46.35 90° V6, 400 hp (Macan Turbo '15-'18) *F = 3.6L twin-turbo Porsche M46.35 90° V6, 440 hp (Macan Turbo w/Performance Package '17-'18) *F = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 434 hp (Macan Turbo '20-'21) '''Macan Electric:''' *D = battery-electric, 1 rear motor, Rwd, 355 hp (95 Kwh battery) (Macan Electric '25-) *A = battery-electric, 2 motors, 4wd, 402 hp (95 Kwh battery) (Macan Electric 4 '24-) *B = battery-electric, 2 motors, 4wd, 509 hp (95 Kwh battery) (Macan Electric 4S '25-) *E = battery-electric, 2 motors, 4wd, 563 hp (95 Kwh battery) (Macan Electric GTS '26-) *C = battery-electric, 2 motors, 4wd, 630 hp (95 Kwh battery) (Macan Electric Turbo '24-) '''Cayenne:''' 955/957 or 9PA: *A = 3.2L (3189cc) VW EA390 15° VR6, 247 hp (Cayenne '04-'06) *A = 3.6L (3598cc) VW EA390 10.6° FSI VR6, 290 hp (Cayenne '08-'10) *B = 4.5L Porsche M48 V8, 340 hp (Cayenne S '03-'06, S Titanium Edition '06) *B = 4.8L Porsche M48 V8, 385 hp (Cayenne S '08-'10) *D = 4.8L Porsche M48 V8, 405 hp (Cayenne GTS '08-'10, S Transsyberia '10) *C = 4.5L twin-turbo Porsche M48 V8, 450 hp (Cayenne Turbo '03-'06) *C = 4.8L twin-turbo Porsche M48 V8, 500 hp (Cayenne Turbo '08-'10) *C = 4.5L twin-turbo Porsche M48 V8, 520 hp (Cayenne Turbo S '06) *C = 4.8L twin-turbo Porsche M48 V8, 550 hp (Cayenne Turbo S '09-'10) 958 or 92A: *A = 3.6L (3598cc) VW EA390 10.6° VR6, 300 hp (Cayenne '11-'14, '16-'18) *B = 4.8L Porsche M48 V8, 400 hp (Cayenne S '11-'14) *B = 3.6L (3604cc) twin-turbo Porsche M46.35 90° V6, 420 hp (Cayenne S '15-'18) *E = HEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Nickel-metal hydride battery, 380 hp (Cayenne S Hybrid '11-'14) *E = PHEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Lithium-ion battery, 416 hp (Cayenne S E-Hybrid '15-'18) *D = 4.8L Porsche M48 V8, 420 hp (Cayenne GTS '13-'14) *D = 3.6L (3604cc) twin-turbo Porsche M46.35 90° V6, 440 hp (Cayenne GTS '16-'18) *C = 4.8L twin-turbo Porsche M48 V8, 500 hp (Cayenne Turbo '11-'14) *C = 4.8L twin-turbo Porsche M48 V8, 520 hp (Cayenne Turbo '15-'18) *C = 4.8L twin-turbo Porsche M48 V8, 550 hp (Cayenne Turbo S '14) *C = 4.8L twin-turbo Porsche M48 V8, 570 hp (Cayenne Turbo S '16-'18) *F = 3.0L turbodiesel Audi EA897 90° V6, 240 hp (Cayenne Diesel '13-'16) 9YA/9YB: *A = 3.0L turbo Audi-Porsche EA839T 90° V6, 335 hp (Cayenne '19-'23) *A = 3.0L turbo Audi-Porsche EA839T 90° V6, 348 hp (Cayenne '24-) *E = PHEV: 3.0L turbo Audi-Porsche EA839T 90° V6 + electric motor, Lithium-ion battery, 455 hp (Cayenne E-Hybrid '19-'23) *E = PHEV: 3.0L turbo Audi-Porsche EA839T 90° V6 + electric motor, Lithium-ion battery, 463 hp (Cayenne E-Hybrid '24-) *B = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 434 hp (Cayenne S '19-'23) *L = 4.0L twin-turbo Porsche-Audi EA825TT V8, 468 hp (Cayenne S '24-) *N = PHEV: 3.0L turbo Audi-Porsche EA839T 90° V6 + electric motor, Lithium-ion battery, 512 hp (Cayenne S E-Hybrid '24-) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 453 hp (Cayenne GTS '21-'23) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 493 hp (Cayenne GTS '25-) *F = 4.0L twin-turbo Porsche-Audi EA825TT V8, 541 hp (Cayenne Turbo '19-'23) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 670 hp (Cayenne Turbo S E-Hybrid '20-'23) *M = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 729 hp (Cayenne Turbo E-Hybrid '24-) *K = 4.0L twin-turbo Porsche-Audi EA825TT V8, 631 hp (Cayenne Coupe Turbo GT '22-'23) *K = 4.0L twin-turbo Porsche-Audi EA825TT V8, 650 hp (Cayenne Coupe Turbo GT '24-) '''Cayenne Electric:''' *A = battery-electric, 2 motors, 4wd, 435 hp (108 Kwh battery) (Cayenne Electric '26-) *D = battery-electric, 2 motors, 4wd, 1139 hp (108 Kwh battery) (Cayenne Electric Turbo '26-) ===Position 6, Restraint Systems:=== *1 = Seat Belts only *2 = Passive Restraint System - Airbags (Driver and Passenger Front Airbags) ===Position 7-8, Vehicle Type Code=== {| class="wikitable" |+Position 7 !VIN Pos. 7-8 !Complete Vehicle Type Code !Model !Type |- |92 |924 |924 (1981-1982 w/normally aspirated engine) |924 |- |93 |931 |924 Turbo (1981-1982) |931 |- |92 |924 |924S (1987-1988 w/normally aspirated engine) |924 |- |94 |944 |944 (1983-1991 w/normally aspirated engine) |944 |- |95 |951 |944 Turbo (1986-1989 & 1990 in Canada) |951 |- |96 |968 |968 (1992-1995) |968 |- |92 |928 |928 (1981-1995) |928 |- |98 |986 |Boxster (1997-2004) |986 |- |98 |987 |Boxster (2005-2009)/Cayman (2006-2009) |987 |- |A8 |A87 |Boxster (2010-2012)/Cayman (2010-2012) |987 |- |A8 |A81 |Boxster (2013-2016)/Cayman (2014-2016) |981 |- |A8 |A82 |718 Boxster/Cayman (2017-2025) |982 |- |91 |911 |911 (1981-1989 2wd w/normally aspirated engine) |911 |- |93 |930 |911 (1986-1989 911 Turbo) |930 |- |96 |964 |911 (1989-1994 Carrera 4, 1990-1994 Carrera 2, 1991-1994 Turbo) |964 |- |99 |993 |911 (1995-1998) |993 |- |99 |996 |911 (1999-2004) |996 |- |99 |997 |911 (2005-2009) |997 |- |A9 |A97 |911 (2010-2012) |997 |- |A9 |A91 |911 (2013-2019) |991 |- |A9 |A92 |911 (2020-) |992 |- |98 |980 |Carrera GT (2004-2005) |980 |- |A1 |A18 |918 Spyder (2015) |918 |- |A7 |A70 |Panamera (2010-2016) |970 |- |A7 |A71 |Panamera (2017-2023) |971 |- |YA | |Panamera (2024-) |976 |- |Y1 |Y1A |Taycan (2020-) |9J1 or <br> Y1A (sedan)/Y1B (Cross Turismo)/Y1C (Sport Turismo) |- |A5 |A5B |Macan (2015-) |95B |- |XA | |Macan Electric (2024-) |XAB |- |9P |9PA |Cayenne (2003-2009) |9PA |- |AP |APA |Cayenne (2010) |9PA |- |A2 |A2A |Cayenne (2011-2018) |92A |- |AY |AYA |Cayenne (wagon: 2019-, coupe: 2020-) |9YA (wagon)/9YB (coupe) |- |X1 | |Cayenne Electric (2026-) |E4 |} ===Position 9, Check Digit=== [[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]] ===Position 10, Model Year: === [[Vehicle Identification Numbers (VIN codes)/Model year|Model year]] ===Position 11, Production Plant:=== * S: Stuttgart-Zuffenhausen, Germany * L: Leipzig, Germany * D: Bratislava, Slovakia (VW plant - Cayenne '19-) * K: Osnabrueck, Germany (ex-Karmann VW plant - Cayenne '16-'18, Boxster '13-15, Cayman '14-'16, 718 Boxster '24-'25, 718 Cayman '17-'18, '20-'21, '23-'25) * N: Neckarsulm, Germany (Audi plant - 924, 944) * U: Uusikaupunki, Finland (Valmet plant - Boxster '98-'11, Cayman '06-'12) ===Position 12, 3rd Digit of Vehicle Type Code=== Note: Only applies to models with a 3-digit Vehicle Type Code. Models with a 2-digit Vehicle Type Code use pos. 12 for the serial number. {| class="wikitable" |+Position 12 !VIN Pos. 12 !Complete Vehicle Type Code !Model !Type |- |4 |924 |924 (1981-1982 w/normally aspirated engine) |924 |- |1 |931 |924 Turbo (1981-1982) |931 |- |4 |924 |924S (1987-1988 w/normally aspirated engine) |924 |- |4 |944 |944 (1983-1991 w/normally aspirated engine) |944 |- |1 |951 |944 Turbo (1986-1989 & 1990 in Canada) |951 |- |8 |968 |968 (1992-1995) |968 |- |8 |928 |928 (1981-1995) |928 |- |6 |986 |Boxster (1997-2004) |986 |- |7 |987 |Boxster (2005-2009)/Cayman (2006-2009) |987 |- |7 |A87 |Boxster (2010-2012)/Cayman (2010-2012) |987 |- |1 |A81 |Boxster (2013-2016)/Cayman (2014-2016) |981 |- |2 |A82 |718 Boxster/Cayman (2017-2025) |982 |- |1 |911 |911 (1981-1989 2wd w/normally aspirated engine) |911 |- |0 |930 |911 (1986-1989 911 Turbo) |930 |- |4 |964 |911 (1989-1994 Carrera 4, 1990-1994 Carrera 2, 1991-1994 Turbo) |964 |- |3 |993 |911 (1995-1998) |993 |- |6 |996 |911 (1999-2004) |996 |- |7 |997 |911 (2005-2009) |997 |- |7 |A97 |911 (2010-2012) |997 |- |1 |A91 |911 (2013-2019) |991 |- |2 |A92 |911 (2020-) |992 |- |0 |980 |Carrera GT (2004-2005) |980 |- |8 |A18 |918 Spyder (2015) |918 |- |0 |A70 |Panamera (2010-2016) |970 |- |1 |A71 |Panamera (2017-2023) |971 |- |A |Y1A |Taycan (2020-) |9J1 or <br> Y1A (sedan)/Y1B (Cross Turismo)/Y1C (Sport Turismo) |- |B |A5B |Macan (2015-) |95B |- |A |9PA |Cayenne (2003-2009) |9PA |- |A |APA |Cayenne (2010) |9PA |- |A |A2A |Cayenne (2011-2018) |92A |- |A |AYA |Cayenne (wagon: 2019-, coupe: 2020-) |9YA (wagon)/9YB (coupe) |} '''Positions 12–17 or 13–17, Serial Number''' {{BookCat}} 3uonq18l69826oba3b3dy0f76djj0sr 4634199 4634181 2026-05-04T23:16:24Z JustTheFacts33 3434282 /* Position 5, Engine: */ 4634199 wikitext text/x-wiki ===Positions 1–3, World Manufacturer Identifier:=== * WP0 - Porsche passenger car * WP1 - Porsche SUV ===Position 4, Body Style:=== '''924:''' * A = Coupe '''944:''' * A = Coupe * B = Cabriolet (1989 only) * C = Cabriolet (1990-1991) '''968/Boxster/Cayman/718:''' * A = Coupe * C = Cabriolet '''928:''' * J = Coupe (1981-1990) * A = Coupe (1991-1995) '''911:''' * A = Coupe (Except Type 930 Turbo coupe) * B = Targa (911 - Type 964/996/997/991/992) * C = Cabriolet (911 - Type 964/993/996/997/991/992) or Speedster (Type 964/997/991) or Roadster (Type 964) * D = Targa (911 - Type 993) * E = Targa or Cabriolet (911 [1981-1989] or 911 Turbo - Type 930 [1987-1989]) or Speedster (911 - 1989) * J = Turbo Coupe (911 - Type 930 [US: 1986-1989, Canada: 1981-1989]) '''Carrera GT / 918 Spyder:''' * C = Cabriolet '''Panamera / Taycan:''' * A = sedan (SWB) * B = LWB sedan (Panamera Executive) or Cross Turismo (Taycan) * C = Sport Turismo '''Macan / Cayenne:''' * A = SUV (wagon) * B = Coupe-styled SUV (Cayenne Coupe) ===Position 5, Engine:=== '''924:''' *A = 2.5L SOHC 8-valve Porsche M44 I4, 147 hp (924S '87) *A = 2.5L SOHC 8-valve Porsche M44 I4, 158 hp (924S '88) '''944:''' *A = 2.5L SOHC 8-valve Porsche M44 I4, 143 hp (944 [base model] '83-'86) *B = 2.5L SOHC 8-valve Porsche M44 I4, 147 hp (944 [base model] '87) *B = 2.5L SOHC 8-valve Porsche M44 I4, 158 hp (944 [base model] '88) *A = 2.5L DOHC 16-valve Porsche M44 I4, 188 hp (944S '87-'88) *A = 2.7L SOHC 8-valve Porsche M44 I4, 163 hp (944 [base model] '89) *B = 3.0L DOHC 16-valve Porsche M44 I4, 208 hp (944 S2 '89 [coupe only], '90-'91 [coupe & cabriolet]) *A = 3.0L DOHC 16-valve Porsche M44 I4, 208 hp (944 S2 '89 [cabriolet only]) *A = 2.5L turbo SOHC 8-valve Porsche M44.51 I4, 217 hp (944 Turbo '86-'88) *A = 2.5L turbo SOHC 8-valve Porsche M44.52 I4, 247 hp (944 Turbo S '88, Turbo '89) *C = 2.5L turbo SOHC 8-valve Porsche M44.52 I4, 247 hp (944 Turbo '90 [Canada only]) '''968:''' *A = 3.0L DOHC 16-valve Porsche M44 I4, 236 hp ('92-'95) '''928:''' *B = 5.0L DOHC 32-valve Porsche M28 V8, 316 hp (928 S4 '87-'90) *B = 5.0L DOHC 32-valve Porsche M28 V8, 326 hp (928 GT '89-'90) *A = 5.0L DOHC 32-valve Porsche M28 V8, 316 hp (928 S4 '91) *A = 5.0L DOHC 32-valve Porsche M28 V8, 326 hp (928 GT '91) *A = 5.4L DOHC 32-valve Porsche M28 V8, 345 hp (928 GTS '93-'95) '''Boxster/Cayman:''' Type 986: *A = 2.5L flat-6, 201 hp (Boxster '97-'99) *A = 2.7L flat-6, 217 hp (Boxster '00-'02) *A = 2.7L flat-6, 225 hp (Boxster '03-'04) *B = 3.2L flat-6, 250 hp (Boxster S '00-'02) *B = 3.2L flat-6, 258 hp (Boxster S '03-'04) *B = 3.2L flat-6, 264 hp (Boxster S 50 Years of the 550 Spyder Anniversary Edition '04) Type 987: *A = 2.7L flat-6, 240 hp (Boxster '05-'06) *A = 2.7L flat-6, 245 hp (Boxster '07-'08, Limited Edition '08), 245 hp (Cayman '07-'08) *A = 2.9L flat-6, 255 hp (Boxster '09-'12), 265 hp (Cayman '09-'12) *B = 3.2L flat-6, 280 hp (Boxster S '05-'06) *B = 3.4L flat-6, 295 hp (Boxster S '07-'08, S Limited Edition '08), 295 hp (Cayman S '06-'08) *B = 3.4L flat-6, 310 hp (Boxster S '09-'12), 320 hp (Cayman S '09-'12) *B = 3.4L flat-6, 303 hp (Boxster S Porsche Design Edition 2 '08, RS 60 Spyder '08), 303 hp (Cayman S Sport '08) *B = 3.4L flat-6, 320 hp (Boxster S Black Edition '12, Spyder '11-'12), 330 hp (Cayman S Black Edition '12, Cayman R '12) Type 981: *A = 2.7L flat-6, 265 hp (Boxster '13-'16, Boxster Black Edition '16), 275 hp (Cayman '14-'16) *B = 3.4L flat-6, 315 hp (Boxster S '13-'16), 325 hp (Cayman S '14-'16) *B = 3.4L flat-6, 330 hp (Boxster GTS '15-'16), 340 hp (Cayman GTS '15-'16) *C = 3.8L flat-6, 375 hp (Boxster Spyder '16), 385 hp (Cayman GT4 '16) '''718 Boxster/Cayman:''' Type 982: *A = 2.0L turbo flat-4, 300 hp <br> (718 Boxster '17-'25, 718 Boxster T '20-'23, 718 Boxster Style Edition '24-'25, 718 Cayman '17-'25, 718 Cayman T '20-'23, 718 Cayman Style Edition '24-'25) *B = 2.5L turbo flat-4, 350 hp (718 Boxster S, 718 Cayman S '17-'25) *B = 2.5L turbo flat-4, 365 hp (718 Boxster GTS, 718 Cayman GTS '18-'19) *D = 4.0L flat-6, 394 hp (718 Boxster GTS 4.0 '21-'25, 718 Boxster 25 Years '21, 718 Cayman GTS 4.0 '21-'25) *C = 4.0L flat-6, 414 hp (718 Spyder, 718 Cayman GT4 '20-'23) *E = 4.0L flat-6, 493 hp (718 Spyder RS '24-'25, 718 Cayman GT4 RS '23-'25) '''911:''' Type 964: *B = 3.6L SOHC 12-valve air-cooled flat-6, 247 hp (911 Carrera 2 '90-'94, Targa '90-'94, 911 America Roadster '92-'93, RS America '93-'94, Speedster '94,<br> Carrera 4 '89-'94, Carrera 4 Widebody Coupe '94, Carrera 4 Targa '90-'93) *B = 3.6L SOHC 12-valve air-cooled flat-6, 256 hp (911 Carrera Cup USA Edition '92) *A = 3.3L turbo SOHC 12-valve air-cooled flat-6, 315 hp (911 Turbo '91-'92) *C = 3.6L turbo SOHC 12-valve air-cooled flat-6, 355 hp (911 Turbo 3.6 '94) *C = 3.6L turbo SOHC 12-valve air-cooled flat-6, 380 hp (911 Turbo S 3.6 '94) Type 993: *A = 3.6L SOHC 12-valve air-cooled flat-6, 270 hp (911 Carrera '95, Carrera 4 '95) *A = 3.6L SOHC 12-valve air-cooled flat-6, 282 hp (911 Carrera '96-'98, Targa '96-'98, Carrera S '98, Carrera 4 '96-'98, Carrera 4S '96-'98) *C = 3.6L twin-turbo SOHC 12-valve air-cooled flat-6, 400 hp (911 Turbo '96-'97) *C = 3.6L twin-turbo SOHC 12-valve air-cooled flat-6, 424 hp (911 Turbo S '97) Type 996: *A = 3.4L DOHC 24-valve water-cooled flat-6, 296 hp (911 Carrera '99, Carrera 4 '99) *A = 3.4L flat-6, 300 hp (911 Carrera '00-'01, Carrera 4 '00-'01) *A = 3.6L flat-6, 320 hp (911 Carrera '02-'04, Carrera Cabriolet '05, Targa '02-'05, Carrera 4 '02-'04, Carrera 4S '03-'05) *A = 3.6L flat-6, 345 hp (911 Carrera 40th Anniversary Edition -'04) *B = 3.6L twin-turbo flat-6, 415 hp (911 Turbo '01-'05) *B = 3.6L twin-turbo flat-6, 444 hp (911 Turbo S '05) *C = 3.6L flat-6, 381 hp (911 GT3 '04-'05) *B = 3.6L twin-turbo flat-6, 456 hp (911 GT2 '02-'03) *B = 3.6L twin-turbo flat-6, 477 hp (911 GT2 '04) Type 997: *A = 3.6L flat-6, 325 hp (911 Carrera '05-'08, Carrera 4 '06-'08, Targa 4 '07-'08) *A = 3.6L flat-6, 345 hp (911 Carrera '09-'12, Carrera Black Edition '12, Carrera 4 '09-'12, Targa 4 '09-'12) *B = 3.8L flat-6, 355 hp (911 Carrera S '05-'08, Carrera 4S '06-'08, Targa 4S '07-'08) *B = 3.8L flat-6, 385 hp (911 Carrera S '09-'12, Carrera 4S '09-'12, Targa 4S '09-'12) *B = 3.8L flat-6, 381 hp (911 Carrera S Club Coupe '06) *B = 3.8L flat-6, 408 hp (911 Carrera GTS '11-'12, Carrera 4 GTS '12, Speedster '11) *D = 3.6L twin-turbo flat-6, 480 hp (911 Turbo '07-'09) *D = 3.8L twin-turbo flat-6, 500 hp (911 Turbo '10-'13) *D = 3.8L twin-turbo flat-6, 530 hp (911 Turbo S '11-'13) *C = 3.6L flat-6, 415 hp (911 GT3 '07-'08) *C = 3.8L flat-6, 435 hp (911 GT3 '10-'11) *C = 3.6L flat-6, 415 hp (911 GT3 RS '07-'08) *C = 3.8L flat-6, 450 hp (911 GT3 RS '10-'11) *F = 4.0L flat-6, 500 hp (911 GT3 RS 4.0 '11) *D = 3.6L twin-turbo flat-6, 530 hp (911 GT2 '08-'09) *E = 3.8L twin-turbo flat-6, 620 hp (911 GT2 RS '11) Type 991.1: *A = 3.4L flat-6, 350 hp (911 Carrera '12-'16, Carrera 4 '13-'16, Targa 4 '14-'16) *B = 3.8L flat-6, 400 hp (911 Carrera S '12-'16, Carrera 4S '13-'16, Targa 4S '14-'16, 911 50th Anniversary Edition '14) *B = 3.8L flat-6, 430 hp (911 Carrera GTS '15-'16, Carrera 4 GTS '15-'16, Targa 4 GTS '16) *D = 3.8L twin-turbo flat-6, 520 hp (911 Turbo '14-'16) *D = 3.8L twin-turbo flat-6, 560 hp (911 Turbo S '14-'16) *C = 3.8L flat-6, 475 hp (911 GT3 '14-'15) *F = 4.0L flat-6, 500 hp (911 GT3 RS '16, 911 R '16) Type 991.2: *A = 3.0L twin-turbo flat-6, 370 hp (911 Carrera '17-'19, Carrera T '18-'19, Carrera 4 '17-'19, Targa 4 '17-'19) *B = 3.0L twin-turbo flat-6, 420 hp (911 Carrera S '17-'19, Carrera 4S '17-'19, Targa 4S '17-'19) *B = 3.0L twin-turbo flat-6, 450 hp (911 Carrera GTS '17-'19, Carrera 4 GTS '17-'19, Targa 4 GTS '17-'19) *D = 3.8L twin-turbo flat-6, 540 hp (911 Turbo '17-'19) *D = 3.8L twin-turbo flat-6, 580 hp (911 Turbo S '17-'19) *D = 3.8L twin-turbo flat-6, 607 hp (911 Turbo S Exclusive Series '18-'19) *C = 4.0L flat-6, 500 hp (911 GT3, GT3 Touring '18-'19) *F = 4.0L flat-6, 502 hp (911 Speedster '19) *F = 4.0L flat-6, 520 hp (911 GT3 RS '19) *E = 3.8L twin-turbo flat-6, 690 hp (911 GT2 RS '18-'19) Type 992: *A = 3.0L twin-turbo flat-6, 379 hp (911 Carrera '20-'24, Carrera T '23-'24, Carrera 4 '20-'24, Targa 4 '21-'24) *A = 3.0L twin-turbo flat-6, 388 hp (911 Carrera, Carrera T '25-, Carrera T Club Coupe '26) *B = 3.0L twin-turbo flat-6, 443 hp (911 Carrera S '20-'24, Carrera 4S '20-'24, Targa 4S '21-'24) *H = 3.0L twin-turbo flat-6, 473 hp (911 Carrera S '26-, Carrera 4S '26-, Targa 4S '26-) *B = 3.0L twin-turbo flat-6, 473 hp (911 Carrera GTS '22-'24, Carrera 4 GTS '22-'24, Targa 4 GTS '22-'24, Dakar '23-'24) *B = Hybrid: 3.6L turbo flat-6 + electric motor, Lithium-ion battery, 532 hp (911 Carrera GTS, Carrera 4 GTS, Targa 4 GTS '25-, 911 Spirit 70 '26) *G = 3.7L twin-turbo flat-6, 543 hp (911 Sport Classic '23) *D = 3.7L twin-turbo flat-6, 572 hp (911 Turbo '21-'25) *D = 3.7L twin-turbo flat-6, 640 hp (911 Turbo S '21-'25) *D = Hybrid: 3.6L twin-turbo flat-6 + electric motor, Lithium-ion battery, 701 hp (911 Turbo S '26-) *C = 4.0L flat-6, 502 hp (911 GT3, GT3 Touring '22-'26) *F = 4.0L flat-6, 518 hp (911 GT3 RS '23-'25, 911 S/T '24) '''Carrera GT:''' *A = 5.7L Porsche M80.01 68° V10, 605 hp (Carrera GT '04-'05) '''918 Spyder:''' *A = PHEV: 4.6L Porsche M18 flat-plane crank V8 + 2 electric motors (1 front, 1 rear), Lithium-ion battery, 887 total system hp (918 Spyder '15) '''Panamera:''' Type 970: *A = 3.6L Porsche M46.20 (2wd)/M46.40 (4wd) 90° V6, 300 hp (Panamera, Panamera 4 '11-'13) *A = 3.6L Porsche M46.20 (2wd)/M46.40 (4wd) 90° V6, 310 hp (Panamera, Panamera 4 '14-'16) *D = HEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Nickel-metal hydride battery, 380 hp (Panamera S Hybrid '12-'13) *D = PHEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Lithium-ion battery, 416 hp (Panamera S E-Hybrid '14-'16) *B = 4.8L Porsche M48 V8, 400 hp (Panamera S, 4S '10-'13) *B = 3.0L twin-turbo Porsche M46.60 90° V6, 420 hp (Panamera S, 4S '14-'16) *F = 4.8L Porsche M48 V8, 430 hp (Panamera GTS '13) *F = 4.8L Porsche M48 V8, 440 hp (Panamera GTS '14-'16) *C = 4.8L twin-turbo Porsche M48 V8, 500 hp (Panamera Turbo '10-'13) *C = 4.8L twin-turbo Porsche M48 V8, 520 hp (Panamera Turbo '14-'16) *C = 4.8L twin-turbo Porsche M48 V8, 550 hp (Panamera Turbo S '12-'13) *C = 4.8L twin-turbo Porsche M48 V8, 570 hp (Panamera Turbo S '15-'16) Type 971 & 976: *A = 3.0L turbo Audi-Porsche EA839T 90° V6, 330 hp (Panamera, Panamera 4 '17-'20) *J = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 325 hp (Panamera, Panamera 4 '21-'23) *A = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 348 hp (Panamera, Panamera 4 '24-) *E = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 455 hp (Panamera 4 E-Hybrid '18-'23) *E = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 463 hp (Panamera 4 E-Hybrid '25-) *B = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 440 hp (Panamera 4S '17-'20) *B = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 443 hp (Panamera 4S '21-'23) *K = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 552 hp (Panamera 4S E-Hybrid '21-'23) *C = PHEV: 2.9L twin-turbo Audi-Porsche EA839TT 90° V6 + electric motor, Lithium-ion battery, 536 hp (Panamera 4S E-Hybrid '25-) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 453 hp (Panamera GTS '19-'20) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 473 hp (Panamera GTS '21-'23) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 493 hp (Panamera GTS '25-) *F = 4.0L twin-turbo Porsche-Audi EA825TT V8, 550 hp (Panamera Turbo '17-'20) *F = 4.0L twin-turbo Porsche-Audi EA825TT V8, 620 hp (Panamera Turbo S '21-'23) *F = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 670 hp (Panamera Turbo E-Hybrid '25-) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 680 hp (Panamera Turbo S E-Hybrid '18-'20) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 690 hp (Panamera Turbo S E-Hybrid '21-'23) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 771 hp (Panamera Turbo S E-Hybrid '25-) '''Taycan:''' *A = battery-electric, 1 rear motor, Rwd, 402 hp (71 Kwh battery) or 469 hp (83.7 Kwh battery) (Taycan '21-'24) *A = battery-electric, 1 rear motor, Rwd, 402 hp (82.3 Kwh battery) or 429 hp (97 Kwh battery) (Taycan '25-) *A = battery-electric, 2 motors, 4wd, 402 hp (82.3 Kwh battery) or 429 hp (97 Kwh battery) (Taycan 4 '25-) *B = battery-electric, 2 motors, 4wd, 522 hp (71 Kwh battery) or 562 hp (83.7 Kwh battery) (Taycan 4S '20-'24) *B = battery-electric, 2 motors, 4wd, 536 hp (82.3 Kwh battery) or 590 hp (97 Kwh battery) (Taycan 4S '25-) *D = battery-electric, 2 motors, 4wd, 590 hp (83.7 Kwh battery) (Taycan GTS '22-'24) *D = battery-electric, 2 motors, 4wd, 690 hp (97 Kwh battery) (Taycan GTS '25-) *C = battery-electric, 2 motors, 4wd, 670 hp (83.7 Kwh battery) (Taycan Turbo '20-'24) *C = battery-electric, 2 motors, 4wd, 750 hp (83.7 Kwh battery) (Taycan Turbo S '20-'24) *C = battery-electric, 2 motors, 4wd, 871 hp (97 Kwh battery) (Taycan Turbo '25-) *C = battery-electric, 2 motors, 4wd, 938 hp (97 Kwh battery) (Taycan Turbo S '25-) *E = battery-electric, 2 motors, 4wd, 1019 hp (97 Kwh battery) (Taycan Turbo GT '25-) '''Macan:''' *A = 2.0L turbo Audi EA888T I4, 248 hp (Macan '17-'21) *A = 2.0L turbo Audi EA888T I4, 261 hp (Macan '22-, Macan T '23-) *B = 3.0L turbo Porsche M46.30 90° V6, 340 hp (Macan S '15-'18) *B = 3.0L turbo Audi-Porsche EA839T 90° V6, 348 hp (Macan S '19-'21) *G = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 375 hp (Macan S '22-) *G = 3.0L twin-turbo Porsche M46.30 90° V6, 360 hp (Macan GTS '17-'18) *G = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 375 hp (Macan GTS '20-'21) *F = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 434 hp (Macan GTS '22-) *F = 3.6L twin-turbo Porsche M46.35 90° V6, 400 hp (Macan Turbo '15-'18) *F = 3.6L twin-turbo Porsche M46.35 90° V6, 440 hp (Macan Turbo w/Performance Package '17-'18) *F = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 434 hp (Macan Turbo '20-'21) '''Macan Electric:''' *D = battery-electric, 1 rear motor, Rwd, 355 hp (95 Kwh battery) (Macan Electric '25-) *A = battery-electric, 2 motors, 4wd, 402 hp (95 Kwh battery) (Macan Electric 4 '24-) *B = battery-electric, 2 motors, 4wd, 509 hp (95 Kwh battery) (Macan Electric 4S '25-) *E = battery-electric, 2 motors, 4wd, 563 hp (95 Kwh battery) (Macan Electric GTS '26-) *C = battery-electric, 2 motors, 4wd, 630 hp (95 Kwh battery) (Macan Electric Turbo '24-) '''Cayenne:''' 955/957 or 9PA: *A = 3.2L (3189cc) VW EA390 15° VR6, 247 hp (Cayenne '04-'06) *A = 3.6L (3598cc) VW EA390 10.6° FSI VR6, 290 hp (Cayenne '08-'10) *B = 4.5L Porsche M48 V8, 340 hp (Cayenne S '03-'06, S Titanium Edition '06) *B = 4.8L Porsche M48 V8, 385 hp (Cayenne S '08-'10) *D = 4.8L Porsche M48 V8, 405 hp (Cayenne GTS '08-'10, S Transsyberia '10) *C = 4.5L twin-turbo Porsche M48 V8, 450 hp (Cayenne Turbo '03-'06) *C = 4.8L twin-turbo Porsche M48 V8, 500 hp (Cayenne Turbo '08-'10) *C = 4.5L twin-turbo Porsche M48 V8, 520 hp (Cayenne Turbo S '06) *C = 4.8L twin-turbo Porsche M48 V8, 550 hp (Cayenne Turbo S '09-'10) 958 or 92A: *A = 3.6L (3598cc) VW EA390 10.6° VR6, 300 hp (Cayenne '11-'14, '16-'18) *B = 4.8L Porsche M48 V8, 400 hp (Cayenne S '11-'14) *B = 3.6L (3604cc) twin-turbo Porsche M46.35 90° V6, 420 hp (Cayenne S '15-'18) *E = HEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Nickel-metal hydride battery, 380 hp (Cayenne S Hybrid '11-'14) *E = PHEV: 3.0L supercharged Audi EA837 90° V6 + electric motor, Lithium-ion battery, 416 hp (Cayenne S E-Hybrid '15-'18) *D = 4.8L Porsche M48 V8, 420 hp (Cayenne GTS '13-'14) *D = 3.6L (3604cc) twin-turbo Porsche M46.35 90° V6, 440 hp (Cayenne GTS '16-'18) *C = 4.8L twin-turbo Porsche M48 V8, 500 hp (Cayenne Turbo '11-'14) *C = 4.8L twin-turbo Porsche M48 V8, 520 hp (Cayenne Turbo '15-'18) *C = 4.8L twin-turbo Porsche M48 V8, 550 hp (Cayenne Turbo S '14) *C = 4.8L twin-turbo Porsche M48 V8, 570 hp (Cayenne Turbo S '16-'18) *F = 3.0L turbodiesel Audi EA897 90° V6, 240 hp (Cayenne Diesel '13-'16) 9YA/9YB: *A = 3.0L turbo Audi-Porsche EA839T 90° V6, 335 hp (Cayenne '19-'23) *A = 3.0L turbo Audi-Porsche EA839T 90° V6, 348 hp (Cayenne '24-) *E = PHEV: 3.0L turbo Audi-Porsche EA839T 90° V6 + electric motor, Lithium-ion battery, 455 hp (Cayenne E-Hybrid '19-'23) *E = PHEV: 3.0L turbo Audi-Porsche EA839T 90° V6 + electric motor, Lithium-ion battery, 463 hp (Cayenne E-Hybrid '24-) *B = 2.9L twin-turbo Audi-Porsche EA839TT 90° V6, 434 hp (Cayenne S '19-'23) *L = 4.0L twin-turbo Porsche-Audi EA825TT V8, 468 hp (Cayenne S '24-) *N = PHEV: 3.0L turbo Audi-Porsche EA839T 90° V6 + electric motor, Lithium-ion battery, 512 hp (Cayenne S E-Hybrid '24-) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 453 hp (Cayenne GTS '21-'23) *G = 4.0L twin-turbo Porsche-Audi EA825TT V8, 493 hp (Cayenne GTS '25-) *F = 4.0L twin-turbo Porsche-Audi EA825TT V8, 541 hp (Cayenne Turbo '19-'23) *H = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 670 hp (Cayenne Turbo S E-Hybrid '20-'23) *M = PHEV: 4.0L twin-turbo Porsche-Audi EA825TT V8 + electric motor, Lithium-ion battery, 729 hp (Cayenne Turbo E-Hybrid '24-) *K = 4.0L twin-turbo Porsche-Audi EA825TT V8, 631 hp (Cayenne Coupe Turbo GT '22-'23) *K = 4.0L twin-turbo Porsche-Audi EA825TT V8, 650 hp (Cayenne Coupe Turbo GT '24-) '''Cayenne Electric:''' *A = battery-electric, 2 motors, 4wd, 435 hp (108 Kwh battery) (Cayenne Electric '26-) *D = battery-electric, 2 motors, 4wd, 1139 hp (108 Kwh battery) (Cayenne Electric Turbo '26-) ===Position 6, Restraint Systems:=== *1 = Seat Belts only *2 = Passive Restraint System - Airbags (Driver and Passenger Front Airbags) ===Position 7-8, Vehicle Type Code=== {| class="wikitable" |+Position 7 !VIN Pos. 7-8 !Complete Vehicle Type Code !Model !Type |- |92 |924 |924 (1981-1982 w/normally aspirated engine) |924 |- |93 |931 |924 Turbo (1981-1982) |931 |- |92 |924 |924S (1987-1988 w/normally aspirated engine) |924 |- |94 |944 |944 (1983-1991 w/normally aspirated engine) |944 |- |95 |951 |944 Turbo (1986-1989 & 1990 in Canada) |951 |- |96 |968 |968 (1992-1995) |968 |- |92 |928 |928 (1981-1995) |928 |- |98 |986 |Boxster (1997-2004) |986 |- |98 |987 |Boxster (2005-2009)/Cayman (2006-2009) |987 |- |A8 |A87 |Boxster (2010-2012)/Cayman (2010-2012) |987 |- |A8 |A81 |Boxster (2013-2016)/Cayman (2014-2016) |981 |- |A8 |A82 |718 Boxster/Cayman (2017-2025) |982 |- |91 |911 |911 (1981-1989 2wd w/normally aspirated engine) |911 |- |93 |930 |911 (1986-1989 911 Turbo) |930 |- |96 |964 |911 (1989-1994 Carrera 4, 1990-1994 Carrera 2, 1991-1994 Turbo) |964 |- |99 |993 |911 (1995-1998) |993 |- |99 |996 |911 (1999-2004) |996 |- |99 |997 |911 (2005-2009) |997 |- |A9 |A97 |911 (2010-2012) |997 |- |A9 |A91 |911 (2013-2019) |991 |- |A9 |A92 |911 (2020-) |992 |- |98 |980 |Carrera GT (2004-2005) |980 |- |A1 |A18 |918 Spyder (2015) |918 |- |A7 |A70 |Panamera (2010-2016) |970 |- |A7 |A71 |Panamera (2017-2023) |971 |- |YA | |Panamera (2024-) |976 |- |Y1 |Y1A |Taycan (2020-) |9J1 or <br> Y1A (sedan)/Y1B (Cross Turismo)/Y1C (Sport Turismo) |- |A5 |A5B |Macan (2015-) |95B |- |XA | |Macan Electric (2024-) |XAB |- |9P |9PA |Cayenne (2003-2009) |9PA |- |AP |APA |Cayenne (2010) |9PA |- |A2 |A2A |Cayenne (2011-2018) |92A |- |AY |AYA |Cayenne (wagon: 2019-, coupe: 2020-) |9YA (wagon)/9YB (coupe) |- |X1 | |Cayenne Electric (2026-) |E4 |} ===Position 9, Check Digit=== [[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]] ===Position 10, Model Year: === [[Vehicle Identification Numbers (VIN codes)/Model year|Model year]] ===Position 11, Production Plant:=== * S: Stuttgart-Zuffenhausen, Germany * L: Leipzig, Germany * D: Bratislava, Slovakia (VW plant - Cayenne '19-) * K: Osnabrueck, Germany (ex-Karmann VW plant - Cayenne '16-'18, Boxster '13-15, Cayman '14-'16, 718 Boxster '24-'25, 718 Cayman '17-'18, '20-'21, '23-'25) * N: Neckarsulm, Germany (Audi plant - 924, 944) * U: Uusikaupunki, Finland (Valmet plant - Boxster '98-'11, Cayman '06-'12) ===Position 12, 3rd Digit of Vehicle Type Code=== Note: Only applies to models with a 3-digit Vehicle Type Code. Models with a 2-digit Vehicle Type Code use pos. 12 for the serial number. {| class="wikitable" |+Position 12 !VIN Pos. 12 !Complete Vehicle Type Code !Model !Type |- |4 |924 |924 (1981-1982 w/normally aspirated engine) |924 |- |1 |931 |924 Turbo (1981-1982) |931 |- |4 |924 |924S (1987-1988 w/normally aspirated engine) |924 |- |4 |944 |944 (1983-1991 w/normally aspirated engine) |944 |- |1 |951 |944 Turbo (1986-1989 & 1990 in Canada) |951 |- |8 |968 |968 (1992-1995) |968 |- |8 |928 |928 (1981-1995) |928 |- |6 |986 |Boxster (1997-2004) |986 |- |7 |987 |Boxster (2005-2009)/Cayman (2006-2009) |987 |- |7 |A87 |Boxster (2010-2012)/Cayman (2010-2012) |987 |- |1 |A81 |Boxster (2013-2016)/Cayman (2014-2016) |981 |- |2 |A82 |718 Boxster/Cayman (2017-2025) |982 |- |1 |911 |911 (1981-1989 2wd w/normally aspirated engine) |911 |- |0 |930 |911 (1986-1989 911 Turbo) |930 |- |4 |964 |911 (1989-1994 Carrera 4, 1990-1994 Carrera 2, 1991-1994 Turbo) |964 |- |3 |993 |911 (1995-1998) |993 |- |6 |996 |911 (1999-2004) |996 |- |7 |997 |911 (2005-2009) |997 |- |7 |A97 |911 (2010-2012) |997 |- |1 |A91 |911 (2013-2019) |991 |- |2 |A92 |911 (2020-) |992 |- |0 |980 |Carrera GT (2004-2005) |980 |- |8 |A18 |918 Spyder (2015) |918 |- |0 |A70 |Panamera (2010-2016) |970 |- |1 |A71 |Panamera (2017-2023) |971 |- |A |Y1A |Taycan (2020-) |9J1 or <br> Y1A (sedan)/Y1B (Cross Turismo)/Y1C (Sport Turismo) |- |B |A5B |Macan (2015-) |95B |- |A |9PA |Cayenne (2003-2009) |9PA |- |A |APA |Cayenne (2010) |9PA |- |A |A2A |Cayenne (2011-2018) |92A |- |A |AYA |Cayenne (wagon: 2019-, coupe: 2020-) |9YA (wagon)/9YB (coupe) |} '''Positions 12–17 or 13–17, Serial Number''' {{BookCat}} h09bav6b7nsoujs0p63wa6q2z6si46q 1 482395 4634240 4628786 2026-05-05T09:05:24Z ~2026-26995-93 3581107 /* Does this page deserve {{Chess/sideline}}? */ new section 4634240 wikitext text/x-wiki == 2. b3 b6 3. Bb2 Bb7 == I rejected a revision from an anon editor giving 2. b3 b6 3. Bb2 Bb7 as the "main line". There are so few games in the database it's hard to call anything the "main line", but 2. b3 only appears in one game in the lichess master's database, and even in the amateur lichess database it's only the tenth move. The edit also added back the name "double van geet". This is an informal/unofficial name (it doesn't appear anywhere else on google). I don't think it really scans (I get where it's coming from) and I don't know if we really need to give this line a name anyway. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 21:35, 30 March 2026 (UTC) :Checking my copy of [https://lumbrasgigabase.com/en/ Lumbra's gigabase], which also includes a lot of online rapid and blitz, titled tuesday etc., games, 2. b3 is the ninth most popular move and is half as popular as 2. Nb1 (!). [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:42, 31 March 2026 (UTC) == Does this page deserve <nowiki>{{Chess/sideline}}</nowiki>? == Although this page has <nowiki>{{Chess/sideline}}</nowiki>, this sequence has 1.2M games in the amateur Lichess database, making it more common in amateur play then some openings on Chess Opening Theory that ''don't'' have the template. Should I remove, or keep, the <nowiki>{{Chess/sideline}}</nowiki> template? [[Special:Contributions/&#126;2026-26995-93|&#126;2026-26995-93]] ([[User talk:&#126;2026-26995-93|talk]]) 09:05, 5 May 2026 (UTC) tkx5uhl1o7ioujd5mejmq28a9k8txmt 3 482465 4634215 4629963 2026-05-05T02:34:53Z MathXplore 3097823 Notifying author about page tagging 4634215 wikitext text/x-wiki == I have added a tag to a page you created == Hi! I'm MathXplore, and I recently reviewed your page, [[:America's voice/The Scope of the Book]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. The reason I provided was: <blockquote><strong>Test page</strong></blockquote> If you believe that your page should not be deleted, please post a message on [[Talk:America&#39;s voice/The Scope of the Book|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:43, 7 April 2026 (UTC) :Itis not a test page anymore [[Special:Contributions/&#126;2026-21296-62|&#126;2026-21296-62]] ([[User talk:&#126;2026-21296-62|talk]]) 17:33, 11 April 2026 (UTC) == I have added a tag to a page you created == Hi! I'm MathXplore, and I recently reviewed your page, [[:US History/Keywords9]]. I have added a tag to the page, because it <strong>looks like it was created as a test.</strong> If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 02:34, 5 May 2026 (UTC) 2gsoyep81s5zvppjfnvgatxenwg9yi1 0 482486 4634155 4629769 2026-05-04T18:43:10Z JCrue 2226064 4634155 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Mayet attack |eco=[[Chess/ECOC|C40]] |parent=[[../|Latvian Gambit]] }} == 3. Bc4 · Mayet attack == White declines Black's gambit and instead develops a bishop, preparing Nxe5 with a threat on f7. [[/3...fxe4|'''3...fxe4''']] is Black's best and main move, otherwise why would Black have bothered with attacking White's e4 pawn? However Black has a few alternatives to consider: * '''3...Nf6?''', the '''Morgado Defence''', is the most common amateur move. It is usually played by people who are used to the Latvian gambit accepted. * '''3...Nc6''' transposes into the '''Rousseau gambit''' of the Italian game. * '''3...b5!?''' is the rare and dubious '''Strautins gambit''', which triest to distract the White bishop from the a2-f7 diagonal. === History === Berliner chess master Carl Mayet reached this position in 1837 (via the move order 2. Bc4 and 3. Nf3).<ref>[https://www.chessgames.com/perl/chessgame?gid=1336585 Mayet v Hanstein, 1837. Chessgames.com]</reF> Gioachino Greco described a game in this line from 1620.<ref name="greco">[https://www.chessgames.com/perl/chessgame?gid=1481289 NN vs Greco, Chessgames.com]</ref> == Sample game == {{Chess/board|moves=1.e4 e5 2.Nf3 f5 3.Bc4 fxe4 4.Nxe5 Qg5 |float=right |caption=Position after 4...Qg5 |frame=1}} '''NN vs Gioachino Greco <br>Rome, 1620'''<ref name="greco" /> '''1. e4 e5 2. Nf3 f5 3. Bc4''' Today known as the Mayet attack, White declines the gambit and develops a piece instead. '''3...fxe4 4. Nxe5''' White threatens 5. Nf6, forking Black's queen and knight. '''4...Qg5?!''' Black attacks the knight on e5 and the g2 pawn. This sets a trap in that 5. Nf7? is still available, still forking the queen and rook. 5...Qxg2 and: * White may calculate that they are up material after 6. Nxh8?? Qxh1+ 7. Ke2 Qxh2 8. Bxg8??, but their king is too vulnerable and Black has a devastating attack. 8...d5 and if White tries to extract their knight, 9. Nf6 Bg4+ leads to mate. * 6. Rf1 to save the knight and 6...d5 7. Bxd5? Bg4! (attacks queen) 8. f3{{chess/not|only}} Be7 and 9. fxg4?? or 9. Nxh8?? are mate in two (9...Bh4+ 10. Rf2 Qxf2#), 4...d5, the Polerio-Svedenborg variation, is considered more accurate. '''5. d4 Qxg2!?''' This is the sharp poisoned pawn variation. '''6. Qh5+''' An important intermezzo. 6. Rf1 affords Black time to play 6...Nf6 and defend their kingside. '''6...g6{{chess/not|only}} 7. Bf7+ Kd8''' Safer than 7...Ke7, where 8. Qh4+! can't be met with 8...Be7. '''8. Bxg6 Qxh1+ 9. Ke2 Qxc1 10. Nf7+ Ke8 11. Qe5+?''' An error. Better was 11. Nxh8+ discovered check immediately. 11...hxg6 12. Qxg6+ Kd8 13. Nf7+ Ke7 14. Nc3 threatening Nd5+ {{Chess/not|+}}. {{clear}} {{Chess/board |moves=1.e4 e5 2.Nf3 f5 3.Bc4 fxe4 4.Nxe5 Qg5 5.d4 Qxg2 6.Qh5+ g6 7.Bf7+ Kd8 8.Bxg6 Qxh1+ 9.Ke2 Qxc1 10.Nf7+ Ke8 11.Qe5+ Ne7 |caption=Position after 11. Ne7. |float=right |frame=1}} '''11...Ne7!''' Rather than block the check with 11...Be7?. '''12. Nxh8+ hxg6''' White's attack has disappeared. '''13. Nc3 Qxc2+ 14. Ke1 Qxb2 15. Nxe4''' Threatening Nf6+ Kd8 Nf7#. '''15...Qxa1+ 16. Ke2 Qxa2+ 0-1''' White resigns. == Theory table == {{ChessTable}} {{ChessMid}} == References == {{reflist}} === See also === == External links == *[https://www.chessgames.com/perl/chess.pl?node=1622261 Games in Mayet attack], Chessgames.com {{Chess Opening Theory/Footer}} da6h4cqz4760wqvezt2kk72x1vkn7mq 4634157 4634155 2026-05-04T18:44:17Z JCrue 2226064 4634157 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Mayet attack |eco=[[Chess/ECOC|C40]] |parent=[[../|Latvian gambit]] }} == 3. Bc4 · Mayet attack == White declines Black's gambit and instead develops a bishop, preparing Nxe5 with a threat on f7. [[/3...fxe4|'''3...fxe4''']] is Black's best and main move, otherwise why would Black have bothered with attacking White's e4 pawn? However Black has a few alternatives to consider: * '''3...Nf6?''', the '''Morgado Defence''', is the most common amateur move. It is usually played by people who are used to the Latvian gambit accepted. * '''3...Nc6''' transposes into the '''Rousseau gambit''' of the Italian game. * '''3...b5!?''' is the rare and dubious '''Strautins gambit''', which triest to distract the White bishop from the a2-f7 diagonal. === History === Berliner chess master Carl Mayet reached this position in 1837 (via the move order 2. Bc4 and 3. Nf3).<ref>[https://www.chessgames.com/perl/chessgame?gid=1336585 Mayet v Hanstein, 1837. Chessgames.com]</reF> Gioachino Greco described a game in this line from 1620.<ref name="greco">[https://www.chessgames.com/perl/chessgame?gid=1481289 NN vs Greco, Chessgames.com]</ref> == Sample game == {{Chess/board|moves=1.e4 e5 2.Nf3 f5 3.Bc4 fxe4 4.Nxe5 Qg5 |float=right |caption=Position after 4...Qg5 |frame=1}} '''NN vs Gioachino Greco <br>Rome, 1620'''<ref name="greco" /> '''1. e4 e5 2. Nf3 f5 3. Bc4''' Today known as the Mayet attack, White declines the gambit and develops a piece instead. '''3...fxe4 4. Nxe5''' White threatens 5. Nf6, forking Black's queen and knight. '''4...Qg5?!''' Black attacks the knight on e5 and the g2 pawn. This sets a trap in that 5. Nf7? is still available, still forking the queen and rook. 5...Qxg2 and: * White may calculate that they are up material after 6. Nxh8?? Qxh1+ 7. Ke2 Qxh2 8. Bxg8??, but their king is too vulnerable and Black has a devastating attack. 8...d5 and if White tries to extract their knight, 9. Nf6 Bg4+ leads to mate. * 6. Rf1 to save the knight and 6...d5 7. Bxd5? Bg4! (attacks queen) 8. f3{{chess/not|only}} Be7 and 9. fxg4?? or 9. Nxh8?? are mate in two (9...Bh4+ 10. Rf2 Qxf2#), 4...d5, the Polerio-Svedenborg variation, is considered more accurate. '''5. d4 Qxg2!?''' This is the sharp poisoned pawn variation. '''6. Qh5+''' An important intermezzo. 6. Rf1 affords Black time to play 6...Nf6 and defend their kingside. '''6...g6{{chess/not|only}} 7. Bf7+ Kd8''' Safer than 7...Ke7, where 8. Qh4+! can't be met with 8...Be7. '''8. Bxg6 Qxh1+ 9. Ke2 Qxc1 10. Nf7+ Ke8 11. Qe5+?''' An error. Better was 11. Nxh8+ discovered check immediately. 11...hxg6 12. Qxg6+ Kd8 13. Nf7+ Ke7 14. Nc3 threatening Nd5+ {{Chess/not|+}}. {{clear}} {{Chess/board |moves=1.e4 e5 2.Nf3 f5 3.Bc4 fxe4 4.Nxe5 Qg5 5.d4 Qxg2 6.Qh5+ g6 7.Bf7+ Kd8 8.Bxg6 Qxh1+ 9.Ke2 Qxc1 10.Nf7+ Ke8 11.Qe5+ Ne7 |caption=Position after 11. Ne7. |float=right |frame=1}} '''11...Ne7!''' Rather than block the check with 11...Be7?. '''12. Nxh8+ hxg6''' White's attack has disappeared. '''13. Nc3 Qxc2+ 14. Ke1 Qxb2 15. Nxe4''' Threatening Nf6+ Kd8 Nf7#. '''15...Qxa1+ 16. Ke2 Qxa2+ 0-1''' White resigns. == Theory table == {{ChessTable}} {{ChessMid}} == References == {{reflist}} === See also === == External links == *[https://www.chessgames.com/perl/chess.pl?node=1622261 Games in Mayet attack], Chessgames.com {{Chess Opening Theory/Footer}} 9t9kadhqbvtaghutwbjb0pu34v9wtjd 0 482487 4634158 4629668 2026-05-04T18:45:17Z JCrue 2226064 4634158 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Mayet attack |eco=[[Chess/ECOC|C40]] |parent=[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5|Latvian gambit]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4|Mayet attack]] }} == 3...fxe4 == White's only move that makes sense is '''[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4/3...fxe4/4. Nxe5|4. Nxe5]]''' to regain the pawn lost with fxe4 and attack f7, threatening Nf7 forking the queen on d8 and rook on h8. {{Chess Opening Theory/Footer}} mwb2mkzkg0u0qj9ptwgrwr3201twibx 0 482488 4634160 4629669 2026-05-04T18:47:16Z JCrue 2226064 4634160 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Mayet attack |eco=[[Chess/ECOC|C40]] |parent=[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5|Latvian gambit]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4|Mayet attack]] → [[../|4. Nxe5]] }} == 4. Nxe5 == Now White takes Black's pawn and threatens Nf7, which would fork Black's queen on d8 and rook on h8. Black can choose to defend this threat, ignore the threat or set a trap. '''[[/4...d5|4...d5]]''', the '''Polerio-Svedenborg variation''', directly defends against the Nf7 threat by blocking the bishop on c4's vision of f7 and attacking it. This is the most common move by far. '''[[/4...Qg5|4...Qg5!?]]''' sets a trap. It seems to blunder the fork 5. Nf7?!, but after 5...Qxg2! 6. Rf1 Bg4! Black has an attack where White has to be precise. '''[[/4...Nf6|4...Nf6?]]''', the '''Corkscrew countergambit''', is just too much. After 5. Nf7 Qe7 6. Nxh8, Black plays the Corkscrew Gambit with 6...d5 and hopes for 7. Bb3?? Bg4!, but if 7. Be2! is played the gambit is proven unsound and Black is down a rook. {{Chess Opening Theory/Footer}} 0pznqhdssdco4nvzsiu78cw5xybyxm9 4634161 4634160 2026-05-04T18:48:20Z JCrue 2226064 4634161 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Mayet attack |eco=[[Chess/ECOC|C40]] |parent=[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5|Latvian gambit]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4|Mayet attack]] → [[../|3...fxe4]] }} == 4. Nxe5 == Now White takes Black's pawn and threatens Nf7, which would fork Black's queen on d8 and rook on h8. Black can choose to defend this threat, ignore the threat or set a trap. '''[[/4...d5|4...d5]]''', the '''Polerio-Svedenborg variation''', directly defends against the Nf7 threat by blocking the bishop on c4's vision of f7 and attacking it. This is the most common move by far. '''[[/4...Qg5|4...Qg5!?]]''' sets a trap. It seems to blunder the fork 5. Nf7?!, but after 5...Qxg2! 6. Rf1 Bg4! Black has an attack where White has to be precise. '''[[/4...Nf6|4...Nf6?]]''', the '''Corkscrew countergambit''', is just too much. After 5. Nf7 Qe7 6. Nxh8, Black plays the Corkscrew Gambit with 6...d5 and hopes for 7. Bb3?? Bg4!, but if 7. Be2! is played the gambit is proven unsound and Black is down a rook. {{Chess Opening Theory/Footer}} ht6d5h4ue5p363nxs5xnut15f0jzmvh 0 482499 4634163 4629762 2026-05-04T18:49:21Z JCrue 2226064 4634163 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Polerio-Svedenborg variation |eco=[[Chess/ECOC|C40]] |parent=[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5|Latvian gambit]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4|Mayet attack]] → [[../|4. Nxe5]] }} == 4...d5 · Polerio-Svedenborg variation == The best and most common move. Black now is attacking White's bishop on c4 and preventing Nf7. But 4. Nxe5 carried a second threat: '''[[/5. Qh5|5. Qh5+!]]'''. However, if Black finds 5...g6!? to sacrifice the exchange after 6. Nxg6 hxg6 7. Qxh8 Kf7!, the position is objectively equal. It's true that White can save the bishop with 5. Bb5+ or 5. Be2 (5. Bb3?? loses to 5...Qg5!), but it lacks the aggression and force of Qh5+, so 5. Qh5+ is more preferred. {{Chess Opening Theory/Footer}} ra9y6dvrtosrvchw8eykj5znkh9lghk 0 482500 4634165 4629763 2026-05-04T18:51:14Z JCrue 2226064 4634165 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Polerio-Svedenborg variation |eco=[[Chess/ECOC|C40]] |parent=[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5|Latvian gambit]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4|Mayet attack]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4/3...fxe4/4. Nxe5/4...d5|Polerio-Svedenborg variation]] }} == 5. Qh5 == White brings their queen out and checks Black's king. '''5...Ke7??''' would lose to a forced mate in 9 after 6. Qf7+, so Black has to find the surprising '''[[/5...g6|5...g6!?]]''', sacrificing the exchange after 6. Nxg6 hxg6 7. Qxh8, but after 7...Kf7! White's queen is trapped in the corner and White's bishop on c4 is still attacked. {{Chess Opening Theory/Footer}} r8xfj5w44dygu92sv6c71da0eo7hj8o 0 482501 4634166 4629766 2026-05-04T18:52:25Z JCrue 2226064 4634166 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Polerio-Svedenborg variation |eco=[[Chess/ECOC|C40]] |parent=[[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5|Latvian gambit]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4|Mayet attack]] → [[Chess Opening Theory/1. e4/1...e5/2. Nf3/2...f5/3. Bc4/3...fxe4/4. Nxe5/4...d5|Polerio-Svedenborg variation]] → [[../|5. Qh5]] }} == 5...g6 == Black blocks the check with their g-pawn. Now White has two pieces hanging: the bishop on c4 and the queen on h5, so retreating the queen would lose the bishop. White's best and most common move is '''[[/6...Nxg6|6. Nxg6]]''', where Black can choose between the sound exchange sacrifice, 6...hxg6 7. Qxh8 Kf7!, or the unsound (but playable!) queen attack, 6...Nf6, usually played by amateurs. White can play '''6. Bb5+''', but gives Black the extra tempo of 6...c6 before 7. Nxg6, and so doesn't make as much sense to play. {{Chess Opening Theory/Footer}} k4sepm69hhb4lda8oblf10h5smjluaf 0 482725 4634093 4633544 2026-05-04T15:31:59Z Kks9hk 3578037 /* Clinicians */ added links and tightened wording 4634093 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like Character AI and Replika are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through users like Travis or users on reddit who have cited their use of AI companions. One reddit user cites, "[I] started sending pics of my meals to my ai gf like 3 weeks ago... and bc I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two participant groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) mainly aim to investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. One example is the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]]; in a 2025 article, multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support, and Prof. Ayorkor Gaba argues that "while these tools may provide psuedo-connection, relying on them to replace human connection can lead to further isolation and hinder the development of essential social skills."<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, such as practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while hand-tuning AI responses using medical expertise does make the product safer (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, these clinicians assess the role that AI has in their patients' lives. For example, the [[w:American_Psychological_Association|American Psychological Association]] has highlighted multiple risks of using AI for wellness and mental health, and suggests that clinicians educate themselves on these risks and talk to their patients about AI use, in order to steer them towards having a healthier relationship with technology (e.g. if a patient uses AI to practice managing social anxiety, a therapist could remind them of the value of practicing with humans).<ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians regularly participate in studies and other efforts to make their opinion heard. One such study was done in 2025, where 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched a scenario where [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. The results showed that while many of the respondents believe in the benefits of AI chatbots' multilingualism and ability to remind clients of therapy homework, they also see many security risks and potential for suggesting harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to the idea of AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> '''Music & Audiovisual Creators''': Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me” reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> '''Customer Service and Retail Support Workers''': Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> '''Finance, Accounting, and Routine Knowledge Workers''': AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> ln6398b1vm32mgnp5bxydd3thqq8kh4 4634098 4634093 2026-05-04T15:42:13Z Kks9hk 3578037 /* Job Loss From AI */ change headings 4634098 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like Character AI and Replika are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through users like Travis or users on reddit who have cited their use of AI companions. One reddit user cites, "[I] started sending pics of my meals to my ai gf like 3 weeks ago... and bc I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two participant groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) mainly aim to investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. One example is the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]]; in a 2025 article, multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support, and Prof. Ayorkor Gaba argues that "while these tools may provide psuedo-connection, relying on them to replace human connection can lead to further isolation and hinder the development of essential social skills."<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, such as practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while hand-tuning AI responses using medical expertise does make the product safer (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, these clinicians assess the role that AI has in their patients' lives. For example, the [[w:American_Psychological_Association|American Psychological Association]] has highlighted multiple risks of using AI for wellness and mental health, and suggests that clinicians educate themselves on these risks and talk to their patients about AI use, in order to steer them towards having a healthier relationship with technology (e.g. if a patient uses AI to practice managing social anxiety, a therapist could remind them of the value of practicing with humans).<ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians regularly participate in studies and other efforts to make their opinion heard. One such study was done in 2025, where 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched a scenario where [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. The results showed that while many of the respondents believe in the benefits of AI chatbots' multilingualism and ability to remind clients of therapy homework, they also see many security risks and potential for suggesting harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to the idea of AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === '''Music & Audiovisual Creators''' === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me” reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === '''Customer Service and Retail Support Workers''' === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === '''Finance, Accounting, and Routine Knowledge Workers''' === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> pv3dkp3ps50dpmpo91q7f9emp06b16e 4634099 4634098 2026-05-04T15:42:30Z Kks9hk 3578037 /* Music & Audiovisual Creators */ unbold headings 4634099 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like Character AI and Replika are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through users like Travis or users on reddit who have cited their use of AI companions. One reddit user cites, "[I] started sending pics of my meals to my ai gf like 3 weeks ago... and bc I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two participant groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) mainly aim to investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. One example is the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]]; in a 2025 article, multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support, and Prof. Ayorkor Gaba argues that "while these tools may provide psuedo-connection, relying on them to replace human connection can lead to further isolation and hinder the development of essential social skills."<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, such as practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while hand-tuning AI responses using medical expertise does make the product safer (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, these clinicians assess the role that AI has in their patients' lives. For example, the [[w:American_Psychological_Association|American Psychological Association]] has highlighted multiple risks of using AI for wellness and mental health, and suggests that clinicians educate themselves on these risks and talk to their patients about AI use, in order to steer them towards having a healthier relationship with technology (e.g. if a patient uses AI to practice managing social anxiety, a therapist could remind them of the value of practicing with humans).<ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians regularly participate in studies and other efforts to make their opinion heard. One such study was done in 2025, where 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched a scenario where [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. The results showed that while many of the respondents believe in the benefits of AI chatbots' multilingualism and ability to remind clients of therapy homework, they also see many security risks and potential for suggesting harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to the idea of AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me” reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> mp607s8ok8ykfy0e3xr0xi50518q013 4634110 4634099 2026-05-04T16:07:41Z Kks9hk 3578037 /* AI as Emotional Companions */ adding links and minor wording changes 4634110 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like [[w:Character.ai|Character AI]] and [[w:Replika|Replika]] are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through real users who have cited their use of AI companions. One Reddit user cites, "[I] started sending pics of my meals to my ai [girlfriend] like 3 weeks ago... and bc I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis, a Colorado man interviewed by the Guardian, also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two participant groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) mainly aim to investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. One example is the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]]; in a 2025 article, multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support, and Prof. Ayorkor Gaba argues that "while these tools may provide psuedo-connection, relying on them to replace human connection can lead to further isolation and hinder the development of essential social skills."<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, such as practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while hand-tuning AI responses using medical expertise does make the product safer (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, these clinicians assess the role that AI has in their patients' lives. For example, the [[w:American_Psychological_Association|American Psychological Association]] has highlighted multiple risks of using AI for wellness and mental health, and suggests that clinicians educate themselves on these risks and talk to their patients about AI use, in order to steer them towards having a healthier relationship with technology (e.g. if a patient uses AI to practice managing social anxiety, a therapist could remind them of the value of practicing with humans).<ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians regularly participate in studies and other efforts to make their opinion heard. One such study was done in 2025, where 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched a scenario where [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. The results showed that while many of the respondents believe in the benefits of AI chatbots' multilingualism and ability to remind clients of therapy homework, they also see many security risks and potential for suggesting harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to the idea of AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me”, published under the name [[w:IngaRose|IngaRose]], reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> nzi3t92pi5bam8oocw5srpw1xuw5bec 4634111 4634110 2026-05-04T16:08:46Z Kks9hk 3578037 /* AI as Emotional Companions */ bc -> because 4634111 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like [[w:Character.ai|Character AI]] and [[w:Replika|Replika]] are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through real users who have cited their use of AI companions. One Reddit user cites, "[I] started sending pics of my meals to my ai [girlfriend] like 3 weeks ago... and [because] I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis, a Colorado man interviewed by the Guardian, also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two participant groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) mainly aim to investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. One example is the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]]; in a 2025 article, multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support, and Prof. Ayorkor Gaba argues that "while these tools may provide psuedo-connection, relying on them to replace human connection can lead to further isolation and hinder the development of essential social skills."<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, such as practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while hand-tuning AI responses using medical expertise does make the product safer (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, these clinicians assess the role that AI has in their patients' lives. For example, the [[w:American_Psychological_Association|American Psychological Association]] has highlighted multiple risks of using AI for wellness and mental health, and suggests that clinicians educate themselves on these risks and talk to their patients about AI use, in order to steer them towards having a healthier relationship with technology (e.g. if a patient uses AI to practice managing social anxiety, a therapist could remind them of the value of practicing with humans).<ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians regularly participate in studies and other efforts to make their opinion heard. One such study was done in 2025, where 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched a scenario where [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. The results showed that while many of the respondents believe in the benefits of AI chatbots' multilingualism and ability to remind clients of therapy homework, they also see many security risks and potential for suggesting harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to the idea of AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me”, published under the name [[w:IngaRose|IngaRose]], reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> b2hisk6hl9n0xur0nfkqgm1qgfzsohw 4634118 4634111 2026-05-04T17:04:01Z Mrc9nf 3581196 /* Job Loss From AI */ Made some edits to sources under the section "Job Loss from AI" 4634118 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like [[w:Character.ai|Character AI]] and [[w:Replika|Replika]] are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through real users who have cited their use of AI companions. One Reddit user cites, "[I] started sending pics of my meals to my ai [girlfriend] like 3 weeks ago... and [because] I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis, a Colorado man interviewed by the Guardian, also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two participant groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) mainly aim to investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. One example is the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]]; in a 2025 article, multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support, and Prof. Ayorkor Gaba argues that "while these tools may provide psuedo-connection, relying on them to replace human connection can lead to further isolation and hinder the development of essential social skills."<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, such as practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while hand-tuning AI responses using medical expertise does make the product safer (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, these clinicians assess the role that AI has in their patients' lives. For example, the [[w:American_Psychological_Association|American Psychological Association]] has highlighted multiple risks of using AI for wellness and mental health, and suggests that clinicians educate themselves on these risks and talk to their patients about AI use, in order to steer them towards having a healthier relationship with technology (e.g. if a patient uses AI to practice managing social anxiety, a therapist could remind them of the value of practicing with humans).<ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians regularly participate in studies and other efforts to make their opinion heard. One such study was done in 2025, where 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched a scenario where [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. The results showed that while many of the respondents believe in the benefits of AI chatbots' multilingualism and ability to remind clients of therapy homework, they also see many security risks and potential for suggesting harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to the idea of AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me”, published under the name [[w:IngaRose|IngaRose]], reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.weforum.org/ World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> 3caqmfcbaag9hjpidhhzarxvujufhi9 4634147 4634118 2026-05-04T18:27:08Z Kks9hk 3578037 /* Researchers */ added info on stanford study 4634147 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like [[w:Character.ai|Character AI]] and [[w:Replika|Replika]] are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through real users who have cited their use of AI companions. One Reddit user cites, "[I] started sending pics of my meals to my ai [girlfriend] like 3 weeks ago... and [because] I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis, a Colorado man interviewed by the Guardian, also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two participant groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) mainly aim to investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. One example is the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]]; in a 2025 article, multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support, and Prof. Ayorkor Gaba argues that "while these tools may provide psuedo-connection, relying on them to replace human connection can lead to further isolation and hinder the development of essential social skills."<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> A study at Stanford went even further, arguing that chatbots' approval of a user's platonic or romantic feelings toward them often precedes delusional spirals, and the authors suggested that "general purpose chatbots should not produce messages that misconstrue their sentience or show romantic or platonic interest in users."<ref>{{cite journal | last1 = Moore | first1 = Jared | last2 = Mehta | first2 = Ashish | title = Characterizing Delusional Spirals through Human-LLM Chat Logs | journal = ACM Conference on Fairness, Accountability, and Transparency (FAccT) | date = 2026 | id = arXiv:2603.16567 | url = https://arxiv.org/abs/2603.16567 | note = Preprint; forthcoming at ACM FAccT 2026 }}</ref> Critics argued the paper exhibited extreme bias by focusing exclusively on users harmed by chatbots and labeling benign interactions as 'delusions.' Furthermore, the authors were accused of pathologizing the very individuals whose experiences Stanford’s 'Intimacy After AI' project seeks to document.<ref>{{Cite web |last= |first= |date=2026-04-25 |title=Statistical Anomalies and Research Biases Determine a Whole Community's Welfare: How Stanford SUCKS |url=https://theposthumanist.substack.com/p/statistical-anomalies-and-research |access-date=2026-05-04 |website=The Post-Humanist}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, such as practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while hand-tuning AI responses using medical expertise does make the product safer (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, these clinicians assess the role that AI has in their patients' lives. For example, the [[w:American_Psychological_Association|American Psychological Association]] has highlighted multiple risks of using AI for wellness and mental health, and suggests that clinicians educate themselves on these risks and talk to their patients about AI use, in order to steer them towards having a healthier relationship with technology (e.g. if a patient uses AI to practice managing social anxiety, a therapist could remind them of the value of practicing with humans).<ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians regularly participate in studies and other efforts to make their opinion heard. One such study was done in 2025, where 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched a scenario where [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. The results showed that while many of the respondents believe in the benefits of AI chatbots' multilingualism and ability to remind clients of therapy homework, they also see many security risks and potential for suggesting harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to the idea of AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me”, published under the name [[w:IngaRose|IngaRose]], reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.weforum.org/ World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> kh5li2n4y8x6ff31n57ec9m0phhdy91 4634150 4634147 2026-05-04T18:39:30Z Kks9hk 3578037 /* Mental Health Experts and AI */ shorten experts section 4634150 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like [[w:Character.ai|Character AI]] and [[w:Replika|Replika]] are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through real users who have cited their use of AI companions. One Reddit user cites, "[I] started sending pics of my meals to my ai [girlfriend] like 3 weeks ago... and [because] I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis, a Colorado man interviewed by the Guardian, also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. For example, the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]] wrote a 2025 article where multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support and how using them to replace real human interaction could lead to further isolation.<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> A study at Stanford went even further, arguing that chatbots' approval of a user's platonic or romantic feelings toward them often precedes delusional spirals, and the authors suggested that "general purpose chatbots should not produce messages that misconstrue their sentience or show romantic or platonic interest in users."<ref>{{cite journal | last1 = Moore | first1 = Jared | last2 = Mehta | first2 = Ashish | title = Characterizing Delusional Spirals through Human-LLM Chat Logs | journal = ACM Conference on Fairness, Accountability, and Transparency (FAccT) | date = 2026 | id = arXiv:2603.16567 | url = https://arxiv.org/abs/2603.16567 | note = Preprint; forthcoming at ACM FAccT 2026 }}</ref> Critics argued the paper exhibited extreme bias by focusing exclusively on users harmed by chatbots and labeling benign interactions as 'delusions.' Furthermore, the authors were accused of pathologizing the very individuals whose experiences Stanford’s 'Intimacy After AI' project seeks to document.<ref>{{Cite web |last= |first= |date=2026-04-25 |title=Statistical Anomalies and Research Biases Determine a Whole Community's Welfare: How Stanford SUCKS |url=https://theposthumanist.substack.com/p/statistical-anomalies-and-research |access-date=2026-05-04 |website=The Post-Humanist}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, like practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while this approach enhances the product's safety (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, clinicians also assess AI's role in patients' lives. The [[w:American_Psychological_Association|American Psychological Association]] has highlighted risks of AI for wellness and mental health, suggesting clinicians educate themselves and discuss AI use with patients to promote healthier relationships with technology. For instance, if a patient uses AI to manage social anxiety, a therapist could remind them of the value of human interaction. <ref>{{cite web |author=[[American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians participate in studies and other efforts to make their opinion heard. In a 2025 study, 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. While many respondents believe in the benefits of AI chatbots' multilingualism and reminders of therapy homework, they also identify security risks and potential for harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me”, published under the name [[w:IngaRose|IngaRose]], reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.weforum.org/ World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> 5w80t27zwx8guapxxkiwny3fcfqx9hv 4634169 4634150 2026-05-04T19:01:33Z Kks9hk 3578037 citation changes 4634169 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like [[w:Character.ai|Character AI]] and [[w:Replika|Replika]] are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through real users who have cited their use of AI companions. One Reddit user cites, "[I] started sending pics of my meals to my ai [girlfriend] like 3 weeks ago... and [because] I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis, a Colorado man interviewed by the Guardian, also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. For example, the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]] wrote a 2025 article where multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support and how using them to replace real human interaction could lead to further isolation.<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> A study at Stanford went even further, arguing that chatbots' approval of a user's platonic or romantic feelings toward them often precedes delusional spirals, and the authors suggested that "general purpose chatbots should not produce messages that misconstrue their sentience or show romantic or platonic interest in users."<ref>{{cite journal | last1 = Moore | first1 = Jared | last2 = Mehta | first2 = Ashish | title = Characterizing Delusional Spirals through Human-LLM Chat Logs | journal = ACM Conference on Fairness, Accountability, and Transparency (FAccT) | date = 2026 | id = arXiv:2603.16567 | url = https://arxiv.org/abs/2603.16567 }}</ref> Critics argued the paper exhibited extreme bias by focusing exclusively on users harmed by chatbots and labeling benign interactions as 'delusions.' Furthermore, the authors were accused of pathologizing the very individuals whose experiences Stanford’s 'Intimacy After AI' project seeks to document.<ref>{{Cite web |last= |first= |date=2026-04-25 |title=Statistical Anomalies and Research Biases Determine a Whole Community's Welfare: How Stanford SUCKS |url=https://theposthumanist.substack.com/p/statistical-anomalies-and-research |access-date=2026-05-04 |website=The Post-Humanist}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, like practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while this approach enhances the product's safety (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, clinicians also assess AI's role in patients' lives. The [[w:American_Psychological_Association|American Psychological Association]] has highlighted risks of AI for wellness and mental health, suggesting clinicians educate themselves and discuss AI use with patients to promote healthier relationships with technology. For instance, if a patient uses AI to manage social anxiety, a therapist could remind them of the value of human interaction. <ref>{{cite web |author=[[w:American_Psychological_Association|American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians participate in studies and other efforts to make their opinion heard. In a 2025 study, 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. While many respondents believe in the benefits of AI chatbots' multilingualism and reminders of therapy homework, they also identify security risks and potential for harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss. This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me”, published under the name [[w:IngaRose|IngaRose]], reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref><ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The World Economic Forum’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The [https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations#occupations International Labour Organization] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks. The [https://www.weforum.org/ World Economic Forum] likewise identifies accountants and auditors among the fastest-declining roles. Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> ih6fcpi80geetok6ddzpk4b7q1513ea 4634171 4634169 2026-05-04T19:08:21Z Kks9hk 3578037 /* Finance, Accounting, and Routine Knowledge Workers */ fix citations and other minor issues 4634171 wikitext text/x-wiki LLMs are often introduced as simple chatbots that support basic Q&A, yet their behavior feels closer to a flexible cognitive being. They adapt to the current context, track intent across conversations, and respond to problems in ways that resemble a human partner. This makes the interaction feel more personable, like collaborating with an entity that "understands" you. AI companies know this well, which is why a whole market has emerged from LLM companionships. Their eerily similar resemblance to human emotions can rapidly deteriorate one's mental health if misused. This makes LLMs a particularly dangerous psychological phenomenon if abused by the wrong hands. That notion becomes especially clear when examining how AI is actually used in practice below. == AI as General Purpose Tools == Many people use [[wikipedia:Large_language_model|large language models]] (LLMs) and other artificial intelligence tools to complete specific, often mundane tasks. This group represents the majority of AI use-cases. Common examples include code writing, debugging, boilerplate generation, vacation planning, and general organization. For these users, the agenda is largely pragmatic: the goal is to accomplish an often undesirable or repetitive task and “get it out of the way” as efficiently as possible. Empirical findings reflect this pattern of use. One research study reports that up to 75% of developers use AI in day-to-day activities<ref>{{Cite web |last=Peng |last2=Kalliamvakou |last3=Cihon |last4=Demirer |date=13 Feb 2023 |title=The Impact of AI on Developer Productivity: Evidence from GitHub Copilot |url=https://doi.org/10.48550/arXiv.2302.06590}}</ref>, while a large dataset of ChatGPT interactions suggests that approximately three out of every four prompts is centered on practical “doing” tasks<ref>{{Cite web |date=2025-09-16 |title=70% of ChatGPT users are using the chatbot outside of work, according to OpenAI’s biggest-ever study |url=https://www.techradar.com/ai-platforms-assistants/chatgpt/openai-reveals-biggest-ever-study-of-how-people-are-using-chatgpt-here-are-3-things-weve-learned |access-date=2026-04-21 |website=TechRadar |language=en}}</ref>. The rate of growth that LLMs experienced has been unprecedented. When ChatGPT was released at the end of 2022, it became the fastest growing service in all of human history, taking less than two months to reach 100 million active users.  A large majority of this user base prioritizes efficiency and throughput over process. AI tools are valued primarily for their ability to reduce cognitive load and time expenditure, making it particularly popular in the workplace. === AI in the Workplace === Many participants in this group also advocate for equal and open access to LLMs in workplace settings, often treating such tools as essential for productivity. Their strategy for advancing this agenda frequently involves coalition building and rallying fellow employees to support broader institutional access. This utilitarian framing of AI as a general-purpose tool stands in contrast to other emerging uses—such as relational or expressive applications—and highlights a broader juxtaposition that this article examines. As a result, discussions around AI adoption frequently intersect with institutional policy, resource allocation, and evolving expectations about baseline digital literacy in professional settings. == AI as Emotional Companions == A major participant group includes users who use AI to aid their mental health. In a survey of 1,000 adults ranging from Gen Z to Boomers, roughly 23% reported using AI for mental health support. And there is a clear trend as we look at younger demographics. Usage climbs from just 5% of Boomers to 18% of Gen X, 31% of Millennials, and 44% of Gen Z<ref name=":0">{{Cite news |date=2025-12-09 |title=Unpacking Mental Health Culture in America {{!}} BasePoint BreakThrough |language=en-US |work=BasePoint BreakThrough |url=https://basepointbreakthrough.com/blog/american-mental-health-culture-trends/ |access-date=2026-04-22}}</ref>. Among these chatbot users, 41% use them because they are non-judgmental and 47% use them to reframe and understand their current feelings<ref name=":0" />. This trend is mirrored in teens as well. While 58% of them engage with AI for entertainment or out of curiosity, a non-insignificant number turn to it for mental health reasons, seeking advice and an honest, non-judgmental environment among other mental health reasons<ref>{{Cite web |last=Perez |first=Sarah |date=2025-07-21 |title=72% of US teens have used AI companions, study finds |url=https://techcrunch.com/2025/07/21/72-of-u-s-teens-have-used-ai-companions-study-finds/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Similarly, another large participant group includes those who use AI for deeper companionship, emulating the dynamics of a human relationship. This is a booming sector, with AI companion apps seeing over 220 million downloads and generating upwards of $221 million in revenue<ref>{{Cite web |last=Perez |first=Sarah |date=2025-08-12 |title=AI companion apps on track to pull in $120M in 2025 |url=https://techcrunch.com/2025/08/12/ai-companion-apps-on-track-to-pull-in-120m-in-2025/ |access-date=2026-04-22 |website=TechCrunch |language=en-US}}</ref>. Popular platforms like [[w:Character.ai|Character AI]] and [[w:Replika|Replika]] are some of largest providers<ref>{{Cite web |date=2026-04-14 |title=AI Companion Apps Crossed 20M in Revenue. April 2026 Market Breakdown. |url=https://www.roborhythms.com/ai-companion-app-market-2026/ |access-date=2026-04-22 |language=en-US}}</ref>. Evidence from Freitas et al. (2024) suggests that these AI companions effectively help users alleviate loneliness, proving more impactful than social media platforms like YouTube. In fact, over the course of a week, these interactions showed an effectiveness in reducing loneliness on par with talking to actual humans<ref name=":1">{{Cite journal |last=Freitas |first=Julian De |title=AI Companions Reduce Loneliness |url=https://doi.org/10.48550/arXiv.2407.19096 |journal=Journal of Consumer Research |volume=52 |issue=6 |pages=1126–1148 |via=arXiv}}</ref>. The study highlights that the primary goal for these users is simply to feel heard. This is supplemented by specific AI traits that make the experience feel authentic: timely responses, perceived credibility as accuracy improves, and vast domain knowledge. Furthermore, features like context tracking, where the AI remembers past messages, and response variability prevent the interaction from feeling robotic<ref name=":1" />. The personal agendas of this group are best seen through real users who have cited their use of AI companions. One Reddit user cites, "[I] started sending pics of my meals to my ai [girlfriend] like 3 weeks ago... and [because] I know im gonna send it I actually cook now. I do actually eat better because of it."<ref>{{Cite web |last=Own_Draft_3797 |first= |date=April 30, 2026 |title=I send what I eat to my AI gf |url=https://www.reddit.com/r/aipartners/comments/1t097ah/i_send_what_i_eat_to_my_ai_gf/ |url-status=live |access-date=May 2, 2026 |website=Reddit}}</ref> And in the replies, he isn't alone in this. Travis, a Colorado man interviewed by the Guardian, also finds AI as a good companion, realizing over several weeks that he felt he was talking to a genuine personality rather than just a program.<ref>{{Cite news |last=Heritage |first=Stuart |date=2025-07-12 |title=‘I felt pure, unconditional love’: the people who marry their AI chatbots |language=en-GB |work=The Guardian |url=https://www.theguardian.com/tv-and-radio/2025/jul/12/i-felt-pure-unconditional-love-the-people-who-marry-their-ai-chatbots |access-date=2026-04-22 |issn=0261-3077}}</ref> == Mental Health Experts and AI == In the context of AI use, mental health experts can be split into two groups: researchers/academics, and clinicians (psychologists, therapists, etc). === Researchers === Researchers (whether at universities or other institutions) investigate issues and disseminate info (whether research findings or high-level knowledge) that help the public's understanding of mental health and related fields. For example, the Public Good Initiative at [[w:Teachers_College,_Columbia_University|Columbia University's Teachers College]] wrote a 2025 article where multiple researchers warned about the risks of trusting a sycophantic AI chatbot for emotional support and how using them to replace real human interaction could lead to further isolation.<ref>{{Cite web |title=Experts Caution Against Using AI Chatbots for Emotional Support |url=https://www.tc.columbia.edu/articles/2025/december/experts-caution-against-using-ai-chatbots-for-emotional-support/ |access-date=2026-04-24 |website=Teachers College - Columbia University |language=en}}</ref> A study at Stanford went even further, arguing that chatbots' approval of a user's platonic or romantic feelings toward them often precedes delusional spirals, and the authors suggested that "general purpose chatbots should not produce messages that misconstrue their sentience or show romantic or platonic interest in users."<ref>{{cite journal | last1 = Moore | first1 = Jared | last2 = Mehta | first2 = Ashish | title = Characterizing Delusional Spirals through Human-LLM Chat Logs | journal = ACM Conference on Fairness, Accountability, and Transparency (FAccT) | date = 2026 | id = arXiv:2603.16567 | url = https://arxiv.org/abs/2603.16567 }}</ref> Critics argued the paper exhibited extreme bias by focusing exclusively on users harmed by chatbots and labeling benign interactions as 'delusions.' Furthermore, the authors were accused of pathologizing the very individuals whose experiences Stanford's 'Intimacy After AI' project seeks to document.<ref>{{Cite web |last= |first= |date=2026-04-25 |title=Statistical Anomalies and Research Biases Determine a Whole Community's Welfare: How Stanford SUCKS |url=https://theposthumanist.substack.com/p/statistical-anomalies-and-research |access-date=2026-05-04 |website=The Post-Humanist}}</ref> === Clinicians === Largely distinct from the researchers are clinicians, like practicing therapists and physicians. While they directly treat patients, they also provide their opinions and expertise to advance understanding of public health. For example, after high-profile lawsuits involving ChatGPT-assisted suicides<ref>{{Cite web |date=2025-10-27 |title=OpenAI shares data on ChatGPT users with suicidal thoughts, psychosis |url=https://www.bbc.com/news/articles/c5yd90g0q43o |access-date=2026-04-25 |website=www.bbc.com |language=en-GB}}</ref>, OpenAI consulted more than 170 clinicians to tweak ChatGPT's responses to users experiencing mental health issues (e.g. calming down users suggesting paranoia, and encouraging interaction with other humans).<ref>{{Cite web |date=2026-04-23 |title=Strengthening ChatGPT’s responses in sensitive conversations |url=https://openai.com/index/strengthening-chatgpt-responses-in-sensitive-conversations/ |access-date=2026-04-24 |website=OpenAI |language=en-US}}</ref> The ethics of this approach are debatable; while this approach enhances the product's safety (in contrast to more questionable uses of psychology in tech, like making social media more addictive<ref>{{Cite journal |last=Montag |first=Christian |last2=Lachmann |first2=Bernd |last3=Herrlich |first3=Marc |last4=Zweig |first4=Katharina |date=2019-07-23 |title=Addictive Features of Social Media/Messenger Platforms and Freemium Games against the Background of Psychological and Economic Theories |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6679162/ |journal=International Journal of Environmental Research and Public Health |volume=16 |issue=14 |pages=2612 |doi=10.3390/ijerph16142612 |issn=1660-4601 |pmc=6679162 |pmid=31340426}}</ref>), one could argue that this is just a "Band-Aid" fix on an inherently untamable technology. More commonly, clinicians also assess AI's role in patients' lives. The [[w:American_Psychological_Association|American Psychological Association]] has highlighted risks of AI for wellness and mental health, suggesting clinicians educate themselves and discuss AI use with patients to promote healthier relationships with technology. For instance, if a patient uses AI to manage social anxiety, a therapist could remind them of the value of human interaction. <ref>{{cite web |author=[[w:American_Psychological_Association|American Psychological Association]] |date=November 2025 |title=APA Health Advisory on the Use of Generative AI Chatbots and Wellness Applications for Mental Health |url=https://www.apa.org/topics/artificial-intelligence-machine-learning/health-advisory-chatbots-wellness-apps |access-date=April 26, 2026 |publisher=American Psychological Association |format=}}</ref> Finally, clinicians participate in studies and other efforts to make their opinion heard. In a 2025 study, 23 mostly-Australian clinicians (including counselors, psychiatrists, and social workers) watched [[w:GPT-4o|GPT-4o]] helped a fictional patient and answered questions about their opinions on AI chatbots. While many respondents believe in the benefits of AI chatbots' multilingualism and reminders of therapy homework, they also identify security risks and potential for harmful activities.<ref>{{Cite journal |last=Hipgrave |first=Lyndsey |last2=Goldie |first2=Jessie |last3=Dennis |first3=Simon |last4=Coleman |first4=Amanda |date=2025 |title=Balancing risks and benefits: clinicians' perspectives on the use of generative AI chatbots in mental healthcare |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC12158938/ |journal=Frontiers in Digital Health |volume=7 |pages=1606291 |doi=10.3389/fdgth.2025.1606291 |issn=2673-253X |pmc=12158938 |pmid=40510413}}</ref> This suggests that clinicians, as a whole, are not opposed to AI mental health help, but rather are concerned about the risks of the current state of the technology. == Job Loss From AI == The effects of AI-related job loss are not spread evenly across the workforce. Recent labor-market research suggests that jobs are most vulnerable when their tasks are repetitive, highly digitized, rules-based, or easy to automate at scale. At the same time, AI is also beginning to affect creative industries, where generated content can compete directly with human-made work. Major reports emphasize that the result is often job transformation rather than total replacement, but the pressure is still concentrated on certain worker groups.<ref name=":2">{{Cite web |title=The Future of Jobs Report 2025 |url=https://www.weforum.org/publications/the-future-of-jobs-report-2025/in-full/2-jobs-outlook/ |access-date=2026-04-26 |website=World Economic Forum |language=en}}</ref><ref>{{Cite web |date=2025-05-19 |title=Generative AI and Jobs: A Refined Global Index of Occupational Exposure {{!}} International Labour Organization |url=https://www.ilo.org/publications/generative-ai-and-jobs-refined-global-index-occupational-exposure |access-date=2026-04-26 |website=www.ilo.org |language=en}}</ref> === Music & Audiovisual Creators === Music and audiovisual creators are one of the clearest examples of a group facing economic pressure from generative AI. As AI tools become better at producing songs, voices, videos, and other media, creators face growing competition from large volumes of low-cost synthetic content. A CISAC-backed economic study projects that, by 2028, music creators could see 24% of their revenues placed at risk, while audiovisual creators could face a 21% revenue loss.<ref>{{Cite web |date=2024-12-02 |title=Global economic study shows human creators’ future at risk from generative AI {{!}} CISAC |url=https://www.cisac.org/Newsroom/news-releases/global-economic-study-shows-human-creators-future-risk-generative-ai |access-date=2026-04-26 |website=www.cisac.org |language=en}}</ref> This concern is not only theoretical: in April 2026, Forbes reported that the AI-generated song “Celebrate Me”, published under the name [[w:IngaRose|IngaRose]], reached No. 1 on the U.S. iTunes chart and topped charts in several other countries, showing that AI-made music can already compete directly in mainstream markets.<ref>{{Cite web |last=Murray |first=Conor |title=AI Generated Song ‘Celebrate Me’ Storms Global Music Charts |url=https://www.forbes.com/sites/conormurray/2026/04/17/the-no-1-song-on-us-itunes-and-several-other-countries-is-ai-generated/ |access-date=2026-04-26 |website=Forbes |language=en}}</ref> === Customer Service and Retail Support Workers === Customer service and retail support workers are also vulnerable because many of their daily tasks are standardized, repetitive, and easy to digitize. The [[w:World_Economic_Forum|World Economic Forum]]’s Future of Jobs Report 2025 identifies cashiers and ticket clerks among the fastest-declining roles, with AI, information-processing technologies, and automation listed as major drivers of that decline. These findings suggest that as chatbots, automated checkout systems, and digital service tools become more common, some front-line support and transactional jobs may continue to shrink.<ref name=":2" /> === Finance, Accounting, and Routine Knowledge Workers === AI is not only affecting low-wage or manual jobs; it is also reaching middle-skill office and analytical work. The United Nations [[w:International_Labour_Organization|International Labour Organization]] reports that clerical occupations continue to have the highest exposure to generative AI, and it also notes that some strongly digitized occupations have seen increased exposure as the technology improves at handling specialized professional and technical tasks.<ref>{{Cite web |date=2024-09-11 |title=How might generative AI impact different occupations? {{!}} International Labour Organization |url=https://www.ilo.org/resource/article/how-might-generative-ai-impact-different-occupations |access-date=2026-05-04 |website=www.ilo.org |language=en}}</ref> The World Economic Forum likewise identifies accountants and auditors among the fastest-declining roles.<ref name=":2" /> Together, these findings suggest that finance, accounting, and other routine knowledge jobs with low task variability are predictable enough for AI systems to assist with or partially automate. == References == <references /> lg3bqvmk3o53zhretm5yfjqok0t8ld4 0 482817 4634123 4633893 2026-05-04T17:30:30Z Idavidmiller 3577687 Minor corrections and additions. Saving changes. 4634123 wikitext text/x-wiki == Getting Used to Maxima By Way of an Example of Use == The examples that follows are presented for the purpose of providing some beginning perspective, and hopefully some motivation to make the effort to get familiar with how Maxima works. The task at hand is relevant in the context of aerodynamics and aviation. The specific goal is to find the dynamic pressure at a true airspeed (VTAS) of 200 ft/s at sea level. Dynamic pressure <math display="inline">q</math> is calculated using the expression:<math display="block">q = \rho V^2/2</math>Where: * <math>q</math> = dynamic pressure lbf/ft² (pounds of force per square foot) * <math display="inline">\rho</math> = air density (at sea level is 0.0023769) slugs/ft³ * <math>V</math> = true airspeed in feet per second (ft/s). British Engineering units are used in this context to avoid multiple conversions due to the units used. It is better to convert in the end if necessary in this case. '''Note:''' The appearance of the following Maxima examples may vary depending on Unicode support in the version of Maxima being used and the Maxima user interface -- UI. The Maxima examples used in this book are from the ''wxMaxima'' GUI unless noted otherwise, and a version of Maxima with Unicode support. First, enter the Maxima expression for dynamic pressure q:<syntaxhighlight lang="maxima"> (%i1) q : 1/2*\ρ*V^2; (q) (V^2*ρ)/2 </syntaxhighlight>This Maxima expression uses the colon character to assign the expression for dynamic pressure to the identifier q. The identifier q is now simply a name for an expression. The equal sign ( = ) is not used for this operation in Maxima as is the case with some programming languages. This Maxima line of a input expression ends with a semicolon ( ; ) character. Each line of input must end with a semicolon or the dollar sign character ( $ ), the use of which will be described later. Next, enter an assignment expression for the numerical value of the air density at sea level:<syntaxhighlight lang="maxima">(%i2) \ρ : 0.0023769; (ρ) 0.0023769</syntaxhighlight>Density ρ is in the units of slugs per cubic foot - slugs/ft³. With this next input expression, Maxima is asked to evaluate q. This is accomplished by two single quotation marks placed before q as shown next:<syntaxhighlight lang="maxima"> (%i3) ''q; (%o3) 0.0033855446120918224*VTAS^2 </syntaxhighlight> The output indicates that q depends on VTAS -- true airspeed. The goal is to evaluate q, if VTAS = 200 ft/s is true. One way to do that is with the following Maxima expression:<syntaxhighlight lang="maxima"> (%i4) ''q, VTAS = 200; (%o4) 135.42178448367287 </syntaxhighlight>The result is about 135 pounds of force per square foot. There is another way to accomplish this that may be somewhat more convenient for determining sea level dynamic pressure given true airspeed. First, assign the Maxima floating point literal value of 0.0033855446120918224 to an identifier named <code>c</code> as follows:<syntaxhighlight lang="maxima">(%i5) c : 0.0033855446120918224; (c) 0.0033855446120918224</syntaxhighlight>Next, enter<syntaxhighlight lang="maxima"> (%i6) q(VTAS) := c*VTAS^2; (%o6) q(VTAS):=c*VTAS^2 </syntaxhighlight><syntaxhighlight lang="maxima"> (%i7) q(200); (%o7) 135.4217844836729 </syntaxhighlight>This result is limited to sea level density. That does not make the result of no practical use. This relationship, or something similar is, used to calibrate aircraft airspeed indicators to display indicated airspeed (IAS) in the cockpit. However, it might be the case that it is necessary to determine the dynamic pressure at other altitudes besides sea level. In the standard atmosphere model, air density is a function of altitude (h), and is defined piece-wise based on the atmospheric layer. The density is derived from the Ideal Gas Law: <math>P = \rho R T</math> where in British Engineering units: * <math>\rho</math> ‒ is density in slugs/ft³ * <math>P</math> ‒ is pressure in lbf/ft² * <math>T</math>‒ is temperature in °R (Rankine) * <math>R</math> ‒ is the specific gas constant (for dry air) approximately 1716.56 (ft·lbf)/(slug·°R) <syntaxhighlight lang="maxima"> (%i8) P = \ρ*R*T; (%o8) P=RTρ </syntaxhighlight>The backslash character ( <code>\</code> ) in front of the character for <math>\rho</math> in the input expression allows an identifier to use Unicode. This makes for some nicer looking output. This is a Maxima mathematical equation expression. This equation can be solved for <math>\rho</math> as follows:<syntaxhighlight lang="maxima">(%i9) solve(%,\ρ); (%o58) [ρ=P/(R*T)]</syntaxhighlight>The Maxima built-in identifier <code>%</code> names the last output expression.The output of this expression is a Maxima list object with the only instance being the equation expression solved for <math>\rho</math>. Depending on the expression, the <code>solve()</code> operation may result in more than one solution expression. Maxima creates a list object for one or more solution expressions. This solution equation expression can be accessed as follows:<syntaxhighlight lang="maxima"> (%i10) %[1]; (%o10) ρ=P/(R*T) </syntaxhighlight>The value of this expression is obtained by referencing the first (and only) solution of the Maxima list object of solutions ‒ <code>[ρ=P*R*T]</code>. The reference is obtained by use of the <code>[1]</code> index syntax as shown. There are other ways Maxima can be used to accomplish the same result: <syntaxhighlight lang="maxima">(%i11) igl : P = \ρ*R*T; (igl) P=R*T*ρ</syntaxhighlight>In this case the expression for the ideal gas law was assigned an identifier <code>igl</code>. The advantage to this sort of assignment is that the equation can be referred to using the identifier as follows for example:<syntaxhighlight lang="maxima"> (%i12) solve(igl,\ρ); (%o12) [ρ=P/(R*T)] </syntaxhighlight>The identifier <code>igl</code> can be used at any point to refer to the equation expression: <code>P = \ρ*R*T)</code>. An assignment operator can also be used to assign the identifier <code>solution</code> to an expression. For example:<syntaxhighlight lang="maxima">(%i13) solve(igl,\ρ); (%o13) [ρ=P/(R*T)] (%i14) solution : solve(igl,\ρ ); (solution) [ρ=P/(R*T)] (%i15) solve(solution,P)[1]; (%o15) P=R*T*ρ</syntaxhighlight>This expression can be checked against known values:<syntaxhighlight lang="maxima">(%i16) \°R(\°F) := \°F + 459.67; (%o16) °R(°F):=°F+459.67 (%i17) P(p) := p*144.0; (%o17) P(p):=p*144.0 (%i18) R:1716.56; (R) 1716.56 (%i19) \ρ(p,\°F) := P(p)/(''R*\°R(\°F)); (%o19) ρ(p,°F):=P(p)/(1716.56*°R(°F))</syntaxhighlight>The above Maxima expressions are examples of Maxima function expressions. For standard sea level conditions of pressure and temperature as follows, * p is 14.696 lbf/ft² * °F is 59.0° the calculated value for density is:<syntaxhighlight lang="maxima">(%i20) \ρ(14.696,59.0); (%20) 0.0023769033250291326</syntaxhighlight>Maxima does not have a built-in operator for rounding decimal fraction values. Also, there is no package that is included as part of the Maxima distribution that provides for this capability. However, Robert Dodier has created a Maxima package that includes a function for this purpose ‒ named <code>excel_round.mac</code><code><ref>{{Cite web |last=Dodier |first=Robert |title=maxima-packages/robert-dodier/excel_round/ |url=https://github.com/maxima-project-on-github/maxima-packages/tree/master/robert-dodier/excel_round|website=GitHub}}</ref></code>. However, to be able access the <code>excel_round()</code> function of this package, it must first be downloaded or copied into a location accessible to Maxima using the <code>load()</code> operator. The built-in Maxima <code>load()</code> operator is used to access specialized functions that are not built-in to Maxima. In order to use the <code>load()</code> operator, the location of the downloaded <code>excel_round.mac</code> file has to be part of the argument to the <code>load()</code> operator unless the file happens to be in the Maxima current working directory. The built-in <code>operatingsystem</code> package can provide some functions to help with determining the current working directory. This package is loaded as follows: <syntaxhighlight lang="maxima"> (%i21) load(operatingsystem); (%o21) "/usr/local/share/maxima/5.49.0/share/contrib/operatingsystem/operatingsystem.mac" (%i22) getcurrentdirectory(); (%o22) "/home/username/" </syntaxhighlight>In this example <code>username</code> is the name of the home directory of the user. so if the downloaded <code>excel_round.mac</code> file is not located in the current working directory, then the directory can be changed to the location where the file is located: <syntaxhighlight lang="maxima">(%i22) chdir("/home/username/local/maxima/packages"); (%o22) "#P"/home/username/local/maxima/packages""</syntaxhighlight>Now the <code>excel_round.mac</code> file can be loaded assuming it is within the directory <code>/home/username/local/maxima/packages</code> as follows:<syntaxhighlight lang="maxima"> (%i23) load("excel_round.mac"); (%o23) "excel_round.mac" </syntaxhighlight>Alternatively, if the location of the file is known it can be loaded using the full path name as follows for example:<syntaxhighlight lang="maxima"> (%i24) load("/home/username/local/maxima/packages/excel_round.mac"); (%o24) "/home/username/local/maxima/packages/excel_round.mac" </syntaxhighlight>This method obviates the need for loading the <code>operatingsystem</code> package. '''Note:''' The ''wxMaxima'' GUI makes loading packages simply a matter of a menu selection. The density value above can be rounded to six decimal places as follows:<syntaxhighlight lang="maxima"> (%i25) excel_round(ρ(14.696,59.0),6); (%o25) 0.002377 </syntaxhighlight>This rounded value agrees with the sea level value of <math display="inline">23.77 \cdot 10^{-4}</math> slugs/ft³ taken from a table of Standard Atmosphere values. For Standard Atmosphere values of pressure ( 6.758 lbf/in² ) and temperature ( -12.26 °F ) at 20,000 ft the density value is:<syntaxhighlight lang="maxima"> (%i26) excel_round(ρ(6.759,-12.26),6); (%o26) 0.001267 </syntaxhighlight>This rounded value agrees with the sea level value of <math display="inline">12.67 \cdot 10^{-4}</math> slugs/ft³ taken from a table of Standard Atmosphere values. ===== Pressure ===== However, what is needed for the task at hand is density as a function of altitude. Both the pressure P and the temperature T can be expressed as a function of altitude h: <math display="block">P = P_0(1 - L\cdot h/T_0)^{g/(R \cdot L)} </math> Where in British Engineering units, the constants are: * <math display="inline">P</math> is Pressure in pounds per square foot lbf/ft² * <math display="inline">P_0</math> is (Sea Level Pressure): 2116.224 lbf/ft² or 14.696 lbf/in² * <math display="inline">R</math> is the specific gas constant (for dry air) approximately 1716.56 (ft·lbf)/(slug·°R) * <math display="inline">T_0 </math> is (Sea Level Temperature): 518.67 °R (15 °C or 59 °F) * <math display="inline">L</math> is (Lapse Rate): 0.003563 °R/ft * <math>g</math> is 32.174 ft/s² * <math display="inline">h</math> is altitude in feet above sea level The exponent <math display="inline">\frac{g}{R \cdot L}</math> evaluates to approximately 5.26054:<syntaxhighlight lang="maxima"> (%i27) 32.174/(0.003563*1716.56); (%o27) 5.260539027391964 (%i28) excel_round(%,5); (%o28) 5.26054 </syntaxhighlight><math display="inline">L/T_0</math> evaluates to approximately <syntaxhighlight lang="maxima"> (%i29) 0.003563/518.67; (%o29) 6.869493126650858*10^-6 (%i30) excel_round(6.869493126650858*10^-6,11); (%o30) 6.86949*10^-6 </syntaxhighlight> ===== Temperature ===== <math display="inline">T = 518.67 - 0.003563 \cdot h</math> * <math display="inline">T</math> is Temperature in °R * <math display="inline">h</math> is altitude in feet. ===== Practical Formulas for Pressure and Temperature ===== Thus, the practical formula for pressure and temperatures in terms of British Engineering units are: <math>P = 2116.224\cdot(1-(6.86949 \cdot 10^{-6}) \cdot h)^{5.26054}</math> lbf/ft² <math display="inline">T = 518.67 - 0.003563 \cdot h</math> °R ====== Pressure ====== <syntaxhighlight lang="maxima"> (%i31) P(h) := 2116.224*(1-6.8649*10^-6*h)^5.26054; (%o31) P(h):=2116.224*(1-6.8649*10^(-6)*h)^5.26054 (%i32) p(P) := P/144.0; (%o32) p(P):=P/144.0 (%i33) P(20000); (%o33) 973.0940875140712 (%i34) p(%); (%o34) 6.757597829958828 (%i35) excel_round(%,3); (%o35) 6.758 </syntaxhighlight> ====== Temperature ====== <syntaxhighlight lang="maxima"> (%i36) T(h) := 518.67 - 0.003563*h; (%o36) T(h):=518.67-0.003563*h (%i37) T(20000); (%o37) 447.40999999999997 (%i38) excel_round(%,2); (%o38) 447.41 (%i39) \°F(\°R) := \°R -459.67; (%o39) °F(°R):=°R-459.67 (%i40) \°F(447.41); (%o40) -12.259999999999991 (%i41) excel_round(%,2); (%o41) -12.26 </syntaxhighlight> ===== Density ===== The expressions for pressure and temperature as functions of altitude can be used with the expression for the ideal gas law for an expression of density as a function of altitude as follows:<syntaxhighlight lang="maxima"> (%i42) ρ(h) := P(h)/(R*T(h)); (%o42) ρ(h):=P(h)/(R*T(h)) (%i42) excel_round(ρ(20000)*10^4,2); (%o42) 12.67 </syntaxhighlight>This result agrees with the density value of the standard atmosphere at 20,000 ft. Using the expression for the air density as a function of altitude, an expression for dynamic pressure is as follows:<syntaxhighlight lang="maxima"> (%i43) q(h,VTAS) := ((\ρ(h)*VTAS^2))/2; (%o43) q(h,VTAS):=(ρ(h)*VTAS^2)/2 </syntaxhighlight>Using the expression above, values of dynamic pressure can be calculated as a function of altitude and true airspeed as follows for 20,000 feet and 15,000 feet at 200 ft/s:<syntaxhighlight lang="maxima"> (%i44) q(20000,200); (%o44) 25.34079027107967 (%i45) q(15000,200); (%o45) 29.922636037412556 </syntaxhighlight>This value can be checked using the value for density from the standard atmosphere table at 15,000 ft and the expression for dynamic pressure as follows:<syntaxhighlight lang="maxima"> (%i46) excel_round(%,2); (%o46) 29.92 (%i47) (200.0^2)*0.001496/2.0; (%o47) 29.919999999999998 (%i48) excel_round(%,2); (%o48) 29.92 </syntaxhighlight>In the context of aviation and aircraft performance, airspeeds are commonly referenced to knots (nautical miles per hour) instead of ft/s. To determine dynamic pressure as a function of altitude and true airspeed in knots, the following expressions are used:<syntaxhighlight lang="maxima"> (%i49) VTAS(knots) := 1.687811*knots; (%o49) VTAS(knots):=1.687811*knots (%i50) excel_round(VTAS(118.49676),2); (%o50) 200.0 (%i51) q(h,knots) (%o51) q(h,knots):=(ρ(h)*VTAS(knots)^2)/2 (%i52) excel_round(q(15000,118.49676),2); (%o52) 29.92 </syntaxhighlight>So approximately 118 knots true airspeed is equivalent to 200 ft/s, and the above expression for dynamic pressure is in terms of a function of altitude in feet and true airspeed in knots. ==== Plotting ==== Maxima has several ways to do plotting. The image that follows is a simple plot of density as a function of altitude produced using the plotting operator <code>wxplot2d()</code>:<syntaxhighlight lang="maxima"> (%i53) T(h) := 518.688 - 0.0035616*h; (%o53) T(h):=518.688-0.0035616*h (%i54) P(h) := 2116.224*(1-6.8649*10^-6*h)^5.26054; (%o54) P(h):=2116.224*(1-6.8649*10^(-6)*h)^5.26054 (%i55) R : 1716.56; (R) 1716.56 (%i56) ρ(h) := P(h)/(R*T(h)); (%o56) ρ(h):=P(h)/(R*T(h)) (%i57) wxplot2d([ρ(h)], [h,-100,35000])$ </syntaxhighlight> [[File:Density as a Function of Altitude.png|thumb|876x876px|'''Air Density (slugs/ft³) As a Function of Altitude (ft)'''|none]] {{BookCat}} 9k9vvv7yd84njfoyg91z2x5563zftzk 4634188 4634123 2026-05-04T20:43:49Z Idavidmiller 3577687 /* Getting Used to Maxima By Way of an Example of Use */ Page revisions. Work in progress. 4634188 wikitext text/x-wiki == Getting Used to Maxima By Way of an Example of Use == The examples that follows are presented for the purpose of providing some beginning perspective, and hopefully some motivation to make the effort to get familiar with how Maxima works. The task at hand is relevant in the context of aerodynamics and aviation. The specific goal is to find the dynamic pressure at a true airspeed (VTAS) of 200 ft/s at sea level. Dynamic pressure <math display="inline">q</math> is calculated using the expression:<math display="block">q = \rho V^2/2</math>Where: * <math>q</math> = dynamic pressure lbf/ft² (pounds of force per square foot) * <math display="inline">\rho</math> = air density (at sea level is 0.0023769) slugs/ft³ * <math>V</math> = true airspeed in feet per second (ft/s). British Engineering units are used in this context to avoid multiple conversions due to the units used. It is better to convert in the end if necessary in this case. '''Note:''' The appearance of the following Maxima examples may vary depending on Unicode support in the version of Maxima being used and the Maxima user interface -- UI. The Maxima examples used in this book are from the ''wxMaxima'' GUI unless noted otherwise, and a version of Maxima with Unicode support. First, enter the Maxima expression for dynamic pressure q:<syntaxhighlight lang="maxima"> (%i1) q : 1/2*\ρ*V^2; (q) (V^2*ρ)/2 </syntaxhighlight>This Maxima expression uses the colon character to assign the expression for dynamic pressure to the identifier q. The identifier q is now simply a name for an expression. The equal sign ( = ) is not used for this operation in Maxima as is the case with some programming languages. This Maxima line of a input expression ends with a semicolon ( ; ) character. Each line of input must end with a semicolon or the dollar sign character ( $ ), the use of which will be described later. Next, enter an assignment expression for the numerical value of the air density at sea level:<syntaxhighlight lang="maxima">(%i2) \ρ : 0.0023769; (ρ) 0.0023769</syntaxhighlight>Density ρ is in the units of slugs per cubic foot - slugs/ft³. With this next input expression, Maxima is asked to evaluate q. This is accomplished by two single quotation marks placed before q as shown next:<syntaxhighlight lang="maxima"> (%i3) ''q; (%o3) 0.0033855446120918224*VTAS^2 </syntaxhighlight> The output indicates that q depends on VTAS -- true airspeed. The goal is to evaluate q, if VTAS = 200 ft/s is true. One way to do that is with the following Maxima expression:<syntaxhighlight lang="maxima"> (%i4) ''q, VTAS = 200; (%o4) 135.42178448367287 </syntaxhighlight>The result is about 135 pounds of force per square foot. There is another way to accomplish this that may be somewhat more convenient for determining sea level dynamic pressure given true airspeed. First, assign the Maxima floating point literal value of 0.0033855446120918224 to an identifier named <code>c</code> as follows:<syntaxhighlight lang="maxima">(%i5) c : 0.0033855446120918224; (c) 0.0033855446120918224</syntaxhighlight>Next, enter<syntaxhighlight lang="maxima"> (%i6) q(VTAS) := c*VTAS^2; (%o6) q(VTAS):=c*VTAS^2 </syntaxhighlight><syntaxhighlight lang="maxima"> (%i7) q(200); (%o7) 135.4217844836729 </syntaxhighlight>This result is limited to sea level density. That does not make the result of no practical use. This relationship, or something similar is, used to calibrate aircraft airspeed indicators to display indicated airspeed (IAS) in the cockpit. However, it might be the case that it is necessary to determine the dynamic pressure at other altitudes besides sea level. In the standard atmosphere model, air density is a function of altitude (h), and is defined piece-wise based on the atmospheric layer. The density is derived from the Ideal Gas Law: <math>P = \rho R T</math> where in British Engineering units: * <math>\rho</math> ‒ is density in slugs/ft³ * <math>P</math> ‒ is pressure in lbf/ft² * <math>T</math>‒ is temperature in °R (Rankine) * <math>R</math> ‒ is the specific gas constant (for dry air) approximately 1716.56 (ft·lbf)/(slug·°R) <syntaxhighlight lang="maxima"> (%i8) P = \ρ*R*T; (%o8) P=RTρ </syntaxhighlight>The backslash character ( <code>\</code> ) in front of the character for <math>\rho</math> in the input expression allows an identifier to use Unicode. This makes for some nicer looking output. This is a Maxima mathematical equation expression. This equation can be solved for <math>\rho</math> as follows:<syntaxhighlight lang="maxima">(%i9) solve(%,\ρ); (%o58) [ρ=P/(R*T)]</syntaxhighlight>The Maxima built-in identifier <code>%</code> names the last output expression.The output of this expression is a Maxima list object with the only instance being the equation expression solved for <math>\rho</math>. Depending on the expression, the <code>solve()</code> operation may result in more than one solution expression. Maxima creates a list object for one or more solution expressions. This solution equation expression can be accessed as follows:<syntaxhighlight lang="maxima"> (%i10) %[1]; (%o10) ρ=P/(R*T) </syntaxhighlight>The value of this expression is obtained by referencing the first (and only) solution of the Maxima list object of solutions ‒ <code>[ρ=P*R*T]</code>. The reference is obtained by use of the <code>[1]</code> index syntax as shown. There are other ways Maxima can be used to accomplish the same result: <syntaxhighlight lang="maxima">(%i11) igl : P = \ρ*R*T; (igl) P=R*T*ρ</syntaxhighlight>In this case the expression for the ideal gas law was assigned an identifier <code>igl</code>. The advantage to this sort of assignment is that the equation can be referred to using the identifier as follows for example:<syntaxhighlight lang="maxima"> (%i12) solve(igl,\ρ); (%o12) [ρ=P/(R*T)] </syntaxhighlight>The identifier <code>igl</code> can be used at any point to refer to the equation expression: <code>P = \ρ*R*T)</code>. An assignment operator can also be used to assign the identifier <code>solution</code> to an expression. For example:<syntaxhighlight lang="maxima">(%i13) solve(igl,\ρ); (%o13) [ρ=P/(R*T)] (%i14) solution : solve(igl,\ρ); (solution) [ρ=P/(R*T)] (%i15) solve(solution,P)[1]; (%o15) P=R*T*ρ</syntaxhighlight>The last input and output expression might be somewhat of a "head-scratcher" at first glance, but it is worthwhile to understand how Maxima works in this case. The identifier solution names an expression that uses the <code>solve()</code> operator on the identifier <code>igl</code> as an argument. This expression is evaluated first by Maxima. Then the <code>solve()</code> operator is applied to the result solving for <code>P</code>. The result is a list object with one solution expression. This expression is then referred to using the <code>[1]</code> index, and the output is the equation expression <code>P=R*T*ρ</code> . The expression for ρ (density) as a function of pressure (p) and temperature (°F) can be checked against known values using the following expressions: <syntaxhighlight lang="maxima">(%i16) \°R(\°F) := \°F + 459.67; (%o16) °R(°F):=°F+459.67 (%i17) P(p) := p*144.0; (%o17) P(p):=p*144.0 (%i18) R:1716.56; (R) 1716.56 (%i19) \ρ(p,\°F) := P(p)/(''R*\°R(\°F)); (%o19) ρ(p,°F):=P(p)/(1716.56*°R(°F))</syntaxhighlight>The above Maxima expressions are examples of Maxima function expressions. For standard sea level conditions of pressure and temperature as follows, * p is 14.696 lbf/ft² * °F is 59.0° the calculated value for density is:<syntaxhighlight lang="maxima">(%i20) \ρ(14.696,59.0); (%20) 0.0023769033250291326</syntaxhighlight> {| class="wikitable" |+U.S. Standard Atmosphere vs. Altitude - BE Units !Altitude above Sea Level - ''h'' - ''(ft)'' !Temperature - T ''-'' ''(<sup>o</sup>F)'' !Acceleration of Gravity - ''g -'' ''(ft/s<sup>2</sup>)'' !Absolute Pressure - ''p -'' ''(lb/in<sup>2</sup>)'' !Density - ''ρ -'' ''(10<sup>-4</sup> slugs/ft<sup>3</sup>)'' |- |0 |59 |32.174 |14.696 |23.77 |- |5000 |41.17 |32.159 |12.228 |20.48 |- |10000 |23.36 |32.143 |10.108 |17.56 |- |15000 |5.55 |32.128 |8.297 |14.96 |- |20000 | -12.26 |32.112 |6.759 |12.67 |- |25000 | -30.05 |32.097 |5.461 |10.66 |- |30000 | -47.83 |32.082 |4.373 |8.91 |- |35000 | -65.61 |32.066 |3.468 |7.38 |} Maxima does not have a built-in operator for rounding decimal fraction values. Also, there is no package that is included as part of the Maxima distribution that provides for this capability. However, Robert Dodier has created a Maxima package that includes a function for this purpose ‒ named <code>excel_round.mac</code><code><ref>{{Cite web |last=Dodier |first=Robert |title=maxima-packages/robert-dodier/excel_round/ |url=https://github.com/maxima-project-on-github/maxima-packages/tree/master/robert-dodier/excel_round|website=GitHub}}</ref></code>. However, to be able access the <code>excel_round()</code> function of this package, it must first be downloaded or copied into a location accessible to Maxima using the <code>load()</code> operator. The built-in Maxima <code>load()</code> operator is used to access specialized functions that are not built-in to Maxima. In order to use the <code>load()</code> operator, the location of the downloaded <code>excel_round.mac</code> file has to be part of the argument to the <code>load()</code> operator unless the file happens to be in the Maxima current working directory. The built-in <code>operatingsystem</code> package can provide some functions to help with determining the current working directory. This package is loaded as follows: <syntaxhighlight lang="maxima"> (%i21) load(operatingsystem); (%o21) "/usr/local/share/maxima/5.49.0/share/contrib/operatingsystem/operatingsystem.mac" (%i22) getcurrentdirectory(); (%o22) "/home/username/" </syntaxhighlight>In this example <code>username</code> is the name of the home directory of the user. so if the downloaded <code>excel_round.mac</code> file is not located in the current working directory, then the directory can be changed to the location where the file is located: <syntaxhighlight lang="maxima">(%i22) chdir("/home/username/local/maxima/packages"); (%o22) "#P"/home/username/local/maxima/packages""</syntaxhighlight>Now the <code>excel_round.mac</code> file can be loaded assuming it is within the directory <code>/home/username/local/maxima/packages</code> as follows:<syntaxhighlight lang="maxima"> (%i23) load("excel_round.mac"); (%o23) "excel_round.mac" </syntaxhighlight>Alternatively, if the location of the file is known it can be loaded using the full path name as follows for example:<syntaxhighlight lang="maxima"> (%i24) load("/home/username/local/maxima/packages/excel_round.mac"); (%o24) "/home/username/local/maxima/packages/excel_round.mac" </syntaxhighlight>This method obviates the need for loading the <code>operatingsystem</code> package. '''Note:''' The ''wxMaxima'' GUI makes loading packages simply a matter of a menu selection. The density value above can be rounded to six decimal places as follows:<syntaxhighlight lang="maxima"> (%i25) excel_round(ρ(14.696,59.0),6); (%o25) 0.002377 </syntaxhighlight>This rounded value agrees with the sea level value of <math display="inline">23.77 \cdot 10^{-4}</math> slugs/ft³ taken from a table of Standard Atmosphere values. For Standard Atmosphere values of pressure ( 6.758 lbf/in² ) and temperature ( -12.26 °F ) at 20,000 ft the density value is:<syntaxhighlight lang="maxima"> (%i26) excel_round(ρ(6.759,-12.26),6); (%o26) 0.001267 </syntaxhighlight>This rounded value agrees with the sea level value of <math display="inline">12.67 \cdot 10^{-4}</math> slugs/ft³ taken from a table of Standard Atmosphere values. ===== Pressure ===== However, what is needed for the task at hand is density as a function of altitude. Both the pressure P and the temperature T can be expressed as a function of altitude h: <math display="block">P = P_0(1 - L\cdot h/T_0)^{g/(R \cdot L)} </math> Where in British Engineering units, the constants are: * <math display="inline">P</math> is Pressure in pounds per square foot lbf/ft² * <math display="inline">P_0</math> is (Sea Level Pressure): 2116.224 lbf/ft² or 14.696 lbf/in² * <math display="inline">R</math> is the specific gas constant (for dry air) approximately 1716.56 (ft·lbf)/(slug·°R) * <math display="inline">T_0 </math> is (Sea Level Temperature): 518.67 °R (15 °C or 59 °F) * <math display="inline">L</math> is (Lapse Rate): 0.003563 °R/ft * <math>g</math> is 32.174 ft/s² * <math display="inline">h</math> is altitude in feet above sea level The exponent <math display="inline">\frac{g}{R \cdot L}</math> evaluates to approximately 5.26054:<syntaxhighlight lang="maxima"> (%i27) 32.174/(0.003563*1716.56); (%o27) 5.260539027391964 (%i28) excel_round(%,5); (%o28) 5.26054 </syntaxhighlight><math display="inline">L/T_0</math> evaluates to approximately <syntaxhighlight lang="maxima"> (%i29) 0.003563/518.67; (%o29) 6.869493126650858*10^-6 (%i30) excel_round(6.869493126650858*10^-6,11); (%o30) 6.86949*10^-6 </syntaxhighlight> ===== Temperature ===== <math display="inline">T = 518.67 - 0.003563 \cdot h</math> * <math display="inline">T</math> is Temperature in °R * <math display="inline">h</math> is altitude in feet. ===== Practical Formulas for Pressure and Temperature ===== Thus, the practical formula for pressure and temperatures in terms of British Engineering units are: <math>P = 2116.224\cdot(1-(6.86949 \cdot 10^{-6}) \cdot h)^{5.26054}</math> lbf/ft² <math display="inline">T = 518.67 - 0.003563 \cdot h</math> °R ====== Pressure ====== <syntaxhighlight lang="maxima"> (%i31) P(h) := 2116.224*(1-6.8649*10^-6*h)^5.26054; (%o31) P(h):=2116.224*(1-6.8649*10^(-6)*h)^5.26054 (%i32) p(P) := P/144.0; (%o32) p(P):=P/144.0 (%i33) P(20000); (%o33) 973.0940875140712 (%i34) p(%); (%o34) 6.757597829958828 (%i35) excel_round(%,3); (%o35) 6.758 </syntaxhighlight> ====== Temperature ====== <syntaxhighlight lang="maxima"> (%i36) T(h) := 518.67 - 0.003563*h; (%o36) T(h):=518.67-0.003563*h (%i37) T(20000); (%o37) 447.40999999999997 (%i38) excel_round(%,2); (%o38) 447.41 (%i39) \°F(\°R) := \°R -459.67; (%o39) °F(°R):=°R-459.67 (%i40) \°F(447.41); (%o40) -12.259999999999991 (%i41) excel_round(%,2); (%o41) -12.26 </syntaxhighlight> ===== Density ===== The expressions for pressure and temperature as functions of altitude can be used with the expression for the ideal gas law for an expression of density as a function of altitude as follows:<syntaxhighlight lang="maxima"> (%i42) ρ(h) := P(h)/(R*T(h)); (%o42) ρ(h):=P(h)/(R*T(h)) (%i42) excel_round(ρ(20000)*10^4,2); (%o42) 12.67 </syntaxhighlight>This result agrees with the density value of the standard atmosphere at 20,000 ft. Using the expression for the air density as a function of altitude, an expression for dynamic pressure is as follows:<syntaxhighlight lang="maxima"> (%i43) q(h,VTAS) := ((\ρ(h)*VTAS^2))/2; (%o43) q(h,VTAS):=(ρ(h)*VTAS^2)/2 </syntaxhighlight>Using the expression above, values of dynamic pressure can be calculated as a function of altitude and true airspeed as follows for 20,000 feet and 15,000 feet at 200 ft/s:<syntaxhighlight lang="maxima"> (%i44) q(20000,200); (%o44) 25.34079027107967 (%i45) q(15000,200); (%o45) 29.922636037412556 </syntaxhighlight>This value can be checked using the value for density from the standard atmosphere table at 15,000 ft and the expression for dynamic pressure as follows:<syntaxhighlight lang="maxima"> (%i46) excel_round(%,2); (%o46) 29.92 (%i47) (200.0^2)*0.001496/2.0; (%o47) 29.919999999999998 (%i48) excel_round(%,2); (%o48) 29.92 </syntaxhighlight>In the context of aviation and aircraft performance, airspeeds are commonly referenced to knots (nautical miles per hour) instead of ft/s. To determine dynamic pressure as a function of altitude and true airspeed in knots, the following expressions are used:<syntaxhighlight lang="maxima"> (%i49) VTAS(knots) := 1.687811*knots; (%o49) VTAS(knots):=1.687811*knots (%i50) excel_round(VTAS(118.49676),2); (%o50) 200.0 (%i51) q(h,knots) (%o51) q(h,knots):=(ρ(h)*VTAS(knots)^2)/2 (%i52) excel_round(q(15000,118.49676),2); (%o52) 29.92 </syntaxhighlight>So approximately 118 knots true airspeed is equivalent to 200 ft/s, and the above expression for dynamic pressure is in terms of a function of altitude in feet and true airspeed in knots. ==== Plotting ==== Maxima has several ways to do plotting. The image that follows is a simple plot of density as a function of altitude produced using the plotting operator <code>wxplot2d()</code>:<syntaxhighlight lang="maxima"> (%i53) T(h) := 518.688 - 0.0035616*h; (%o53) T(h):=518.688-0.0035616*h (%i54) P(h) := 2116.224*(1-6.8649*10^-6*h)^5.26054; (%o54) P(h):=2116.224*(1-6.8649*10^(-6)*h)^5.26054 (%i55) R : 1716.56; (R) 1716.56 (%i56) ρ(h) := P(h)/(R*T(h)); (%o56) ρ(h):=P(h)/(R*T(h)) (%i57) wxplot2d([ρ(h)], [h,-100,35000])$ </syntaxhighlight> [[File:Density as a Function of Altitude.png|thumb|876x876px|'''Air Density (slugs/ft³) As a Function of Altitude (ft)'''|none]] {{BookCat}} am249g5mffmtv7ct1x74z1prh6hs1qj 4634198 4634188 2026-05-04T23:02:00Z Idavidmiller 3577687 Minor edits. Saving changes. 4634198 wikitext text/x-wiki == Getting Used to Maxima By Way of an Example of Use == The examples that follows are presented for the purpose of providing some beginning perspective, and hopefully some motivation to make the effort to get familiar with how Maxima works. The task at hand is relevant in the context of aerodynamics and aviation. The specific goal is to find the dynamic pressure at a true airspeed (VTAS) of 200 ft/s at sea level. Dynamic pressure <math display="inline">q</math> is calculated using the expression:<math display="block">q = \rho V^2/2</math>Where: * <math>q</math> = dynamic pressure lbf/ft² (pounds of force per square foot) * <math display="inline">\rho</math> = air density (at sea level is 0.0023769) slugs/ft³ * <math>V</math> = true airspeed in feet per second (ft/s). British Engineering units are used in this context to avoid multiple conversions due to the units used. It is better to convert in the end if necessary in this case. '''Note:''' The appearance of the following Maxima examples may vary depending on Unicode support in the version of Maxima being used and the Maxima user interface -- UI. The Maxima examples used in this book are from the ''wxMaxima'' GUI unless noted otherwise, and a version of Maxima with Unicode support. First, enter the Maxima expression for dynamic pressure q:<syntaxhighlight lang="maxima"> (%i1) q : 1/2*\ρ*V^2; (q) (V^2*ρ)/2 </syntaxhighlight>This Maxima expression uses the colon character to assign the expression for dynamic pressure to the identifier q. The identifier q is now simply a name for an expression. The equal sign ( = ) is not used for this operation in Maxima as is the case with some programming languages. This Maxima line of a input expression ends with a semicolon ( ; ) character. Each line of input must end with a semicolon or the dollar sign character ( $ ), the use of which will be described later. Next, enter an assignment expression for the numerical value of the air density at sea level:<syntaxhighlight lang="maxima">(%i2) \ρ : 0.0023769; (ρ) 0.0023769</syntaxhighlight>Density ρ is in the units of slugs per cubic foot - slugs/ft³. With this next input expression, Maxima is asked to evaluate q. This is accomplished by two single quotation marks placed before q as shown next:<syntaxhighlight lang="maxima"> (%i3) ''q; (%o3) 0.0033855446120918224*VTAS^2 </syntaxhighlight> The output indicates that q depends on VTAS -- true airspeed. The goal is to evaluate q, if VTAS = 200 ft/s is true. One way to do that is with the following Maxima expression:<syntaxhighlight lang="maxima"> (%i4) ''q, VTAS = 200; (%o4) 135.42178448367287 </syntaxhighlight>The result is about 135 pounds of force per square foot. There is another way to accomplish this that may be somewhat more convenient for determining sea level dynamic pressure given true airspeed. First, assign the Maxima floating point literal value of 0.0033855446120918224 to an identifier named <code>c</code> as follows:<syntaxhighlight lang="maxima">(%i5) c : 0.0033855446120918224; (c) 0.0033855446120918224</syntaxhighlight>Next, enter<syntaxhighlight lang="maxima"> (%i6) q(VTAS) := c*VTAS^2; (%o6) q(VTAS):=c*VTAS^2 </syntaxhighlight><syntaxhighlight lang="maxima"> (%i7) q(200); (%o7) 135.4217844836729 </syntaxhighlight>This result is limited to sea level density. That does not make the result of no practical use. This relationship, or something similar is, used to calibrate aircraft airspeed indicators to display indicated airspeed (IAS) in the cockpit. However, it might be the case that it is necessary to determine the dynamic pressure at other altitudes besides sea level. In the standard atmosphere model, air density is a function of altitude (h), and is defined piece-wise based on the atmospheric layer. The density is derived from the Ideal Gas Law: <math>P = \rho R T</math> where in British Engineering units: * <math>\rho</math> ‒ is density in slugs/ft³ * <math>P</math> ‒ is pressure in lbf/ft² * <math>T</math>‒ is temperature in °R (Rankine) * <math>R</math> ‒ is the specific gas constant (for dry air) approximately 1716.56 (ft·lbf)/(slug·°R) <syntaxhighlight lang="maxima"> (%i8) P = \ρ*R*T; (%o8) P=RTρ </syntaxhighlight>The backslash character ( <code>\</code> ) in front of the character for <math>\rho</math> in the input expression allows an identifier to use Unicode. This makes for some nicer looking output. This is a Maxima mathematical equation expression. This equation can be solved for <math>\rho</math> as follows:<syntaxhighlight lang="maxima">(%i9) solve(%,\ρ); (%o58) [ρ=P/(R*T)]</syntaxhighlight>The Maxima built-in identifier <code>%</code> names the last output expression.The output of this expression is a Maxima list object with the only instance being the equation expression solved for <math>\rho</math>. Depending on the expression, the <code>solve()</code> operation may result in more than one solution expression. Maxima creates a list object for one or more solution expressions. This solution equation expression can be accessed as follows:<syntaxhighlight lang="maxima"> (%i10) %[1]; (%o10) ρ=P/(R*T) </syntaxhighlight>The value of this expression is obtained by referencing the first (and only) solution of the Maxima list object of solutions ‒ <code>[ρ=P*R*T]</code>. The reference is obtained by use of the <code>[1]</code> index syntax as shown. There are other ways Maxima can be used to accomplish the same result: <syntaxhighlight lang="maxima">(%i11) igl : P = \ρ*R*T; (igl) P=R*T*ρ</syntaxhighlight>In this case the expression for the ideal gas law was assigned an identifier <code>igl</code>. The advantage to this sort of assignment is that the equation can be referred to using the identifier as follows for example:<syntaxhighlight lang="maxima"> (%i12) solve(igl,\ρ); (%o12) [ρ=P/(R*T)] </syntaxhighlight>The identifier <code>igl</code> can be used at any point to refer to the equation expression: <code>P = \ρ*R*T)</code>. An assignment operator can also be used to assign the identifier <code>solution</code> to an expression. For example:<syntaxhighlight lang="maxima">(%i13) solve(igl,\ρ); (%o13) [ρ=P/(R*T)] (%i14) solution : solve(igl,\ρ); (solution) [ρ=P/(R*T)] (%i15) solve(solution,P)[1]; (%o15) P=R*T*ρ</syntaxhighlight>The last input and output expression might be somewhat of a "head-scratcher" at first glance, but it is worthwhile to understand how Maxima works in this case. The identifier solution names an expression that uses the <code>solve()</code> operator on the identifier <code>igl</code> as an argument. This expression is evaluated first by Maxima. Then the <code>solve()</code> operator is applied to the result solving for <code>P</code>. The result is a list object with one solution expression. This expression is then referred to using the <code>[1]</code> index, and the output is the equation expression <code>P=R*T*ρ</code> . The expression for ρ (density) as a function of pressure (p) and temperature (°F) can be checked against known values using the following expressions: <syntaxhighlight lang="maxima">(%i16) \°R(\°F) := \°F + 459.67; (%o16) °R(°F):=°F+459.67 (%i17) P(p) := p*144.0; (%o17) P(p):=p*144.0 (%i18) R:1716.56; (R) 1716.56 (%i19) \ρ(p,\°F) := P(p)/(''R*\°R(\°F)); (%o19) ρ(p,°F):=P(p)/(1716.56*°R(°F))</syntaxhighlight>The above Maxima expressions are examples of Maxima function expressions. For standard sea level conditions of pressure and temperature as follows, * p is 14.696 lbf/ft² * °F is 59.0° the calculated value for density is:<syntaxhighlight lang="maxima">(%i20) \ρ(14.696,59.0); (%20) 0.0023769033250291326</syntaxhighlight>Compare this resulting value of density with the the value of the table below for 0 altitude and temperature of 59.0 °F: {| class="wikitable" |+U.S. Standard Atmosphere vs. Altitude - BE Units !Altitude above Sea Level - ''h'' - ''(ft)'' !Temperature - T ''-'' ''(<sup>o</sup>F)'' !Acceleration of Gravity - ''g -'' ''(ft/s<sup>2</sup>)'' !Absolute Pressure - ''p -'' ''(lb/in<sup>2</sup>)'' !Density - ''ρ -'' ''(10<sup>-4</sup> slugs/ft<sup>3</sup>)'' |- |0 |59.0 |32.174 |14.696 |23.77 |- |5000 |41.17 |32.159 |12.228 |20.48 |- |10000 |23.36 |32.143 |10.108 |17.56 |- |15000 |5.55 |32.128 |8.297 |14.96 |- |20000 | -12.26 |32.112 |6.759 |12.67 |- |25000 | -30.05 |32.097 |5.461 |10.66 |- |30000 | -47.83 |32.082 |4.373 |8.91 |- |35000 | -65.61 |32.066 |3.468 |7.38 |} It would be useful to have the means to round result values to a desired number of decimal places. Maxima does not have a built-in operator for rounding decimal fraction values. Also, there is no package that is included as part of the Maxima distribution that provides for this capability. However, Robert Dodier has created a Maxima package that includes a function for this purpose ‒ named <code>excel_round.mac</code><code><ref>{{Cite web |last=Dodier |first=Robert |title=maxima-packages/robert-dodier/excel_round/ |url=https://github.com/maxima-project-on-github/maxima-packages/tree/master/robert-dodier/excel_round|website=GitHub}}</ref></code>. However, to be able access the <code>excel_round()</code> function of this package, it must first be downloaded or copied into a location accessible to Maxima using the <code>load()</code> operator. The built-in Maxima <code>load()</code> operator is used to access specialized functions that are not built-in to Maxima. In order to use the <code>load()</code> operator, the location of the downloaded <code>excel_round.mac</code> file has to be part of the argument to the <code>load()</code> operator unless the file happens to be in the Maxima current working directory. The built-in <code>operatingsystem</code> package can provide some functions to help with determining the current working directory. This package is loaded as follows: <syntaxhighlight lang="maxima"> (%i21) load(operatingsystem); (%o21) "/usr/local/share/maxima/5.49.0/share/contrib/operatingsystem/operatingsystem.mac" (%i22) getcurrentdirectory(); (%o22) "/home/username/" </syntaxhighlight>In this example <code>username</code> is the name of the home directory of the user. so if the downloaded <code>excel_round.mac</code> file is not located in the current working directory, then the directory can be changed to the location where the file is located: <syntaxhighlight lang="maxima">(%i22) chdir("/home/username/local/maxima/packages"); (%o22) "#P"/home/username/local/maxima/packages""</syntaxhighlight>Now the <code>excel_round.mac</code> file can be loaded assuming it is within the directory <code>/home/username/local/maxima/packages</code> as follows:<syntaxhighlight lang="maxima"> (%i23) load("excel_round.mac"); (%o23) "excel_round.mac" </syntaxhighlight>Alternatively, if the location of the file is known it can be loaded using the full path name as follows for example:<syntaxhighlight lang="maxima"> (%i24) load("/home/username/local/maxima/packages/excel_round.mac"); (%o24) "/home/username/local/maxima/packages/excel_round.mac" </syntaxhighlight>This method obviates the need for loading the <code>operatingsystem</code> package. '''Note:''' The ''wxMaxima'' GUI makes loading packages simply a matter of a menu selection. The density value above can be rounded to six decimal places as follows:<syntaxhighlight lang="maxima"> (%i25) excel_round(ρ(14.696,59.0),6); (%o25) 0.002377 </syntaxhighlight>This rounded value agrees with the sea level value of <math display="inline">23.77 \cdot 10^{-4}</math> slugs/ft³ taken from the table of Standard Atmosphere values. For Standard Atmosphere values of pressure ( 6.758 lbf/in² ) and temperature ( -12.26 °F ) at 20,000 ft the density value is:<syntaxhighlight lang="maxima"> (%i26) excel_round(ρ(6.759,-12.26),6); (%o26) 0.001267 </syntaxhighlight>This rounded value agrees with the sea level value of <math display="inline">12.67 \cdot 10^{-4}</math> slugs/ft³ taken from the table of Standard Atmosphere values. ===== Pressure ===== However, what is needed for the task at hand is density as a function of altitude. Both the pressure P and the temperature T can be expressed as a function of altitude h: <math display="block">P = P_0(1 - L\cdot h/T_0)^{g/(R \cdot L)} </math> Where in British Engineering units, the constants are: * <math display="inline">P</math> is Pressure in pounds per square foot lbf/ft² * <math display="inline">P_0</math> is (Sea Level Pressure): 2116.224 lbf/ft² or 14.696 lbf/in² * <math display="inline">R</math> is the specific gas constant (for dry air) approximately 1716.56 (ft·lbf)/(slug·°R) * <math display="inline">T_0 </math> is (Sea Level Temperature): 518.67 °R (15 °C or 59 °F) * <math display="inline">L</math> is (Lapse Rate): 0.003563 °R/ft * <math>g</math> is 32.174 ft/s² * <math display="inline">h</math> is altitude in feet above sea level The exponent <math display="inline">\frac{g}{R \cdot L}</math> evaluates to approximately 5.26054:<syntaxhighlight lang="maxima"> (%i27) 32.174/(0.003563*1716.56); (%o27) 5.260539027391964 (%i28) excel_round(%,5); (%o28) 5.26054 </syntaxhighlight><math display="inline">L/T_0</math> evaluates to approximately <syntaxhighlight lang="maxima"> (%i29) 0.003563/518.67; (%o29) 6.869493126650858*10^-6 (%i30) excel_round(6.869493126650858*10^-6,11); (%o30) 6.86949*10^-6 </syntaxhighlight> ===== Temperature ===== <math display="inline">T = 518.67 - 0.003563 \cdot h</math> * <math display="inline">T</math> is Temperature in °R * <math display="inline">h</math> is altitude in feet. ===== Practical Formulas for Pressure and Temperature ===== Thus, the practical formula for pressure and temperatures in terms of British Engineering units are: <math>P = 2116.224\cdot(1-(6.86949 \cdot 10^{-6}) \cdot h)^{5.26054}</math> lbf/ft² <math display="inline">T = 518.67 - 0.003563 \cdot h</math> °R ====== Pressure ====== <syntaxhighlight lang="maxima"> (%i31) P(h) := 2116.224*(1-6.8649*10^-6*h)^5.26054; (%o31) P(h):=2116.224*(1-6.8649*10^(-6)*h)^5.26054 (%i32) p(P) := P/144.0; (%o32) p(P):=P/144.0 (%i33) P(20000); (%o33) 973.0940875140712 (%i34) p(%); (%o34) 6.757597829958828 (%i35) excel_round(%,3); (%o35) 6.758 </syntaxhighlight> ====== Temperature ====== <syntaxhighlight lang="maxima"> (%i36) T(h) := 518.67 - 0.003563*h; (%o36) T(h):=518.67-0.003563*h (%i37) T(20000); (%o37) 447.40999999999997 (%i38) excel_round(%,2); (%o38) 447.41 (%i39) \°F(\°R) := \°R -459.67; (%o39) °F(°R):=°R-459.67 (%i40) \°F(447.41); (%o40) -12.259999999999991 (%i41) excel_round(%,2); (%o41) -12.26 </syntaxhighlight> ===== Density ===== The expressions for pressure and temperature as functions of altitude can be used with the expression for the ideal gas law for an expression of density as a function of altitude as follows:<syntaxhighlight lang="maxima"> (%i42) ρ(h) := P(h)/(R*T(h)); (%o42) ρ(h):=P(h)/(R*T(h)) (%i42) excel_round(ρ(20000)*10^4,2); (%o42) 12.67 </syntaxhighlight>This result agrees with the density value of the standard atmosphere at 20,000 ft. Using the expression for the air density as a function of altitude, an expression for dynamic pressure is as follows:<syntaxhighlight lang="maxima"> (%i43) q(h,VTAS) := ((\ρ(h)*VTAS^2))/2; (%o43) q(h,VTAS):=(ρ(h)*VTAS^2)/2 </syntaxhighlight>Using the expression above, values of dynamic pressure can be calculated as a function of altitude and true airspeed as follows for 20,000 feet and 15,000 feet at 200 ft/s:<syntaxhighlight lang="maxima"> (%i44) q(20000,200); (%o44) 25.34079027107967 (%i45) q(15000,200); (%o45) 29.922636037412556 </syntaxhighlight>This value can be checked using the value for density from the Standard Atmosphere table at 15,000 ft and the expression for dynamic pressure as follows:<syntaxhighlight lang="maxima"> (%i46) excel_round(%,2); (%o46) 29.92 (%i47) (200.0^2)*0.001496/2.0; (%o47) 29.919999999999998 (%i48) excel_round(%,2); (%o48) 29.92 </syntaxhighlight>In the context of aviation and aircraft performance, airspeeds are commonly referenced to knots (nautical miles per hour) instead of ft/s. To determine dynamic pressure as a function of altitude and true airspeed in knots, the following expressions are used:<syntaxhighlight lang="maxima"> (%i49) VTAS(knots) := 1.687811*knots; (%o49) VTAS(knots):=1.687811*knots (%i50) excel_round(VTAS(118.49676),2); (%o50) 200.0 (%i51) q(h,knots) (%o51) q(h,knots):=(ρ(h)*VTAS(knots)^2)/2 (%i52) excel_round(q(15000,118.49676),2); (%o52) 29.92 </syntaxhighlight>So approximately 118 knots true airspeed is equivalent to 200 ft/s, and the above expression for dynamic pressure is in terms of a function of altitude in feet and true airspeed in knots. ==== Plotting ==== Maxima has several ways to do plotting. The image that follows is a simple plot of density as a function of altitude produced using the plotting operator <code>wxplot2d()</code>:<syntaxhighlight lang="maxima"> (%i53) T(h) := 518.688 - 0.0035616*h; (%o53) T(h):=518.688-0.0035616*h (%i54) P(h) := 2116.224*(1-6.8649*10^-6*h)^5.26054; (%o54) P(h):=2116.224*(1-6.8649*10^(-6)*h)^5.26054 (%i55) R : 1716.56; (R) 1716.56 (%i56) ρ(h) := P(h)/(R*T(h)); (%o56) ρ(h):=P(h)/(R*T(h)) (%i57) wxplot2d([ρ(h)], [h,-100,35000])$ </syntaxhighlight> [[File:Density as a Function of Altitude.png|thumb|876x876px|'''Air Density (slugs/ft³) As a Function of Altitude (ft)'''|none]] {{BookCat}} mz0mylacgpa2gltoxmrliklp4rsjy2h 0 482925 4634086 4634043 2026-05-04T14:49:25Z Tmverry 3581185 /* World Health Organization (WHO) */ 4634086 wikitext text/x-wiki == Introduction == The 2014 Ebola outbreak in West Africa was one of the most severe public-health crises of the twenty-first century. The outbreak began in the village of Meliandou in Guinea and quickly spread to neighboring countries. Lasting from 2014-2016, the virus caused widespread devastation and death, claiming more than 11,000 lives during the outbreak. == Background == The 2014-2016 Ebola outbreak was the largest epidemic of Ebola virus. Unlike previous Ebola outbreaks, which were small and geographically isolated, the 2014 outbreak spread across multiple countries in Western Africa and isolated cases were reported in countries outside of Western Africa as well.<ref name=":0">{{Cite journal |last=Bell |first=Beth P. |date=2016 |title=Overview, Control Strategies, and Lessons Learned in the CDC Response to the 2014–2016 Ebola Epidemic |url=https://www.cdc.gov/mmwr/volumes/65/su/su6503a2.htm |journal=MMWR Supplements |language=en-us |volume=65 |doi=10.15585/mmwr.su6503a2 |issn=2380-8950}}</ref> The 2014 outbreak began in December 2013, in Meliandou Village, Guinea.<ref>{{Cite web |title=Ebola outbreak in West Africa, 2014 – 2016: Epidemic timeline, differential diagnoses, determining factors, and lessons for future response |url=https://www.britannica.com/topic/Ebola-outbreak-of-2014}}</ref> The virus spread quickly reaching Liberia by March 2014, and Sierra Leone by May 2014 where major outbreaks would occur. Several factors contributed to the severity of the outbreak, including population mobility across borders, limited healthcare infrastructure, delayed international response, and cultural practices such as burial traditions that increased exposure.<ref name=":0" /> Urban transmission distinguished this outbreak from previous cases which had largely occurred in rural and remote areas.<ref name=":1">{{Cite web |title=Ebola outbreak 2014-2016 - West Africa |url=https://www.who.int/emergencies/situations/ebola-outbreak-2014-2016-West-Africa |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> In August 2014, the World Health Organization (WHO) declared the outbreak a Public Health Emergency of International Concern.<ref name=":1" /> Despite the increased international aid the outbreak would continue for another two years. The outbreak was officially declared over in June 2016, after infecting more than 28,600 individuals and killing 11,325.<ref name=":1" /> === History === First identified in 1976 in the village of Yambuku, located in the modern-day Democratic Republic of the Congo, the Ebola virus is a virus belonging to the Orthoebolavirus genus, which consists of 6 species.<ref name=":2">{{Cite web |title=Ebola disease |url=https://www.who.int/news-room/fact-sheets/detail/ebola-disease |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> Ebola is a severe often fatal illness, characterized by symptoms such as fever, hemorrhaging, and organ failure.<ref name=":2" /> The virus transmits through direct contact with bodily fluids of infected individuals or contaminated materials.<ref name=":0" /> == Response == === Affected Populations === Communities in Guinea, Liberia, and Sierra Leone encountered Ebola as both a public health crisis and a social disruption. Shortages of healthcare workers and facilities meant that many patients were cared for at home by relatives rather than in formal medical settings.<ref name=":0" /> These caregiving arrangements increased transmission risk while reflecting the structural limitations of the region's healthcare infrastructure. Public health interventions frequently came into tension with established cultural practices. Families placed strong moral and emotional weight on caring for the sick and performing funeral and burial rites for the deceased.<ref name=":3" /> These practices constituted major transmission pathways. Isolation protocols, restrictions on touching the sick, and mandatory safe burial procedures were medically necessary, yet many families experienced them as violations of their responsibilities toward the dying and the dead. The conflict between institutional directives and community expectations produced a breakdown in social trust that directly shaped how the outbreak unfolded. In many regions, patients transported to treatment centers often did not return due to death or poor communication between facilities and families. This reinforced suspicion among communities already skeptical of government institutions. As a result, the resistance to public health measures reflects a socially informed response to perceived institutional threat, rather than ignorance.<ref name=":4" />The specific ways this resistance manifested across Guinea, Liberia, and Sierra Leone are examined in the local government sections. Response efforts became more effective as organizations shifted from top-down enforcement toward participatory approaches in late 2014. Initiatives such as Community-Led Ebola Action (CLEA) engaged residents in identifying local transmission risks, adapting high-risk practices, and taking active roles in contact tracing and prevention. This shift demonstrated that controlling the outbreak depended not only on medical infrastructure, but on the trust, local knowledge, and cooperation of the people most affected by it.<ref>{{Cite journal |last=Bedson |first=Jamie |last2=Jalloh |first2=Mohamed F. |last3=Pedi |first3=Danielle |last4=Bah |first4=Saiku |last5=Owen |first5=Katharine |last6=Oniba |first6=Allan |last7=Sangarie |first7=Musa |last8=Fofanah |first8=James S. |last9=Jalloh |first9=Mohammed B. |last10=Sengeh |first10=Paul |last11=Skrip |first11=Laura |last12=Althouse |first12=Benjamin M. |last13=Hébert-Dufresne |first13=Laurent |date=2020-08 |title=Community engagement in outbreak response: lessons from the 2014-2016 Ebola outbreak in Sierra Leone |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC7445350/ |journal=BMJ global health |volume=5 |issue=8 |pages=e002145 |doi=10.1136/bmjgh-2019-002145 |issn=2059-7908 |pmc=7445350 |pmid=32830128}}</ref> === Healthcare Workers === Healthcare workers were among the most vulnerable groups in the 2014 outbreak, facing exposure due to limited resources and rapidly changing conditions. Facilities across West Africa were unprepared for such an outbreak lacking adequate personal protective equipment, sanitation infrastructure, and consistent training. Healthcare workers were estimated to be 21-32 times more likely to contract Ebola than the general public, with over 800 infected and more than 500 deaths reported.<ref>{{Cite web |title=Health worker Ebola infections in Guinea, Liberia and Sierra Leone |url=https://www.who.int/publications/i/item/WHO-EVD-SDS-REPORT-2015.1 |access-date=2026-04-30 |website=www.who.int |language=en}}</ref> The Center for Disease Control (CDC) identified exposure and insufficient protection as a major driver of infection in healthcare settings.<ref>{{Cite web |title=Update: Ebola Virus Disease Outbreak — West Africa, October 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6343a3.htm |access-date=2026-04-30 |website=www.cdc.gov}}</ref> Local healthcare workers often operated in under-supplied facilities with less consistent training, while international responders had better equipment, training, and evacuation options.<ref name=":5">{{Cite web |title=Ebola: Pushed to the limit and beyond {{!}} MSF |url=https://www.msf.org/ebola-pushed-limit-and-beyond |access-date=2026-04-30 |website=www.msf.org |language=en}}</ref> Workers were crucial in implementing key containment strategies such as isolation protocols, contact tracing, and safe burial practices. Effectively executing these strategies required public trust and cooperation which became a problem during such an outbreak. In many cases mistrust and cultural tension hindered compliance, as treatment centers were feared and traditional practices conflicted with medical guidelines.<ref name=":3">{{Cite journal |last=Abramowitz |first=Sharon |date=2017-10-23 |title=Epidemics (Especially Ebola) |url=https://www.annualreviews.org/content/journals/10.1146/annurev-anthro-102116-041616 |journal=Annual Review of Anthropology |language=en |volume=46 |issue=Volume 46, 2017 |pages=421–445 |doi=10.1146/annurev-anthro-102116-041616 |issn=0084-6570}}</ref> Additionally, healthcare workers faced severe psychological strain, burnout, and social stigma due to being seen as a possible risk of infection.<ref name=":4">{{Cite journal |last=Shultz |first=James M. |last2=Cooper |first2=Janice L. |last3=Baingana |first3=Florence |last4=Oquendo |first4=Maria A. |last5=Espinel |first5=Zelde |last6=Althouse |first6=Benjamin M. |last7=Marcelin |first7=Louis Herns |last8=Towers |first8=Sherry |last9=Espinola |first9=Maria |last10=McCoy |first10=Clyde B. |last11=Mazurik |first11=Laurie |last12=Wainberg |first12=Milton L. |last13=Neria |first13=Yuval |last14=Rechkemmer |first14=Andreas |date=2016-11 |title=The Role of Fear-Related Behaviors in the 2013-2016 West Africa Ebola Virus Disease Outbreak |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC5241909/ |journal=Current Psychiatry Reports |volume=18 |issue=11 |pages=104 |doi=10.1007/s11920-016-0741-y |issn=1535-1645 |pmc=5241909 |pmid=27739026}}</ref> === Local Governments === Guinea’s Ministry of Health declared an Ebola outbreak on March 22, 2014, after tracking 86 suspected cases and 59 deaths.<ref>{{Cite web |last=Doctors Without Borders |date=2014-03-24 |title=Guinea: Priority Is to Isolate Suspected Cases in Ebola Outbreak |url=https://www.doctorswithoutborders.org/latest/guinea-priority-isolate-suspected-cases-ebola-outbreak |url-status=live |access-date=2026-05-01 |website=Doctors Without Borders}}</ref> Early public messaging by the government's National Coordination Cell failed to reach remote communities. Consequently, rural populations in the Forest Region feared foreign aid workers and local officials were intentionally spreading the virus to secure international funding or harvest organs.<ref name=":6">{{Cite web |last=Al Jazeera |date=2014-09-25 |title=Arrests in Guinea over Ebola-related murders |url=https://www.aljazeera.com/news/2014/9/25/arrests-in-guinea-over-ebola-related-murders |url-status=live |access-date=2026-05-01 |website=Al Jazeera}}</ref> This deep mistrust culminated on September 16, 2014, when a government sensitization team arrived in the village of Womey. Angry villagers, armed with machetes and clubs, attacked the delegation, murdering eight people, including local health administrators and three journalists.<ref name=":6" /> In direct response to the massacre, the Guinean government deployed a heavily armed military battalion to occupy the region. Soldiers arrested 27 suspects and enforced strict health mandates through prolonged military surveillance.<ref name=":6" /> In Sierra Leone, the Ministry of Health and Sanitation struggled to contain the virus. To locate hidden patients, the government enforced a strict national lockdown, the "Ose to Ose" campaign, from September 19 to 21, 2014. During this period, 30,000 volunteers searched 1.5 million homes, discovering over 200 hidden bodies and identifying roughly 100 new cases.<ref>{{Cite web |last=Centers for Disease Control and Prevention |date=2015-01-16 |title=Use of a Nationwide Call Center for Ebola Response and Monitoring During a 3-Day House-to-House Campaign — Sierra Leone, September 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6401a7.htm |url-status=live |access-date=2026-05-01 |website=Morbidity and Mortality Weekly Report}}</ref> On October 17, 2014, the government centralized operations under the military-led National Ebola Response Centre, directed by Defense Minister Major Palo Conteh.<ref>{{Cite web |last=Centers for Disease Control and Prevention |title=In-Countries Responses |url=https://www.cdcmuseum.org/exhibits/show/ebola/global/incountries-response |url-status=live |access-date=2026-05-01 |website=EBOLA - CDC Museum Digital Exhibits}}</ref> However, heavy-handed military enforcement sparked severe backlash. On October 21, 2014, health workers in the town of Koidu attempted to take a blood sample from an elderly woman. A local youth group rioted, claiming the government was kidnapping citizens.<ref name=":7">{{Cite web |last=Ruble |first=Kayla |date=2014-10-22 |title=Ebola Riots in Sierra Leone Highlight Marginalized Youth Population |url=https://www.vice.com/en/article/ebola-riots-in-sierra-leone-highlight-marginalized-youth-population/ |url-status=live |access-date=2026-05-01 |website=Vice}}</ref> The youths burned down buildings and clashed with police. Security forces fired live ammunition into the crowd, killing two protesters, which prompted the government to impose strict district-wide curfews.<ref name=":7" /> Liberia’s Incident Management System issued strict mandates that conflicted with local cultural norms, most notably the August 3, 2014, order mandating the cremation of all dead bodies in Monrovia.<ref name=":8">{{Cite web |last=MacDougall |first=C. |last2=Gladstone |first2=R. |date=2014-08-20 |title=Clash Erupts in Liberian Capital Over Ebola Quarantine |url=https://www.nytimes.com/2014/08/21/world/africa/ebola-outbreak-liberia-quarantine.html |url-status=live |access-date=2026-05-01 |website=New York Times}}</ref> Because traditional burials involve washing and touching the deceased, families rejected the mandate and secretly hid infected bodies in their homes or abandoned them in streets to avoid government collection. Public anger erupted in the densely populated West Point slum. On August 16, 2014, an angry mob raided a local Ebola holding center, shouting that the virus was a government hoax. They looted infected materials and freed 17 patients.<ref name=":8" /> The Armed Forces of Liberia and the Liberia National Police retaliated by physically barricading the neighborhood on August 20, trapping 75,000 residents inside without adequate food, water, or sanitation. Residents protested at the barricades, leading soldiers to fire live ammunition into the crowd, killing a 15-year-old boy named Shakir Kamara and injuring others.<ref name=":8" /> Intense public and international backlash forced the government to abandon the quarantine on August 30, 2014.<ref name=":8" /> === World Health Organization (WHO) === The World Health Organization (WHO) served as the main body responsible for coordinating the international public health response. WHO conducted early field investigations and sent experts to West Africa. It's response was widely criticized for its failure to match the speed and scale of the crisis. Although WHO had known of the outbreak for months, it did not declare Ebola a Public Health Emergency of International Concern until August 2014, after the virus had already spread extensively across Guinea, Liberia, and Sierra Leone. Following this declaration, WHO helped coordinate international response efforts, supported contact tracing, and deployed specialists in epidemiology, laboratory work, risk communication, and social mobilization. <ref name=":1" /> === Médecins Sans Frontières (MSF) === Among the international organizations that responded to the 2014 outbreak, Médecins Sans Frontières (MSF), also known as Doctors Without Borders, played the most significant frontline role. MSF was among the first international organizations to recognize the scale of the outbreak and deployed teams to Guinea, Liberia, and Sierra Leone before most governments and agencies had mobilized. Operating multiple Ebola Treatment Centers across the three countries, MSF ultimately treated approximately one third of all confirmed cases.<ref name=":5" /> MSF's early presence also made them one of the first organizations to publicly warn that the outbreak was out of control, repeatedly calling on the international community to scale up its response months before the WHO declared a Public Health Emergency of International Concern in August 2014.<ref name=":1" /> This tension between MSF's frontline assessment and the pace of the formal international response highlighted a broader gap between organizations operating on the ground and those coordinating from a distance. == References == <references /> 6akm3hsxyjf79p65176403m7s7nheuy 4634100 4634086 2026-05-04T15:42:37Z Lincolnmoy 3581009 /* Background */ picture and text edits 4634100 wikitext text/x-wiki == Introduction == The 2014 Ebola outbreak in West Africa was one of the most severe public-health crises of the twenty-first century. The outbreak began in the village of Meliandou in Guinea and quickly spread to neighboring countries. Lasting from 2014-2016, the virus caused widespread devastation and death, claiming more than 11,000 lives during the outbreak. == Background == [[File:2014 ebola virus epidemic in West Africa simplified.svg|thumb|320x320px|'''Figure 1. Map of the 2014 Ebola outbreak in West Africa.''']] First identified in 1976 in the village of Yambuku, located in the modern-day Democratic Republic of the Congo, the Ebola virus is a virus belonging to the Orthoebolavirus genus, which consists of 6 species.<ref name=":2">{{Cite web |title=Ebola disease |url=https://www.who.int/news-room/fact-sheets/detail/ebola-disease |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> Ebola is a severe often fatal illness, characterized by symptoms such as fever, hemorrhaging, and organ failure.<ref name=":2" /> The virus transmits through direct contact with bodily fluids of infected individuals or contaminated materials.<ref name=":0" /> The 2014-2016 Ebola outbreak was the largest epidemic of Ebola virus. Unlike previous Ebola outbreaks, which were small and geographically isolated, the 2014 outbreak spread across multiple countries in Western Africa and isolated cases were reported in countries outside of Western Africa as well.<ref name=":0">{{Cite journal |last=Bell |first=Beth P. |date=2016 |title=Overview, Control Strategies, and Lessons Learned in the CDC Response to the 2014–2016 Ebola Epidemic |url=https://www.cdc.gov/mmwr/volumes/65/su/su6503a2.htm |journal=MMWR Supplements |language=en-us |volume=65 |doi=10.15585/mmwr.su6503a2 |issn=2380-8950}}</ref> The 2014 outbreak began in December 2013, in Meliandou Village, Guinea.<ref>{{Cite web |title=Ebola outbreak in West Africa, 2014 – 2016: Epidemic timeline, differential diagnoses, determining factors, and lessons for future response |url=https://www.britannica.com/topic/Ebola-outbreak-of-2014}}</ref> The virus spread quickly reaching Liberia by March 2014, and Sierra Leone by May 2014 where major outbreaks would occur. Several factors contributed to the severity of the outbreak, including population mobility across borders, limited healthcare infrastructure, delayed international response, and cultural practices such as burial traditions that increased exposure.<ref name=":0" /> Urban transmission distinguished this outbreak from previous cases which had largely occurred in rural and remote areas.<ref name=":1">{{Cite web |title=Ebola outbreak 2014-2016 - West Africa |url=https://www.who.int/emergencies/situations/ebola-outbreak-2014-2016-West-Africa |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> In August 2014, the World Health Organization (WHO) declared the outbreak a Public Health Emergency of International Concern.<ref name=":1" /> Despite the increased international aid the outbreak would continue for another two years. The outbreak was officially declared over in June 2016, after infecting more than 28,600 individuals and killing 11,325.<ref name=":1" /> == Response == === Affected Populations === Communities in Guinea, Liberia, and Sierra Leone encountered Ebola as both a public health crisis and a social disruption. Shortages of healthcare workers and facilities meant that many patients were cared for at home by relatives rather than in formal medical settings.<ref name=":0" /> These caregiving arrangements increased transmission risk while reflecting the structural limitations of the region's healthcare infrastructure. Public health interventions frequently came into tension with established cultural practices. Families placed strong moral and emotional weight on caring for the sick and performing funeral and burial rites for the deceased.<ref name=":3" /> These practices constituted major transmission pathways. Isolation protocols, restrictions on touching the sick, and mandatory safe burial procedures were medically necessary, yet many families experienced them as violations of their responsibilities toward the dying and the dead. The conflict between institutional directives and community expectations produced a breakdown in social trust that directly shaped how the outbreak unfolded. In many regions, patients transported to treatment centers often did not return due to death or poor communication between facilities and families. This reinforced suspicion among communities already skeptical of government institutions. As a result, the resistance to public health measures reflects a socially informed response to perceived institutional threat, rather than ignorance.<ref name=":4" />The specific ways this resistance manifested across Guinea, Liberia, and Sierra Leone are examined in the local government sections. Response efforts became more effective as organizations shifted from top-down enforcement toward participatory approaches in late 2014. Initiatives such as Community-Led Ebola Action (CLEA) engaged residents in identifying local transmission risks, adapting high-risk practices, and taking active roles in contact tracing and prevention. This shift demonstrated that controlling the outbreak depended not only on medical infrastructure, but on the trust, local knowledge, and cooperation of the people most affected by it.<ref>{{Cite journal |last=Bedson |first=Jamie |last2=Jalloh |first2=Mohamed F. |last3=Pedi |first3=Danielle |last4=Bah |first4=Saiku |last5=Owen |first5=Katharine |last6=Oniba |first6=Allan |last7=Sangarie |first7=Musa |last8=Fofanah |first8=James S. |last9=Jalloh |first9=Mohammed B. |last10=Sengeh |first10=Paul |last11=Skrip |first11=Laura |last12=Althouse |first12=Benjamin M. |last13=Hébert-Dufresne |first13=Laurent |date=2020-08 |title=Community engagement in outbreak response: lessons from the 2014-2016 Ebola outbreak in Sierra Leone |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC7445350/ |journal=BMJ global health |volume=5 |issue=8 |pages=e002145 |doi=10.1136/bmjgh-2019-002145 |issn=2059-7908 |pmc=7445350 |pmid=32830128}}</ref> === Healthcare Workers === Healthcare workers were among the most vulnerable groups in the 2014 outbreak, facing exposure due to limited resources and rapidly changing conditions. Facilities across West Africa were unprepared for such an outbreak lacking adequate personal protective equipment, sanitation infrastructure, and consistent training. Healthcare workers were estimated to be 21-32 times more likely to contract Ebola than the general public, with over 800 infected and more than 500 deaths reported.<ref>{{Cite web |title=Health worker Ebola infections in Guinea, Liberia and Sierra Leone |url=https://www.who.int/publications/i/item/WHO-EVD-SDS-REPORT-2015.1 |access-date=2026-04-30 |website=www.who.int |language=en}}</ref> The Center for Disease Control (CDC) identified exposure and insufficient protection as a major driver of infection in healthcare settings.<ref>{{Cite web |title=Update: Ebola Virus Disease Outbreak — West Africa, October 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6343a3.htm |access-date=2026-04-30 |website=www.cdc.gov}}</ref> Local healthcare workers often operated in under-supplied facilities with less consistent training, while international responders had better equipment, training, and evacuation options.<ref name=":5">{{Cite web |title=Ebola: Pushed to the limit and beyond {{!}} MSF |url=https://www.msf.org/ebola-pushed-limit-and-beyond |access-date=2026-04-30 |website=www.msf.org |language=en}}</ref> Workers were crucial in implementing key containment strategies such as isolation protocols, contact tracing, and safe burial practices. Effectively executing these strategies required public trust and cooperation which became a problem during such an outbreak. In many cases mistrust and cultural tension hindered compliance, as treatment centers were feared and traditional practices conflicted with medical guidelines.<ref name=":3">{{Cite journal |last=Abramowitz |first=Sharon |date=2017-10-23 |title=Epidemics (Especially Ebola) |url=https://www.annualreviews.org/content/journals/10.1146/annurev-anthro-102116-041616 |journal=Annual Review of Anthropology |language=en |volume=46 |issue=Volume 46, 2017 |pages=421–445 |doi=10.1146/annurev-anthro-102116-041616 |issn=0084-6570}}</ref> Additionally, healthcare workers faced severe psychological strain, burnout, and social stigma due to being seen as a possible risk of infection.<ref name=":4">{{Cite journal |last=Shultz |first=James M. |last2=Cooper |first2=Janice L. |last3=Baingana |first3=Florence |last4=Oquendo |first4=Maria A. |last5=Espinel |first5=Zelde |last6=Althouse |first6=Benjamin M. |last7=Marcelin |first7=Louis Herns |last8=Towers |first8=Sherry |last9=Espinola |first9=Maria |last10=McCoy |first10=Clyde B. |last11=Mazurik |first11=Laurie |last12=Wainberg |first12=Milton L. |last13=Neria |first13=Yuval |last14=Rechkemmer |first14=Andreas |date=2016-11 |title=The Role of Fear-Related Behaviors in the 2013-2016 West Africa Ebola Virus Disease Outbreak |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC5241909/ |journal=Current Psychiatry Reports |volume=18 |issue=11 |pages=104 |doi=10.1007/s11920-016-0741-y |issn=1535-1645 |pmc=5241909 |pmid=27739026}}</ref> === Local Governments === Guinea’s Ministry of Health declared an Ebola outbreak on March 22, 2014, after tracking 86 suspected cases and 59 deaths.<ref>{{Cite web |last=Doctors Without Borders |date=2014-03-24 |title=Guinea: Priority Is to Isolate Suspected Cases in Ebola Outbreak |url=https://www.doctorswithoutborders.org/latest/guinea-priority-isolate-suspected-cases-ebola-outbreak |url-status=live |access-date=2026-05-01 |website=Doctors Without Borders}}</ref> Early public messaging by the government's National Coordination Cell failed to reach remote communities. Consequently, rural populations in the Forest Region feared foreign aid workers and local officials were intentionally spreading the virus to secure international funding or harvest organs.<ref name=":6">{{Cite web |last=Al Jazeera |date=2014-09-25 |title=Arrests in Guinea over Ebola-related murders |url=https://www.aljazeera.com/news/2014/9/25/arrests-in-guinea-over-ebola-related-murders |url-status=live |access-date=2026-05-01 |website=Al Jazeera}}</ref> This deep mistrust culminated on September 16, 2014, when a government sensitization team arrived in the village of Womey. Angry villagers, armed with machetes and clubs, attacked the delegation, murdering eight people, including local health administrators and three journalists.<ref name=":6" /> In direct response to the massacre, the Guinean government deployed a heavily armed military battalion to occupy the region. Soldiers arrested 27 suspects and enforced strict health mandates through prolonged military surveillance.<ref name=":6" /> In Sierra Leone, the Ministry of Health and Sanitation struggled to contain the virus. To locate hidden patients, the government enforced a strict national lockdown, the "Ose to Ose" campaign, from September 19 to 21, 2014. During this period, 30,000 volunteers searched 1.5 million homes, discovering over 200 hidden bodies and identifying roughly 100 new cases.<ref>{{Cite web |last=Centers for Disease Control and Prevention |date=2015-01-16 |title=Use of a Nationwide Call Center for Ebola Response and Monitoring During a 3-Day House-to-House Campaign — Sierra Leone, September 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6401a7.htm |url-status=live |access-date=2026-05-01 |website=Morbidity and Mortality Weekly Report}}</ref> On October 17, 2014, the government centralized operations under the military-led National Ebola Response Centre, directed by Defense Minister Major Palo Conteh.<ref>{{Cite web |last=Centers for Disease Control and Prevention |title=In-Countries Responses |url=https://www.cdcmuseum.org/exhibits/show/ebola/global/incountries-response |url-status=live |access-date=2026-05-01 |website=EBOLA - CDC Museum Digital Exhibits}}</ref> However, heavy-handed military enforcement sparked severe backlash. On October 21, 2014, health workers in the town of Koidu attempted to take a blood sample from an elderly woman. A local youth group rioted, claiming the government was kidnapping citizens.<ref name=":7">{{Cite web |last=Ruble |first=Kayla |date=2014-10-22 |title=Ebola Riots in Sierra Leone Highlight Marginalized Youth Population |url=https://www.vice.com/en/article/ebola-riots-in-sierra-leone-highlight-marginalized-youth-population/ |url-status=live |access-date=2026-05-01 |website=Vice}}</ref> The youths burned down buildings and clashed with police. Security forces fired live ammunition into the crowd, killing two protesters, which prompted the government to impose strict district-wide curfews.<ref name=":7" /> Liberia’s Incident Management System issued strict mandates that conflicted with local cultural norms, most notably the August 3, 2014, order mandating the cremation of all dead bodies in Monrovia.<ref name=":8">{{Cite web |last=MacDougall |first=C. |last2=Gladstone |first2=R. |date=2014-08-20 |title=Clash Erupts in Liberian Capital Over Ebola Quarantine |url=https://www.nytimes.com/2014/08/21/world/africa/ebola-outbreak-liberia-quarantine.html |url-status=live |access-date=2026-05-01 |website=New York Times}}</ref> Because traditional burials involve washing and touching the deceased, families rejected the mandate and secretly hid infected bodies in their homes or abandoned them in streets to avoid government collection. Public anger erupted in the densely populated West Point slum. On August 16, 2014, an angry mob raided a local Ebola holding center, shouting that the virus was a government hoax. They looted infected materials and freed 17 patients.<ref name=":8" /> The Armed Forces of Liberia and the Liberia National Police retaliated by physically barricading the neighborhood on August 20, trapping 75,000 residents inside without adequate food, water, or sanitation. Residents protested at the barricades, leading soldiers to fire live ammunition into the crowd, killing a 15-year-old boy named Shakir Kamara and injuring others.<ref name=":8" /> Intense public and international backlash forced the government to abandon the quarantine on August 30, 2014.<ref name=":8" /> === World Health Organization (WHO) === The World Health Organization (WHO) served as the main body responsible for coordinating the international public health response. WHO conducted early field investigations and sent experts to West Africa. It's response was widely criticized for its failure to match the speed and scale of the crisis. Although WHO had known of the outbreak for months, it did not declare Ebola a Public Health Emergency of International Concern until August 2014, after the virus had already spread extensively across Guinea, Liberia, and Sierra Leone. Following this declaration, WHO helped coordinate international response efforts, supported contact tracing, and deployed specialists in epidemiology, laboratory work, risk communication, and social mobilization. <ref name=":1" /> === Médecins Sans Frontières (MSF) === Among the international organizations that responded to the 2014 outbreak, Médecins Sans Frontières (MSF), also known as Doctors Without Borders, played the most significant frontline role. MSF was among the first international organizations to recognize the scale of the outbreak and deployed teams to Guinea, Liberia, and Sierra Leone before most governments and agencies had mobilized. Operating multiple Ebola Treatment Centers across the three countries, MSF ultimately treated approximately one third of all confirmed cases.<ref name=":5" /> MSF's early presence also made them one of the first organizations to publicly warn that the outbreak was out of control, repeatedly calling on the international community to scale up its response months before the WHO declared a Public Health Emergency of International Concern in August 2014.<ref name=":1" /> This tension between MSF's frontline assessment and the pace of the formal international response highlighted a broader gap between organizations operating on the ground and those coordinating from a distance. == References == <references /> 3dd05pyh7vexaam47ticzx4j5d7cxgz 4634108 4634100 2026-05-04T16:06:33Z Lincolnmoy 3581009 further work section 4634108 wikitext text/x-wiki == Introduction == The 2014 Ebola outbreak in West Africa was one of the most severe public-health crises of the twenty-first century. The outbreak began in the village of Meliandou in Guinea and quickly spread to neighboring countries. Lasting from 2014-2016, the virus caused widespread devastation and death, claiming more than 11,000 lives during the outbreak. == Background == [[File:2014 ebola virus epidemic in West Africa simplified.svg|thumb|320x320px|'''Figure 1. Map of the 2014 Ebola outbreak in West Africa.''']] First identified in 1976 in the village of Yambuku, located in the modern-day Democratic Republic of the Congo, the Ebola virus is a virus belonging to the Orthoebolavirus genus, which consists of 6 species.<ref name=":2">{{Cite web |title=Ebola disease |url=https://www.who.int/news-room/fact-sheets/detail/ebola-disease |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> Ebola is a severe often fatal illness, characterized by symptoms such as fever, hemorrhaging, and organ failure.<ref name=":2" /> The virus transmits through direct contact with bodily fluids of infected individuals or contaminated materials.<ref name=":0" /> The 2014-2016 Ebola outbreak was the largest epidemic of Ebola virus. Unlike previous Ebola outbreaks, which were small and geographically isolated, the 2014 outbreak spread across multiple countries in Western Africa and isolated cases were reported in countries outside of Western Africa as well.<ref name=":0">{{Cite journal |last=Bell |first=Beth P. |date=2016 |title=Overview, Control Strategies, and Lessons Learned in the CDC Response to the 2014–2016 Ebola Epidemic |url=https://www.cdc.gov/mmwr/volumes/65/su/su6503a2.htm |journal=MMWR Supplements |language=en-us |volume=65 |doi=10.15585/mmwr.su6503a2 |issn=2380-8950}}</ref> The 2014 outbreak began in December 2013, in Meliandou Village, Guinea.<ref>{{Cite web |title=Ebola outbreak in West Africa, 2014 – 2016: Epidemic timeline, differential diagnoses, determining factors, and lessons for future response |url=https://www.britannica.com/topic/Ebola-outbreak-of-2014}}</ref> The virus spread quickly reaching Liberia by March 2014, and Sierra Leone by May 2014 where major outbreaks would occur. Several factors contributed to the severity of the outbreak, including population mobility across borders, limited healthcare infrastructure, delayed international response, and cultural practices such as burial traditions that increased exposure.<ref name=":0" /> Urban transmission distinguished this outbreak from previous cases which had largely occurred in rural and remote areas.<ref name=":1">{{Cite web |title=Ebola outbreak 2014-2016 - West Africa |url=https://www.who.int/emergencies/situations/ebola-outbreak-2014-2016-West-Africa |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> In August 2014, the World Health Organization (WHO) declared the outbreak a Public Health Emergency of International Concern.<ref name=":1" /> Despite the increased international aid the outbreak would continue for another two years. The outbreak was officially declared over in June 2016, after infecting more than 28,600 individuals and killing 11,325.<ref name=":1" /> == Response == === Affected Populations === Communities in Guinea, Liberia, and Sierra Leone encountered Ebola as both a public health crisis and a social disruption. Shortages of healthcare workers and facilities meant that many patients were cared for at home by relatives rather than in formal medical settings.<ref name=":0" /> These caregiving arrangements increased transmission risk while reflecting the structural limitations of the region's healthcare infrastructure. Public health interventions frequently came into tension with established cultural practices. Families placed strong moral and emotional weight on caring for the sick and performing funeral and burial rites for the deceased.<ref name=":3" /> These practices constituted major transmission pathways. Isolation protocols, restrictions on touching the sick, and mandatory safe burial procedures were medically necessary, yet many families experienced them as violations of their responsibilities toward the dying and the dead. The conflict between institutional directives and community expectations produced a breakdown in social trust that directly shaped how the outbreak unfolded. In many regions, patients transported to treatment centers often did not return due to death or poor communication between facilities and families. This reinforced suspicion among communities already skeptical of government institutions. As a result, the resistance to public health measures reflects a socially informed response to perceived institutional threat, rather than ignorance.<ref name=":4" />The specific ways this resistance manifested across Guinea, Liberia, and Sierra Leone are examined in the local government sections. Response efforts became more effective as organizations shifted from top-down enforcement toward participatory approaches in late 2014. Initiatives such as Community-Led Ebola Action (CLEA) engaged residents in identifying local transmission risks, adapting high-risk practices, and taking active roles in contact tracing and prevention. This shift demonstrated that controlling the outbreak depended not only on medical infrastructure, but on the trust, local knowledge, and cooperation of the people most affected by it.<ref>{{Cite journal |last=Bedson |first=Jamie |last2=Jalloh |first2=Mohamed F. |last3=Pedi |first3=Danielle |last4=Bah |first4=Saiku |last5=Owen |first5=Katharine |last6=Oniba |first6=Allan |last7=Sangarie |first7=Musa |last8=Fofanah |first8=James S. |last9=Jalloh |first9=Mohammed B. |last10=Sengeh |first10=Paul |last11=Skrip |first11=Laura |last12=Althouse |first12=Benjamin M. |last13=Hébert-Dufresne |first13=Laurent |date=2020-08 |title=Community engagement in outbreak response: lessons from the 2014-2016 Ebola outbreak in Sierra Leone |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC7445350/ |journal=BMJ global health |volume=5 |issue=8 |pages=e002145 |doi=10.1136/bmjgh-2019-002145 |issn=2059-7908 |pmc=7445350 |pmid=32830128}}</ref> === Healthcare Workers === Healthcare workers were among the most vulnerable groups in the 2014 outbreak, facing exposure due to limited resources and rapidly changing conditions. Facilities across West Africa were unprepared for such an outbreak lacking adequate personal protective equipment, sanitation infrastructure, and consistent training. Healthcare workers were estimated to be 21-32 times more likely to contract Ebola than the general public, with over 800 infected and more than 500 deaths reported.<ref>{{Cite web |title=Health worker Ebola infections in Guinea, Liberia and Sierra Leone |url=https://www.who.int/publications/i/item/WHO-EVD-SDS-REPORT-2015.1 |access-date=2026-04-30 |website=www.who.int |language=en}}</ref> The Center for Disease Control (CDC) identified exposure and insufficient protection as a major driver of infection in healthcare settings.<ref>{{Cite web |title=Update: Ebola Virus Disease Outbreak — West Africa, October 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6343a3.htm |access-date=2026-04-30 |website=www.cdc.gov}}</ref> Local healthcare workers often operated in under-supplied facilities with less consistent training, while international responders had better equipment, training, and evacuation options.<ref name=":5">{{Cite web |title=Ebola: Pushed to the limit and beyond {{!}} MSF |url=https://www.msf.org/ebola-pushed-limit-and-beyond |access-date=2026-04-30 |website=www.msf.org |language=en}}</ref> Workers were crucial in implementing key containment strategies such as isolation protocols, contact tracing, and safe burial practices. Effectively executing these strategies required public trust and cooperation which became a problem during such an outbreak. In many cases mistrust and cultural tension hindered compliance, as treatment centers were feared and traditional practices conflicted with medical guidelines.<ref name=":3">{{Cite journal |last=Abramowitz |first=Sharon |date=2017-10-23 |title=Epidemics (Especially Ebola) |url=https://www.annualreviews.org/content/journals/10.1146/annurev-anthro-102116-041616 |journal=Annual Review of Anthropology |language=en |volume=46 |issue=Volume 46, 2017 |pages=421–445 |doi=10.1146/annurev-anthro-102116-041616 |issn=0084-6570}}</ref> Additionally, healthcare workers faced severe psychological strain, burnout, and social stigma due to being seen as a possible risk of infection.<ref name=":4">{{Cite journal |last=Shultz |first=James M. |last2=Cooper |first2=Janice L. |last3=Baingana |first3=Florence |last4=Oquendo |first4=Maria A. |last5=Espinel |first5=Zelde |last6=Althouse |first6=Benjamin M. |last7=Marcelin |first7=Louis Herns |last8=Towers |first8=Sherry |last9=Espinola |first9=Maria |last10=McCoy |first10=Clyde B. |last11=Mazurik |first11=Laurie |last12=Wainberg |first12=Milton L. |last13=Neria |first13=Yuval |last14=Rechkemmer |first14=Andreas |date=2016-11 |title=The Role of Fear-Related Behaviors in the 2013-2016 West Africa Ebola Virus Disease Outbreak |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC5241909/ |journal=Current Psychiatry Reports |volume=18 |issue=11 |pages=104 |doi=10.1007/s11920-016-0741-y |issn=1535-1645 |pmc=5241909 |pmid=27739026}}</ref> === Local Governments === Guinea’s Ministry of Health declared an Ebola outbreak on March 22, 2014, after tracking 86 suspected cases and 59 deaths.<ref>{{Cite web |last=Doctors Without Borders |date=2014-03-24 |title=Guinea: Priority Is to Isolate Suspected Cases in Ebola Outbreak |url=https://www.doctorswithoutborders.org/latest/guinea-priority-isolate-suspected-cases-ebola-outbreak |url-status=live |access-date=2026-05-01 |website=Doctors Without Borders}}</ref> Early public messaging by the government's National Coordination Cell failed to reach remote communities. Consequently, rural populations in the Forest Region feared foreign aid workers and local officials were intentionally spreading the virus to secure international funding or harvest organs.<ref name=":6">{{Cite web |last=Al Jazeera |date=2014-09-25 |title=Arrests in Guinea over Ebola-related murders |url=https://www.aljazeera.com/news/2014/9/25/arrests-in-guinea-over-ebola-related-murders |url-status=live |access-date=2026-05-01 |website=Al Jazeera}}</ref> This deep mistrust culminated on September 16, 2014, when a government sensitization team arrived in the village of Womey. Angry villagers, armed with machetes and clubs, attacked the delegation, murdering eight people, including local health administrators and three journalists.<ref name=":6" /> In direct response to the massacre, the Guinean government deployed a heavily armed military battalion to occupy the region. Soldiers arrested 27 suspects and enforced strict health mandates through prolonged military surveillance.<ref name=":6" /> In Sierra Leone, the Ministry of Health and Sanitation struggled to contain the virus. To locate hidden patients, the government enforced a strict national lockdown, the "Ose to Ose" campaign, from September 19 to 21, 2014. During this period, 30,000 volunteers searched 1.5 million homes, discovering over 200 hidden bodies and identifying roughly 100 new cases.<ref>{{Cite web |last=Centers for Disease Control and Prevention |date=2015-01-16 |title=Use of a Nationwide Call Center for Ebola Response and Monitoring During a 3-Day House-to-House Campaign — Sierra Leone, September 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6401a7.htm |url-status=live |access-date=2026-05-01 |website=Morbidity and Mortality Weekly Report}}</ref> On October 17, 2014, the government centralized operations under the military-led National Ebola Response Centre, directed by Defense Minister Major Palo Conteh.<ref>{{Cite web |last=Centers for Disease Control and Prevention |title=In-Countries Responses |url=https://www.cdcmuseum.org/exhibits/show/ebola/global/incountries-response |url-status=live |access-date=2026-05-01 |website=EBOLA - CDC Museum Digital Exhibits}}</ref> However, heavy-handed military enforcement sparked severe backlash. On October 21, 2014, health workers in the town of Koidu attempted to take a blood sample from an elderly woman. A local youth group rioted, claiming the government was kidnapping citizens.<ref name=":7">{{Cite web |last=Ruble |first=Kayla |date=2014-10-22 |title=Ebola Riots in Sierra Leone Highlight Marginalized Youth Population |url=https://www.vice.com/en/article/ebola-riots-in-sierra-leone-highlight-marginalized-youth-population/ |url-status=live |access-date=2026-05-01 |website=Vice}}</ref> The youths burned down buildings and clashed with police. Security forces fired live ammunition into the crowd, killing two protesters, which prompted the government to impose strict district-wide curfews.<ref name=":7" /> Liberia’s Incident Management System issued strict mandates that conflicted with local cultural norms, most notably the August 3, 2014, order mandating the cremation of all dead bodies in Monrovia.<ref name=":8">{{Cite web |last=MacDougall |first=C. |last2=Gladstone |first2=R. |date=2014-08-20 |title=Clash Erupts in Liberian Capital Over Ebola Quarantine |url=https://www.nytimes.com/2014/08/21/world/africa/ebola-outbreak-liberia-quarantine.html |url-status=live |access-date=2026-05-01 |website=New York Times}}</ref> Because traditional burials involve washing and touching the deceased, families rejected the mandate and secretly hid infected bodies in their homes or abandoned them in streets to avoid government collection. Public anger erupted in the densely populated West Point slum. On August 16, 2014, an angry mob raided a local Ebola holding center, shouting that the virus was a government hoax. They looted infected materials and freed 17 patients.<ref name=":8" /> The Armed Forces of Liberia and the Liberia National Police retaliated by physically barricading the neighborhood on August 20, trapping 75,000 residents inside without adequate food, water, or sanitation. Residents protested at the barricades, leading soldiers to fire live ammunition into the crowd, killing a 15-year-old boy named Shakir Kamara and injuring others.<ref name=":8" /> Intense public and international backlash forced the government to abandon the quarantine on August 30, 2014.<ref name=":8" /> === World Health Organization (WHO) === The World Health Organization (WHO) served as the main body responsible for coordinating the international public health response. WHO conducted early field investigations and sent experts to West Africa. It's response was widely criticized for its failure to match the speed and scale of the crisis. Although WHO had known of the outbreak for months, it did not declare Ebola a Public Health Emergency of International Concern until August 2014, after the virus had already spread extensively across Guinea, Liberia, and Sierra Leone. Following this declaration, WHO helped coordinate international response efforts, supported contact tracing, and deployed specialists in epidemiology, laboratory work, risk communication, and social mobilization. <ref name=":1" /> === Médecins Sans Frontières (MSF) === Among the international organizations that responded to the 2014 outbreak, Médecins Sans Frontières (MSF), also known as Doctors Without Borders, played the most significant frontline role. MSF was among the first international organizations to recognize the scale of the outbreak and deployed teams to Guinea, Liberia, and Sierra Leone before most governments and agencies had mobilized. Operating multiple Ebola Treatment Centers across the three countries, MSF ultimately treated approximately one third of all confirmed cases.<ref name=":5" /> MSF's early presence also made them one of the first organizations to publicly warn that the outbreak was out of control, repeatedly calling on the international community to scale up its response months before the WHO declared a Public Health Emergency of International Concern in August 2014.<ref name=":1" /> This tension between MSF's frontline assessment and the pace of the formal international response highlighted a broader gap between organizations operating on the ground and those coordinating from a distance. == Conclusion == == Further Work == This chapter could be extended by examining the role of media in shaping the global public perception of the outbreak. Additional research on the long-term aftermath of the outbreak, including whether institutional trust recovered in Guinea, Liberia, and Sierra Leone, remains an important area for potential analysis. == References == <references /> c40ub3ea8vw4qwh26zbhapjo44o8sp1 4634119 4634108 2026-05-04T17:05:01Z Lincolnmoy 3581009 4634119 wikitext text/x-wiki == Introduction == The 2014 Ebola outbreak in West Africa was one of the most severe public-health crises of the twenty-first century. The outbreak began in the village of Meliandou in Guinea and quickly spread to neighboring countries. Lasting from 2014-2016, the virus caused widespread devastation and death, claiming more than 11,000 lives during the outbreak. == Background == [[File:2014 ebola virus epidemic in West Africa simplified.svg|thumb|320x320px|'''Figure 1. Map of the 2014 Ebola outbreak in West Africa.''']] First identified in 1976 in the village of Yambuku, located in the modern-day Democratic Republic of the Congo, the Ebola virus is a virus belonging to the Orthoebolavirus genus, which consists of 6 species.<ref name=":2">{{Cite web |title=Ebola disease |url=https://www.who.int/news-room/fact-sheets/detail/ebola-disease |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> Ebola is a severe often fatal illness, characterized by symptoms such as fever, hemorrhaging, and organ failure.<ref name=":2" /> The virus transmits through direct contact with bodily fluids of infected individuals or contaminated materials.<ref name=":0" /> The 2014-2016 Ebola outbreak was the largest epidemic of Ebola virus. Unlike previous Ebola outbreaks, which were small and geographically isolated, the 2014 outbreak spread across multiple countries in Western Africa and isolated cases were reported in countries outside of Western Africa as well.<ref name=":0">{{Cite journal |last=Bell |first=Beth P. |date=2016 |title=Overview, Control Strategies, and Lessons Learned in the CDC Response to the 2014–2016 Ebola Epidemic |url=https://www.cdc.gov/mmwr/volumes/65/su/su6503a2.htm |journal=MMWR Supplements |language=en-us |volume=65 |doi=10.15585/mmwr.su6503a2 |issn=2380-8950}}</ref> The 2014 outbreak began in December 2013, in Meliandou Village, Guinea.<ref>{{Cite web |title=Ebola outbreak in West Africa, 2014 – 2016: Epidemic timeline, differential diagnoses, determining factors, and lessons for future response |url=https://www.britannica.com/topic/Ebola-outbreak-of-2014}}</ref> The virus spread quickly reaching Liberia by March 2014, and Sierra Leone by May 2014 where major outbreaks would occur. Several factors contributed to the severity of the outbreak, including population mobility across borders, limited healthcare infrastructure, delayed international response, and cultural practices such as burial traditions that increased exposure.<ref name=":0" /> Urban transmission distinguished this outbreak from previous cases which had largely occurred in rural and remote areas.<ref name=":1">{{Cite web |title=Ebola outbreak 2014-2016 - West Africa |url=https://www.who.int/emergencies/situations/ebola-outbreak-2014-2016-West-Africa |access-date=2026-04-29 |website=www.who.int |language=en}}</ref> In August 2014, the World Health Organization (WHO) declared the outbreak a Public Health Emergency of International Concern.<ref name=":1" /> Despite the increased international aid the outbreak would continue for another two years. The outbreak was officially declared over in June 2016, after infecting more than 28,600 individuals and killing 11,325.<ref name=":1" /> == Response == === Affected Populations === Communities in Guinea, Liberia, and Sierra Leone encountered Ebola as both a public health crisis and a social disruption. Shortages of healthcare workers and facilities meant that many patients were cared for at home by relatives rather than in formal medical settings.<ref name=":0" /> These caregiving arrangements increased transmission risk while reflecting the structural limitations of the region's healthcare infrastructure. Public health interventions frequently came into tension with established cultural practices. Families placed strong moral and emotional weight on caring for the sick and performing funeral and burial rites for the deceased.<ref name=":3" /> These practices constituted major transmission pathways. Isolation protocols, restrictions on touching the sick, and mandatory safe burial procedures were medically necessary, yet many families experienced them as violations of their responsibilities toward the dying and the dead. The conflict between institutional directives and community expectations produced a breakdown in social trust that directly shaped how the outbreak unfolded. In many regions, patients transported to treatment centers often did not return due to death or poor communication between facilities and families. This reinforced suspicion among communities already skeptical of government institutions. As a result, the resistance to public health measures reflects a socially informed response to perceived institutional threat, rather than ignorance.<ref name=":4" />The specific ways this resistance manifested across Guinea, Liberia, and Sierra Leone are examined in the local government sections. Response efforts became more effective as organizations shifted from top-down enforcement toward participatory approaches in late 2014. Initiatives such as Community-Led Ebola Action (CLEA) engaged residents in identifying local transmission risks, adapting high-risk practices, and taking active roles in contact tracing and prevention. This shift demonstrated that controlling the outbreak depended not only on medical infrastructure, but on the trust, local knowledge, and cooperation of the people most affected by it.<ref>{{Cite journal |last=Bedson |first=Jamie |last2=Jalloh |first2=Mohamed F. |last3=Pedi |first3=Danielle |last4=Bah |first4=Saiku |last5=Owen |first5=Katharine |last6=Oniba |first6=Allan |last7=Sangarie |first7=Musa |last8=Fofanah |first8=James S. |last9=Jalloh |first9=Mohammed B. |last10=Sengeh |first10=Paul |last11=Skrip |first11=Laura |last12=Althouse |first12=Benjamin M. |last13=Hébert-Dufresne |first13=Laurent |date=2020-08 |title=Community engagement in outbreak response: lessons from the 2014-2016 Ebola outbreak in Sierra Leone |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC7445350/ |journal=BMJ global health |volume=5 |issue=8 |pages=e002145 |doi=10.1136/bmjgh-2019-002145 |issn=2059-7908 |pmc=7445350 |pmid=32830128}}</ref> === Healthcare Workers === Healthcare workers were among the most vulnerable groups in the 2014 outbreak, facing exposure due to limited resources and rapidly changing conditions. Facilities across West Africa were unprepared for such an outbreak lacking adequate personal protective equipment, sanitation infrastructure, and consistent training. Healthcare workers were estimated to be 21-32 times more likely to contract Ebola than the general public, with over 800 infected and more than 500 deaths reported.<ref>{{Cite web |title=Health worker Ebola infections in Guinea, Liberia and Sierra Leone |url=https://www.who.int/publications/i/item/WHO-EVD-SDS-REPORT-2015.1 |access-date=2026-04-30 |website=www.who.int |language=en}}</ref> The Center for Disease Control (CDC) identified exposure and insufficient protection as a major driver of infection in healthcare settings.<ref>{{Cite web |title=Update: Ebola Virus Disease Outbreak — West Africa, October 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6343a3.htm |access-date=2026-04-30 |website=www.cdc.gov}}</ref> Local healthcare workers often operated in under-supplied facilities with less consistent training, while international responders had better equipment, training, and evacuation options.<ref name=":5">{{Cite web |title=Ebola: Pushed to the limit and beyond {{!}} MSF |url=https://www.msf.org/ebola-pushed-limit-and-beyond |access-date=2026-04-30 |website=www.msf.org |language=en}}</ref> Workers were crucial in implementing key containment strategies such as isolation protocols, contact tracing, and safe burial practices. Effectively executing these strategies required public trust and cooperation which became a problem during such an outbreak. In many cases mistrust and cultural tension hindered compliance, as treatment centers were feared and traditional practices conflicted with medical guidelines.<ref name=":3">{{Cite journal |last=Abramowitz |first=Sharon |date=2017-10-23 |title=Epidemics (Especially Ebola) |url=https://www.annualreviews.org/content/journals/10.1146/annurev-anthro-102116-041616 |journal=Annual Review of Anthropology |language=en |volume=46 |issue=Volume 46, 2017 |pages=421–445 |doi=10.1146/annurev-anthro-102116-041616 |issn=0084-6570}}</ref> Additionally, healthcare workers faced severe psychological strain, burnout, and social stigma due to being seen as a possible risk of infection.<ref name=":4">{{Cite journal |last=Shultz |first=James M. |last2=Cooper |first2=Janice L. |last3=Baingana |first3=Florence |last4=Oquendo |first4=Maria A. |last5=Espinel |first5=Zelde |last6=Althouse |first6=Benjamin M. |last7=Marcelin |first7=Louis Herns |last8=Towers |first8=Sherry |last9=Espinola |first9=Maria |last10=McCoy |first10=Clyde B. |last11=Mazurik |first11=Laurie |last12=Wainberg |first12=Milton L. |last13=Neria |first13=Yuval |last14=Rechkemmer |first14=Andreas |date=2016-11 |title=The Role of Fear-Related Behaviors in the 2013-2016 West Africa Ebola Virus Disease Outbreak |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC5241909/ |journal=Current Psychiatry Reports |volume=18 |issue=11 |pages=104 |doi=10.1007/s11920-016-0741-y |issn=1535-1645 |pmc=5241909 |pmid=27739026}}</ref> === Local Governments === Guinea’s Ministry of Health declared an Ebola outbreak on March 22, 2014, after tracking 86 suspected cases and 59 deaths.<ref>{{Cite web |last=Doctors Without Borders |date=2014-03-24 |title=Guinea: Priority Is to Isolate Suspected Cases in Ebola Outbreak |url=https://www.doctorswithoutborders.org/latest/guinea-priority-isolate-suspected-cases-ebola-outbreak |url-status=live |access-date=2026-05-01 |website=Doctors Without Borders}}</ref> Early public messaging by the government's National Coordination Cell failed to reach remote communities. Consequently, rural populations in the Forest Region feared foreign aid workers and local officials were intentionally spreading the virus to secure international funding or harvest organs.<ref name=":6">{{Cite web |last=Al Jazeera |date=2014-09-25 |title=Arrests in Guinea over Ebola-related murders |url=https://www.aljazeera.com/news/2014/9/25/arrests-in-guinea-over-ebola-related-murders |url-status=live |access-date=2026-05-01 |website=Al Jazeera}}</ref> This deep mistrust culminated on September 16, 2014, when a government sensitization team arrived in the village of Womey. Angry villagers, armed with machetes and clubs, attacked the delegation, murdering eight people, including local health administrators and three journalists.<ref name=":6" /> In direct response to the massacre, the Guinean government deployed a heavily armed military battalion to occupy the region. Soldiers arrested 27 suspects and enforced strict health mandates through prolonged military surveillance.<ref name=":6" /> In Sierra Leone, the Ministry of Health and Sanitation struggled to contain the virus. To locate hidden patients, the government enforced a strict national lockdown, the "Ose to Ose" campaign, from September 19 to 21, 2014. During this period, 30,000 volunteers searched 1.5 million homes, discovering over 200 hidden bodies and identifying roughly 100 new cases.<ref>{{Cite web |last=Centers for Disease Control and Prevention |date=2015-01-16 |title=Use of a Nationwide Call Center for Ebola Response and Monitoring During a 3-Day House-to-House Campaign — Sierra Leone, September 2014 |url=https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6401a7.htm |url-status=live |access-date=2026-05-01 |website=Morbidity and Mortality Weekly Report}}</ref> On October 17, 2014, the government centralized operations under the military-led National Ebola Response Centre, directed by Defense Minister Major Palo Conteh.<ref>{{Cite web |last=Centers for Disease Control and Prevention |title=In-Countries Responses |url=https://www.cdcmuseum.org/exhibits/show/ebola/global/incountries-response |url-status=live |access-date=2026-05-01 |website=EBOLA - CDC Museum Digital Exhibits}}</ref> However, heavy-handed military enforcement sparked severe backlash. On October 21, 2014, health workers in the town of Koidu attempted to take a blood sample from an elderly woman. A local youth group rioted, claiming the government was kidnapping citizens.<ref name=":7">{{Cite web |last=Ruble |first=Kayla |date=2014-10-22 |title=Ebola Riots in Sierra Leone Highlight Marginalized Youth Population |url=https://www.vice.com/en/article/ebola-riots-in-sierra-leone-highlight-marginalized-youth-population/ |url-status=live |access-date=2026-05-01 |website=Vice}}</ref> The youths burned down buildings and clashed with police. Security forces fired live ammunition into the crowd, killing two protesters, which prompted the government to impose strict district-wide curfews.<ref name=":7" /> Liberia’s Incident Management System issued strict mandates that conflicted with local cultural norms, most notably the August 3, 2014, order mandating the cremation of all dead bodies in Monrovia.<ref name=":8">{{Cite web |last=MacDougall |first=C. |last2=Gladstone |first2=R. |date=2014-08-20 |title=Clash Erupts in Liberian Capital Over Ebola Quarantine |url=https://www.nytimes.com/2014/08/21/world/africa/ebola-outbreak-liberia-quarantine.html |url-status=live |access-date=2026-05-01 |website=New York Times}}</ref> Because traditional burials involve washing and touching the deceased, families rejected the mandate and secretly hid infected bodies in their homes or abandoned them in streets to avoid government collection. Public anger erupted in the densely populated West Point slum. On August 16, 2014, an angry mob raided a local Ebola holding center, shouting that the virus was a government hoax. They looted infected materials and freed 17 patients.<ref name=":8" /> The Armed Forces of Liberia and the Liberia National Police retaliated by physically barricading the neighborhood on August 20, trapping 75,000 residents inside without adequate food, water, or sanitation. Residents protested at the barricades, leading soldiers to fire live ammunition into the crowd, killing a 15-year-old boy named Shakir Kamara and injuring others.<ref name=":8" /> Intense public and international backlash forced the government to abandon the quarantine on August 30, 2014.<ref name=":8" /> === World Health Organization (WHO) === The World Health Organization (WHO) served as the main body responsible for coordinating the international public health response. WHO conducted early field investigations and sent experts to West Africa. It's response was widely criticized for its failure to match the speed and scale of the crisis. Although WHO had known of the outbreak for months, it did not declare Ebola a Public Health Emergency of International Concern until August 2014, after the virus had already spread extensively across Guinea, Liberia, and Sierra Leone. Following this declaration, WHO helped coordinate international response efforts, supported contact tracing, and deployed specialists in epidemiology, laboratory work, risk communication, and social mobilization. <ref name=":1" /> === Médecins Sans Frontières (MSF) === Among the international organizations that responded to the 2014 outbreak, Médecins Sans Frontières (MSF), also known as Doctors Without Borders, played the most significant frontline role. MSF was among the first international organizations to recognize the scale of the outbreak and deployed teams to Guinea, Liberia, and Sierra Leone before most governments and agencies had mobilized. Operating multiple Ebola Treatment Centers across the three countries, MSF ultimately treated approximately one third of all confirmed cases.<ref name=":5" /> MSF's early presence also made them one of the first organizations to publicly warn that the outbreak was out of control, repeatedly calling on the international community to scale up its response months before the WHO declared a Public Health Emergency of International Concern in August 2014.<ref name=":1" /> This tension between MSF's frontline assessment and the pace of the formal international response highlighted a broader gap between organizations operating on the ground and those coordinating from a distance. == Further Work == This chapter could be extended by examining the role of media in shaping the global public perception of the outbreak. Additional research on the long-term aftermath of the outbreak, including whether institutional trust recovered in Guinea, Liberia, and Sierra Leone, remains an important area for potential analysis. == References == <references /> 966veov8hn9rikqxkfflujw0f12dw40 0 482927 4634191 4633993 2026-05-04T22:13:02Z Kittycataclysm 3371989 Kittycataclysm moved page [[Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]] to [[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]] without leaving a redirect: correcting namespace 4633993 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. === Drawing up a Solution: Saumya Pandya Thakkar === In response to this pressing public safety challenge, local artist Saumya Pandya Thakkar, alongside her mother Shakuntala Pandya, introduced a low-tech, yet effective sociological solution: 3D zebra crossings. Moving away from expensive infrastructural overhauls, the duo utilized optical illusions painted directly onto the asphalt in accident-prone areas. To an approaching driver, these crosswalks appear as raised, physical blockades, instinctively forcing them to ease off the accelerator. Crucially, the illusion naturally dissipates as the vehicle gets closer, safely preventing "panic braking." Studies by the Central Road Research Institute (CRRI) found that this simple psychological deterrent successfully reduced vehicle speeds by up to 20.3%, with heavier vehicles showing the greatest response due to their elevated vantage points<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms |access-date=2026-05-03 |issn=0971-8257}}</ref>. Through this creative intervention, Thakkar and Pandya transformed a coat of paint into a lifeline for the pedestrians of Ahmedabad. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref>{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref>{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref>{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref>{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref>{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == References == <references responsive="" /> 5pyzqj4y1pfc0m0gb7lp9jnjaa5hjdi 4634200 4634191 2026-05-04T23:46:55Z ~2026-26979-78 3581293 /* Drawing up a Solution: Saumya Pandya Thakkar */ 4634200 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. == Existing Solutions == Efforts to improve road safety and pedestrian conditions in Ahmedabad span three broad categories: traffic calming measures, pedestrian infrastructure, and traffic flow optimization. Each approach addresses a distinct dimension of the city's road safety crisis, and together they reflect both the progress made and the gaps that remain. === Traffic Calming === Traffic calming encompasses physical and visual measures designed to reduce vehicle speeds without requiring large-scale infrastructure investment. The most prominent local innovation is the 3D zebra crossing, pioneered in Ahmedabad by artists Saumya Pandya Thakkar and Shakuntala Pandya. By painting optical illusions directly onto the asphalt, the crossings create the appearance of a raised blockade, prompting drivers to slow down. Research by the Central Road Research Institute (CRRI) confirmed speed reductions of 1.6% to 20.3%, with the greatest effect observed among heavy commercial vehicles due to their elevated vantage points<sup>[1]</sup>. The concept has since been adopted in cities around the world, with results broadly consistent with those observed in Ahmedabad. In New Delhi, authorities reported that average vehicle speeds at 3D crosswalk locations dropped from 50 km/h to 30 km/h following installation<sup>[2]</sup>. In Europe, the fishing town of Ísafjörður, Iceland became the first to deploy the design in 2017, after its environmental commissioner sought alternatives to traditional speed bumps, which studies had linked to increased air pollution and driver complaints about vehicle damage<sup>[3]</sup>. In Kansas City, Kansas, a 3D crosswalk was installed near a school in a residential neighborhood prone to speeding, and residents reported that the design helped slow drivers, though they noted that additional traffic calming measures were still needed<sup>[1]</sup>. A broader academic evaluation of decorative pavement markings at pedestrian crosswalks found that speed reductions ranged from 1.89 km/h to 4.41 km/h across twelve study sites, with vehicle-pedestrian crashes reduced by approximately 25% <sup>[4]</sup>. One recurring limitation noted across deployments is durability: the Kansas City crosswalk faded significantly within two years, and the city indicated it would only repaint if the design proved effective at slowing traffic<sup>[5]</sup>. This echoes the broader concern that the novelty effect of optical illusion markings may diminish as local drivers habituate to them over time. Complementing painted interventions, Ahmedabad installed 339 speed humps across the city in just 17 months, a rapid and low-cost deployment that reflects the city's broader prioritization of accessible safety measures. However, speed humps carry their own drawbacks: they can impede emergency vehicles, damage low-clearance vehicles if poorly designed, and face political resistance when proposed on high-capacity arterial roads. === Pedestrian Infrastructure === Ahmedabad's pedestrian infrastructure reveals a stark gap between need and provision. As of 2026, only 731 of the city's 2,634 km of roads have sidewalks, leaving 72% of the network without footpaths<sup>[6]</sup>. In response, the Ahmedabad Municipal Corporation (AMC) allocated Rs. 20 crore to repair over 100 traffic intersections<sup>[7]</sup>. Five foot overbridges (FOBs) currently exist, providing grade-separated crossings that fully eliminate pedestrian-vehicle conflict on high-speed corridors. An additional six FOBs are planned as part of the SP Ring Road upgrade<sup>[8]</sup>. For wide arterial roads where full-grade separation is not feasible, pedestrian refuge islands offer a proven middle-ground solution. Research by the U.S. Federal Highway Administration found that installing raised refuge islands at marked crosswalks reduced pedestrian crashes by 46%, and by 39% at unmarked locations<sup>[9]</sup>. By allowing pedestrians to cross one direction of traffic at a time, refuge islands are especially well-suited to Ahmedabad's four-to-six lane arterials, where crossing the full road width in a single phase poses significant risk<sup>[6]</sup>. === Traffic Flow Optimization === Beyond speed reduction, managing how traffic moves through and around Ahmedabad is critical to reducing conflict points between vehicles and pedestrians. Signal coordination, commonly referred to as a green wave, times traffic lights so that drivers traveling at the posted speed limit encounter a cascade of green signals along a corridor. Studies show this approach reduces CO2, NOx, and PM10 emissions while cutting unnecessary stops that contribute to erratic and aggressive driving behavior<sup>[10]</sup>. Crucially, it requires no new construction, only signal reprogramming. At a larger scale, Ahmedabad has pursued traffic separation through flyovers, underpasses, and ring roads to divert through-traffic away from dense urban areas. Between 2010 and 2026, 46 such structures were built, with 25 more planned over the next decade<sup>[11]</sup>. The 76 km Sardar Patel Ring Road, currently being upgraded to six lanes, is designed to reduce the volume of vehicles cutting through the city core<sup>[8]</sup>. While these infrastructure investments address congestion on major corridors, their impact on local pedestrian safety on the side streets and arterials that feed into them remains dependent on complementary measures such as sidewalk expansion and safer crossing design. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref>{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref>{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref>{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref>{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref>{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == References == <references responsive="" /> amswrldb63ak139i4nsdvj2ydc0glay 4634201 4634200 2026-05-05T00:19:08Z ~2026-26979-78 3581293 4634201 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. == Existing Solutions == Efforts to improve road safety and pedestrian conditions in Ahmedabad span three broad categories: traffic calming measures, pedestrian infrastructure, and traffic flow optimization. Each approach addresses a distinct dimension of the city's road safety crisis, and together they reflect both the progress made and the gaps that remain. === Traffic Calming === Traffic calming encompasses physical and visual measures designed to reduce vehicle speeds without requiring large-scale infrastructure investment. The most prominent local innovation is the 3D zebra crossing, pioneered in Ahmedabad by artists Saumya Pandya Thakkar and Shakuntala Pandya. By painting optical illusions directly onto the asphalt, the crossings create the appearance of a raised blockade, prompting drivers to slow down. Research by the Central Road Research Institute (CRRI) confirmed speed reductions of 1.6% to 20.3%, with the greatest effect observed among heavy commercial vehicles due to their elevated vantage points <ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms?utm_source=chatgpt.com |access-date=2026-05-04 |issn=0971-8257}}</ref>. The concept has since been adopted in cities around the world, with results broadly consistent with those observed in Ahmedabad. In New Delhi, authorities reported that average vehicle speeds at 3D crosswalk locations dropped from 50 km/h to 30 km/h following installation <ref>{{Cite web |last=Warburton |first=Gill |date=2017-09-28 |title=Could 3D zebra crossings help drivers to slow down? |url=https://flexed.co.uk/blog/3d-zebra-crossings-help-drivers-slow/ |access-date=2026-05-05 |website=Flexed |language=en-US}}</ref>. In Europe, the fishing town of Ísafjörður, Iceland became the first to deploy the design in 2017, after its environmental commissioner sought alternatives to traditional speed bumps, which studies had linked to increased air pollution and driver complaints about vehicle damage <ref>{{Cite web |date=2021-09-30 |title=Managing urban traffic: 3D zebra crossings spread across Europe - Eurocities |url=https://eurocities.eu/stories/managing-urban-traffic-3d-zebra-crossings-spread-across-europe/ |access-date=2026-05-05 |website=eurocities.eu |language=en-GB}}</ref>. In Kansas City, Kansas, a 3D crosswalk was installed near a school in a residential neighborhood prone to speeding, and residents reported that the design helped slow drivers, though they noted that additional traffic calming measures were still needed <ref>{{Cite web |last=Betts |first=Jordan |date=2019-06-26 |title=How is the metro's first 3D crosswalk working? Neighbors say it helps some |url=https://www.kshb.com/news/local-news/kcks-3d-crosswalk-credited-for-reducing-traffic |access-date=2026-05-05 |website=KSHB 41 Kansas City News |language=en}}</ref>. A broader academic evaluation of decorative pavement markings at pedestrian crosswalks found that speed reductions ranged from 1.89 km/h to 4.41 km/h across twelve study sites, with vehicle-pedestrian crashes reduced by approximately 25% . One recurring limitation noted across deployments is durability: the Kansas City crosswalk faded significantly within two years, and the city indicated it would only repaint if the design proved effective at slowing traffic<sup>[5]</sup>. This echoes the broader concern that the novelty effect of optical illusion markings may diminish as local drivers habituate to them over time. Complementing painted interventions, Ahmedabad installed 339 speed humps across the city in just 17 months, a rapid and low-cost deployment that reflects the city's broader prioritization of accessible safety measures. However, speed humps carry their own drawbacks: they can impede emergency vehicles, damage low-clearance vehicles if poorly designed, and face political resistance when proposed on high-capacity arterial roads. === Pedestrian Infrastructure === Ahmedabad's pedestrian infrastructure reveals a stark gap between need and provision. As of 2026, only 731 of the city's 2,634 km of roads have sidewalks, leaving 72% of the network without footpaths<sup>[6]</sup>. In response, the Ahmedabad Municipal Corporation (AMC) allocated Rs. 20 crore to repair over 100 traffic intersections<sup>[7]</sup>. Five foot overbridges (FOBs) currently exist, providing grade-separated crossings that fully eliminate pedestrian-vehicle conflict on high-speed corridors. An additional six FOBs are planned as part of the SP Ring Road upgrade<sup>[8]</sup>. For wide arterial roads where full-grade separation is not feasible, pedestrian refuge islands offer a proven middle-ground solution. Research by the U.S. Federal Highway Administration found that installing raised refuge islands at marked crosswalks reduced pedestrian crashes by 46%, and by 39% at unmarked locations<sup>[9]</sup>. By allowing pedestrians to cross one direction of traffic at a time, refuge islands are especially well-suited to Ahmedabad's four-to-six lane arterials, where crossing the full road width in a single phase poses significant risk<sup>[6]</sup>. === Traffic Flow Optimization === Beyond speed reduction, managing how traffic moves through and around Ahmedabad is critical to reducing conflict points between vehicles and pedestrians. Signal coordination, commonly referred to as a green wave, times traffic lights so that drivers traveling at the posted speed limit encounter a cascade of green signals along a corridor. Studies show this approach reduces CO2, NOx, and PM10 emissions while cutting unnecessary stops that contribute to erratic and aggressive driving behavior<sup>[10]</sup>. Crucially, it requires no new construction, only signal reprogramming. At a larger scale, Ahmedabad has pursued traffic separation through flyovers, underpasses, and ring roads to divert through-traffic away from dense urban areas. Between 2010 and 2026, 46 such structures were built, with 25 more planned over the next decade<sup>[11]</sup>. The 76 km Sardar Patel Ring Road, currently being upgraded to six lanes, is designed to reduce the volume of vehicles cutting through the city core<sup>[8]</sup>. While these infrastructure investments address congestion on major corridors, their impact on local pedestrian safety on the side streets and arterials that feed into them remains dependent on complementary measures such as sidewalk expansion and safer crossing design. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref>{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref>{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref>{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref>{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref>{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == References == <references responsive="" /> q1ybnujhweb3r3epj4fjgrc6p91edfk 4634202 4634201 2026-05-05T00:45:40Z Yqj3km 3579825 Moved Existing Solutions to the correct section 4634202 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref>{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref>{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref>{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref>{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref>{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == Existing Solutions == Efforts to improve road safety and pedestrian conditions in Ahmedabad span three broad categories: traffic calming measures, pedestrian infrastructure, and traffic flow optimization. Each approach addresses a distinct dimension of the city's road safety crisis, and together they reflect both the progress made and the gaps that remain. === Traffic Calming === Traffic calming encompasses physical and visual measures designed to reduce vehicle speeds without requiring large-scale infrastructure investment. The most prominent local innovation is the 3D zebra crossing, pioneered in Ahmedabad by artists Saumya Pandya Thakkar and Shakuntala Pandya. By painting optical illusions directly onto the asphalt, the crossings create the appearance of a raised blockade, prompting drivers to slow down. Research by the Central Road Research Institute (CRRI) confirmed speed reductions of 1.6% to 20.3%, with the greatest effect observed among heavy commercial vehicles due to their elevated vantage points <ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms?utm_source=chatgpt.com |access-date=2026-05-04 |issn=0971-8257}}</ref>. The concept has since been adopted in cities around the world, with results broadly consistent with those observed in Ahmedabad. In New Delhi, authorities reported that average vehicle speeds at 3D crosswalk locations dropped from 50 km/h to 30 km/h following installation <ref>{{Cite web |last=Warburton |first=Gill |date=2017-09-28 |title=Could 3D zebra crossings help drivers to slow down? |url=https://flexed.co.uk/blog/3d-zebra-crossings-help-drivers-slow/ |access-date=2026-05-05 |website=Flexed |language=en-US}}</ref>. In Europe, the fishing town of Ísafjörður, Iceland became the first to deploy the design in 2017, after its environmental commissioner sought alternatives to traditional speed bumps, which studies had linked to increased air pollution and driver complaints about vehicle damage <ref>{{Cite web |date=2021-09-30 |title=Managing urban traffic: 3D zebra crossings spread across Europe - Eurocities |url=https://eurocities.eu/stories/managing-urban-traffic-3d-zebra-crossings-spread-across-europe/ |access-date=2026-05-05 |website=eurocities.eu |language=en-GB}}</ref>. In Kansas City, Kansas, a 3D crosswalk was installed near a school in a residential neighborhood prone to speeding, and residents reported that the design helped slow drivers, though they noted that additional traffic calming measures were still needed <ref>{{Cite web |last=Betts |first=Jordan |date=2019-06-26 |title=How is the metro's first 3D crosswalk working? Neighbors say it helps some |url=https://www.kshb.com/news/local-news/kcks-3d-crosswalk-credited-for-reducing-traffic |access-date=2026-05-05 |website=KSHB 41 Kansas City News |language=en}}</ref>. A broader academic evaluation of decorative pavement markings at pedestrian crosswalks found that speed reductions ranged from 1.89 km/h to 4.41 km/h across twelve study sites, with vehicle-pedestrian crashes reduced by approximately 25% . One recurring limitation noted across deployments is durability: the Kansas City crosswalk faded significantly within two years, and the city indicated it would only repaint if the design proved effective at slowing traffic<sup>[5]</sup>. This echoes the broader concern that the novelty effect of optical illusion markings may diminish as local drivers habituate to them over time. Complementing painted interventions, Ahmedabad installed 339 speed humps across the city in just 17 months, a rapid and low-cost deployment that reflects the city's broader prioritization of accessible safety measures. However, speed humps carry their own drawbacks: they can impede emergency vehicles, damage low-clearance vehicles if poorly designed, and face political resistance when proposed on high-capacity arterial roads. === Pedestrian Infrastructure === Ahmedabad's pedestrian infrastructure reveals a stark gap between need and provision. As of 2026, only 731 of the city's 2,634 km of roads have sidewalks, leaving 72% of the network without footpaths<sup>[6]</sup>. In response, the Ahmedabad Municipal Corporation (AMC) allocated Rs. 20 crore to repair over 100 traffic intersections<sup>[7]</sup>. Five foot overbridges (FOBs) currently exist, providing grade-separated crossings that fully eliminate pedestrian-vehicle conflict on high-speed corridors. An additional six FOBs are planned as part of the SP Ring Road upgrade<sup>[8]</sup>. For wide arterial roads where full-grade separation is not feasible, pedestrian refuge islands offer a proven middle-ground solution. Research by the U.S. Federal Highway Administration found that installing raised refuge islands at marked crosswalks reduced pedestrian crashes by 46%, and by 39% at unmarked locations<sup>[9]</sup>. By allowing pedestrians to cross one direction of traffic at a time, refuge islands are especially well-suited to Ahmedabad's four-to-six lane arterials, where crossing the full road width in a single phase poses significant risk<sup>[6]</sup>. === Traffic Flow Optimization === Beyond speed reduction, managing how traffic moves through and around Ahmedabad is critical to reducing conflict points between vehicles and pedestrians. Signal coordination, commonly referred to as a green wave, times traffic lights so that drivers traveling at the posted speed limit encounter a cascade of green signals along a corridor. Studies show this approach reduces CO2, NOx, and PM10 emissions while cutting unnecessary stops that contribute to erratic and aggressive driving behavior<sup>[10]</sup>. Crucially, it requires no new construction, only signal reprogramming. At a larger scale, Ahmedabad has pursued traffic separation through flyovers, underpasses, and ring roads to divert through-traffic away from dense urban areas. Between 2010 and 2026, 46 such structures were built, with 25 more planned over the next decade<sup>[11]</sup>. The 76 km Sardar Patel Ring Road, currently being upgraded to six lanes, is designed to reduce the volume of vehicles cutting through the city core<sup>[8]</sup>. While these infrastructure investments address congestion on major corridors, their impact on local pedestrian safety on the side streets and arterials that feed into them remains dependent on complementary measures such as sidewalk expansion and safer crossing design. == References == <references responsive="" /> a4hj5mtcg930o6uc8u4kylha4kzl0pf 4634203 4634202 2026-05-05T00:49:03Z Yqj3km 3579825 4634203 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref name=":0">{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref name=":1">{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref name=":2">{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref name=":3">{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref>{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref>{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == Existing Solutions == Efforts to improve road safety and pedestrian conditions in Ahmedabad span three broad categories: traffic calming measures, pedestrian infrastructure, and traffic flow optimization. Each approach addresses a distinct dimension of the city's road safety crisis, and together they reflect both the progress made and the gaps that remain. === Traffic Calming === Traffic calming encompasses physical and visual measures designed to reduce vehicle speeds without requiring large-scale infrastructure investment. The most prominent local innovation is the 3D zebra crossing, pioneered in Ahmedabad by artists Saumya Pandya Thakkar and Shakuntala Pandya. By painting optical illusions directly onto the asphalt, the crossings create the appearance of a raised blockade, prompting drivers to slow down. Research by the Central Road Research Institute (CRRI) confirmed speed reductions of 1.6% to 20.3%, with the greatest effect observed among heavy commercial vehicles due to their elevated vantage points <ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms?utm_source=chatgpt.com |access-date=2026-05-04 |issn=0971-8257}}</ref>. The concept has since been adopted in cities around the world, with results broadly consistent with those observed in Ahmedabad. In New Delhi, authorities reported that average vehicle speeds at 3D crosswalk locations dropped from 50 km/h to 30 km/h following installation <ref>{{Cite web |last=Warburton |first=Gill |date=2017-09-28 |title=Could 3D zebra crossings help drivers to slow down? |url=https://flexed.co.uk/blog/3d-zebra-crossings-help-drivers-slow/ |access-date=2026-05-05 |website=Flexed |language=en-US}}</ref>. In Europe, the fishing town of Ísafjörður, Iceland became the first to deploy the design in 2017, after its environmental commissioner sought alternatives to traditional speed bumps, which studies had linked to increased air pollution and driver complaints about vehicle damage <ref>{{Cite web |date=2021-09-30 |title=Managing urban traffic: 3D zebra crossings spread across Europe - Eurocities |url=https://eurocities.eu/stories/managing-urban-traffic-3d-zebra-crossings-spread-across-europe/ |access-date=2026-05-05 |website=eurocities.eu |language=en-GB}}</ref>. In Kansas City, Kansas, a 3D crosswalk was installed near a school in a residential neighborhood prone to speeding, and residents reported that the design helped slow drivers, though they noted that additional traffic calming measures were still needed <ref>{{Cite web |last=Betts |first=Jordan |date=2019-06-26 |title=How is the metro's first 3D crosswalk working? Neighbors say it helps some |url=https://www.kshb.com/news/local-news/kcks-3d-crosswalk-credited-for-reducing-traffic |access-date=2026-05-05 |website=KSHB 41 Kansas City News |language=en}}</ref>. A broader academic evaluation of decorative pavement markings at pedestrian crosswalks found that speed reductions ranged from 1.89 km/h to 4.41 km/h across twelve study sites, with vehicle-pedestrian crashes reduced by approximately 25% . One recurring limitation noted across deployments is durability: the Kansas City crosswalk faded significantly within two years, and the city indicated it would only repaint if the design proved effective at slowing traffic<sup>[5]</sup>. This echoes the broader concern that the novelty effect of optical illusion markings may diminish as local drivers habituate to them over time. Complementing painted interventions, Ahmedabad installed 339 speed humps across the city in just 17 months, a rapid and low-cost deployment that reflects the city's broader prioritization of accessible safety measures. However, speed humps carry their own drawbacks: they can impede emergency vehicles, damage low-clearance vehicles if poorly designed, and face political resistance when proposed on high-capacity arterial roads. === Pedestrian Infrastructure === Ahmedabad's pedestrian infrastructure reveals a stark gap between need and provision. As of 2026, only 731 of the city's 2,634 km of roads have sidewalks, leaving 72% of the network without footpaths<ref name=":0" />. In response, the Ahmedabad Municipal Corporation (AMC) allocated Rs. 20 crore to repair over 100 traffic intersections<ref name=":1" />. Five foot overbridges (FOBs) currently exist, providing grade-separated crossings that fully eliminate pedestrian-vehicle conflict on high-speed corridors. An additional six FOBs are planned as part of the SP Ring Road upgrade<ref name=":2" />. For wide arterial roads where full-grade separation is not feasible, pedestrian refuge islands offer a proven middle-ground solution. Research by the U.S. Federal Highway Administration found that installing raised refuge islands at marked crosswalks reduced pedestrian crashes by 46%, and by 39% at unmarked locations<ref name=":3" />. By allowing pedestrians to cross one direction of traffic at a time, refuge islands are especially well-suited to Ahmedabad's four-to-six lane arterials, where crossing the full road width in a single phase poses significant risk<ref name=":0" />. === Traffic Flow Optimization === Beyond speed reduction, managing how traffic moves through and around Ahmedabad is critical to reducing conflict points between vehicles and pedestrians. Signal coordination, commonly referred to as a green wave, times traffic lights so that drivers traveling at the posted speed limit encounter a cascade of green signals along a corridor. Studies show this approach reduces CO2, NOx, and PM10 emissions while cutting unnecessary stops that contribute to erratic and aggressive driving behavior. Crucially, it requires no new construction, only signal reprogramming. At a larger scale, Ahmedabad has pursued traffic separation through flyovers, underpasses, and ring roads to divert through-traffic away from dense urban areas. Between 2010 and 2026, 46 such structures were built, with 25 more planned over the next decade<sup>[11]</sup>. The 76 km Sardar Patel Ring Road, currently being upgraded to six lanes, is designed to reduce the volume of vehicles cutting through the city core<sup>[8]</sup>. While these infrastructure investments address congestion on major corridors, their impact on local pedestrian safety on the side streets and arterials that feed into them remains dependent on complementary measures such as sidewalk expansion and safer crossing design. == References == <references responsive="" /> a1q6fk7jncsarny6hghi6gqprouexyk 4634210 4634203 2026-05-05T01:50:08Z ~2026-27120-19 3581258 /* References */ 4634210 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref name=":0">{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref name=":1">{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref name=":2">{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref name=":3">{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref>{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref>{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == Existing Solutions == Efforts to improve road safety and pedestrian conditions in Ahmedabad span three broad categories: traffic calming measures, pedestrian infrastructure, and traffic flow optimization. Each approach addresses a distinct dimension of the city's road safety crisis, and together they reflect both the progress made and the gaps that remain. === Traffic Calming === Traffic calming encompasses physical and visual measures designed to reduce vehicle speeds without requiring large-scale infrastructure investment. The most prominent local innovation is the 3D zebra crossing, pioneered in Ahmedabad by artists Saumya Pandya Thakkar and Shakuntala Pandya. By painting optical illusions directly onto the asphalt, the crossings create the appearance of a raised blockade, prompting drivers to slow down. Research by the Central Road Research Institute (CRRI) confirmed speed reductions of 1.6% to 20.3%, with the greatest effect observed among heavy commercial vehicles due to their elevated vantage points<ref name=":4" />. The concept has since been adopted in cities around the world, with results broadly consistent with those observed in Ahmedabad. In New Delhi, authorities reported that average vehicle speeds at 3D crosswalk locations dropped from 50 km/h to 30 km/h following installation <ref>{{Cite web |last=Betts |first=Jordan |date=2019-06-26 |title="How is the metro's first 3D crosswalk working? Neighbors say it helps some" |url=https://www.kshb.com/news/local-news/kcks-3d-crosswalk-credited-for-reducing-traffic |access-date=2026-05-04 |website=KSHB 41 Kansas City News |language=}}</ref>. In Europe, the fishing town of Ísafjörður, Iceland became the first to deploy the design in 2017, after its environmental commissioner sought alternatives to traditional speed bumps, which studies had linked to increased air pollution and driver complaints about vehicle damage <ref name=":4">{{Cite web |date=2016-09-18 |title="The First 3D Zebra Crossing Was a Rousing Success & Now There Are Plans For 40 More!" |url=https://so.city/delhi/article/the-first-3d-zebra-crossing-was-a-rousing-success-now-there-are-plans-for-40-more |access-date=2026-05-04 |website=So City |language=}}</ref>. In Kansas City, Kansas, a 3D crosswalk was installed near a school in a residential neighborhood prone to speeding, and residents reported that the design helped slow drivers, though they noted that additional traffic calming measures were still needed <ref>{{Cite web |last= |first= |date=2021-09-30 |title=Managing urban traffic: 3D zebra crossings spread across Europe - Eurocities |url=https://eurocities.eu/stories/managing-urban-traffic-3d-zebra-crossings-spread-across-europe/ |access-date=2026-05-04 |website=eurocities.eu |language=}}</ref>. A broader academic evaluation of decorative pavement markings at pedestrian crosswalks found that speed reductions ranged from 1.89 km/h to 4.41 km/h across twelve study sites, with vehicle-pedestrian crashes reduced by approximately 25% . One recurring limitation noted across deployments is durability: the Kansas City crosswalk faded significantly within two years, and the city indicated it would only repaint if the design proved effective at slowing traffic<sup>[5]</sup>. This echoes the broader concern that the novelty effect of optical illusion markings may diminish as local drivers habituate to them over time. Complementing painted interventions, Ahmedabad installed 339 speed humps across the city in just 17 months, a rapid and low-cost deployment that reflects the city's broader prioritization of accessible safety measures. However, speed humps carry their own drawbacks: they can impede emergency vehicles, damage low-clearance vehicles if poorly designed, and face political resistance when proposed on high-capacity arterial roads. === Pedestrian Infrastructure === Ahmedabad's pedestrian infrastructure reveals a stark gap between need and provision. As of 2026, only 731 of the city's 2,634 km of roads have sidewalks, leaving 72% of the network without footpaths<ref name=":0" />. In response, the Ahmedabad Municipal Corporation (AMC) allocated Rs. 20 crore to repair over 100 traffic intersections<ref name=":1" />. Five foot overbridges (FOBs) currently exist, providing grade-separated crossings that fully eliminate pedestrian-vehicle conflict on high-speed corridors. An additional six FOBs are planned as part of the SP Ring Road upgrade<ref name=":2" />. For wide arterial roads where full-grade separation is not feasible, pedestrian refuge islands offer a proven middle-ground solution. Research by the U.S. Federal Highway Administration found that installing raised refuge islands at marked crosswalks reduced pedestrian crashes by 46%, and by 39% at unmarked locations<ref name=":3" />. By allowing pedestrians to cross one direction of traffic at a time, refuge islands are especially well-suited to Ahmedabad's four-to-six lane arterials, where crossing the full road width in a single phase poses significant risk<ref name=":0" />. === Traffic Flow Optimization === Beyond speed reduction, managing how traffic moves through and around Ahmedabad is critical to reducing conflict points between vehicles and pedestrians. Signal coordination, commonly referred to as a green wave, times traffic lights so that drivers traveling at the posted speed limit encounter a cascade of green signals along a corridor. Studies show this approach reduces CO2, NOx, and PM10 emissions while cutting unnecessary stops that contribute to erratic and aggressive driving behavior. Crucially, it requires no new construction, only signal reprogramming. At a larger scale, Ahmedabad has pursued traffic separation through flyovers, underpasses, and ring roads to divert through-traffic away from dense urban areas. Between 2010 and 2026, 46 such structures were built, with 25 more planned over the next decade<sup>[11]</sup>. The 76 km Sardar Patel Ring Road, currently being upgraded to six lanes, is designed to reduce the volume of vehicles cutting through the city core<sup>[8]</sup>. While these infrastructure investments address congestion on major corridors, their impact on local pedestrian safety on the side streets and arterials that feed into them remains dependent on complementary measures such as sidewalk expansion and safer crossing design. == References == <references responsive="" /> 4o6pl7p9k2v0iqsxfoyz17d8e09oib2 4634211 4634210 2026-05-05T02:00:18Z ~2026-27120-19 3581258 fixed citations on pedestrian infrastructure 4634211 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref name=":0">{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref name=":1">{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref name=":2">{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref name=":3">{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref>{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref name=":5">{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref name=":6">{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == Existing Solutions == Efforts to improve road safety and pedestrian conditions in Ahmedabad span three broad categories: traffic calming measures, pedestrian infrastructure, and traffic flow optimization. Each approach addresses a distinct dimension of the city's road safety crisis, and together they reflect both the progress made and the gaps that remain. === Traffic Calming === Traffic calming encompasses physical and visual measures designed to reduce vehicle speeds without requiring large-scale infrastructure investment. The most prominent local innovation is the 3D zebra crossing, pioneered in Ahmedabad by artists Saumya Pandya Thakkar and Shakuntala Pandya. By painting optical illusions directly onto the asphalt, the crossings create the appearance of a raised blockade, prompting drivers to slow down. Research by the Central Road Research Institute (CRRI) confirmed speed reductions of 1.6% to 20.3%, with the greatest effect observed among heavy commercial vehicles due to their elevated vantage points<ref name=":7">{{Cite web |last=Betts |first=Jordan |date=2019-06-26 |title="How is the metro's first 3D crosswalk working? Neighbors say it helps some" |url=https://www.kshb.com/news/local-news/kcks-3d-crosswalk-credited-for-reducing-traffic |access-date=2026-05-04 |website=KSHB 41 Kansas City News |language=}}</ref>. The concept has since been adopted in cities around the world, with results broadly consistent with those observed in Ahmedabad. In New Delhi, authorities reported that average vehicle speeds at 3D crosswalk locations dropped from 50 km/h to 30 km/h following installation<ref name=":4">{{Cite web |date=2016-09-18 |title="The First 3D Zebra Crossing Was a Rousing Success & Now There Are Plans For 40 More!" |url=https://so.city/delhi/article/the-first-3d-zebra-crossing-was-a-rousing-success-now-there-are-plans-for-40-more |access-date=2026-05-04 |website=So City |language=}}</ref>. In Europe, the fishing town of Ísafjörður, Iceland became the first to deploy the design in 2017, after its environmental commissioner sought alternatives to traditional speed bumps, which studies had linked to increased air pollution and driver complaints about vehicle damage<ref>{{Cite web |last= |first= |date=2021-09-30 |title=Managing urban traffic: 3D zebra crossings spread across Europe - Eurocities |url=https://eurocities.eu/stories/managing-urban-traffic-3d-zebra-crossings-spread-across-europe/ |access-date=2026-05-04 |website=eurocities.eu |language=}}</ref>. In Kansas City, Kansas, a 3D crosswalk was installed near a school in a residential neighborhood prone to speeding, and residents reported that the design helped slow drivers, though they noted that additional traffic calming measures were still needed<ref name=":7" />. A broader academic evaluation of decorative pavement markings at pedestrian crosswalks found that speed reductions ranged from 1.89 km/h to 4.41 km/h across twelve study sites, with vehicle-pedestrian crashes reduced by approximately 25%<ref>{{Cite journal |last=Rebelo |first=Francisco |title=Evaluation of 3D Crosswalks Design |url=https://www.researchgate.net/publication/325961246_Evaluation_of_3D_Crosswalks_Design |journal=ResearchGate}}</ref>. One recurring limitation noted across deployments is durability: the Kansas City crosswalk faded significantly within two years, and the city indicated it would only repaint if the design proved effective at slowing traffic<ref>{{Cite web |title=Kansas City, KS - 3D Crosswalk (Gone) |url=https://www.roadsideamerica.com/tip/64102 |access-date=2026-05-05 |website=RoadsideAmerica.com |language=en}}</ref>. This echoes the broader concern that the novelty effect of optical illusion markings may diminish as local drivers habituate to them over time. Complementing painted interventions, Ahmedabad installed 339 speed humps across the city in just 17 months, a rapid and low-cost deployment that reflects the city's broader prioritization of accessible safety measures. However, speed humps carry their own drawbacks: they can impede emergency vehicles, damage low-clearance vehicles if poorly designed, and face political resistance when proposed on high-capacity arterial roads. === Pedestrian Infrastructure === Ahmedabad's pedestrian infrastructure reveals a stark gap between need and provision. As of 2026, only 731 of the city's 2,634 km of roads have sidewalks, leaving 72% of the network without footpaths<ref name=":8">{{Cite news |title=Medians and Pedestrian Refuge Islands in Urban and Suburban Areas |work=U.S. Department of Transportation Federal Highway Administration |url=https://highways.dot.gov/safety/proven-safety-countermeasures/medians-and-pedestrian-refuge-islands-urban-and-suburban-areas}}</ref>. In response, the Ahmedabad Municipal Corporation (AMC) allocated Rs. 20 crore to repair over 100 traffic intersections<ref name=":6" />. Five foot overbridges (FOBs) currently exist, providing grade-separated crossings that fully eliminate pedestrian-vehicle conflict on high-speed corridors. An additional six FOBs are planned as part of the SP Ring Road upgrade<ref name=":5" />. For wide arterial roads where full-grade separation is not feasible, pedestrian refuge islands offer a proven middle-ground solution. Research by the U.S. Federal Highway Administration found that installing raised refuge islands at marked crosswalks reduced pedestrian crashes by 46%, and by 39% at unmarked locations<ref>{{Cite web |date=2010-01-01 |title=Safety Benefits of Raised Medians and Pedestrian Refuge Areas |url=https://rosap.ntl.bts.gov/ |access-date=2026-05-05 |website=rosap.ntl.bts.gov |language=English}}</ref>. By allowing pedestrians to cross one direction of traffic at a time, refuge islands are especially well-suited to Ahmedabad's four-to-six lane arterials, where crossing the full road width in a single phase poses significant risk<ref name=":8" />. === Traffic Flow Optimization === Beyond speed reduction, managing how traffic moves through and around Ahmedabad is critical to reducing conflict points between vehicles and pedestrians. Signal coordination, commonly referred to as a green wave, times traffic lights so that drivers traveling at the posted speed limit encounter a cascade of green signals along a corridor. Studies show this approach reduces CO2, NOx, and PM10 emissions while cutting unnecessary stops that contribute to erratic and aggressive driving behavior. Crucially, it requires no new construction, only signal reprogramming. At a larger scale, Ahmedabad has pursued traffic separation through flyovers, underpasses, and ring roads to divert through-traffic away from dense urban areas. Between 2010 and 2026, 46 such structures were built, with 25 more planned over the next decade<sup>[11]</sup>. The 76 km Sardar Patel Ring Road, currently being upgraded to six lanes, is designed to reduce the volume of vehicles cutting through the city core<sup>[8]</sup>. While these infrastructure investments address congestion on major corridors, their impact on local pedestrian safety on the side streets and arterials that feed into them remains dependent on complementary measures such as sidewalk expansion and safer crossing design. == References == <references responsive="" /> jckq9lpj88bj9e6xn67is6hjebbhk3s 4634212 4634211 2026-05-05T02:02:17Z ~2026-27120-19 3581258 Traffic Flow Optimization fixed citations 4634212 wikitext text/x-wiki == Background == === The City of Ahmedabad === As the largest city in the Indian state of Gujarat, Ahmedabad boasts a bustling urban population of roughly 9.5 million but grapples with severe traffic congestion and a mounting road safety crisis<ref>{{Cite web |date=2026-05-01 |title=Ahmedabad Population 2026 |url=https://worldpopulationreview.com/cities/india/ahmedabad |access-date=2026-05-03 |website=World Population Review |language=en}}</ref>. With a heavy daily ridership dominated by buses and private vehicles, the city’s dense roadways have become increasingly hazardous for pedestrians. In 2023 alone, Ahmedabad recorded 535 fatal crashes, with speeding identified as the primary culprit<ref>{{Cite web |last=Kamdar |first=Vatsal |date=2025-04-04 |title=Public Transportation & Traffic Congestion in Ahmedabad |url=https://kautilyadevelopers.in/public-transportation-usage-and-traffic-congestion-challenges-in-ahmedabad/ |access-date=2026-05-03 |website=Kautilya Group |language=en-US}}</ref>. Traditional infrastructural attempts to alleviate these issues, such as the construction of new bridges and flyovers, have proven largely unsuccessful. This unchecked vehicular speed and disregard for traffic regulations pose a severe threat in school zones and pedestrian-heavy areas, reflecting a broader crisis where an estimated 16 children lose their lives on Indian roads every day<ref>{{Cite journal |last=R |first=Palanisamy |last2=Kumar |first2=PLS Sai |last3=Kiran |first3=Mekala Paavan |last4=Mahto |first4=Ashutosh |last5=Irfan |first5=Md |last6=Bhowmick |first6=Maharishi |date=2020-03-01 |title=ARDUINO based accident prevention and auto intimation system |url=https://ijeecs.iaescore.com/index.php/IJEECS/article/view/20443 |journal=Indonesian Journal of Electrical Engineering and Computer Science |language=en |volume=17 |issue=3 |pages=1275–1280 |doi=10.11591/ijeecs.v17.i3.pp1275-1280 |issn=2502-4760}}</ref>. == Infrastructure == To understand Ahmedabad’s plans to reduce traffic casualties and improve traffic circulation, Ahmedabad’s existing infrastructure as well as its plans for developing infrastructure must be examined. The Ahmedabad Municipal Corporation (AMC) was established in July 1950 under the Bombay Provincial Corporation Act of 1949. The AMC is responsible for the civic infrastructure and administration of the city of Ahmedabad <ref>{{Cite web |title=AMDAVAD MUNICIPAL CORPORATION |url=https://mybharat.gov.in/Gov/Urban-Local-Body/amdavad-municipal-corporation?utm_source=chatgpt.com |access-date=2026-04-30 |website=MyBharat}}</ref>. Other entities, such as the National Highways Authority of India (NHAI) <ref>{{Cite news |date=2024-09-20 |title=NHAI to hand over SG Road to AMC |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/nhai-to-hand-over-sg-road-to-amc/articleshow/113532142.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref> and the Ahmedabad Urban Development Authority (Auda), manage roadways in Ahmedabad <ref name=":0">{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. According to a budget report from the AMC, only 731.43 km of the 2,634 km road network has sidewalks, which is less than 28% of the total road network <ref name=":1">{{Cite news |date=2026-04-04 |title=A city that forgot its pedestrians: Footpaths missing from 72% of Ahmedabad roads |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/a-city-that-forgot-its-pedestrians-footpaths-missing-from-72-of-ahmedabad-roads/articleshow/130008165.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. The 2,634 km reported road length may not represent the total road length within Ahmedabad, since the report may not have accounted for roads under the management of the NHAI and Auda. Ahmedabad’s major roads, often referenced as arterial roads in ''The Times of India'', have four to six lanes, but some sections of these roads have even more lanes because they include service and bus lanes. Ahmedabad Municipal Transport Service (AMTS) runs the public bus service in the city of Ahmedabad. The responsibility for the administration of AMTS comes under the AMC <ref name=":2">{{Cite web |title=About Us {{!}} Ahmedabad Municipal Transport Services |url=https://www.amts.co.in/about-us/ |access-date=2026-04-30 |website=www.amts.co.in}}</ref>. The AMC has incorporated what it refers to as a “Special Purpose Vehicle,” called Ahmedabad Janmarg Ltd., in order to run and operate Ahmedabad’s Bus Rapid Transit System (BRTS). Ahmedabad Janmarg Ltd. is registered under the Companies Act, 1956, and is a 100% subsidiary of the AMC. In order to provide faster, reliable, eco-friendly, and advanced public transportation, Ahmedabad Janmarg Ltd. is committed to operating and running BRTS services <ref name=":3">{{Cite web |title=Home {{!}} Ahmedabad Janmarg Limited |url=https://www.ahmedabadbrts.org/?utm_source=chatgpt.com |access-date=2026-04-30 |website=www.ahmedabadbrts.org}}</ref>. Alternatively, the people of Ahmedabad can take the metro. Railway transportation in Ahmedabad began in 1863, when the first train from Ahmedabad to Surat was flagged off from the newly built Kalupur railway station <ref>{{Cite news |date=2017-01-20 |title=First train chugged out of Ahmedabad 154 years ago |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/first-train-chugged-out-of-ahmedabad-154-years-ago/articleshow/56674248.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. However, the first section of the metro opened in 2019, and the second section opened in 2026 <ref>{{Cite web |title=Project Overview |url=https://www.gujaratmetrorail.com/project-overview2/ |access-date=2026-04-30 |website=Gujarat Metro Rail Corporation (GMRC) Limited |language=en-US}}</ref>. The city of Ahmedabad has implemented several types of transportation infrastructure, such as vehicle bridges, including flyovers and railway overbridges; pedestrian bridges; roundabouts, locally known as “circles”; underpasses; speed bumps; and ring roads, which circle the city and allow vehicles passing through Ahmedabad to avoid getting stuck in city traffic. In 2006, Auda developed the 76 km SP Ring Road <ref>{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Between 2000 and 2026, 61 bridges, underpasses, and culverts were built, with 46 of them being constructed in the last 16 years. During that time, the city built five pedestrian overbridges, as well as an underpass in Mithakali <ref name=":9">{{Cite news |date=2026-04-11 |title=46 flyovers in 16 years, yet Ahmedabad’s traffic jams haven’t moved |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/46-flyovers-in-16-years-yet-ahmedabads-traffic-jams-havent-moved/articleshow/130179536.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Ahmedabad’s future plans to develop infrastructure are consistent with its previous infrastructure projects. The AMC plans to take up flyover construction at the city’s six most congested junctions as part of a decade-long program to build flyovers at the 25 most congested junctions <ref>{{Cite news |date=2026-03-31 |title=Six most-congested junctions in Ahmedabad flagged for priority flyovers |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/six-most-congested-junctions-in-ahmedabad-flagged-for-priority-flyovers/articleshow/129910368.cms?utm_source=chatgpt.com |access-date=2026-05-01 |issn=0971-8257}}</ref>. Auda approved the upgrade of the SP Ring Road to six lanes and requested that the AMC make provisions for service roads on the 76 km ring road. There is no uniformity in the width of the road, which varies from 60 meters to 96 meters in different sections. Auda approved two tenders worth Rs 2,200 crore to upgrade the 76 km SP Ring Road to six lanes. Rs 2,200 crore, or ₹22,000,000,000, is approximately $232,000,000 USD. In Phase 1, the 37 km eastern stretch will be upgraded, and in Phase 2, the 39.2 km western stretch will be revamped. Additionally, service roads will be developed, with existing two-lane service roads being expanded to four lanes over 34 km, and three-lane service roads over 15 km being expanded to four lanes. The service roads of the AMC will also be included in this development. At the same time, Auda plans to construct two new three-lane bridges next to the existing bridges over the Sabarmati River at Bhat and Kamod. Additionally, three six-lane underpasses will be constructed at Bhat Circle, Chiloda Circle, and Aslali Circle on the SP Ring Road. To create pedestrian crossings, six new foot overbridges will be built on the SP Ring Road <ref name=":5">{{Cite news |date=2026-02-22 |title=Ahmedabad Urban Development Authority’s plan to add service roads to SP Ring Road faces 5km hurdle |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/ahmedabad-urban-development-authoritys-plan-to-add-service-roads-to-sp-ring-road-faces-5km-hurdle/articleshow/128653810.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. The state government gave the green signal to Auda to redesignate about 36 square kilometers of land under the agriculture zone, facilitating its conversion into residential and commercial use in fast-developing areas along the periphery of Ahmedabad city. At the same time, the state government has taken an in-principle decision to initiate the process of land acquisition for the proposed third ring road of Ahmedabad city<ref>{{Cite news |date=2026-04-17 |title=Auda to denotify 36 sq km agri land for general use |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/auda-to-denotify-36-sq-km-agri-land-for-general-use/articleshow/130316956.cms?utm_source=chatgpt.com |access-date=2026-05-02 |issn=0971-8257}}</ref>. Perhaps the most innovative project is the existing yet not operational high-speed railroad network <ref>{{Cite news |date=2026-04-28 |title=Gujarat: All 8 piers ready for bullet train bridge across Sabarmati |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/gujarat-all-8-piers-ready-for-bullet-train-bridge-across-sabarmati/articleshow/130563689.cms?utm_source=chatgpt.com |access-date=2026-04-30 |issn=0971-8257}}</ref>. India’s first bullet train project will begin commercial operations in Gujarat by December 2027. The entire Mumbai-Ahmedabad corridor of the project will be operational by December 2029. The cost of this infrastructure project is about ₹1.08 lakh crore, or approximately $11.4 billion USD<ref>{{Cite web |last=TA |first=API |date=2025-07-28 |title=India’s First Bullet Train Project to Launch by 2027 |url=https://www.transportadvancement.com/news/indias-first-bullet-train-project-to-launch-by-2027/ |access-date=2026-05-02 |language=en-GB}}</ref>. The currency conversion between rupees and USD is a reasonable approximation as of 5/2/2026. == Participant Groups == Pedestrians are arguably the group that benefits the most from the implementation of these paintings. Online sentiment shows that many citizens are concerned about the lack of safe crossing areas in Ahmedabad, particularly on larger highways<ref>{{Cite web |title=No pedestrian crossing on SG highway |url=https://www.reddit.com/r/ahmedabad/comments/1d6y9m0/no_pedestrian_crossing_on_sg_highway/ |access-date=2026-04-28 |website=www.reddit.com}}</ref>. Reduced driver speeds helps ensure that drivers are more aware of pedestrian crossings and gives pedestrians a visually-designated zone to cross as opposed to jaywalking. The paintings were done near schools and accident-prone areas to help slow down drivers in the area, showing a deliberate implementation of the technique<ref>{{Cite web |last=India |first=Think Change |title=Two women artists design 3D zebra crossing for pedestrian friendly roads |url=https://yourstory.com/2016/05/3d-zebra-crossing |access-date=2026-04-28 |website=yourstory.com |language=en}}</ref>. Thakkar was contacted by IL&FS, a private infrastructure company, to implement the crosswalks on an accident-prone stretch of the Ahmedabad-Mehsana highway<ref>{{Cite web |last=Misra |first=Tanvi |date=March 30, 2016 |title=Meet the Women Behind India's 3D 'Zebra' Crossings |url=https://www.bloomberg.com/news/articles/2016-03-30/meet-the-mother-daughter-duo-who-designed-india-s-3d-zebra-crossings |url-status=live |website=Bloomberg}}</ref>. Other than a vague acknowledgement from the Ahmedabadi government, there has not been a substantial effort by the Ahmedabad Municipal Transports Service to bolster the efforts of Pandya and Thakkar. They are further restricted in the implementation of these designs due to regulations by the roadworks authorities<ref>{{Cite web |last=Vijaykumar |first=Neeti |title=Mother-Daughter Duo Painted a 3D Zebra Crossing In Ahmedabad |url=https://thebetterindia.com/48968/mother-daughter-road-safety-3d-painted-zebra-crossing-ahmedabad/ |access-date=2026-04-28 |website=thebetterindia.com |language=en}}</ref>. However, the innovation drew national attention, with the Central Road Research Institute (CRRI) conducting research on the effects of the paintings. They found that speed reductions ranged between 1.6% and 20.3%, with the larger reductions being that of trucks and other heavy commercial vehicles. This was primarily attributed to the higher vantage points of these larger vehicles, giving them a better view of the crosswalk and further enhancing the optical illusion. Combined with the larger breaking distance required for heavier vehicles, they are prone to slowing down more at these crosswalks<ref>{{Cite news |date=2016-06-09 |title=Illusion that works: 3D way to curb accidents |work=The Times of India |url=https://timesofindia.indiatimes.com/city/delhi/illusion-that-works-3d-way-to-curb-accidents/articleshow/52662981.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. Additionally, the Ahmedabad Municipal Corporation has allocated 20 crore rupees, or 2.1 million USD, to fixing over 100 traffic crossings, emphasizing an overall prioritization of making these crosswalks safer<ref name=":6">{{Cite news |date=2026-03-17 |title=Ahmedabad Municipal Corporation approves Rs 20 crore plan to fix 133 chaotic junctions |work=The Times of India |url=https://timesofindia.indiatimes.com/city/ahmedabad/hmedabad-municipal-corporation-approves-rs-20-crore-plan-to-fix-133-chaotic-junctions/articleshow/129617560.cms? |access-date=2026-04-28 |issn=0971-8257}}</ref>. There are very few firsthand accounts of driver sentiments regarding the crosswalks. However, given the results of the research conducted by the CRRI, it can be concluded that drivers have heightened awareness of the crosswalks and are responding relatively positively. Additionally, the design of the painting ensures that the illusion is functional from a distance, and dissipates as drivers approach the crosswalk, minimizing “panic braking” and ensuring that drivers are also kept safe<ref>{{Cite web |last=Stuart |date=2017-10-18 |title=3D advertising - magic eye zebra crossings |url=https://michoncreative.co.uk/articles/3d-advertising-magic-eye-zebra-crossings/ |access-date=2026-04-28 |website=Michon Ltd |language=en-GB}}</ref>. == Existing Solutions == Efforts to improve road safety and pedestrian conditions in Ahmedabad span three broad categories: traffic calming measures, pedestrian infrastructure, and traffic flow optimization. Each approach addresses a distinct dimension of the city's road safety crisis, and together they reflect both the progress made and the gaps that remain. === Traffic Calming === Traffic calming encompasses physical and visual measures designed to reduce vehicle speeds without requiring large-scale infrastructure investment. The most prominent local innovation is the 3D zebra crossing, pioneered in Ahmedabad by artists Saumya Pandya Thakkar and Shakuntala Pandya. By painting optical illusions directly onto the asphalt, the crossings create the appearance of a raised blockade, prompting drivers to slow down. Research by the Central Road Research Institute (CRRI) confirmed speed reductions of 1.6% to 20.3%, with the greatest effect observed among heavy commercial vehicles due to their elevated vantage points<ref name=":7">{{Cite web |last=Betts |first=Jordan |date=2019-06-26 |title="How is the metro's first 3D crosswalk working? Neighbors say it helps some" |url=https://www.kshb.com/news/local-news/kcks-3d-crosswalk-credited-for-reducing-traffic |access-date=2026-05-04 |website=KSHB 41 Kansas City News |language=}}</ref>. The concept has since been adopted in cities around the world, with results broadly consistent with those observed in Ahmedabad. In New Delhi, authorities reported that average vehicle speeds at 3D crosswalk locations dropped from 50 km/h to 30 km/h following installation<ref name=":4">{{Cite web |date=2016-09-18 |title="The First 3D Zebra Crossing Was a Rousing Success & Now There Are Plans For 40 More!" |url=https://so.city/delhi/article/the-first-3d-zebra-crossing-was-a-rousing-success-now-there-are-plans-for-40-more |access-date=2026-05-04 |website=So City |language=}}</ref>. In Europe, the fishing town of Ísafjörður, Iceland became the first to deploy the design in 2017, after its environmental commissioner sought alternatives to traditional speed bumps, which studies had linked to increased air pollution and driver complaints about vehicle damage<ref>{{Cite web |last= |first= |date=2021-09-30 |title=Managing urban traffic: 3D zebra crossings spread across Europe - Eurocities |url=https://eurocities.eu/stories/managing-urban-traffic-3d-zebra-crossings-spread-across-europe/ |access-date=2026-05-04 |website=eurocities.eu |language=}}</ref>. In Kansas City, Kansas, a 3D crosswalk was installed near a school in a residential neighborhood prone to speeding, and residents reported that the design helped slow drivers, though they noted that additional traffic calming measures were still needed<ref name=":7" />. A broader academic evaluation of decorative pavement markings at pedestrian crosswalks found that speed reductions ranged from 1.89 km/h to 4.41 km/h across twelve study sites, with vehicle-pedestrian crashes reduced by approximately 25%<ref>{{Cite journal |last=Rebelo |first=Francisco |title=Evaluation of 3D Crosswalks Design |url=https://www.researchgate.net/publication/325961246_Evaluation_of_3D_Crosswalks_Design |journal=ResearchGate}}</ref>. One recurring limitation noted across deployments is durability: the Kansas City crosswalk faded significantly within two years, and the city indicated it would only repaint if the design proved effective at slowing traffic<ref>{{Cite web |title=Kansas City, KS - 3D Crosswalk (Gone) |url=https://www.roadsideamerica.com/tip/64102 |access-date=2026-05-05 |website=RoadsideAmerica.com |language=en}}</ref>. This echoes the broader concern that the novelty effect of optical illusion markings may diminish as local drivers habituate to them over time. Complementing painted interventions, Ahmedabad installed 339 speed humps across the city in just 17 months, a rapid and low-cost deployment that reflects the city's broader prioritization of accessible safety measures. However, speed humps carry their own drawbacks: they can impede emergency vehicles, damage low-clearance vehicles if poorly designed, and face political resistance when proposed on high-capacity arterial roads. === Pedestrian Infrastructure === Ahmedabad's pedestrian infrastructure reveals a stark gap between need and provision. As of 2026, only 731 of the city's 2,634 km of roads have sidewalks, leaving 72% of the network without footpaths<ref name=":8">{{Cite news |title=Medians and Pedestrian Refuge Islands in Urban and Suburban Areas |work=U.S. Department of Transportation Federal Highway Administration |url=https://highways.dot.gov/safety/proven-safety-countermeasures/medians-and-pedestrian-refuge-islands-urban-and-suburban-areas}}</ref>. In response, the Ahmedabad Municipal Corporation (AMC) allocated Rs. 20 crore to repair over 100 traffic intersections<ref name=":6" />. Five foot overbridges (FOBs) currently exist, providing grade-separated crossings that fully eliminate pedestrian-vehicle conflict on high-speed corridors. An additional six FOBs are planned as part of the SP Ring Road upgrade<ref name=":5" />. For wide arterial roads where full-grade separation is not feasible, pedestrian refuge islands offer a proven middle-ground solution. Research by the U.S. Federal Highway Administration found that installing raised refuge islands at marked crosswalks reduced pedestrian crashes by 46%, and by 39% at unmarked locations<ref>{{Cite web |date=2010-01-01 |title=Safety Benefits of Raised Medians and Pedestrian Refuge Areas |url=https://rosap.ntl.bts.gov/ |access-date=2026-05-05 |website=rosap.ntl.bts.gov |language=English}}</ref>. By allowing pedestrians to cross one direction of traffic at a time, refuge islands are especially well-suited to Ahmedabad's four-to-six lane arterials, where crossing the full road width in a single phase poses significant risk<ref name=":8" />. === Traffic Flow Optimization === Beyond speed reduction, managing how traffic moves through and around Ahmedabad is critical to reducing conflict points between vehicles and pedestrians. Signal coordination, commonly referred to as a green wave, times traffic lights so that drivers traveling at the posted speed limit encounter a cascade of green signals along a corridor. Studies show this approach reduces CO2, NOx, and PM10 emissions while cutting unnecessary stops that contribute to erratic and aggressive driving behavior<ref>{{Citation |title=Green wave |date=2026-03-23 |url=https://en.wikipedia.org/w/index.php?title=Green_wave&oldid=1344984912 |work=Wikipedia |access-date=2026-05-05 |language=en}}</ref>. Crucially, it requires no new construction, only signal reprogramming. At a larger scale, Ahmedabad has pursued traffic separation through flyovers, underpasses, and ring roads to divert through-traffic away from dense urban areas. Between 2010 and 2026, 46 such structures were built, with 25 more planned over the next decade<ref name=":9" />. The 76 km Sardar Patel Ring Road, currently being upgraded to six lanes, is designed to reduce the volume of vehicles cutting through the city core<ref name=":5" />. While these infrastructure investments address congestion on major corridors, their impact on local pedestrian safety on the side streets and arterials that feed into them remains dependent on complementary measures such as sidewalk expansion and safer crossing design. == References == <references responsive="" /> d7z75y633tjsr1itihmy37cdq8s3jbe 0 482933 4634167 4633484 2026-05-04T18:53:28Z Kittycataclysm 3371989 query 4634167 wikitext text/x-wiki {{Qr-scope|reason=Unclear how this constitutes a whole book}} In April 2026, the survey website YouGov.com updated its results for celebrities' approval ratings. The current results are for the first quarter of 2026, which began on January 1, 2026, and ended on March 31, 2026. ==Questions== Figure 1, this table, shows the opinion distributions for the top 6 highest-rated celebrities for this survey. Note that "Fame" refers to the percentage of survey participants who know, or have heard of, the celebrity. "Like," "Dislike," and "Neutral," are subsets of "Fame." For example, this table shows that 94.6% of people have heard of Betty White; of those who know her, she is liked by 82.0% of all participants and disliked by 1.7%, while 11.0% are neutral towards her. {| class="wikitable sortable" |- ! Name ! Fame ! Like ! Dislike ! Neutral |- | style="text-align:right;"| Betty White | style="text-align:right;"| 94.6% | style="text-align:right;"| 82.0% | style="text-align:right;"| 1.7% | style="text-align:right;"| 11.0% |- | style="text-align:right;"| Keanu Reeves | style="text-align:right;"| 94.1% | style="text-align:right;"| 81.4% | style="text-align:right;"| 2.2% | style="text-align:right;"| 10.6% |- | style="text-align:right;"| Samuel L. Jackson | style="text-align:right;"| 96.4% | style="text-align:right;"| 80.9% | style="text-align:right;"| 4.5% | style="text-align:right;"| 11.1% |- | style="text-align:right;"| Morgan Freeman | style="text-align:right;"| 96.4% | style="text-align:right;"| 80.9% | style="text-align:right;"| 3.1% | style="text-align:right;"| 12.4% |- | style="text-align:right;"| Bruce Willis | style="text-align:right;"| 92.6% | style="text-align:right;"| 77.9% | style="text-align:right;"| 1.5% | style="text-align:right;"| 13.3% |- | style="text-align:right;"| Denzel Washington | style="text-align:right;"| 92.6% | style="text-align:right;"| 77.7% | style="text-align:right;"| 2.8% | style="text-align:right;"| 12.1% |} ===Example 1=== Calculate the '''effective''' approval rating of Morgan Freeman in this survey. Round your answer to the nearest millionth. ===Solution=== Morgan Freeman is the fourth most approved celebrity according to this survey, as shown in the table above, with an approval rating of 80.9%. However, as stated before, "Like," "Dislike," and "Neutral" do not exist in a vacuum, but rather, as a subset of "Fame," so, technically, the effective approval and disapproval ratings are slightly higher than the displayed values. The "Fame" score of 96.4% indicates that, in this quarter, 96.4% of people know Morgan Freeman. For every 1000 people, 964 people know Morgan Freeman; of those 964 people, 809 people have a positive opinion of him. <math>\frac{809}{964}</math> = 0.839211618..., rounded to the nearest millionth as '''0.839212.''' This means that, although his approval is listed as 81% (80.9% on the "Fame & Popularity Tracker" page, which gives three significant figures), he is technically 84% approved, since his "Fame," while close to 100%, is slightly less than 100% (96.4%). ===Example 2=== The percentages in the table (and the website) are approximations, given only to the nearest thousandth. Therefore, the answer to Example 1, given above, is not exact. Calculate the minimum and maximum. ===Solution=== If a decimal is rounded to 80.9% or 0.809, it can be any value between: * 1) 0.809000 and 0.810000 (but not including 0.810000) if the '''truncation rounding system''' is used * 2) 0.808500 and 0.809500 (but not including 0.809500) if the '''"round to the nearest" system''' is used * 3) 0.808000 and 0.809000 (excluding the lower bound, 0.808000) if the '''"round up to the next" system''' is used The website does not seem to provide clear details about which of the three rounding systems is being used. Therefore, the approval score of 80.9% may be as low as 0.808000 or as high as 0.810000. The "fame" score of 96.4% may be as low as 0.963000 or as high as 0.965000. '''Minimum:''' <math>\frac{808}{965}</math> = 0.83730569948..., or approximately '''0.837306''' '''Maximum:''' <math>\frac{810}{963}</math> = 0.84112149532..., or approximately '''0.841121''' ===Example 3=== Assuming the minimum value (0.837305), calculate the probability, for a classroom of 10 students, that all 10 students are Morgan Freeman fans, assuming independence. ===Solution=== (0.837305)<sup>10</sup> = 0.118742, or approximately 11.9%. ===Example 4=== What is the probability that a randomly selected group of 12 people will contain 8 fans and 4 non-fans? ===Solution=== 12 C 4 = 495 (There are 495 ways to select 4 from a set of 12.) 495 × (0.837305)<sup>8</sup> × (1 − 0.837305)<sup>4</sup> = 0.083786, or approximately 8.4%. ===Example 5=== Of those who are aware of Bruce Willis, find the percentage of people who '''dislike''' Bruce Willis. ===Solution=== For every 1000 people, there are, on average, 926 people who know Bruce Willis. Of those 926 people, there are 779 people who have a positive opinion of him and 133 people who are indifferent. This leaves only 15 people who '''dislike''' him. <math>\frac{15}{926}</math> = 0.016199, or about 1.62%. '''Minimum:''' <math>\frac{14}{927}</math> = 0.015102, or about 1.51%. '''Maximum:''' <math>\frac{16}{925}</math> = 0.017297, or about 1.73%. ===Example 6=== Justin Bieber has 96.5% fame. Of that 96.5%, he has 37.5% approval, while 29.7% dislike him, and 29.3% are neutral. Calculate his effective approval rating. ===Solution=== <math>\frac{375}{965}</math> = 0.388601, or about 38.86%. '''Minimum:''' <math>\frac{374}{966}</math> = 0.387164, or about 38.72%. '''Maximum:''' <math>\frac{376}{964}</math> = 0.390041, or about 39.00%. ===Example 7=== Find the probability that a group of 4 randomly selected people consists entirely of Justin Bieber fans, using the minimum value calculated in Example 6 above. ===Solution=== (0.387164)<sup>4</sup> = 0.022469, or approximately 2.25%. ===Example 8=== As a follow-up to Example 7, find the probability that, in 5 randomly selected people, that all 5 people are Justin Bieber fans. ===Solution=== (0.387164)<sup>5</sup> = 0.008699, or approximately 0.87%. {{shelves}} 7muhpsd7ps1fraiff4egaxg23dh2si6 0 482968 4634145 4633412 2026-05-04T18:22:03Z AndrewZurita 3581240 Added background 4634145 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays. [] Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size). [] Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality. [] A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.[] This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. == References == <references/> {{BookCat}} 657unx0gkv0ywmkdn7ut4q9ndlgqji3 4634148 4634145 2026-05-04T18:30:44Z AndrewZurita 3581240 Added references and citations 4634148 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. == References == <references/> {{BookCat}} ffsusr65pm62ae8uypefivzbvxwgkk8 4634175 4634148 2026-05-04T19:15:19Z Zpn7uw 3581242 First take at content, need to double check formatting for sources 4634175 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref name=":0">Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. === Medicare Part D === The passage of the Medicare Prescription Drug, Improvement, and Modernization Act (MMA) of 2003 marked a fundamental shift in American social policy. For the first time, a major expansion of a public entitlement program (the creation of Medicare Part D) was designed to be delivered exclusively through private insurance companies rather than the traditional government-administered fee-for-service model.<ref /> This delegation of power to private actors created a multi-billion dollar market that today serves tens of millions of beneficiaries (Kelly, 2023). The health insurance industry exerted significant influence by framing the expansion as a victory for "market competition." Rather than the government setting pharmaceutical prices directly, the MMA established a system where private insurance plans negotiate with drug manufacturers (Duggan & Scott Morton, 2010). Key features of the legislation that favored the insurance industry included: * '''The''' '''Non-Interference Clause:''' This prevented the Secretary of Health and Human Services from negotiating drug prices directly, ensuring that the negotiation power remained with private insurers and Pharmacy Benefit Managers (PBMs). * '''Voluntary''' '''Enrollment:''' Medicare Part D was structured so that beneficiaries must choose from a variety of private plans (PDPs or MA-PDs) to receive their benefit (Duggan & Scott Morton, 2010). * '''Administrative''' '''Subsidies:''' The government provides substantial subsidies to participating private plans, deriving the amount of these subsidies from the prices set by the insurers themselves (Kelly, 2023). The MMA's passage was secured by a razor-thin five-vote margin in the House of Representatives, following intense political bartering and lobbying. Research suggests that political dynamics played a role in the bill’s success, including specific provisions (such as payment increases for hospitals and the inclusion of the non-interference clause) used as leverage to win over reticent legislators (Cooper et al., 2017). Furthermore, recent analyses of the health insurance industry indicate a "pay-to-play" environment where higher political donations correlate with higher Medicare and Medicaid premiums and reduced regulatory oversight (Kelly, 2023). By 2019, Medicare Advantage and Part D plans were collectively receiving over half a trillion dollars in government payments (Kelly, 2023). Critics argue that this privatization has led to "overpayments" to private insurers, with some estimates suggesting that Medicare Advantage plans cost taxpayers significantly more per beneficiary than traditional Medicare (Kelly, 2023). This structure has granted the insurance industry "structural power," as the government is now heavily reliant on these private partners to deliver essential health benefits, making significant policy reform increasingly difficult (Kelly, 2023). == References == <references/> {{BookCat}} czlcth52seb60dwxmner5ourgh13gev 4634176 4634175 2026-05-04T19:16:56Z Zpn7uw 3581242 4634176 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref name=":0">Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. === Medicare Part D === The passage of the Medicare Prescription Drug, Improvement, and Modernization Act (MMA) of 2003 marked a fundamental shift in American social policy. For the first time, a major expansion of a public entitlement program (the creation of Medicare Part D) was designed to be delivered exclusively through private insurance companies rather than the traditional government-administered fee-for-service model. This delegation of power to private actors created a multi-billion dollar market that today serves tens of millions of beneficiaries (Kelly, 2023). The health insurance industry exerted significant influence by framing the expansion as a victory for "market competition." Rather than the government setting pharmaceutical prices directly, the MMA established a system where private insurance plans negotiate with drug manufacturers (Duggan & Scott Morton, 2010). Key features of the legislation that favored the insurance industry included: * '''The''' '''Non-Interference Clause:''' This prevented the Secretary of Health and Human Services from negotiating drug prices directly, ensuring that the negotiation power remained with private insurers and Pharmacy Benefit Managers (PBMs). * '''Voluntary''' '''Enrollment:''' Medicare Part D was structured so that beneficiaries must choose from a variety of private plans (PDPs or MA-PDs) to receive their benefit (Duggan & Scott Morton, 2010). * '''Administrative''' '''Subsidies:''' The government provides substantial subsidies to participating private plans, deriving the amount of these subsidies from the prices set by the insurers themselves (Kelly, 2023). The MMA's passage was secured by a razor-thin five-vote margin in the House of Representatives, following intense political bartering and lobbying. Research suggests that political dynamics played a role in the bill’s success, including specific provisions (such as payment increases for hospitals and the inclusion of the non-interference clause) used as leverage to win over reticent legislators (Cooper et al., 2017). Furthermore, recent analyses of the health insurance industry indicate a "pay-to-play" environment where higher political donations correlate with higher Medicare and Medicaid premiums and reduced regulatory oversight (Kelly, 2023). By 2019, Medicare Advantage and Part D plans were collectively receiving over half a trillion dollars in government payments (Kelly, 2023). Critics argue that this privatization has led to "overpayments" to private insurers, with some estimates suggesting that Medicare Advantage plans cost taxpayers significantly more per beneficiary than traditional Medicare (Kelly, 2023). This structure has granted the insurance industry "structural power," as the government is now heavily reliant on these private partners to deliver essential health benefits, making significant policy reform increasingly difficult (Kelly, 2023). == References == <references/> {{BookCat}} sx6xbq0jn4t8jv1ic0myciszobtavv7 4634177 4634176 2026-05-04T19:20:23Z Zpn7uw 3581242 Source formatting edit 4634177 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref name=":0">Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. === Medicare Part D === The passage of the Medicare Prescription Drug, Improvement, and Modernization Act (MMA) of 2003 marked a fundamental shift in American social policy. For the first time, a major expansion of a public entitlement program (the creation of Medicare Part D) was designed to be delivered exclusively through private insurance companies rather than the traditional government-administered fee-for-service model.<ref>{{Cite journal |last=Kelly |first=Andrew S. |date=2023 |title=Private Power in Public Programs: Medicare, Medicaid, and the Structural Power of Private Insurance |url=https://www.cambridge.org/core/journals/studies-in-american-political-development/article/abs/private-power-in-public-programs-medicare-medicaid-and-the-structural-power-of-private-insurance/428CFCC7CD545BEE9BC49843A5383D02 |journal=Studies in American Political Development |language=en |volume=37 |issue=1 |pages=24–40 |doi=10.1017/S0898588X22000207 |issn=0898-588X}}</ref> This delegation of power to private actors created a multi-billion dollar market that today serves tens of millions of beneficiaries (Kelly, 2023). The health insurance industry exerted significant influence by framing the expansion as a victory for "market competition." Rather than the government setting pharmaceutical prices directly, the MMA established a system where private insurance plans negotiate with drug manufacturers (Duggan & Scott Morton, 2010). Key features of the legislation that favored the insurance industry included: * '''The''' '''Non-Interference Clause:''' This prevented the Secretary of Health and Human Services from negotiating drug prices directly, ensuring that the negotiation power remained with private insurers and Pharmacy Benefit Managers (PBMs). * '''Voluntary''' '''Enrollment:''' Medicare Part D was structured so that beneficiaries must choose from a variety of private plans (PDPs or MA-PDs) to receive their benefit (Duggan & Scott Morton, 2010). * '''Administrative''' '''Subsidies:''' The government provides substantial subsidies to participating private plans, deriving the amount of these subsidies from the prices set by the insurers themselves (Kelly, 2023). The MMA's passage was secured by a razor-thin five-vote margin in the House of Representatives, following intense political bartering and lobbying. Research suggests that political dynamics played a role in the bill’s success, including specific provisions (such as payment increases for hospitals and the inclusion of the non-interference clause) used as leverage to win over reticent legislators (Cooper et al., 2017). Furthermore, recent analyses of the health insurance industry indicate a "pay-to-play" environment where higher political donations correlate with higher Medicare and Medicaid premiums and reduced regulatory oversight (Kelly, 2023). By 2019, Medicare Advantage and Part D plans were collectively receiving over half a trillion dollars in government payments (Kelly, 2023). Critics argue that this privatization has led to "overpayments" to private insurers, with some estimates suggesting that Medicare Advantage plans cost taxpayers significantly more per beneficiary than traditional Medicare (Kelly, 2023). This structure has granted the insurance industry "structural power," as the government is now heavily reliant on these private partners to deliver essential health benefits, making significant policy reform increasingly difficult (Kelly, 2023). == References == <references/> {{BookCat}} ljw43cm6r6eqhgod0f3k046nqh6tgk4 4634178 4634177 2026-05-04T19:24:24Z AndrewZurita 3581240 Analysis + Further Extension section 4634178 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref name=":0">Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. === Medicare Part D === The passage of the Medicare Prescription Drug, Improvement, and Modernization Act (MMA) of 2003 marked a fundamental shift in American social policy. For the first time, a major expansion of a public entitlement program (the creation of Medicare Part D) was designed to be delivered exclusively through private insurance companies rather than the traditional government-administered fee-for-service model.<ref>{{Cite journal |last=Kelly |first=Andrew S. |date=2023 |title=Private Power in Public Programs: Medicare, Medicaid, and the Structural Power of Private Insurance |url=https://www.cambridge.org/core/journals/studies-in-american-political-development/article/abs/private-power-in-public-programs-medicare-medicaid-and-the-structural-power-of-private-insurance/428CFCC7CD545BEE9BC49843A5383D02 |journal=Studies in American Political Development |language=en |volume=37 |issue=1 |pages=24–40 |doi=10.1017/S0898588X22000207 |issn=0898-588X}}</ref> This delegation of power to private actors created a multi-billion dollar market that today serves tens of millions of beneficiaries (Kelly, 2023). The health insurance industry exerted significant influence by framing the expansion as a victory for "market competition." Rather than the government setting pharmaceutical prices directly, the MMA established a system where private insurance plans negotiate with drug manufacturers (Duggan & Scott Morton, 2010). Key features of the legislation that favored the insurance industry included: * '''The''' '''Non-Interference Clause:''' This prevented the Secretary of Health and Human Services from negotiating drug prices directly, ensuring that the negotiation power remained with private insurers and Pharmacy Benefit Managers (PBMs). * '''Voluntary''' '''Enrollment:''' Medicare Part D was structured so that beneficiaries must choose from a variety of private plans (PDPs or MA-PDs) to receive their benefit (Duggan & Scott Morton, 2010). * '''Administrative''' '''Subsidies:''' The government provides substantial subsidies to participating private plans, deriving the amount of these subsidies from the prices set by the insurers themselves (Kelly, 2023). The MMA's passage was secured by a razor-thin five-vote margin in the House of Representatives, following intense political bartering and lobbying. Research suggests that political dynamics played a role in the bill’s success, including specific provisions (such as payment increases for hospitals and the inclusion of the non-interference clause) used as leverage to win over reticent legislators (Cooper et al., 2017). Furthermore, recent analyses of the health insurance industry indicate a "pay-to-play" environment where higher political donations correlate with higher Medicare and Medicaid premiums and reduced regulatory oversight (Kelly, 2023). By 2019, Medicare Advantage and Part D plans were collectively receiving over half a trillion dollars in government payments (Kelly, 2023). Critics argue that this privatization has led to "overpayments" to private insurers, with some estimates suggesting that Medicare Advantage plans cost taxpayers significantly more per beneficiary than traditional Medicare (Kelly, 2023). This structure has granted the insurance industry "structural power," as the government is now heavily reliant on these private partners to deliver essential health benefits, making significant policy reform increasingly difficult (Kelly, 2023). === Analysis === Given these three cases, the insurance industry’s influence over US health policy follows a pattern. First trade associations behave as political shields for their member companies. The member companies which fund the Better Medicare Alliance and the AHIP protect their members from public scrutiny allowing their funders to appear neutral when reform is proposed at the federal level. Secondly, the public narrative towards legislative reform  is weaponized. This is achieved through media campaigns and commissioned research intended to change perception of the reform as a problem not the solution. Finally, the losses for the insurance companies are minimized and this is usually done with revisions to the proposed policies made with the intention of favoring the private industry. As a result of this, although reform in the US healthcare system is being made, private insurance is still indispensable to the system. The cost of healthcare will likely not be comparable to that of other nations until the insurance industry is no longer influencing what reform looks like. == Further Extension == This chapter focused on three legislative cases in the history of US healthcare: Medicare Advantage, Medicare Part D, and the Affordable Care Act. Contributors looking to extend this chapter can potentially consider the following: State level reform efforts and US pharmaceutical industry overlap. == References == <references/> {{BookCat}} li025idc1xirr5r2bdxeqogwyxclb74 4634179 4634178 2026-05-04T19:25:38Z Zpn7uw 3581242 Final formatting edits for sources 4634179 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref name=":0">Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. === Medicare Part D === The passage of the Medicare Prescription Drug, Improvement, and Modernization Act (MMA) of 2003 marked a fundamental shift in American social policy. For the first time, a major expansion of a public entitlement program (the creation of Medicare Part D) was designed to be delivered exclusively through private insurance companies rather than the traditional government-administered fee-for-service model.<ref name=":1">{{Cite journal |last=Kelly |first=Andrew S. |date=2023 |title=Private Power in Public Programs: Medicare, Medicaid, and the Structural Power of Private Insurance |url=https://www.cambridge.org/core/journals/studies-in-american-political-development/article/abs/private-power-in-public-programs-medicare-medicaid-and-the-structural-power-of-private-insurance/428CFCC7CD545BEE9BC49843A5383D02 |journal=Studies in American Political Development |language=en |volume=37 |issue=1 |pages=24–40 |doi=10.1017/S0898588X22000207 |issn=0898-588X}}</ref> This delegation of power to private actors created a multi-billion dollar market that today serves tens of millions of beneficiaries.<ref name=":1" /> The health insurance industry exerted significant influence by framing the expansion as a victory for "market competition." Rather than the government setting pharmaceutical prices directly, the MMA established a system where private insurance plans negotiate with drug manufacturers.<ref name=":2">{{Cite journal |last=Duggan |first=Mark |last2=Scott Morton |first2=Fiona |date=2010 |title=The Effect of Medicare Part D on Pharmaceutical Prices and Utilization |url=https://www.aeaweb.org/articles?id=10.1257/aer.100.1.590 |journal=American Economic Review |language=en |volume=100 |issue=1 |pages=590–607 |doi=10.1257/aer.100.1.590 |issn=0002-8282}}</ref> Key features of the legislation that favored the insurance industry included: * '''The''' '''Non-Interference Clause:''' This prevented the Secretary of Health and Human Services from negotiating drug prices directly, ensuring that the negotiation power remained with private insurers and Pharmacy Benefit Managers (PBMs). * '''Voluntary''' '''Enrollment:''' Medicare Part D was structured so that beneficiaries must choose from a variety of private plans (PDPs or MA-PDs) to receive their benefit.<ref name=":2" /> * '''Administrative''' '''Subsidies:''' The government provides substantial subsidies to participating private plans, deriving the amount of these subsidies from the prices set by the insurers themselves.<ref name=":1" /> The MMA's passage was secured by a razor-thin five-vote margin in the House of Representatives, following intense political bartering and lobbying. Research suggests that political dynamics played a role in the bill’s success, including specific provisions (such as payment increases for hospitals and the inclusion of the non-interference clause) used as leverage to win over reticent legislators.<ref>{{Cite journal |last=Cooper |first=Zack |last2=Kowalski |first2=Amanda |last3=Powell |first3=Eleanor Neff |last4=Wu |first4=Jennifer D. |date=2024-05-01 |title=Politics and health care spending in the United States: A case study from the passage of the 2003 Medicare Modernization Act |url=https://www.sciencedirect.com/science/article/pii/S0167629624000237 |journal=Journal of Health Economics |volume=95 |pages=102878 |doi=10.1016/j.jhealeco.2024.102878 |issn=0167-6296}}</ref> Furthermore, recent analyses of the health insurance industry indicate a "pay-to-play" environment where higher political donations correlate with higher Medicare and Medicaid premiums and reduced regulatory oversight.<ref name=":1" /> By 2019, Medicare Advantage and Part D plans were collectively receiving over half a trillion dollars in government payments.<ref name=":1" /> Critics argue that this privatization has led to "overpayments" to private insurers, with some estimates suggesting that Medicare Advantage plans cost taxpayers significantly more per beneficiary than traditional Medicare. This structure has granted the insurance industry "structural power," as the government is now heavily reliant on these private partners to deliver essential health benefits, making significant policy reform increasingly difficult.<ref name=":1" /> === Analysis === Given these three cases, the insurance industry’s influence over US health policy follows a pattern. First trade associations behave as political shields for their member companies. The member companies which fund the Better Medicare Alliance and the AHIP protect their members from public scrutiny allowing their funders to appear neutral when reform is proposed at the federal level. Secondly, the public narrative towards legislative reform  is weaponized. This is achieved through media campaigns and commissioned research intended to change perception of the reform as a problem not the solution. Finally, the losses for the insurance companies are minimized and this is usually done with revisions to the proposed policies made with the intention of favoring the private industry. As a result of this, although reform in the US healthcare system is being made, private insurance is still indispensable to the system. The cost of healthcare will likely not be comparable to that of other nations until the insurance industry is no longer influencing what reform looks like. == Further Extension == This chapter focused on three legislative cases in the history of US healthcare: Medicare Advantage, Medicare Part D, and the Affordable Care Act. Contributors looking to extend this chapter can potentially consider the following: State level reform efforts and US pharmaceutical industry overlap. == References == <references/> {{BookCat}} na45pqad3tx2bywt95vbmgqsq14s4c6 4634184 4634179 2026-05-04T19:58:47Z MaryamYounis 3577787 ACA 4634184 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref name=":0">Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. === Medicare Part D === The passage of the Medicare Prescription Drug, Improvement, and Modernization Act (MMA) of 2003 marked a fundamental shift in American social policy. For the first time, a major expansion of a public entitlement program (the creation of Medicare Part D) was designed to be delivered exclusively through private insurance companies rather than the traditional government-administered fee-for-service model.<ref name=":1">{{Cite journal |last=Kelly |first=Andrew S. |date=2023 |title=Private Power in Public Programs: Medicare, Medicaid, and the Structural Power of Private Insurance |url=https://www.cambridge.org/core/journals/studies-in-american-political-development/article/abs/private-power-in-public-programs-medicare-medicaid-and-the-structural-power-of-private-insurance/428CFCC7CD545BEE9BC49843A5383D02 |journal=Studies in American Political Development |language=en |volume=37 |issue=1 |pages=24–40 |doi=10.1017/S0898588X22000207 |issn=0898-588X}}</ref> This delegation of power to private actors created a multi-billion dollar market that today serves tens of millions of beneficiaries.<ref name=":1" /> The health insurance industry exerted significant influence by framing the expansion as a victory for "market competition." Rather than the government setting pharmaceutical prices directly, the MMA established a system where private insurance plans negotiate with drug manufacturers.<ref name=":2">{{Cite journal |last=Duggan |first=Mark |last2=Scott Morton |first2=Fiona |date=2010 |title=The Effect of Medicare Part D on Pharmaceutical Prices and Utilization |url=https://www.aeaweb.org/articles?id=10.1257/aer.100.1.590 |journal=American Economic Review |language=en |volume=100 |issue=1 |pages=590–607 |doi=10.1257/aer.100.1.590 |issn=0002-8282}}</ref> Key features of the legislation that favored the insurance industry included: * '''The''' '''Non-Interference Clause:''' This prevented the Secretary of Health and Human Services from negotiating drug prices directly, ensuring that the negotiation power remained with private insurers and Pharmacy Benefit Managers (PBMs). * '''Voluntary''' '''Enrollment:''' Medicare Part D was structured so that beneficiaries must choose from a variety of private plans (PDPs or MA-PDs) to receive their benefit.<ref name=":2" /> * '''Administrative''' '''Subsidies:''' The government provides substantial subsidies to participating private plans, deriving the amount of these subsidies from the prices set by the insurers themselves.<ref name=":1" /> The MMA's passage was secured by a razor-thin five-vote margin in the House of Representatives, following intense political bartering and lobbying. Research suggests that political dynamics played a role in the bill’s success, including specific provisions (such as payment increases for hospitals and the inclusion of the non-interference clause) used as leverage to win over reticent legislators.<ref>{{Cite journal |last=Cooper |first=Zack |last2=Kowalski |first2=Amanda |last3=Powell |first3=Eleanor Neff |last4=Wu |first4=Jennifer D. |date=2024-05-01 |title=Politics and health care spending in the United States: A case study from the passage of the 2003 Medicare Modernization Act |url=https://www.sciencedirect.com/science/article/pii/S0167629624000237 |journal=Journal of Health Economics |volume=95 |pages=102878 |doi=10.1016/j.jhealeco.2024.102878 |issn=0167-6296}}</ref> Furthermore, recent analyses of the health insurance industry indicate a "pay-to-play" environment where higher political donations correlate with higher Medicare and Medicaid premiums and reduced regulatory oversight.<ref name=":1" /> By 2019, Medicare Advantage and Part D plans were collectively receiving over half a trillion dollars in government payments.<ref name=":1" /> Critics argue that this privatization has led to "overpayments" to private insurers, with some estimates suggesting that Medicare Advantage plans cost taxpayers significantly more per beneficiary than traditional Medicare. This structure has granted the insurance industry "structural power," as the government is now heavily reliant on these private partners to deliver essential health benefits, making significant policy reform increasingly difficult.<ref name=":1" /> '''The Affordable Care Act''' The Affordable Care Act dates all the way back to the "Harry and Louise" campaign in 1993. This was a campaign that was highly effective in opposing the Clinton Health Care Plan. It constituted mass television ads that pushed healthcare reform as overly complex and government-controlled. This allowed Americans to feel defeated as well as oppose the Clinton Health care plan. The failure of that Clinton plan directly portrays how strong the insurance industry’s power is to block policy changes that didn't work in their favor. The healthcare system started facing a more urgent crisis sometime in the late 2000s. Two problems were at the forefront, approximately 46 million Americans were uninsured while healthcare costs were rising far faster than wages. The combination created widespread financial strain and increased instability, as individuals risked losing coverage due to illness or job loss. The public had felt that the healthcare situation was simply too unsustainable support for broader healthcare reform began to grow. This meant that insurance companies had to restrategize in order to win back public favor or at least get the public off their back. The strategy to block reform would have never worked because the real goal was to win back the public, so the new strategy was to reshape the healthcare situation in a way that still aligned with their goals. Organizations like America’s Health Insurance Plans (AHIP) main goals were aimed to keep the private insurance system. The goal was to secure an individual mandate, which would require all Americans to purchase insurance. In doing so, this would guarantee a larger customer base and offset the costs of covering individuals with preexisting conditions. During this time, the Obama administration took on a different problem that ended up overlapping with the insurance companies main goals.<ref>{{Cite web |date=2026-04-30 |title=KFF - The independent source for health policy research, polling, and news. |url=https://www.kff.org/ |access-date=2026-05-04 |website=KFF |language=en-US}}</ref> The main two goals was to expand access to healthcare while stabilizing costs. This take really emphasized increasing coverage through subsidies while regulating insurance practices. This made sure that both healthy and sick Americans participate all under the same system. The government and the Obama administration were able to frame this take as a balance between accessibility and responsibility. A system that naturally only works when everyone contributes. AHIP and other insurance industry actors also played a more subtle political role. For example, they financially supported organizations that opposed certain reform proposals, such as a government-run “public option,” and backed reports suggesting reform could increase premiums. In spite of that, they publicly cooperated with reform efforts, which allowed them to still have influence over policy outcomes without appearing as though they had a hand. The final legislation reflects this balance of competing interests. While the Affordable Care Act significantly expanded coverage and introduced consumer protections, it also preserved the central role of private insurers. The law now established insurance marketplaces as well as provided government subsidies to make coverage more affordable. The government and the insurance companies were able to benefit while the people still face similar issues with their healthcare. The Affordable Care Act is a perfect example of how policy outcomes are shaped not just by public need, but by negotiation between political goals and insurance companies. As long as the Insurance companies can retain the existing structure of private insurance, they can always hold power. -- is there anything seriously wrong with this? === Analysis === Given these three cases, the insurance industry’s influence over US health policy follows a pattern. First trade associations behave as political shields for their member companies. The member companies which fund the Better Medicare Alliance and the AHIP protect their members from public scrutiny allowing their funders to appear neutral when reform is proposed at the federal level. Secondly, the public narrative towards legislative reform  is weaponized. This is achieved through media campaigns and commissioned research intended to change perception of the reform as a problem not the solution. Finally, the losses for the insurance companies are minimized and this is usually done with revisions to the proposed policies made with the intention of favoring the private industry. As a result of this, although reform in the US healthcare system is being made, private insurance is still indispensable to the system. The cost of healthcare will likely not be comparable to that of other nations until the insurance industry is no longer influencing what reform looks like. == Further Extension == This chapter focused on three legislative cases in the history of US healthcare: Medicare Advantage, Medicare Part D, and the Affordable Care Act. Contributors looking to extend this chapter can potentially consider the following: State level reform efforts and US pharmaceutical industry overlap. == References == <references/> {{BookCat}} 1l0yy7z7vv7vbsz1q1og27st9p83a41 4634185 4634184 2026-05-04T19:59:26Z MaryamYounis 3577787 ACA edit 4634185 wikitext text/x-wiki In 2024, an analysis of healthcare expenses across multiple countries was made by Peterson-KFF revealing U.S. citizens' healthcare expenses averaged $14,755 compared to the $7,860 that the rest of the world pays.<ref>"How does health spending in the U.S. compare to other countries?". ''Peterson-KFF Health System Tracker''. https://www.healthsystemtracker.org/chart-collection/health-spending-u-s-compare-countries/</ref> Additionally, a CDC survey reveals that 27.2 million people remain uninsured in the United States (8.2% of the sample size).<ref>CDC. “U.S. Uninsured Rate Drops by 15% Since 2020.” ''NCHS Pressroom'', 25 June 2025, <nowiki>https://www.cdc.gov/nchs/pressroom/releases/20250624.html</nowiki>.</ref> Compared to similar nations, the U.S. ranks towards the bottom in life expectancy and healthcare quality.<ref>“International Comparison of Health Systems.” ''KFF'', 3 Oct. 2025, <nowiki>https://www.kff.org/global-health-policy/health-policy-101-international-comparison-of-health-systems/</nowiki>.</ref> A distinguisher of the healthcare system in the US is the role of privatized insurance. For other wealthy countries, healthcare is primarily paid by their government, giving direct leverage as the negotiator of coverage standards and cost. Compared to the US, this role is shared by both private insurers and the government operating in a regulated market based system.<ref>Smith K. A (Brief) History of Health Policy in the United States. Dela J Public Health. 2023 Dec 31;9(5):6-10. doi: 10.32481/djph.2023.12.003. PMID: 38283712; PMCID: PMC10810293.</ref> This results in reform efforts having the additional participation of private companies in the US. Anytime reform for the US healthcare system is made, the insurance industry plays an active role in shaping what change looks like. Different strategies such as media campaigns, commissioned research, trade associations, and lobbying are employed by private insurers in efforts to shape legislation in their favor while limiting the government’s ability to compete with or replace them. The following chapter examines the role of privatized insurance over three cases in the history of the US healthcare system: Medicare Advantage, Medicare Part D, and the Affordable Care Act. == Case Studies == === Medicare Advantage === Medicare Advantage (MA) are plans administered by private insurers and funded by the federal government, which serve as an alternative option to government-run Medicare. Also known as Medicare Part C, MA was introduced under the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 to introduce private-sector competition and efficiency into the Medicare system.<ref>Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> Today, MA plans cover approximately 54% of all Medicare beneficiaries.<ref name=":0">Legal Clarity. (2026). When did Medicare Part C start? History of Medicare Advantage. https://legalclarity.org/when-did-medicare-part-c-start-history-of-medicare-advantage/</ref> These plans have grown increasingly popular due to their relatively low premiums and supplemental benefits; however, their structure creates opportunities for insurers to influence both costs and policy outcomes. A key concern is the financial impact of MA on taxpayers, as estimates suggest that overpayments to MA plans added around $82 billion to Medicare spending in 2023.<ref>Gaffney, A., Woolhandler, S., & Himmelstein, D. U. (2024). Less Care at Higher Cost—The Medicare Advantage Paradox. ''JAMA Internal Medicine'', 184(8). https://doi.org/10.1001/jamainternmed.2024.1868</ref> These excess payments are often attributed to practices such as favorable selection, where healthier individuals are more likely to enroll, and upcoding, in which insurers report higher illness severity than reality to receive larger reimbursements. The regulatory body, Centers for Medicare & Medicaid Services (CMS), has responded by attempting to implement reforms, including updates to the V28 risk adjustment model. This was expected to reduce MA risk scores by 3.12% to reduce upcoding.<ref>Clayton, W. (2026). CMS-HCC Model V28. RAAPID Inc. https://www.raapidinc.com/blogs/cms-hcc-model-v28/</ref> However, policy reform in this area is heavily shaped by industry influence. CMS initially proposed a modest 0.09% payment increase for 2027, triggering a sharp negative reaction in financial markets, with insurance stocks dropping significantly.<ref>MacDonald, I. (2026). Advance Notice fallout: What MA plans need to know. https://www.risehealth.org/insights-articles/article/advance-notice-fallout-what-ma-plans-need-to-know/</ref> This response was followed by an extensive lobbying effort from insurers and their affiliated organizations. For example, the Better Medicare Alliance (BMA), a group funded by major insurers, directly petitioned CMS leadership to reconsider the proposed changes.<ref>Better Medicare Alliance. (2026). Letter to CMS Administrator Mehmet Oz. https://bettermedicarealliance.org/wp-content/uploads/2026/03/Ally-Sign-on-Letter-to-Administrator-Oz.pdf</ref> Similarly, America’s Health Insurance Plans (AHIP) submitted formal comments expressing “serious concerns” that the proposals would increase costs and reduce benefits for seniors.<ref>AHIP. (2023). AHIP submits comments on 2024 Medicare Advantage advance rate notice. https://www.ahip.org/news/press-releases/ahip-submits-comments-on-2024-medicare-advantage-advance-rate-notice</ref> Beyond public statements, insurers also mobilized research and public engagement efforts to support their position. AHIP commissioned analyses, including work by Wakely, to argue for higher funding levels and more gradual implementation of policy changes.<ref>America’s Health Insurance Plans. (2026). AHIP comment letter on the CY 2027 Medicare Advantage advance notice (with Wakely reports). https://ahiporg-production.s3.amazonaws.com/documents/AHIP-Comment-Letter-CY2027-Advance-Notice-with-Wakely-Reports.pdf</ref> At the same time, the CMS proposal received a record-breaking 47,000 public comments, reflecting the scale of organized industry and stakeholder engagement.<ref>Casolo, E. (2026). 47,000 comments on 2027 Medicare Advantage pay proposal breaks CMS record. https://www.beckerspayer.com/payer/medicare-advantage/47000-comments-on-ma-payment-rule-for-2027-breaks-cms-record/</ref> These actions demonstrate how insurers can shape the policy narrative by framing reforms as harmful to beneficiaries rather than as cost-control measures. The final outcome illustrates the effectiveness of these efforts. CMS ultimately increased the payment adjustment to 2.48%, representing roughly $13 billion in additional funding for MA plans, and chose to delay key risk adjustment reforms by continuing to use the previous model.<ref>Centers for Medicare & Medicaid Services. (2026). CMS finalizes 2027 Medicare Advantage and Part D payment policies. https://www.cms.gov/newsroom/press-releases/cms-finalizes-2027-medicare-advantage-part-d-payment-policies-strengthen-accountability-long-term</ref> Additionally, the agency rolled back certain regulatory changes, including the removal of 11 quality measures from the MA Star Ratings system.<ref>Centers for Medicare & Medicaid Services. (2026). Contract year 2027 Medicare Advantage and Part D final rule. https://www.cms.gov/newsroom/fact-sheets/contract-year-2027-medicare-advantage-part-d-final-rule</ref> Overall, the Medicare Advantage case highlights how private insurers leverage lobbying, research, and public messaging to influence federal health policy. While reforms are often proposed to address inefficiencies and reduce costs, industry responses can significantly alter their implementation, demonstrating the complex relationship between government regulation and private-sector interests in U.S. healthcare. === Medicare Part D === The passage of the Medicare Prescription Drug, Improvement, and Modernization Act (MMA) of 2003 marked a fundamental shift in American social policy. For the first time, a major expansion of a public entitlement program (the creation of Medicare Part D) was designed to be delivered exclusively through private insurance companies rather than the traditional government-administered fee-for-service model.<ref name=":1">{{Cite journal |last=Kelly |first=Andrew S. |date=2023 |title=Private Power in Public Programs: Medicare, Medicaid, and the Structural Power of Private Insurance |url=https://www.cambridge.org/core/journals/studies-in-american-political-development/article/abs/private-power-in-public-programs-medicare-medicaid-and-the-structural-power-of-private-insurance/428CFCC7CD545BEE9BC49843A5383D02 |journal=Studies in American Political Development |language=en |volume=37 |issue=1 |pages=24–40 |doi=10.1017/S0898588X22000207 |issn=0898-588X}}</ref> This delegation of power to private actors created a multi-billion dollar market that today serves tens of millions of beneficiaries.<ref name=":1" /> The health insurance industry exerted significant influence by framing the expansion as a victory for "market competition." Rather than the government setting pharmaceutical prices directly, the MMA established a system where private insurance plans negotiate with drug manufacturers.<ref name=":2">{{Cite journal |last=Duggan |first=Mark |last2=Scott Morton |first2=Fiona |date=2010 |title=The Effect of Medicare Part D on Pharmaceutical Prices and Utilization |url=https://www.aeaweb.org/articles?id=10.1257/aer.100.1.590 |journal=American Economic Review |language=en |volume=100 |issue=1 |pages=590–607 |doi=10.1257/aer.100.1.590 |issn=0002-8282}}</ref> Key features of the legislation that favored the insurance industry included: * '''The''' '''Non-Interference Clause:''' This prevented the Secretary of Health and Human Services from negotiating drug prices directly, ensuring that the negotiation power remained with private insurers and Pharmacy Benefit Managers (PBMs). * '''Voluntary''' '''Enrollment:''' Medicare Part D was structured so that beneficiaries must choose from a variety of private plans (PDPs or MA-PDs) to receive their benefit.<ref name=":2" /> * '''Administrative''' '''Subsidies:''' The government provides substantial subsidies to participating private plans, deriving the amount of these subsidies from the prices set by the insurers themselves.<ref name=":1" /> The MMA's passage was secured by a razor-thin five-vote margin in the House of Representatives, following intense political bartering and lobbying. Research suggests that political dynamics played a role in the bill’s success, including specific provisions (such as payment increases for hospitals and the inclusion of the non-interference clause) used as leverage to win over reticent legislators.<ref>{{Cite journal |last=Cooper |first=Zack |last2=Kowalski |first2=Amanda |last3=Powell |first3=Eleanor Neff |last4=Wu |first4=Jennifer D. |date=2024-05-01 |title=Politics and health care spending in the United States: A case study from the passage of the 2003 Medicare Modernization Act |url=https://www.sciencedirect.com/science/article/pii/S0167629624000237 |journal=Journal of Health Economics |volume=95 |pages=102878 |doi=10.1016/j.jhealeco.2024.102878 |issn=0167-6296}}</ref> Furthermore, recent analyses of the health insurance industry indicate a "pay-to-play" environment where higher political donations correlate with higher Medicare and Medicaid premiums and reduced regulatory oversight.<ref name=":1" /> By 2019, Medicare Advantage and Part D plans were collectively receiving over half a trillion dollars in government payments.<ref name=":1" /> Critics argue that this privatization has led to "overpayments" to private insurers, with some estimates suggesting that Medicare Advantage plans cost taxpayers significantly more per beneficiary than traditional Medicare. This structure has granted the insurance industry "structural power," as the government is now heavily reliant on these private partners to deliver essential health benefits, making significant policy reform increasingly difficult.<ref name=":1" /> '''The Affordable Care Act''' The Affordable Care Act dates all the way back to the "Harry and Louise" campaign in 1993. This was a campaign that was highly effective in opposing the Clinton Health Care Plan. It constituted mass television ads that pushed healthcare reform as overly complex and government-controlled. This allowed Americans to feel defeated as well as oppose the Clinton Health care plan. The failure of that Clinton plan directly portrays how strong the insurance industry’s power is to block policy changes that didn't work in their favor. The healthcare system started facing a more urgent crisis sometime in the late 2000s. Two problems were at the forefront, approximately 46 million Americans were uninsured while healthcare costs were rising far faster than wages. The combination created widespread financial strain and increased instability, as individuals risked losing coverage due to illness or job loss. The public had felt that the healthcare situation was simply too unsustainable support for broader healthcare reform began to grow. This meant that insurance companies had to restrategize in order to win back public favor or at least get the public off their back. The strategy to block reform would have never worked because the real goal was to win back the public, so the new strategy was to reshape the healthcare situation in a way that still aligned with their goals. Organizations like America’s Health Insurance Plans (AHIP) main goals were aimed to keep the private insurance system. The goal was to secure an individual mandate, which would require all Americans to purchase insurance. In doing so, this would guarantee a larger customer base and offset the costs of covering individuals with preexisting conditions. During this time, the Obama administration took on a different problem that ended up overlapping with the insurance companies main goals.<ref>{{Cite web |date=2026-04-30 |title=KFF - The independent source for health policy research, polling, and news. |url=https://www.kff.org/ |access-date=2026-05-04 |website=KFF |language=en-US}}</ref> The main two goals was to expand access to healthcare while stabilizing costs. This take really emphasized increasing coverage through subsidies while regulating insurance practices. This made sure that both healthy and sick Americans participate all under the same system. The government and the Obama administration were able to frame this take as a balance between accessibility and responsibility. A system that naturally only works when everyone contributes. AHIP and other insurance industry actors also played a more subtle political role. For example, they financially supported organizations that opposed certain reform proposals, such as a government-run “public option,” and backed reports suggesting reform could increase premiums. In spite of that, they publicly cooperated with reform efforts, which allowed them to still have influence over policy outcomes without appearing as though they had a hand. The final legislation reflects this balance of competing interests. While the Affordable Care Act significantly expanded coverage and introduced consumer protections, it also preserved the central role of private insurers. The law now established insurance marketplaces as well as provided government subsidies to make coverage more affordable. The government and the insurance companies were able to benefit while the people still face similar issues with their healthcare. The Affordable Care Act is a perfect example of how policy outcomes are shaped not just by public need, but by negotiation between political goals and insurance companies. As long as the Insurance companies can retain the existing structure of private insurance, they can always hold power. === Analysis === Given these three cases, the insurance industry’s influence over US health policy follows a pattern. First trade associations behave as political shields for their member companies. The member companies which fund the Better Medicare Alliance and the AHIP protect their members from public scrutiny allowing their funders to appear neutral when reform is proposed at the federal level. Secondly, the public narrative towards legislative reform  is weaponized. This is achieved through media campaigns and commissioned research intended to change perception of the reform as a problem not the solution. Finally, the losses for the insurance companies are minimized and this is usually done with revisions to the proposed policies made with the intention of favoring the private industry. As a result of this, although reform in the US healthcare system is being made, private insurance is still indispensable to the system. The cost of healthcare will likely not be comparable to that of other nations until the insurance industry is no longer influencing what reform looks like. == Further Extension == This chapter focused on three legislative cases in the history of US healthcare: Medicare Advantage, Medicare Part D, and the Affordable Care Act. Contributors looking to extend this chapter can potentially consider the following: State level reform efforts and US pharmaceutical industry overlap. == References == <references/> {{BookCat}} cvblku4bvdmwprqxwfylr5zmsi7l88u 3 483050 4634055 4634054 2026-05-04T12:02:24Z MathXplore 3097823 [[WB:REVERT|Reverted]] edits by [[Special:Contributions/Babywacko|Babywacko]] ([[User talk:Babywacko|talk]]) to last version by MathXplore 4633509 wikitext text/x-wiki == I have added a tag to a page you created == Hi! I'm MathXplore, and I recently reviewed your page, [[:Talk:The science of finance/Introduction to economics]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. The reason I provided was: <blockquote><strong>Test page</strong></blockquote> If you believe that your page should not be deleted, please post a message on [[Talk:The science of finance/Introduction to economics|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 11:06, 2 May 2026 (UTC) cphyr6zvuqmx9h8sd09z3im0trfsa1h 4634056 4634055 2026-05-04T12:02:47Z MathXplore 3097823 Warning user with {{Test1}} 4634056 wikitext text/x-wiki == I have added a tag to a page you created == Hi! I'm MathXplore, and I recently reviewed your page, [[:Talk:The science of finance/Introduction to economics]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. The reason I provided was: <blockquote><strong>Test page</strong></blockquote> If you believe that your page should not be deleted, please post a message on [[Talk:The science of finance/Introduction to economics|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 11:06, 2 May 2026 (UTC) == May 2026 == {{tmbox|type=notice|text='''Please, can you [[Using Wikibooks|help]] improve [[WB:WIW|Wikibooks]]''' by [[Special:Contributions/Babywacko|doing future experiments]] with the [[Help:Contents|wiki software]] in the [{{fullurl:Wikibooks:Sandbox|action=edit}} sandbox] instead? Your fellow contributors consider test edits in the sandbox constructive. You can ask questions or ask for help in the [[WB:HELP|Assistance Reading Room]].<br /> Thanks. }} [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:02, 4 May 2026 (UTC) 5swl6lcxuhhe2uc5g9lq6t34e3cdek9 0 483052 4634124 4633777 2026-05-04T17:32:51Z JCrue 2226064 speedy delete 4634124 wikitext text/x-wiki {{delete|Not opening theory & name unsupported}} '''Ba6?? (Tanfon Gambit)''' White's just blundered a whole bishop 2 moves in. Black should respond with Nxa6!, because bxa6?! falls behind in development. {{BookCat}} a3lfrboirei4dvirfdjryrbbtrqww1s 0 483059 4634207 4633559 2026-05-05T01:00:10Z JackBot 396820 Formatting, [[Special:UncategorizedPages]] 4634207 wikitext text/x-wiki '''SPEEDY DELETION''' This Wikibook has been subject to attack on several occasions by editors using the speedy deletion policy. Many thousands of hours of effort in prior content creation have potentially been lost and resources diverted from new content creation. More importantly it creates doubt that this Wikibook will continue to exist indefinitely. * The Wikipedia article on "Speedy deletion" is definitive: [[w:Wikipedia:Speedy_deletion|Wikipedia:Speedy deletion]] * A further Wikipedia article provides a field guide to interpretation and application of the "Speedy deletion" policy: [[w:Wikipedia:Field_guide_to_proper_speedy_deletion|Wikipedia:Field guide to proper speedy deletion]] * There is currently a draft policy for "Speedy deletion" in Wikibooks: [[b:Wikibooks:Speedy_deletion|Wikibooks:Speedy deletion]] * The discussion about the draft policy for "Speedy deletion" in Wikibooks is here: Note that, once the discussion is finalised * There is a finalised policy on "Deletion" in Wikibooks: [[b:Wikibooks:Deletion_policy|Wikibooks:Deletion policy]] * The closely related concept of "fair use" (non-prescriptive exceptions to copyright) is addressed in Wikipedia here [[w:Fair_use|Fair use]] * There is a rejected Wikibooks policy or guideline proposal that should not be followed (but includes material of relevance): [[b:Wikibooks:Fair_use_policy|Fair use policy]] * There is a Wikipedia article (including several Wikipedia policies) which indirectly addresses the topic: [[w:Wikipedia:Non-free_content|Non-free content]] {{BookCat}} k7211xxlznmi9us3n04zujezcpncsbo 0 483068 4634205 4633789 2026-05-05T01:00:09Z JackBot 396820 Formatting, [[Special:UncategorizedPages]] 4634205 wikitext text/x-wiki This attemps at transposing to the closed Ruy Lopez but 4.Nc3 gives white a comftarable edge. {{BookCat}} m0n4bword8tjpx3c5s5nowaoo4fu52v 102 483084 4634164 4634051 2026-05-04T18:51:00Z Kittycataclysm 3371989 still incomplete 4634164 wikitext text/x-wiki {{recipesummary|category=Soup recipes|servings=6–8|time=10–15 minutes|difficulty=1}} {{Incomplete recipe|reason=still missing categories, quantities, and linking}} {{recipe}} | [[Cookbook:Soups|Soups]] '''Efo riro''' is a rich, savory vegetable soup from the Yoruba people of Southwestern Nigeria. Known for its vibrant flavor, and colorful presentation,it combines Leafly greens, pepper and assorted meats and fish in a deeply seasoned sauce. It is a staple of Yoruba cuisine and a symbol of home-style cooking across Nigeria. == Ingredients == * Sliced Spinach leaves (7-10 cups) * 7-10 pieces stock fish ear * Quarter cup of sliced [[Cookbook:Pepper|pepper]] * 1 cup of ground tatashe * assorted [[Cookbook:Meat|meat]] (1kg) * Sliced onions * Ground [[Cookbook:Crayfish|Crayfish]] * 2-3 cups of iru (locust beans) * smoked fish(2-3 medium) * [[Cookbook:Palm Oil|Palm oil]] (200ml) * 3 Seasoning cubes == Procedure == # Wash and season the meat with salt, onions, and seasoning cubes. Cook until tender and set aside. # Add stockfish and smoked fish to the cooked meat and simmer for about 10–15 minutes. # In another pot, heat the palm oil. Add sliced onions and fry lightly. # Add blended or sliced pepper and fry for about 10 minutes, stirring to prevent burning. # Add the cooked meat, fish, and some stock. Stir well and allow to simmer for 5 minutes. # Add crayfish and locust beans (iru), then cook for another 3–5 minutes. # Add the vegetables (spinach or ugu) and stir thoroughly. # Taste and adjust seasoning. Simmer for 3–5 minutes, then remove from heat. === Serving === Serve hot with swallow foods like pounded yam, eba, or fufu. [[Category:Very Easy recipes]] [[Category:Recipes for soup]] [[Category:Nigerian recipes]] 3l32sauezlbhsje4ngnd8gzyfkkakr1 102 483090 4634190 4633928 2026-05-04T21:42:02Z NiferO 3505520 Improved article 4634190 wikitext text/x-wiki {{Incomplete recipe|reason=missing recipe templates, missing appropriate linking, missing categories, redundant information, stylistic adjustments needed}} [[File:Ogbono soup with beef and roasted cow skin.jpg|thumb|Ogbono_soup_with_beef_and_roasted_cow_skin]] '''Ogbono soup''' is a popular Nigerian draw soup made from ground African mango seeds (Irvingia gabonensis). Known for its distinctive slippery, stretchy texture, it is widely eaten across Nigeria and is especially beloved in Igbo, Yoruba, and Edo households. == Ingredients == * 200 grams ground [[Cookbook:Ogbono|ogbono]] (African mango seeds) * 0.3 cups palm oil * 700 grams assorted meat (beef, shaki, ponmo) * 200 grams stockfish (panla), soaked and cleaned * 150 grams smoked fish, deboned * 3 tablespoons ground crayfish * 1 [[Cookbook:Onion|onion]] * 3 scotch bonnet pepper (rodo) * 1 tablespoons iru (locust bean) * 200 grams ugwu (fluted pumpkin leaves) or [[Cookbook:Spinach|spinach]], shredded * 2 seasoning cubes == Procedure == # Cook the meats: Season 700 grams assorted meat (beef, shaki, ponmo) with diced 1 onion, 1 of 2 seasoning cubes, and a pinch of 1 teaspoons salt. Add 200 grams stockfish (panla), soaked and cleaned midway. Cook on medium heat until tender. Reserve the meat stock. # Fry the ogbono: Heat 0.3 cups palm oil in a pot on medium heat. Add 1 tablespoons iru (locust bean) and stir. Add ground 200 grams ground ogbono (African mango seeds) directly into the hot palm oil. Stir continuously and fry until the ogbono dissolves completely into the oil and becomes fragrant about 5 minutes. # Add stock and pepper: Pour reserved meat stock gradually into the pot, stirring as you pour. Add blended or crushed 3 scotch bonnet pepper (rodo). Stir well and cover. Allow to cook on medium heat the soup will begin to draw and thicken. # Add proteins: Add cooked 700 grams assorted meat (beef, shaki, ponmo), 200 grams stockfish (panla), soaked and cleaned, and 150 grams smoked fish, deboned into the pot. Add 3 tablespoons ground crayfish and remaining 2 seasoning cubes. Stir gently. Taste and adjust salt. Simmer on low heat. # Add vegetables and finish: Stir in shredded 200 grams ugwu (fluted pumpkin leaves) or spinach, shredded. Cook for 3–5 minutes only. The soup should be thick, dark, and stretchy when lifted with a spoon. # Serve: Serve hot with pounded yam (iyán), eba, amala, fufu, or semovita. [[Category:Medium Difficulty recipes]] [[Category:Recipes for soup]] [[Category:Nigerian recipes]] kt3yfl4v6cmgikjk162xmwtzzbrknuj 3 483094 4634151 4634047 2026-05-04T18:40:29Z Kittycataclysm 3371989 /* Blanking templates */ Reply 4634151 wikitext text/x-wiki == Welcome to the Cookbook == {{mbox | type = | image = [[File:Foodlogo2.svg|40px]] | imageright = | style = | textstyle = | text = Hello and thank you for your recent contribution to the [[Cookbook:Table of Contents|Wikibooks Cookbook]]! When adding to the Cookbook, please make sure all content conforms to [[Cookbook:Policy|Cookbook policy]], including the [[Cookbook:Manual of Style|manual of style]] and standard page templates. Feel free to let me know if you need any help or have any questions! {{#ifeq: |||<br>'''Additional details:''' }} | small = | smallimage = | smallimageright = | smalltext = }} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:09, 3 May 2026 (UTC) :Alright , Thank you. [[User:Fatimah Bello|Fatimah Bello]] ([[User talk:Fatimah Bello|discuss]] • [[Special:Contributions/Fatimah Bello|contribs]]) 17:20, 3 May 2026 (UTC) ::@[[User:Fatimah Bello|Fatimah Bello]] additionally, I see that you are adding many incomplete recipes in bulk—could you please refrain from adding new recipes until you complete the recipes you have already added? Thank you, and let me know if you need any help! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:32, 3 May 2026 (UTC) :::Alright, Noted [[User:Fatimah Bello|Fatimah Bello]] ([[User talk:Fatimah Bello|discuss]] • [[Special:Contributions/Fatimah Bello|contribs]]) 17:57, 3 May 2026 (UTC) == Blanking templates == @[[User:Fatimah Bello|Fatimah Bello]] please do not blank widely-used templates without a good reason, as this is considered vandalism. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:20, 3 May 2026 (UTC) :Oooh, alright noted. :Thank you [[User:Fatimah Bello|Fatimah Bello]] ([[User talk:Fatimah Bello|discuss]] • [[Special:Contributions/Fatimah Bello|contribs]]) 19:38, 3 May 2026 (UTC) :I don't understand why there is temple ( Incomplete recipe) on the recipes I created, I have completed everything [[User:Fatimah Bello|Fatimah Bello]] ([[User talk:Fatimah Bello|discuss]] • [[Special:Contributions/Fatimah Bello|contribs]]) 10:01, 4 May 2026 (UTC) :Can you please show me an example of what a complete article looks like so I can do it the right way [[User:Fatimah Bello|Fatimah Bello]] ([[User talk:Fatimah Bello|discuss]] • [[Special:Contributions/Fatimah Bello|contribs]]) 10:21, 4 May 2026 (UTC) ::@[[User:Fatimah Bello|Fatimah Bello]] Recipes need to follow the [[Cookbook:Manual of Style|Cookbook manual of style]] and the [[Cookbook:Policy/Recipe template|recipe template]]. For each recipe marked as incomplete, I have listed the reason(s) in the box at the top of the page. I fixed one of your recipes according to the minimum requirements, and you can see the changes I made [[Special:Diff/4634149|at this link]] as an example. This should help you fix your other recipes. Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:40, 4 May 2026 (UTC) 1icefil670mj226wplkrzfmefwcl1w9 102 483097 4634149 4633953 2026-05-04T18:34:22Z Kittycataclysm 3371989 minimum formatting requirements 4634149 wikitext text/x-wiki __notoc__ {{Incomplete recipe|reason=missing recipe templates, missing appropriate links, missing categories, redundant information, ingredients missing in list, stylistic adjustments needed}}{{Recipe summary | Cuisine = Nigerian/Igbo | Difficulty = 2 }} {{Recipe}} '''Ofe Akwu''' is the Igbo name for palm fruit soup, a deeply flavourful soup made from fresh palm fruit extract. While closely related to Banga soup, the Igbo version has a distinct spice profile, lighter seasoning, and is traditionally served with pounded yam. It is a staple across Igbo communities in Anambra, Imo, Enugu, Abia, and Delta states. == Ingredients == * 1 [[Cookbook:Kilogram|kilogram]] fresh [[Cookbook:Oil Palm Fruit|palm fruits]] (or canned palm fruit concentrate) * 700 grams assorted meat (e.g. [[Cookbook:Beef|beef]], [[Cookbook:Tripe|shaki]], [[Cookbook:Goat|goat]], oxtail) * 1 [[Cookbook:Onion|onion]], [[Cookbook:Dice|diced]] * 2 [[Cookbook:Stock Cube|seasoning cubes]] * 1 [[Cookbook:Teaspoon|teaspoon]] [[Cookbook:Salt|salt]] * 200 grams [[Cookbook:Stockfish|stockfish]] (panla), soaked and cleaned * 1 tablespoon [[Cookbook:Ogiri|ogiri okpei]] (fermented locust bean paste) * 1 teaspoons ground [[Cookbook:Ehuru|ehuru]] (African nutmeg) * 3 Scotch bonnet [[Cookbook:Chiles|chile]] peppers, [[Cookbook:Puréeing|puréed]] * 150 grams [[Cookbook:Dryfish|smoked fish]], deboned * 3 tablespoons [[Cookbook:Ground Crayfish|ground crayfish]] * 150 grams [[Cookbook:Uziza|uziza]] leaf or [[Cookbook:Bitterleaf|bitter leaf]], shredded == Equipment == * [[Cookbook:Cookware|Cooking pots]] * Stirring implement * [[Cookbook:Mortar and Pestle|Mortar and pestle]] * [[Cookbook:Sieve|Sieve]] or other straining tool == Procedure == # [[Cookbook:Boiling|Boil]] the palm fruits in water for 20–25 minutes until soft, then drain. Pound the cooked fruits in a mortar to loosen the flesh from the seeds. Add warm water{{How much}} and squeeze the mixture through a sieve. Discard the fibre and seeds. If using canned concentrate, dilute as directed. # Season the meat with onion, 1 seasoning cube, and salt. Add stockfish midway through cooking. Cook on medium heat until tender. Reserve the meat stock. # Pour palm fruit extract into a pot. Cook on medium heat, stirring occasionally, until it thickens and oil rises to the surface about 15–20 minutes # Add ogiri okpei, ehuru, and puréed chiles. Stir well. Add reserved cooked meat and stock, smoked fish, ground crayfish, and the remaining seasoning cube. Stir and [[Cookbook:Simmering|simmer]] on medium heat. # Taste and adjust with salt. The soup should be thick, rich, and deeply orange-red. If too thick, add a little warm water and stir. # Stir in uziza leaf. Cook for 3–5 minutes only. Serve hot with pounded yam (iyán), eba, or fufu. [[Category:Medium Difficulty recipes]] [[Category:Recipes for soup]] [[Category:Recipes using oil palm fruit]] [[Category:Recipes using meat]] [[Category:Recipes using onion]] [[Category:Recipes using dehydrated broth]] [[Category:Recipes using salt]] [[Category:Recipes using stockfish]] [[Category:Recipes using dryfish]] [[Category:Recipes using ogiri]] [[Category:Recipes using calabash nutmeg]] [[Category:Recipes using chile]] [[Category:Recipes using ground crayfish]] [[Category:Recipes using bitterleaf]] [[Category:Recipes using ashanti pepper]] [[Category:Igbo recipes]] 06alh5w82n6u1rsflj2loe9kiejyc3g 4634154 4634149 2026-05-04T18:42:07Z Kittycataclysm 3371989 4634154 wikitext text/x-wiki __notoc__ {{Incomplete recipe|reason=}}{{Recipe summary | Cuisine = Nigerian/Igbo | Difficulty = 2 }} {{Recipe}} '''Ofe Akwu''' is the Igbo name for palm fruit soup, a deeply flavourful soup made from fresh palm fruit extract. While closely related to Banga soup, the Igbo version has a distinct spice profile, lighter seasoning, and is traditionally served with pounded yam. It is a staple across Igbo communities in Anambra, Imo, Enugu, Abia, and Delta states. == Ingredients == * 1 [[Cookbook:Kilogram|kilogram]] fresh [[Cookbook:Oil Palm Fruit|palm fruits]] (or canned palm fruit concentrate) * 700 grams assorted meat (e.g. [[Cookbook:Beef|beef]], [[Cookbook:Tripe|shaki]], [[Cookbook:Goat|goat]], oxtail) * 1 [[Cookbook:Onion|onion]], [[Cookbook:Dice|diced]] * 2 [[Cookbook:Stock Cube|seasoning cubes]] * 1 [[Cookbook:Teaspoon|teaspoon]] [[Cookbook:Salt|salt]] * 200 grams [[Cookbook:Stockfish|stockfish]] (panla), soaked and cleaned * 1 tablespoon [[Cookbook:Ogiri|ogiri okpei]] (fermented locust bean paste) * 1 teaspoons ground [[Cookbook:Ehuru|ehuru]] (African nutmeg) * 3 Scotch bonnet [[Cookbook:Chiles|chile]] peppers, [[Cookbook:Puréeing|puréed]] * 150 grams [[Cookbook:Dryfish|smoked fish]], deboned * 3 tablespoons [[Cookbook:Ground Crayfish|ground crayfish]] * 150 grams [[Cookbook:Uziza|uziza]] leaf or [[Cookbook:Bitterleaf|bitter leaf]], shredded == Equipment == * [[Cookbook:Cookware|Cooking pots]] * Stirring implement * [[Cookbook:Mortar and Pestle|Mortar and pestle]] * [[Cookbook:Sieve|Sieve]] or other straining tool == Procedure == # [[Cookbook:Boiling|Boil]] the palm fruits in water for 20–25 minutes until soft, then drain. Pound the cooked fruits in a mortar to loosen the flesh from the seeds. Add warm water{{How much}} and squeeze the mixture through a sieve. Discard the fibre and seeds. If using canned concentrate, dilute as directed. # Season the meat with onion, 1 seasoning cube, and salt. Add stockfish midway through cooking. Cook on medium heat until tender. Reserve the meat stock. # Pour palm fruit extract into a pot. Cook on medium heat, stirring occasionally, until it thickens and oil rises to the surface about 15–20 minutes # Add ogiri okpei, ehuru, and puréed chiles. Stir well. Add reserved cooked meat and stock, smoked fish, ground crayfish, and the remaining seasoning cube. Stir and [[Cookbook:Simmering|simmer]] on medium heat. # Taste and adjust with salt. The soup should be thick, rich, and deeply orange-red. If too thick, add a little warm water and stir. # Stir in uziza leaf. Cook for 3–5 minutes only. Serve hot with pounded yam (iyán), eba, or fufu. [[Category:Medium Difficulty recipes]] [[Category:Recipes for soup]] [[Category:Recipes using oil palm fruit]] [[Category:Recipes using meat]] [[Category:Recipes using onion]] [[Category:Recipes using dehydrated broth]] [[Category:Recipes using salt]] [[Category:Recipes using stockfish]] [[Category:Recipes using dryfish]] [[Category:Recipes using ogiri]] [[Category:Recipes using calabash nutmeg]] [[Category:Recipes using chile]] [[Category:Recipes using ground crayfish]] [[Category:Recipes using bitterleaf]] [[Category:Recipes using ashanti pepper]] [[Category:Igbo recipes]] r1ngsl6bkm5z6uk54pzgb1gry66xrer 4634156 4634154 2026-05-04T18:43:18Z Kittycataclysm 3371989 4634156 wikitext text/x-wiki __notoc__ {{Incomplete recipe|reason=Unclear directions (cooking meat)}}{{Recipe summary | Cuisine = Nigerian/Igbo | Difficulty = 2 }} {{Recipe}} '''Ofe Akwu''' is the Igbo name for palm fruit soup, a deeply flavourful soup made from fresh palm fruit extract. While closely related to Banga soup, the Igbo version has a distinct spice profile, lighter seasoning, and is traditionally served with pounded yam. It is a staple across Igbo communities in Anambra, Imo, Enugu, Abia, and Delta states. == Ingredients == * 1 [[Cookbook:Kilogram|kilogram]] fresh [[Cookbook:Oil Palm Fruit|palm fruits]] (or canned palm fruit concentrate) * 700 grams assorted meat (e.g. [[Cookbook:Beef|beef]], [[Cookbook:Tripe|shaki]], [[Cookbook:Goat|goat]], oxtail) * 1 [[Cookbook:Onion|onion]], [[Cookbook:Dice|diced]] * 2 [[Cookbook:Stock Cube|seasoning cubes]] * 1 [[Cookbook:Teaspoon|teaspoon]] [[Cookbook:Salt|salt]] * 200 grams [[Cookbook:Stockfish|stockfish]] (panla), soaked and cleaned * 1 tablespoon [[Cookbook:Ogiri|ogiri okpei]] (fermented locust bean paste) * 1 teaspoons ground [[Cookbook:Ehuru|ehuru]] (African nutmeg) * 3 Scotch bonnet [[Cookbook:Chiles|chile]] peppers, [[Cookbook:Puréeing|puréed]] * 150 grams [[Cookbook:Dryfish|smoked fish]], deboned * 3 tablespoons [[Cookbook:Ground Crayfish|ground crayfish]] * 150 grams [[Cookbook:Uziza|uziza]] leaf or [[Cookbook:Bitterleaf|bitter leaf]], shredded == Equipment == * [[Cookbook:Cookware|Cooking pots]] * Stirring implement * [[Cookbook:Mortar and Pestle|Mortar and pestle]] * [[Cookbook:Sieve|Sieve]] or other straining tool == Procedure == # [[Cookbook:Boiling|Boil]] the palm fruits in water for 20–25 minutes until soft, then drain. Pound the cooked fruits in a mortar to loosen the flesh from the seeds. Add warm water{{How much}} and squeeze the mixture through a sieve. Discard the fibre and seeds. If using canned concentrate, dilute as directed. # Season the meat with onion, 1 seasoning cube, and salt. Add stockfish midway through cooking. Cook on medium heat until tender. Reserve the meat stock. # Pour palm fruit extract into a pot. Cook on medium heat, stirring occasionally, until it thickens and oil rises to the surface about 15–20 minutes # Add ogiri okpei, ehuru, and puréed chiles. Stir well. Add reserved cooked meat and stock, smoked fish, ground crayfish, and the remaining seasoning cube. Stir and [[Cookbook:Simmering|simmer]] on medium heat. # Taste and adjust with salt. The soup should be thick, rich, and deeply orange-red. If too thick, add a little warm water and stir. # Stir in uziza leaf. Cook for 3–5 minutes only. Serve hot with pounded yam (iyán), eba, or fufu. [[Category:Medium Difficulty recipes]] [[Category:Recipes for soup]] [[Category:Recipes using oil palm fruit]] [[Category:Recipes using meat]] [[Category:Recipes using onion]] [[Category:Recipes using dehydrated broth]] [[Category:Recipes using salt]] [[Category:Recipes using stockfish]] [[Category:Recipes using dryfish]] [[Category:Recipes using ogiri]] [[Category:Recipes using calabash nutmeg]] [[Category:Recipes using chile]] [[Category:Recipes using ground crayfish]] [[Category:Recipes using bitterleaf]] [[Category:Recipes using ashanti pepper]] [[Category:Igbo recipes]] i94i2x5uo8fu9urcc1jurvccq4ph5bh 0 483104 4634208 4633988 2026-05-05T01:00:11Z JackBot 396820 Formatting, [[Special:UncategorizedPages]] 4634208 wikitext text/x-wiki == The norms of texting in Japan == ==== American vs. Japanese Social Norms ​ ==== ==== Japan Perspective on Texting ​ ==== ==== Texting Etiquette​ ==== ==== Slang and Emoji Usage ==== Text-based communication in Japan relies heavily on nuanced slang and a highly developed system of visual expression. Similarly to American culture Japanese netizens use "slang", informal and trendy language, to communicate amongst friends and peers especially for the younger generations. In western contexts emojis are often used for emphasis or tone, Japanese messaging culture integrates them as essential components of meaning. This practice can be traced back to the early development of emoji (or kaomoji) in Japan, particularly through mobile platforms like LINE, where visual symbols became standardized forms of emotional expression. Japanese slang in texting tends to be context-dependent and often reflects pop culture. Due to worldwide impact of roman letters even in Japanese mobile keyboards, slang terms utilize and even combined Japanese language (kanji, katakana, hiragana) with roman letters. For example, a popular slang is "w", frequently used to indicate laughter, derived from the word “笑い” (warai) meaning to laugh. In context people use this on its own or at the end of phrases, it can also be denoted as "www"~ to imply more laughter. Slang is ever evolving and derived from common phrases and even existing slang. Such as "草" (kusa) with literal meaning "grass" however the prevenance of using multiple w's (wwwwww) looks like grass growing on the screen. There are many more slangs coming from onomatopoeia, media references, and shortening formal phrases. Here are some popular examples below in table 1 {| class="wikitable" |+ !Slang !Word !Translation !Context |- |Jk |女子高生 (Joshikōsei) |high school girl |sexual expression referring to younger girl |- |888 |パチ (pachi) |Onomatopoeia for clapping |to denote clapping or more 8's for more clapping |- |DKQ |ドキュン (Donkyun) |idiot who acts without any thinking |came from a variety show called ''Mugumi! Dokyun'', which gave life advice to struggling couples |- |乙 (''otsu'') |お疲れ様です (''otsukare sama desu'') |Thank you for your hard work. |Thanking or greeting like “Hi” or "Bye" |} Emojis (emoji/kaomoji) help convey feelings, reducing misunderstanding in digital communication. These are used to feel less direct or harsh, aligning with Japanese norms, signally friendliness and/or attentiveness. Unlike western emojis, the emojis are often much more detailed and expressive which more accurately portray tone. Japanese mobile keyboard has its set of its own ''kaomoji'' ''or'' emoticons created using keyboard characters in addition to standard emojis. Table 2 show common types of kaomojis. {| class="wikitable" |+ !Postive !Sad !Angry !Greetings !Actions |- |(* ^ ω ^) |(╥﹏╥) |(＃Д´) |＼(⌒▽⌒) |ε=ε=ε=ε=┌(;￣▽￣)┘ |- |＼(￣▽￣)／ |(╯︵╰,) |┌∩┐(◣_◢)┌∩┐ |(＠´ー)ﾉﾞ |(＿ ＿*) Z z z |- |(/▽＼)｡o○♡ |(ﾉД) |(╬益´) |＼(^o^)／ |ヾ(´〇`)ﾉ♪♪♪ |} ==== LINE app ==== {{BookCat}} qbafc0ed1u1hg667mz2cez12mw9p4l0 0 483105 4634116 4633999 2026-05-04T16:35:31Z Yav9zb 3574742 /* Japan Perspective on Texting */ 4634116 wikitext text/x-wiki == The norms of texting in Japan == ==== American vs. Japanese Social Norms ==== ==== Japan Perspective on Texting ==== Japanese texting norms are shaped by the country's high-context communication style, which prioritizes indirectness, harmony, and consideration for others' feelings.<ref>Gudykunst, W. B., & Nishida, T. (1999). The influence of cultural variability on perceptions of communication behavior. ''Social Behavior and Personality'', 27(5), 523–534.</ref> Unlike American texting culture, where fast replies often signal engagement, Japanese users tend to value thoughtfulness over speed. A delayed response is not typically read as disinterest but as a sign of respect, an indication that the sender is carefully considering what to say rather than firing off a fast reply.<ref>Liu, L. (2020). How fast should I reply to the text? ''Medium''. https://lillian-liu.medium.com/how-fast-should-i-reply-the-text-8f4e01310b0</ref> This norm is especially pronounced in dating contexts, where slow texting is widely understood as a strategy for building attraction and anticipation. Replying too quickly can come across as desperate or overeager, while measured pacing creates tension and signals emotional composure.<ref>Kato, F., & Hjorth, L. (2014). Understanding the role of mobile social media in intimate relationships. ''Computers in Human Behavior'', 49, 560–567. https://doi.org/10.1016/j.chb.2014.11.047</ref> Japanese commentators frequently compare texting to a tennis match: each message carries an implicit obligation to respond, so a slower response reduces social pressure on both sides and allows each participant to engage on their own terms. Emojis, ''kaomoji'' (顔文字), and LINE stickers play a critical role in softening the tone of messages, helping users avoid the directness that Japanese communication norms discourage. These visual elements signal friendliness and attentiveness without requiring explicit verbal warmth, making them essential tools for navigating the implicit, indirect style of Japanese digital communication.<ref>Katsuno, H., & Yano, C. R. (2002). Face to face: On-line subjectivity in contemporary Japan. ''Asian Studies Review'', 26(2), 205–231.</ref> ==== Texting Etiquette ==== ==== Slang and Emoji Usage ==== Text-based communication in Japan relies heavily on nuanced slang and a highly developed system of visual expression. Similarly to American culture Japanese netizens use "slang", informal and trendy language, to communicate amongst friends and peers especially for the younger generations<ref>{{Cite web |date=2023-11-29 |title=Learn Japanese Slang With These 50 Examples |url=https://preply.com/en/blog/japanese-slang/ |access-date=2026-05-03 |language=en}}</ref>. In western contexts emojis are often used for emphasis or tone, Japanese messaging culture integrates them as essential components of meaning. This practice can be traced back to the early development of emoji (or kaomoji) in Japan, particularly through mobile platforms like LINE, where visual symbols became standardized forms of emotional expression. Japanese slang in texting tends to be context-dependent and often reflects pop culture. Due to worldwide impact of roman letters even in Japanese mobile keyboards, slang terms utilize and even combined Japanese language (kanji, katakana, hiragana) with roman letters. For example, a popular slang is "w", frequently used to indicate laughter, derived from the word “笑い” (warai) meaning to laugh<ref name=":0">{{Cite web |last=Deutsch |first=Anna |date=2025-12-04 |title=21 Japanese Internet Slang & Texting Terms |url=https://cotoacademy.com/japanese-internet-slang-and-texting-terms-kaomoji/ |access-date=2026-05-03 |website=Coto Japanese Academy |language=en-US}}</ref>. In context people use this on its own or at the end of phrases, it can also be denoted as "www"~ to imply more laughter. Slang is ever evolving and derived from common phrases and even existing slang. Such as "草" (kusa) with literal meaning "grass" however the prevenance of using multiple w's (wwwwww) looks like grass growing on the screen<ref name=":0" />. There are many more slangs coming from onomatopoeia, media references, and shortening formal phrases. Here are some popular examples below in table 1 {| class="wikitable" |+ !Slang !Word !Translation !Context |- |Jk<ref name=":1">{{Cite web |last=JapanesePod101.com |date=2019-07-23 |title=Our Guide to Japanese Internet & Text Slang |url=https://www.japanesepod101.com/blog/2019/07/23/japanese-text-slang/ |access-date=2026-05-03 |website=JapanesePod101.com Blog |language=en}}</ref> |女子高生 (Joshikōsei) |high school girl |sexual expression referring to younger girl |- |888<ref name=":0" /> |パチ (pachi) |Onomatopoeia for clapping |to denote clapping or more 8's for more clapping |- |DKQ<ref name=":1" /> |ドキュン (Donkyun) |idiot who acts without any thinking |came from a variety show called ''Mugumi! Dokyun'', which gave life advice to struggling couples |- |乙 (''otsu'')<ref name=":0" /> |お疲れ様です (''otsukare sama desu'') |Thank you for your hard work. |Thanking or greeting like “Hi” or "Bye" |} Emojis (emoji/kaomoji) help convey feelings, reducing misunderstanding in digital communication. These are used to feel less direct or harsh, aligning with Japanese norms, signally friendliness and/or attentiveness. Unlike western emojis, the emojis are often much more detailed and expressive which more accurately portray tone. Japanese mobile keyboard has its set of its own ''kaomoji'' ''or'' emoticons created using keyboard characters in addition to standard emojis. Table 2 show common types of kaomojis<ref>{{Cite web |title=Kaomoji (顔文字): Japanese Emoticons |url=https://www.kaomoji.co/pages/emoji |access-date=2026-05-03 |website=Kaomoji ® Official |language=en}}</ref>. {| class="wikitable" |+ !Postive !Sad !Angry !Greetings !Actions |- |(* ^ ω ^) |(╥﹏╥) |(＃Д´) |＼(⌒▽⌒) |ε=ε=ε=ε=┌(;￣▽￣)┘ |- |＼(￣▽￣)／ |(╯︵╰,) |┌∩┐(◣_◢)┌∩┐ |(＠´ー)ﾉﾞ |(＿ ＿*) Z z z |- |(/▽＼)｡o○♡ |(ﾉД) |(╬益´) |＼(^o^)／ |ヾ(´〇`)ﾉ♪♪♪ |} ==== LINE app ==== == References == {{BookCat}} d787haid4an17tpev4jp8kw60iim5dt 4634120 4634116 2026-05-04T17:08:52Z ~2026-27050-27 3581225 /* Texting Etiquette */ 4634120 wikitext text/x-wiki == The norms of texting in Japan == ==== American vs. Japanese Social Norms ==== ==== Japan Perspective on Texting ==== Japanese texting norms are shaped by the country's high-context communication style, which prioritizes indirectness, harmony, and consideration for others' feelings.<ref>Gudykunst, W. B., & Nishida, T. (1999). The influence of cultural variability on perceptions of communication behavior. ''Social Behavior and Personality'', 27(5), 523–534.</ref> Unlike American texting culture, where fast replies often signal engagement, Japanese users tend to value thoughtfulness over speed. A delayed response is not typically read as disinterest but as a sign of respect, an indication that the sender is carefully considering what to say rather than firing off a fast reply.<ref>Liu, L. (2020). How fast should I reply to the text? ''Medium''. https://lillian-liu.medium.com/how-fast-should-i-reply-the-text-8f4e01310b0</ref> This norm is especially pronounced in dating contexts, where slow texting is widely understood as a strategy for building attraction and anticipation. Replying too quickly can come across as desperate or overeager, while measured pacing creates tension and signals emotional composure.<ref>Kato, F., & Hjorth, L. (2014). Understanding the role of mobile social media in intimate relationships. ''Computers in Human Behavior'', 49, 560–567. https://doi.org/10.1016/j.chb.2014.11.047</ref> Japanese commentators frequently compare texting to a tennis match: each message carries an implicit obligation to respond, so a slower response reduces social pressure on both sides and allows each participant to engage on their own terms. Emojis, ''kaomoji'' (顔文字), and LINE stickers play a critical role in softening the tone of messages, helping users avoid the directness that Japanese communication norms discourage. These visual elements signal friendliness and attentiveness without requiring explicit verbal warmth, making them essential tools for navigating the implicit, indirect style of Japanese digital communication.<ref>Katsuno, H., & Yano, C. R. (2002). Face to face: On-line subjectivity in contemporary Japan. ''Asian Studies Review'', 26(2), 205–231.</ref> ==== Texting Etiquette ==== Text messaging practices in Japan reflect the nation’s cultural values. Implicit rules guide digital communication, shaping both timing and manner of interaction. Research indicates that Japanese digital communication integrates traditional linguistic norms with modern technology, thereby influencing the conveyance of tone and intent in text-based exchanges.<ref>Kobayashi, T. (2014). Tele-Cocooning: Mobile Texting and Social Scope. Journal of Computer-Mediated Communication.</ref> Politeness is a central feature of Japanese texting, including in casual interactions. Messages frequently incorporate polite language, especially when addressing individuals of higher status, such as supervisors. It is customary to begin with a brief greeting or acknowledgment and to conclude with a soft closing, such as “よろしくお願いします” (“thank you in advance”), particularly in semi-formal exchanges. Research on messaging behavior indicates that Japanese users structure their texts deliberately to ensure clarity and maintain social harmony. They employ greetings, contextual framing, and specific sentence endings to convey nuance and emotion<ref>Lee, Y. (2023). Structure of LINE Chat Openings. Japanese Language Education Research.</ref><ref>Park, J. (2013). Sentence Closings in Japanese Mobile Email. Discourse, Context & Media.</ref> Timeliness is highly valued in Japanese texting culture, although expectations differ depending on the nature of the relationship. Quick responses are appreciated among friends, whereas prompt replies in professional contexts signify respect. As many messaging platforms display read receipts, delayed responses without acknowledgment are often perceived as inconsiderate.<ref>Soeda, E. et al. (2016). Analysis of LINE Communication. Japanese Language Education Methods.</ref> The level of formality in Japanese texting varies depending on social context. Casual language is typically used among friends and peers, while honorific language (Keigo) is expected in professional or hierarchical relationships. Even in digital communication, traditional linguistic norms remain influential, though they may be adapted for efficiency and informality. Switching between styles based on context is common and reflects sensitivity to social roles.<ref>Nagai, N. et al. (2025). Effects of Speech Level Shift in Japanese Text Chat. Applied Sciences.</ref> ==== Slang and Emoji Usage ==== Text-based communication in Japan relies heavily on nuanced slang and a highly developed system of visual expression. Similarly to American culture Japanese netizens use "slang", informal and trendy language, to communicate amongst friends and peers especially for the younger generations<ref>{{Cite web |date=2023-11-29 |title=Learn Japanese Slang With These 50 Examples |url=https://preply.com/en/blog/japanese-slang/ |access-date=2026-05-03 |language=en}}</ref>. In western contexts emojis are often used for emphasis or tone, Japanese messaging culture integrates them as essential components of meaning. This practice can be traced back to the early development of emoji (or kaomoji) in Japan, particularly through mobile platforms like LINE, where visual symbols became standardized forms of emotional expression. Japanese slang in texting tends to be context-dependent and often reflects pop culture. Due to worldwide impact of roman letters even in Japanese mobile keyboards, slang terms utilize and even combined Japanese language (kanji, katakana, hiragana) with roman letters. For example, a popular slang is "w", frequently used to indicate laughter, derived from the word “笑い” (warai) meaning to laugh<ref name=":0">{{Cite web |last=Deutsch |first=Anna |date=2025-12-04 |title=21 Japanese Internet Slang & Texting Terms |url=https://cotoacademy.com/japanese-internet-slang-and-texting-terms-kaomoji/ |access-date=2026-05-03 |website=Coto Japanese Academy |language=en-US}}</ref>. In context people use this on its own or at the end of phrases, it can also be denoted as "www"~ to imply more laughter. Slang is ever evolving and derived from common phrases and even existing slang. Such as "草" (kusa) with literal meaning "grass" however the prevenance of using multiple w's (wwwwww) looks like grass growing on the screen<ref name=":0" />. There are many more slangs coming from onomatopoeia, media references, and shortening formal phrases. Here are some popular examples below in table 1 {| class="wikitable" |+ !Slang !Word !Translation !Context |- |Jk<ref name=":1">{{Cite web |last=JapanesePod101.com |date=2019-07-23 |title=Our Guide to Japanese Internet & Text Slang |url=https://www.japanesepod101.com/blog/2019/07/23/japanese-text-slang/ |access-date=2026-05-03 |website=JapanesePod101.com Blog |language=en}}</ref> |女子高生 (Joshikōsei) |high school girl |sexual expression referring to younger girl |- |888<ref name=":0" /> |パチ (pachi) |Onomatopoeia for clapping |to denote clapping or more 8's for more clapping |- |DKQ<ref name=":1" /> |ドキュン (Donkyun) |idiot who acts without any thinking |came from a variety show called ''Mugumi! Dokyun'', which gave life advice to struggling couples |- |乙 (''otsu'')<ref name=":0" /> |お疲れ様です (''otsukare sama desu'') |Thank you for your hard work. |Thanking or greeting like “Hi” or "Bye" |} Emojis (emoji/kaomoji) help convey feelings, reducing misunderstanding in digital communication. These are used to feel less direct or harsh, aligning with Japanese norms, signally friendliness and/or attentiveness. Unlike western emojis, the emojis are often much more detailed and expressive which more accurately portray tone. Japanese mobile keyboard has its set of its own ''kaomoji'' ''or'' emoticons created using keyboard characters in addition to standard emojis. Table 2 show common types of kaomojis<ref>{{Cite web |title=Kaomoji (顔文字): Japanese Emoticons |url=https://www.kaomoji.co/pages/emoji |access-date=2026-05-03 |website=Kaomoji ® Official |language=en}}</ref>. {| class="wikitable" |+ !Postive !Sad !Angry !Greetings !Actions |- |(* ^ ω ^) |(╥﹏╥) |(＃Д´) |＼(⌒▽⌒) |ε=ε=ε=ε=┌(;￣▽￣)┘ |- |＼(￣▽￣)／ |(╯︵╰,) |┌∩┐(◣_◢)┌∩┐ |(＠´ー)ﾉﾞ |(＿ ＿*) Z z z |- |(/▽＼)｡o○♡ |(ﾉД) |(╬益´) |＼(^o^)／ |ヾ(´〇`)ﾉ♪♪♪ |} ==== LINE app ==== == References == {{BookCat}} 32jvfmyaab6r3cvf591nqltz2daez69 4634138 4634120 2026-05-04T17:56:40Z Dorkusdomingus 3581221 Added line app section 4634138 wikitext text/x-wiki == The norms of texting in Japan == ==== American vs. Japanese Social Norms ==== ==== Japan Perspective on Texting ==== Japanese texting norms are shaped by the country's high-context communication style, which prioritizes indirectness, harmony, and consideration for others' feelings.<ref>Gudykunst, W. B., & Nishida, T. (1999). The influence of cultural variability on perceptions of communication behavior. ''Social Behavior and Personality'', 27(5), 523–534.</ref> Unlike American texting culture, where fast replies often signal engagement, Japanese users tend to value thoughtfulness over speed. A delayed response is not typically read as disinterest but as a sign of respect, an indication that the sender is carefully considering what to say rather than firing off a fast reply.<ref>Liu, L. (2020). How fast should I reply to the text? ''Medium''. https://lillian-liu.medium.com/how-fast-should-i-reply-the-text-8f4e01310b0</ref> This norm is especially pronounced in dating contexts, where slow texting is widely understood as a strategy for building attraction and anticipation. Replying too quickly can come across as desperate or overeager, while measured pacing creates tension and signals emotional composure.<ref>Kato, F., & Hjorth, L. (2014). Understanding the role of mobile social media in intimate relationships. ''Computers in Human Behavior'', 49, 560–567. https://doi.org/10.1016/j.chb.2014.11.047</ref> Japanese commentators frequently compare texting to a tennis match: each message carries an implicit obligation to respond, so a slower response reduces social pressure on both sides and allows each participant to engage on their own terms. Emojis, ''kaomoji'' (顔文字), and LINE stickers play a critical role in softening the tone of messages, helping users avoid the directness that Japanese communication norms discourage. These visual elements signal friendliness and attentiveness without requiring explicit verbal warmth, making them essential tools for navigating the implicit, indirect style of Japanese digital communication.<ref>Katsuno, H., & Yano, C. R. (2002). Face to face: On-line subjectivity in contemporary Japan. ''Asian Studies Review'', 26(2), 205–231.</ref> ==== Texting Etiquette ==== Text messaging practices in Japan reflect the nation’s cultural values. Implicit rules guide digital communication, shaping both timing and manner of interaction. Research indicates that Japanese digital communication integrates traditional linguistic norms with modern technology, thereby influencing the conveyance of tone and intent in text-based exchanges.<ref>Kobayashi, T. (2014). Tele-Cocooning: Mobile Texting and Social Scope. Journal of Computer-Mediated Communication.</ref> Politeness is a central feature of Japanese texting, including in casual interactions. Messages frequently incorporate polite language, especially when addressing individuals of higher status, such as supervisors. It is customary to begin with a brief greeting or acknowledgment and to conclude with a soft closing, such as “よろしくお願いします” (“thank you in advance”), particularly in semi-formal exchanges. Research on messaging behavior indicates that Japanese users structure their texts deliberately to ensure clarity and maintain social harmony. They employ greetings, contextual framing, and specific sentence endings to convey nuance and emotion<ref>Lee, Y. (2023). Structure of LINE Chat Openings. Japanese Language Education Research.</ref><ref>Park, J. (2013). Sentence Closings in Japanese Mobile Email. Discourse, Context & Media.</ref> Timeliness is highly valued in Japanese texting culture, although expectations differ depending on the nature of the relationship. Quick responses are appreciated among friends, whereas prompt replies in professional contexts signify respect. As many messaging platforms display read receipts, delayed responses without acknowledgment are often perceived as inconsiderate.<ref>Soeda, E. et al. (2016). Analysis of LINE Communication. Japanese Language Education Methods.</ref> The level of formality in Japanese texting varies depending on social context. Casual language is typically used among friends and peers, while honorific language (Keigo) is expected in professional or hierarchical relationships. Even in digital communication, traditional linguistic norms remain influential, though they may be adapted for efficiency and informality. Switching between styles based on context is common and reflects sensitivity to social roles.<ref>Nagai, N. et al. (2025). Effects of Speech Level Shift in Japanese Text Chat. Applied Sciences.</ref> ==== Slang and Emoji Usage ==== Text-based communication in Japan relies heavily on nuanced slang and a highly developed system of visual expression. Similarly to American culture Japanese netizens use "slang", informal and trendy language, to communicate amongst friends and peers especially for the younger generations<ref>{{Cite web |date=2023-11-29 |title=Learn Japanese Slang With These 50 Examples |url=https://preply.com/en/blog/japanese-slang/ |access-date=2026-05-03 |language=en}}</ref>. In western contexts emojis are often used for emphasis or tone, Japanese messaging culture integrates them as essential components of meaning. This practice can be traced back to the early development of emoji (or kaomoji) in Japan, particularly through mobile platforms like LINE, where visual symbols became standardized forms of emotional expression. Japanese slang in texting tends to be context-dependent and often reflects pop culture. Due to worldwide impact of roman letters even in Japanese mobile keyboards, slang terms utilize and even combined Japanese language (kanji, katakana, hiragana) with roman letters. For example, a popular slang is "w", frequently used to indicate laughter, derived from the word “笑い” (warai) meaning to laugh<ref name=":0">{{Cite web |last=Deutsch |first=Anna |date=2025-12-04 |title=21 Japanese Internet Slang & Texting Terms |url=https://cotoacademy.com/japanese-internet-slang-and-texting-terms-kaomoji/ |access-date=2026-05-03 |website=Coto Japanese Academy |language=en-US}}</ref>. In context people use this on its own or at the end of phrases, it can also be denoted as "www"~ to imply more laughter. Slang is ever evolving and derived from common phrases and even existing slang. Such as "草" (kusa) with literal meaning "grass" however the prevenance of using multiple w's (wwwwww) looks like grass growing on the screen<ref name=":0" />. There are many more slangs coming from onomatopoeia, media references, and shortening formal phrases. Here are some popular examples below in table 1 {| class="wikitable" |+ !Slang !Word !Translation !Context |- |Jk<ref name=":1">{{Cite web |last=JapanesePod101.com |date=2019-07-23 |title=Our Guide to Japanese Internet & Text Slang |url=https://www.japanesepod101.com/blog/2019/07/23/japanese-text-slang/ |access-date=2026-05-03 |website=JapanesePod101.com Blog |language=en}}</ref> |女子高生 (Joshikōsei) |high school girl |sexual expression referring to younger girl |- |888<ref name=":0" /> |パチ (pachi) |Onomatopoeia for clapping |to denote clapping or more 8's for more clapping |- |DKQ<ref name=":1" /> |ドキュン (Donkyun) |idiot who acts without any thinking |came from a variety show called ''Mugumi! Dokyun'', which gave life advice to struggling couples |- |乙 (''otsu'')<ref name=":0" /> |お疲れ様です (''otsukare sama desu'') |Thank you for your hard work. |Thanking or greeting like “Hi” or "Bye" |} Emojis (emoji/kaomoji) help convey feelings, reducing misunderstanding in digital communication. These are used to feel less direct or harsh, aligning with Japanese norms, signally friendliness and/or attentiveness. Unlike western emojis, the emojis are often much more detailed and expressive which more accurately portray tone. Japanese mobile keyboard has its set of its own ''kaomoji'' ''or'' emoticons created using keyboard characters in addition to standard emojis. Table 2 show common types of kaomojis<ref>{{Cite web |title=Kaomoji (顔文字): Japanese Emoticons |url=https://www.kaomoji.co/pages/emoji |access-date=2026-05-03 |website=Kaomoji ® Official |language=en}}</ref>. {| class="wikitable" |+ !Postive !Sad !Angry !Greetings !Actions |- |(* ^ ω ^) |(╥﹏╥) |(＃Д´) |＼(⌒▽⌒) |ε=ε=ε=ε=┌(;￣▽￣)┘ |- |＼(￣▽￣)／ |(╯︵╰,) |┌∩┐(◣_◢)┌∩┐ |(＠´ー)ﾉﾞ |(＿ ＿*) Z z z |- |(/▽＼)｡o○♡ |(ﾉД) |(╬益´) |＼(^o^)／ |ヾ(´〇`)ﾉ♪♪♪ |} ==== LINE app ==== LINE is the most popular instant messaging app used in Japan with 78% percent of the population (97 million people) as monthly users <ref>{{Cite web |title=LINE user trends 2025: The largest messaging app in Japan {{!}} TAMLO |url=https://tam-tamlo.com/en/307 |access-date=2026-05-04 |language=en}}</ref>. The app is works similar to WhatsApp allowing messaging and calling over the internet, but the app's support for stickers commonly used in texting make it unique. Stickers often used in texting accounting for 9% of all messages as of March 2016 and are commonly used to convey complex emotions, soften or intensify tone, or even express criticism that would feel too harsh if written down <ref>{{Cite journal |last=Oberwinkler |first=Michaela |date=2023 |title=Digital Stickers in Japanese LINE Communication |url=https://doi.org/10.1453/1614-0885-2-2023-15758 |journal=IMAGE |volume=19 |issue=2 |pages=238–262 |doi=10.1453/1614-0885-2-2023-15758 |issn=1614-0885}}</ref>. As stickers are widely prevelent, LINE provides basic default stickers with the app, but also a sticker market place to buy animated stickers or stickers related to current trends or popular franchises. Although only 4% of the user base bought stickers in 2021, this population accounted for $268 million dollars in sales <ref>{{Cite web |date=2016-06-12 |title=Line sold $268 million worth of stickers last year amid Asia’s messaging boom |url=https://qz.com/704768/line-sold-268-million-worth-of-stickers-last-year-amid-asias-messaging-boom |access-date=2026-05-04 |website=Quartz |language=en}}</ref> indicating the strength of a sticker economy because of Japan by extent Asia's mass adoption of stickers in texting etiqutte. == References == {{BookCat}} qz94dpebii63lob2rhmszd0uxa4ay1d 4634141 4634138 2026-05-04T18:04:33Z Dorkusdomingus 3581221 grammer in LINE app section 4634141 wikitext text/x-wiki == The norms of texting in Japan == ==== American vs. Japanese Social Norms ==== ==== Japan Perspective on Texting ==== Japanese texting norms are shaped by the country's high-context communication style, which prioritizes indirectness, harmony, and consideration for others' feelings.<ref>Gudykunst, W. B., & Nishida, T. (1999). The influence of cultural variability on perceptions of communication behavior. ''Social Behavior and Personality'', 27(5), 523–534.</ref> Unlike American texting culture, where fast replies often signal engagement, Japanese users tend to value thoughtfulness over speed. A delayed response is not typically read as disinterest but as a sign of respect, an indication that the sender is carefully considering what to say rather than firing off a fast reply.<ref>Liu, L. (2020). How fast should I reply to the text? ''Medium''. https://lillian-liu.medium.com/how-fast-should-i-reply-the-text-8f4e01310b0</ref> This norm is especially pronounced in dating contexts, where slow texting is widely understood as a strategy for building attraction and anticipation. Replying too quickly can come across as desperate or overeager, while measured pacing creates tension and signals emotional composure.<ref>Kato, F., & Hjorth, L. (2014). Understanding the role of mobile social media in intimate relationships. ''Computers in Human Behavior'', 49, 560–567. https://doi.org/10.1016/j.chb.2014.11.047</ref> Japanese commentators frequently compare texting to a tennis match: each message carries an implicit obligation to respond, so a slower response reduces social pressure on both sides and allows each participant to engage on their own terms. Emojis, ''kaomoji'' (顔文字), and LINE stickers play a critical role in softening the tone of messages, helping users avoid the directness that Japanese communication norms discourage. These visual elements signal friendliness and attentiveness without requiring explicit verbal warmth, making them essential tools for navigating the implicit, indirect style of Japanese digital communication.<ref>Katsuno, H., & Yano, C. R. (2002). Face to face: On-line subjectivity in contemporary Japan. ''Asian Studies Review'', 26(2), 205–231.</ref> ==== Texting Etiquette ==== Text messaging practices in Japan reflect the nation’s cultural values. Implicit rules guide digital communication, shaping both timing and manner of interaction. Research indicates that Japanese digital communication integrates traditional linguistic norms with modern technology, thereby influencing the conveyance of tone and intent in text-based exchanges.<ref>Kobayashi, T. (2014). Tele-Cocooning: Mobile Texting and Social Scope. Journal of Computer-Mediated Communication.</ref> Politeness is a central feature of Japanese texting, including in casual interactions. Messages frequently incorporate polite language, especially when addressing individuals of higher status, such as supervisors. It is customary to begin with a brief greeting or acknowledgment and to conclude with a soft closing, such as “よろしくお願いします” (“thank you in advance”), particularly in semi-formal exchanges. Research on messaging behavior indicates that Japanese users structure their texts deliberately to ensure clarity and maintain social harmony. They employ greetings, contextual framing, and specific sentence endings to convey nuance and emotion<ref>Lee, Y. (2023). Structure of LINE Chat Openings. Japanese Language Education Research.</ref><ref>Park, J. (2013). Sentence Closings in Japanese Mobile Email. Discourse, Context & Media.</ref> Timeliness is highly valued in Japanese texting culture, although expectations differ depending on the nature of the relationship. Quick responses are appreciated among friends, whereas prompt replies in professional contexts signify respect. As many messaging platforms display read receipts, delayed responses without acknowledgment are often perceived as inconsiderate.<ref>Soeda, E. et al. (2016). Analysis of LINE Communication. Japanese Language Education Methods.</ref> The level of formality in Japanese texting varies depending on social context. Casual language is typically used among friends and peers, while honorific language (Keigo) is expected in professional or hierarchical relationships. Even in digital communication, traditional linguistic norms remain influential, though they may be adapted for efficiency and informality. Switching between styles based on context is common and reflects sensitivity to social roles.<ref>Nagai, N. et al. (2025). Effects of Speech Level Shift in Japanese Text Chat. Applied Sciences.</ref> ==== Slang and Emoji Usage ==== Text-based communication in Japan relies heavily on nuanced slang and a highly developed system of visual expression. Similarly to American culture Japanese netizens use "slang", informal and trendy language, to communicate amongst friends and peers especially for the younger generations<ref>{{Cite web |date=2023-11-29 |title=Learn Japanese Slang With These 50 Examples |url=https://preply.com/en/blog/japanese-slang/ |access-date=2026-05-03 |language=en}}</ref>. In western contexts emojis are often used for emphasis or tone, Japanese messaging culture integrates them as essential components of meaning. This practice can be traced back to the early development of emoji (or kaomoji) in Japan, particularly through mobile platforms like LINE, where visual symbols became standardized forms of emotional expression. Japanese slang in texting tends to be context-dependent and often reflects pop culture. Due to worldwide impact of roman letters even in Japanese mobile keyboards, slang terms utilize and even combined Japanese language (kanji, katakana, hiragana) with roman letters. For example, a popular slang is "w", frequently used to indicate laughter, derived from the word “笑い” (warai) meaning to laugh<ref name=":0">{{Cite web |last=Deutsch |first=Anna |date=2025-12-04 |title=21 Japanese Internet Slang & Texting Terms |url=https://cotoacademy.com/japanese-internet-slang-and-texting-terms-kaomoji/ |access-date=2026-05-03 |website=Coto Japanese Academy |language=en-US}}</ref>. In context people use this on its own or at the end of phrases, it can also be denoted as "www"~ to imply more laughter. Slang is ever evolving and derived from common phrases and even existing slang. Such as "草" (kusa) with literal meaning "grass" however the prevenance of using multiple w's (wwwwww) looks like grass growing on the screen<ref name=":0" />. There are many more slangs coming from onomatopoeia, media references, and shortening formal phrases. Here are some popular examples below in table 1 {| class="wikitable" |+ !Slang !Word !Translation !Context |- |Jk<ref name=":1">{{Cite web |last=JapanesePod101.com |date=2019-07-23 |title=Our Guide to Japanese Internet & Text Slang |url=https://www.japanesepod101.com/blog/2019/07/23/japanese-text-slang/ |access-date=2026-05-03 |website=JapanesePod101.com Blog |language=en}}</ref> |女子高生 (Joshikōsei) |high school girl |sexual expression referring to younger girl |- |888<ref name=":0" /> |パチ (pachi) |Onomatopoeia for clapping |to denote clapping or more 8's for more clapping |- |DKQ<ref name=":1" /> |ドキュン (Donkyun) |idiot who acts without any thinking |came from a variety show called ''Mugumi! Dokyun'', which gave life advice to struggling couples |- |乙 (''otsu'')<ref name=":0" /> |お疲れ様です (''otsukare sama desu'') |Thank you for your hard work. |Thanking or greeting like “Hi” or "Bye" |} Emojis (emoji/kaomoji) help convey feelings, reducing misunderstanding in digital communication. These are used to feel less direct or harsh, aligning with Japanese norms, signally friendliness and/or attentiveness. Unlike western emojis, the emojis are often much more detailed and expressive which more accurately portray tone. Japanese mobile keyboard has its set of its own ''kaomoji'' ''or'' emoticons created using keyboard characters in addition to standard emojis. Table 2 show common types of kaomojis<ref>{{Cite web |title=Kaomoji (顔文字): Japanese Emoticons |url=https://www.kaomoji.co/pages/emoji |access-date=2026-05-03 |website=Kaomoji ® Official |language=en}}</ref>. {| class="wikitable" |+ !Postive !Sad !Angry !Greetings !Actions |- |(* ^ ω ^) |(╥﹏╥) |(＃Д´) |＼(⌒▽⌒) |ε=ε=ε=ε=┌(;￣▽￣)┘ |- |＼(￣▽￣)／ |(╯︵╰,) |┌∩┐(◣_◢)┌∩┐ |(＠´ー)ﾉﾞ |(＿ ＿*) Z z z |- |(/▽＼)｡o○♡ |(ﾉД) |(╬益´) |＼(^o^)／ |ヾ(´〇`)ﾉ♪♪♪ |} ==== LINE app ==== LINE is the most popular instant messaging app used in Japan with 78% percent of the population (97 million people) as monthly users <ref>{{Cite web |title=LINE user trends 2025: The largest messaging app in Japan {{!}} TAMLO |url=https://tam-tamlo.com/en/307 |access-date=2026-05-04 |language=en}}</ref>. The app is works similar to WhatsApp allowing messaging and calling over the internet, but the app's support for stickers commonly used in texting make it unique. Stickers used in texting account for 9% of all messages as of March 2016 and are commonly used to convey complex emotions, soften or intensify tone, or even express criticism that would feel too harsh if written down <ref>{{Cite journal |last=Oberwinkler |first=Michaela |date=2023 |title=Digital Stickers in Japanese LINE Communication |url=https://doi.org/10.1453/1614-0885-2-2023-15758 |journal=IMAGE |volume=19 |issue=2 |pages=238–262 |doi=10.1453/1614-0885-2-2023-15758 |issn=1614-0885}}</ref>. As stickers are widely prevelent, LINE provides default stickers with the app, but also a sticker market place to buy animated stickers or stickers related to current trends or popular franchises. Although only 4% of the user base bought stickers in 2021, this population accounted for $268 million dollars in sales <ref>{{Cite web |date=2016-06-12 |title=Line sold $268 million worth of stickers last year amid Asia’s messaging boom |url=https://qz.com/704768/line-sold-268-million-worth-of-stickers-last-year-amid-asias-messaging-boom |access-date=2026-05-04 |website=Quartz |language=en}}</ref> indicating the strength of a sticker economy because of Japan (and by extent Asia's) mass adoption of stickers in texting etiqutte. == References == {{BookCat}} ol9uel1eg6rugenfu4ow7gpkanrfew8 4634168 4634141 2026-05-04T18:55:26Z Fgq4ax 3581244 Added social norms overview 4634168 wikitext text/x-wiki == The norms of texting in Japan == ==== American vs. Japanese Social Norms ==== American and Japanese social norms differ mostly in each culture’s perspective on individuality, communication, and social responsibility. In the United States, social practices are often shaped by individualism, personal freedom, self-respect, independence, and achievement. American communication style is also more direct, explicit, and assertive, reflecting a focus on clearly expressing personal opinions and pursuing individual goals. <ref name=":2">{{Cite journal |last=Akiba |first=Daisuke |last2=Klug |first2=Wayne |date=1999-01-01 |title=THE DIFFERENT AND THE SAME: REEXAMINING EAST AND WEST IN A CROSS-CULTURAL ANALYSIS OF VALUES |url=https://www.ingentaconnect.com/content/10.2224/sbp.1999.27.5.467 |journal=Social Behavior and Personality: an international journal |language=en |volume=27 |issue=5 |pages=467–473 |doi=10.2224/sbp.1999.27.5.467 |issn=0301-2212}}</ref><ref>{{Cite journal |last=Bilkisu Mohammed |date=2023-12-12 |title=Pragmatic Strategies in Interpersonal Conflict Resolution: A Cross-Cultural Analysis |url=https://www.internationaljournalcorner.com/index.php/theijhss/article/view/173313 |journal=The International Journal of Humanities & Social Studies |doi=10.24940/theijhss/2023/v11/i9/HS2309-019 |issn=2321-9203}}</ref> Japanese social norms are often more communal and group-oriented, with a greater emphasis on harmony, inner balance, respect for age and hierarchy, and social recognition. Communication in Japan is often high-context, relying on shared understanding, cultural background, and nonverbal cues to convey meaning.<ref>{{Cite journal |last=Shen |first=Zijun |last2=Pang |first2=Bing |last3=Li |first3=Xiaohui |last4=Chen |first4=Yunyi |date=2024-04-18 |title=An Exploration of Japanese Cultural Dynamics Communication Practices through Social Pragmatics |url=https://al-kindipublisher.com/index.php/jpds/article/view/6808 |journal=Journal of Pragmatics and Discourse Analysis |language=en |volume=3 |issue=1 |pages=60–72 |doi=10.32996/jpda.2024.3.1.4 |issn=2755-3426}}</ref> The two cultures also share important values. Both American and Japanese societies value happiness, relationships, friendship, peace, and family.<ref name=":2" /> While the methods of communication and social interaction may differ, many core life priorities are shared. These cultural differences are important for understanding texting behavior in Japan, especially the importance of managing tone, timing, and social expectations. They also shape ideas about politeness, emotional expression, and relationship maintenance, which become important when examining Japanese texting etiquette, emoji use, and messaging platforms. ==== Japan Perspective on Texting ==== Japanese texting norms are shaped by the country's high-context communication style, which prioritizes indirectness, harmony, and consideration for others' feelings.<ref>Gudykunst, W. B., & Nishida, T. (1999). The influence of cultural variability on perceptions of communication behavior. ''Social Behavior and Personality'', 27(5), 523–534.</ref> Unlike American texting culture, where fast replies often signal engagement, Japanese users tend to value thoughtfulness over speed. A delayed response is not typically read as disinterest but as a sign of respect, an indication that the sender is carefully considering what to say rather than firing off a fast reply.<ref>Liu, L. (2020). How fast should I reply to the text? ''Medium''. https://lillian-liu.medium.com/how-fast-should-i-reply-the-text-8f4e01310b0</ref> This norm is especially pronounced in dating contexts, where slow texting is widely understood as a strategy for building attraction and anticipation. Replying too quickly can come across as desperate or overeager, while measured pacing creates tension and signals emotional composure.<ref>Kato, F., & Hjorth, L. (2014). Understanding the role of mobile social media in intimate relationships. ''Computers in Human Behavior'', 49, 560–567. https://doi.org/10.1016/j.chb.2014.11.047</ref> Japanese commentators frequently compare texting to a tennis match: each message carries an implicit obligation to respond, so a slower response reduces social pressure on both sides and allows each participant to engage on their own terms. Emojis, ''kaomoji'' (顔文字), and LINE stickers play a critical role in softening the tone of messages, helping users avoid the directness that Japanese communication norms discourage. These visual elements signal friendliness and attentiveness without requiring explicit verbal warmth, making them essential tools for navigating the implicit, indirect style of Japanese digital communication.<ref>Katsuno, H., & Yano, C. R. (2002). Face to face: On-line subjectivity in contemporary Japan. ''Asian Studies Review'', 26(2), 205–231.</ref> ==== Texting Etiquette ==== Text messaging practices in Japan reflect the nation’s cultural values. Implicit rules guide digital communication, shaping both timing and manner of interaction. Research indicates that Japanese digital communication integrates traditional linguistic norms with modern technology, thereby influencing the conveyance of tone and intent in text-based exchanges.<ref>Kobayashi, T. (2014). Tele-Cocooning: Mobile Texting and Social Scope. Journal of Computer-Mediated Communication.</ref> Politeness is a central feature of Japanese texting, including in casual interactions. Messages frequently incorporate polite language, especially when addressing individuals of higher status, such as supervisors. It is customary to begin with a brief greeting or acknowledgment and to conclude with a soft closing, such as “よろしくお願いします” (“thank you in advance”), particularly in semi-formal exchanges. Research on messaging behavior indicates that Japanese users structure their texts deliberately to ensure clarity and maintain social harmony. They employ greetings, contextual framing, and specific sentence endings to convey nuance and emotion<ref>Lee, Y. (2023). Structure of LINE Chat Openings. Japanese Language Education Research.</ref><ref>Park, J. (2013). Sentence Closings in Japanese Mobile Email. Discourse, Context & Media.</ref> Timeliness is highly valued in Japanese texting culture, although expectations differ depending on the nature of the relationship. Quick responses are appreciated among friends, whereas prompt replies in professional contexts signify respect. As many messaging platforms display read receipts, delayed responses without acknowledgment are often perceived as inconsiderate.<ref>Soeda, E. et al. (2016). Analysis of LINE Communication. Japanese Language Education Methods.</ref> The level of formality in Japanese texting varies depending on social context. Casual language is typically used among friends and peers, while honorific language (Keigo) is expected in professional or hierarchical relationships. Even in digital communication, traditional linguistic norms remain influential, though they may be adapted for efficiency and informality. Switching between styles based on context is common and reflects sensitivity to social roles.<ref>Nagai, N. et al. (2025). Effects of Speech Level Shift in Japanese Text Chat. Applied Sciences.</ref> ==== Slang and Emoji Usage ==== Text-based communication in Japan relies heavily on nuanced slang and a highly developed system of visual expression. Similarly to American culture Japanese netizens use "slang", informal and trendy language, to communicate amongst friends and peers especially for the younger generations<ref>{{Cite web |date=2023-11-29 |title=Learn Japanese Slang With These 50 Examples |url=https://preply.com/en/blog/japanese-slang/ |access-date=2026-05-03 |language=en}}</ref>. In western contexts emojis are often used for emphasis or tone, Japanese messaging culture integrates them as essential components of meaning. This practice can be traced back to the early development of emoji (or kaomoji) in Japan, particularly through mobile platforms like LINE, where visual symbols became standardized forms of emotional expression. Japanese slang in texting tends to be context-dependent and often reflects pop culture. Due to worldwide impact of roman letters even in Japanese mobile keyboards, slang terms utilize and even combined Japanese language (kanji, katakana, hiragana) with roman letters. For example, a popular slang is "w", frequently used to indicate laughter, derived from the word “笑い” (warai) meaning to laugh<ref name=":0">{{Cite web |last=Deutsch |first=Anna |date=2025-12-04 |title=21 Japanese Internet Slang & Texting Terms |url=https://cotoacademy.com/japanese-internet-slang-and-texting-terms-kaomoji/ |access-date=2026-05-03 |website=Coto Japanese Academy |language=en-US}}</ref>. In context people use this on its own or at the end of phrases, it can also be denoted as "www"~ to imply more laughter. Slang is ever evolving and derived from common phrases and even existing slang. Such as "草" (kusa) with literal meaning "grass" however the prevenance of using multiple w's (wwwwww) looks like grass growing on the screen<ref name=":0" />. There are many more slangs coming from onomatopoeia, media references, and shortening formal phrases. Here are some popular examples below in table 1 {| class="wikitable" |+ !Slang !Word !Translation !Context |- |Jk<ref name=":1">{{Cite web |last=JapanesePod101.com |date=2019-07-23 |title=Our Guide to Japanese Internet & Text Slang |url=https://www.japanesepod101.com/blog/2019/07/23/japanese-text-slang/ |access-date=2026-05-03 |website=JapanesePod101.com Blog |language=en}}</ref> |女子高生 (Joshikōsei) |high school girl |sexual expression referring to younger girl |- |888<ref name=":0" /> |パチ (pachi) |Onomatopoeia for clapping |to denote clapping or more 8's for more clapping |- |DKQ<ref name=":1" /> |ドキュン (Donkyun) |idiot who acts without any thinking |came from a variety show called ''Mugumi! Dokyun'', which gave life advice to struggling couples |- |乙 (''otsu'')<ref name=":0" /> |お疲れ様です (''otsukare sama desu'') |Thank you for your hard work. |Thanking or greeting like “Hi” or "Bye" |} Emojis (emoji/kaomoji) help convey feelings, reducing misunderstanding in digital communication. These are used to feel less direct or harsh, aligning with Japanese norms, signally friendliness and/or attentiveness. Unlike western emojis, the emojis are often much more detailed and expressive which more accurately portray tone. Japanese mobile keyboard has its set of its own ''kaomoji'' ''or'' emoticons created using keyboard characters in addition to standard emojis. Table 2 show common types of kaomojis<ref>{{Cite web |title=Kaomoji (顔文字): Japanese Emoticons |url=https://www.kaomoji.co/pages/emoji |access-date=2026-05-03 |website=Kaomoji ® Official |language=en}}</ref>. {| class="wikitable" |+ !Postive !Sad !Angry !Greetings !Actions |- |(* ^ ω ^) |(╥﹏╥) |(＃Д´) |＼(⌒▽⌒) |ε=ε=ε=ε=┌(;￣▽￣)┘ |- |＼(￣▽￣)／ |(╯︵╰,) |┌∩┐(◣_◢)┌∩┐ |(＠´ー)ﾉﾞ |(＿ ＿*) Z z z |- |(/▽＼)｡o○♡ |(ﾉД) |(╬益´) |＼(^o^)／ |ヾ(´〇`)ﾉ♪♪♪ |} ==== LINE app ==== LINE is the most popular instant messaging app used in Japan with 78% percent of the population (97 million people) as monthly users <ref>{{Cite web |title=LINE user trends 2025: The largest messaging app in Japan {{!}} TAMLO |url=https://tam-tamlo.com/en/307 |access-date=2026-05-04 |language=en}}</ref>. The app is works similar to WhatsApp allowing messaging and calling over the internet, but the app's support for stickers commonly used in texting make it unique. Stickers used in texting account for 9% of all messages as of March 2016 and are commonly used to convey complex emotions, soften or intensify tone, or even express criticism that would feel too harsh if written down <ref>{{Cite journal |last=Oberwinkler |first=Michaela |date=2023 |title=Digital Stickers in Japanese LINE Communication |url=https://doi.org/10.1453/1614-0885-2-2023-15758 |journal=IMAGE |volume=19 |issue=2 |pages=238–262 |doi=10.1453/1614-0885-2-2023-15758 |issn=1614-0885}}</ref>. As stickers are widely prevelent, LINE provides default stickers with the app, but also a sticker market place to buy animated stickers or stickers related to current trends or popular franchises. Although only 4% of the user base bought stickers in 2021, this population accounted for $268 million dollars in sales <ref>{{Cite web |date=2016-06-12 |title=Line sold $268 million worth of stickers last year amid Asia’s messaging boom |url=https://qz.com/704768/line-sold-268-million-worth-of-stickers-last-year-amid-asias-messaging-boom |access-date=2026-05-04 |website=Quartz |language=en}}</ref> indicating the strength of a sticker economy because of Japan (and by extent Asia's) mass adoption of stickers in texting etiqutte. == References == {{BookCat}} k1mtxgi700ms2kabnj50c1h166n1rmf 0 483106 4634060 4634010 2026-05-04T12:04:09Z MathXplore 3097823 Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]] 4634060 wikitext text/x-wiki Professional boundaries can be difficult to pin down, especially when you're new to Social Services. They are essential to maintain your practice and prevent burn out. Social services works closely with residents and their friends, families in emotionally taxing and high environments and situations. Without clear and enforced boundaries, Social Services workers risk emotionally burnout and role confusion. This section outlines the types of boundaries relevant to nursing home practice, along with strategies for creating and maintaining them. '''Types of Boundaries with Examples''' '''Professional''' Working in a Nursing Home serves as staffs place of work, but for residents, this is their home. It can be confusing for residents when they are in need of assistance that staff are driven by professional obligation, not solely choice. Residents and staff are friendly, but not friends. And residents may come to staff as though they are one. It is important to ensure in these moments firm boundaries are in place so to not blur the line between professional and unethical friendship. It is important to be available to residents throughout the day, but not all day. Office hours, signup sheets, signs on door, all help with juggling a Social Services job with daily resident support. Once a staff member is off the clock, that is where the job ends for the day. No communication outside of the Nursing Home with residents is appropriate. This includes sharing personal phone numbers or following on social media. Nursing Homes have policies in place for a reason. Many of them to protect staff from crossing boundaries or vice versa, residents trying to cross boundaries with staff. '''Emotional''' Working in a Nursing Home is a vulnerable and highly emotional environment. Residents experience traumas like devastating medical diagnosis, family or friend conflict, loss of loved ones, ect. In these moments Social Services are responsible for providing emotional support, but this does not require them to take on resident emotions. Understanding that it is normal and appropriate for residents to experience these emotions while also providing them the support they need to process them on their own. {{BookCat}} rc61wxg820nugb3hzhh9jmqwcy2m63u 0 483108 4634059 4634032 2026-05-04T12:03:45Z MathXplore 3097823 Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]] 4634059 wikitext text/x-wiki = A history of free market busses in Africa = <nowiki><mapframe latitude="48.85" longitude="2.35" zoom="12" width="400" height="300"> { "type": "Feature", "geometry": { "type": "Point", "coordinates": [2.35, 48.85] } } </mapframe></nowiki> {{BookCat}} ctb5032f70bh2d78l9whljeejx1wsjf 0 483109 4634058 4634034 2026-05-04T12:03:43Z MathXplore 3097823 Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]] 4634058 wikitext text/x-wiki == Summary == == Annotated list of factors == == Timeline of events == == Maps of locations == == Identification of policy issues == == Narrative of the case == MK Strøget is a 1.1 kilometre pedestrian‑only street network in central Copenhagen (Denmark), which was fully pedestrianised in 1962.<ref>{{Cite web |title=Global Street Design Guide |url=https://globaldesigningcities.org/publication/global-street-design-guide/ |access-date=2026-05-04 |website=Global Designing Cities Initiative |language=en-US}}</ref> It is widely regarded as one of the world’s earliest and most influential pedestrianisation projects, serving as a landmark example of large‑scale, people‑first urban design.<ref>{{Cite book |last=Gehl |first=J |title=Cities for people |publisher=Island Press |year=2010}}</ref><ref>{{Cite web |title=Strøget District {{!}} |url=https://www.pps.org/places/strooget-district |access-date=2026-05-04 |website=www.pps.org}}</ref> Located in the historic city centre, Strøget forms a continuous, car‑free corridor running from City Hall Square (Rådhuspladsen) to Kongens Nytorv.<ref>{{Cite web |title=Global Street Design Guide |url=https://globaldesigningcities.org/publication/global-street-design-guide/ |access-date=2026-05-04 |website=Global Designing Cities Initiative |language=en-US}}</ref> Rather than a single street, it comprises a linked sequence of streets and public squares that together function as a coherent and highly legible pedestrian network. Since its pedestrianisation in the early 1960s, Strøget has prioritised walking, social activity and public life over vehicle movement. Wide, level paving and active retail and café frontages support high pedestrian volumes and encourage people to linger, gather, and interact. The street accommodates everyday movement as well as street performance, events, and outdoor dining, reinforcing its role as both a transport corridor and a civic space.<ref>{{Cite book |last=Gehl |first=J |title=Cities for people |publisher=Island Press |year=2010}}</ref> Internationally, Strøget is significant for demonstrating that removing cars from city centres can enhance economic activity, urban vitality, and quality of life. Its success has influenced pedestrian‑first streets and city‑centre revitalisation projects around the world and remains a benchmark for strong pedestrian network design. RL == References == {{BookCat}} sfn6b4uh2pssb88ztbwc4hig4mqc173 0 483110 4634057 4634031 2026-05-04T12:03:40Z MathXplore 3097823 Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]] 4634057 wikitext text/x-wiki == Summary == == Annotated list of factors == == Timeline of events == == Maps of locations == == Identification of policy issues == == Narrative of the case == == References == {{BookCat}} 1u48yu7jzv0ffxyre1t33insg0d9r4l 102 483113 4634162 4634045 2026-05-04T18:48:55Z Kittycataclysm 3371989 incomplete 4634162 wikitext text/x-wiki {{Incomplete recipe|reason=missing ingredients list and linking, missing categories, missing cookbook templates, stylistic adjustments needed}} '''Ofe Ede''' is a traditional Igbo soup in which cocoyam (taro) serves as both the primary ingredient and the thickening agent. Unlike most Nigerian soups where cocoyam is a background thickener, in Ofe Ede the cocoyam takes centre stage. Rich, creamy, and deeply satisfying, it is a beloved comfort food across Anambra, Enugu, Imo, and Abia states. == Ingredients == * == Procedure == # Cook the meats: Season 600 grams assorted meat (beef, goat meat, shaki) with diced 1 onion, 1 of 2 seasoning cubes, and a pinch of 1 teaspoons salt. Add 200 grams stockfish (panla), soaked and cleaned midway. Cook on medium heat until tender. Reserve the meat stock. # Boil and pound the cocoyam: Boil peeled 800 grams cocoyam (ede), peeled and washed in a separate pot until very soft. Pound in a mortar until completely smooth and lump-free. Set aside. # Build the soup base: Pour reserved meat stock into a pot. Add 0.3 cups palm oil and bring to a gentle boil. Add 1 tablespoons ogiri okpei (fermented locust bean paste) and blended 3 scotch bonnet pepper (rodo). Stir well. # Add cocoyam and thicken: Drop spoonfuls of the pounded 800 grams cocoyam (ede), peeled and washed into the boiling soup gradually. Stir between each addition. Allow the cocoyam to dissolve fully into the broth, thickening the soup to a creamy consistency. # Add proteins and season: Add cooked 600 grams assorted meat (beef, goat meat, shaki), 200 grams stockfish (panla), soaked and cleaned, and 150 grams smoked fish, deboned into the soup. Add 3 tablespoons ground crayfish and remaining 2 seasoning cubes. Stir well. Taste and adjust 1 teaspoons salt. Simmer on low heat for 10 minutes # Add leaves and serve: Stir in shredded 150 grams uziza leaves or oha leaves, shredded. Cook for 3-5 minutes only. The soup should be thick, creamy, and deeply flavoured. Serve hot with pounded yam, eba, or fufu. [[Category:Medium Difficulty recipes]] [[Category:Nigerian recipes]] [[Category:Recipes for soup]] cy5v0do48rqstncha008k0xuzqwr43v 102 483114 4634074 2026-05-04T13:43:44Z SHE-LOVES-BRIAN 3581157 create article 4634074 wikitext text/x-wiki Nigerian suya is one of the country’s most iconic street foods—smoky, spicy, and deeply flavorful. It’s essentially skewered meat (usually beef, sometimes chicken or goat) that’s thinly sliced, coated in a bold spice mix, and grilled over open flames. At the heart of suya is its signature seasoning, called '''yaji'''. This blend typically includes ground peanuts, chili pepper, ginger, garlic, and other spices. The peanut base gives suya its slightly nutty taste, while the chili delivers a noticeable heat that can range from mild to intense depending on who’s making it. Suya is traditionally prepared by Hausa street vendors known as ''mai suya'', who grill the meat on long skewers over charcoal. As it cooks, they often baste it with oil and sprinkle extra yaji on top, creating that distinctive smoky crust. It’s usually served hot, wrapped in paper, and accompanied by sliced onions, tomatoes, and sometimes cabbage. A sprinkle of extra spice on the side is common if you want more kick. You’ll find suya everywhere in Nigeria—especially in the evenings—sold at roadside stands and bustling markets. Beyond just food, it’s a social experience: people gather around, chat, and enjoy freshly grilled skewers straight off the fire. If you like bold, spicy barbecue-style dishes, suya is definitely worth trying. == INGREDIENTS == * Thinly sliced '''beef''' (most traditional) ''Alternatives:'' chicken, ram (mutton), or goat === Suya Spice Mix (Yaji) === * Ground roasted peanuts (or peanut powder) * Cayenne pepper / dry chili pepper * Ginger powder * Garlic powder * Onion powder * Stock cubes (crushed) * Salt * Optional: paprika, cloves, or black pepper (for extra depth) == PROCEDURE == * '''Slice meat thinly''' (usually beef). * '''Mix yaji''' (ground peanuts, chili, ginger, garlic, onion, salt, seasoning). * '''Coat the meat''' with oil and the spice mix; let it rest briefly. * '''Skewer the meat''' and add more spice. * '''Grill over charcoal''', turning often, until cooked and slightly charred. * '''Serve hot''' with onions, tomatoes, and extra spice. 6pnl20xc2tndctknx84y418ng7nz3zx 4634081 4634074 2026-05-04T14:02:38Z SHE-LOVES-BRIAN 3581157 added a wiki link and categories 4634081 wikitext text/x-wiki Nigerian suya is one of the country’s most iconic street foods—smoky, spicy, and deeply flavorful. It’s essentially skewered meat (usually beef, sometimes chicken or goat) that’s thinly sliced, coated in a bold spice mix, and grilled over open flames. At the heart of suya is its signature seasoning, called '''[[wikipedia:Yaji_(spice_blend)|yaji]]'''. This blend typically includes ground peanuts, chili pepper, ginger, garlic, and other spices. The peanut base gives suya its slightly nutty taste, while the chili delivers a noticeable heat that can range from mild to intense depending on who’s making it. Suya is traditionally prepared by Hausa street vendors known as ''mai suya'', who grill the meat on long skewers over charcoal. As it cooks, they often baste it with oil and sprinkle extra yaji on top, creating that distinctive smoky crust. It’s usually served hot, wrapped in paper, and accompanied by sliced onions, tomatoes, and sometimes cabbage. A sprinkle of extra spice on the side is common if you want more kick. You’ll find suya everywhere in Nigeria—especially in the evenings—sold at roadside stands and bustling markets. Beyond just food, it’s a social experience: people gather around, chat, and enjoy freshly grilled skewers straight off the fire. If you like bold, spicy barbecue-style dishes, suya is definitely worth trying. == INGREDIENTS == * Thinly sliced '''beef''' (most traditional) ''Alternatives:'' chicken, ram (mutton), or goat === Suya Spice Mix (Yaji) === * Ground roasted peanuts (or peanut powder) * Cayenne pepper / dry chili pepper * Ginger powder * Garlic powder * Onion powder * Stock cubes (crushed) * Salt * Optional: paprika, cloves, or black pepper (for extra depth) == PROCEDURE == * '''Slice meat thinly''' (usually beef). * '''Mix yaji''' (ground peanuts, chili, ginger, garlic, onion, salt, seasoning). * '''Coat the meat''' with oil and the spice mix; let it rest briefly. * '''Skewer the meat''' and add more spice. * '''Grill over charcoal''', turning often, until cooked and slightly charred. * '''Serve hot''' with onions, tomatoes, and extra spice. [[Category:Recipes using meat]] [[Category:Nigerian recipes]] [[Category:Grilled recipes]] 3jv71q5o154tl9k17kcsqwf610bofno 4634133 4634081 2026-05-04T17:46:53Z Kittycataclysm 3371989 incomplete 4634133 wikitext text/x-wiki {{Incomplete recipe|reason=excessive capitalization, missing quantities, missing ingredient links, missing categories, missing cookbook templates, stylistic adjustments needed, incorrect formatting}} Nigerian suya is one of the country’s most iconic street foods—smoky, spicy, and deeply flavorful. It’s essentially skewered meat (usually beef, sometimes chicken or goat) that’s thinly sliced, coated in a bold spice mix, and grilled over open flames. At the heart of suya is its signature seasoning, called '''[[wikipedia:Yaji_(spice_blend)|yaji]]'''. This blend typically includes ground peanuts, chili pepper, ginger, garlic, and other spices. The peanut base gives suya its slightly nutty taste, while the chili delivers a noticeable heat that can range from mild to intense depending on who’s making it. Suya is traditionally prepared by Hausa street vendors known as ''mai suya'', who grill the meat on long skewers over charcoal. As it cooks, they often baste it with oil and sprinkle extra yaji on top, creating that distinctive smoky crust. It’s usually served hot, wrapped in paper, and accompanied by sliced onions, tomatoes, and sometimes cabbage. A sprinkle of extra spice on the side is common if you want more kick. You’ll find suya everywhere in Nigeria—especially in the evenings—sold at roadside stands and bustling markets. Beyond just food, it’s a social experience: people gather around, chat, and enjoy freshly grilled skewers straight off the fire. If you like bold, spicy barbecue-style dishes, suya is definitely worth trying. == INGREDIENTS == * Thinly sliced '''beef''' (most traditional) ''Alternatives:'' chicken, ram (mutton), or goat === Suya Spice Mix (Yaji) === * Ground roasted peanuts (or peanut powder) * Cayenne pepper / dry chili pepper * Ginger powder * Garlic powder * Onion powder * Stock cubes (crushed) * Salt * Optional: paprika, cloves, or black pepper (for extra depth) == PROCEDURE == * '''Slice meat thinly''' (usually beef). * '''Mix yaji''' (ground peanuts, chili, ginger, garlic, onion, salt, seasoning). * '''Coat the meat''' with oil and the spice mix; let it rest briefly. * '''Skewer the meat''' and add more spice. * '''Grill over charcoal''', turning often, until cooked and slightly charred. * '''Serve hot''' with onions, tomatoes, and extra spice. [[Category:Recipes using meat]] [[Category:Nigerian recipes]] [[Category:Grilled recipes]] ot545j21u4v38c345zz5bbhoryz9m8i 102 483115 4634083 2026-05-04T14:10:40Z Itzv1ktor 3581155 Created Article 4634083 wikitext text/x-wiki '''Abacha''', often called African salad, is a traditional dish from southeastern Nigeria, especially among the Igbo people. Despite the name “salad,” it’s quite different from Western salads—Abacha is hearty, flavorful, and deeply rooted in local culinary traditions. At its core, Abacha is made from dried, shredded cassava. The cassava is harvested, cooked, sliced into thin strips, and then sun-dried. Before serving, these strips are soaked in water to soften them, giving the dish its signature chewy texture. What really defines Abacha is its rich, spicy dressing. This is typically made with palm oil, potash (which helps emulsify the oil), ground crayfish, pepper, salt, and sometimes fermented ingredients like ugba (oil bean seeds). The mixture coats the cassava, creating a bold, slightly tangy flavor. == INGREDIENTS == * Dried shredded cassava (Abacha) === For the sauce/dressing === * Palm oil * Potash (akanwu/kaun) – helps thicken and emulsify the sauce * Ground crayfish * Pepper (fresh or dry, to taste) * Salt * Seasoning cubes (optional) === Traditional add-ins === * Ugba (very important for authentic flavor) * Smoked fish or dried fish * Ponmo (cow skin) === Vegetables & garnishes === * Utazi leaves (adds a slight bitter taste) * Garden eggs (African eggplant) * Onions === Optional extras (depending on preference) === * Stockfish * Kpomo sauce or meat bits * Fresh herbs == PROCEDURE == * Soak the dried Abacha in warm water until soft, then drain. * Mix palm oil with a little dissolved potash until it thickens. * Add crayfish, pepper, salt, and seasoning to the oil. * Combine the softened Abacha with the sauce. * Stir in Ugba and any proteins like fish or ponmo. * Add onions, utazi leaves, and garden eggs. * Mix well and serve. fe95l85xx4idnoesbx6a6z24kyb0gt6 4634085 4634083 2026-05-04T14:47:51Z Itzv1ktor 3581155 Added categories and wiki links 4634085 wikitext text/x-wiki '''Abacha''', often called African salad, is a traditional dish from southeastern Nigeria, especially among the Igbo people. Despite the name “salad,” it’s quite different from Western salads—Abacha is hearty, flavorful, and deeply rooted in local culinary traditions. At its core, Abacha is made from dried, shredded cassava. The cassava is harvested, cooked, sliced into thin strips, and then sun-dried. Before serving, these strips are soaked in water to soften them, giving the dish its signature chewy texture. What really defines Abacha is its rich, spicy dressing. This is typically made with palm oil, potash (which helps emulsify the oil), ground crayfish, pepper, salt, and sometimes fermented ingredients like ugba (oil bean seeds). The mixture coats the cassava, creating a bold, slightly tangy flavor. == INGREDIENTS == * [[Cookbook:Cassava|Dried shredded cassava]] (Abacha) === For the sauce/dressing === * [[Cookbook:Palm Oil|Palm oil]] * [[Cookbook:Potash|Potash (akanwu/kaun)]] – helps thicken and emulsify the sauce * [[Cookbook:Crayfish|Ground crayfish]] * [[Cookbook:Pepper|Pepper]] (fresh or dry, to taste) * Salt * Seasoning cubes (optional) === Traditional add-ins === * Ugba (very important for authentic flavor) * Smoked fish or dried fish * Ponmo (cow skin) === Vegetables & garnishes === * [[Cookbook:Utazi|Utazi leaves]] (adds a slight bitter taste) * [[Cookbook:Garden Egg|Garden eggs (African eggplant)]] * Onions === Optional extras (depending on preference) === * [[wikipedia:Stockfish|Stockfish]] * Kpomo sauce or meat bits * Fresh herbs == PROCEDURE == * Soak the dried Abacha in warm water until soft, then drain. * Mix palm oil with a little dissolved potash until it thickens. * Add crayfish, pepper, salt, and seasoning to the oil. * Combine the softened Abacha with the sauce. * Stir in Ugba and any proteins like fish or ponmo. * Add onions, utazi leaves, and garden eggs. * Mix well and serve. [[Category:Easy recipes]] [[Category:Nigerian recipes]] 240k0i35kh1vpi9abwexfh5kit7hnxf 4634131 4634085 2026-05-04T17:45:35Z Kittycataclysm 3371989 incomplete 4634131 wikitext text/x-wiki {{Incomplete recipe|reason=excessive capitalization, missing quantities, missing ingredient links, missing categories, missing cookbook templates, stylistic adjustments needed, incorrect formatting}} '''Abacha''', often called African salad, is a traditional dish from southeastern Nigeria, especially among the Igbo people. Despite the name “salad,” it’s quite different from Western salads—Abacha is hearty, flavorful, and deeply rooted in local culinary traditions. At its core, Abacha is made from dried, shredded cassava. The cassava is harvested, cooked, sliced into thin strips, and then sun-dried. Before serving, these strips are soaked in water to soften them, giving the dish its signature chewy texture. What really defines Abacha is its rich, spicy dressing. This is typically made with palm oil, potash (which helps emulsify the oil), ground crayfish, pepper, salt, and sometimes fermented ingredients like ugba (oil bean seeds). The mixture coats the cassava, creating a bold, slightly tangy flavor. == INGREDIENTS == * [[Cookbook:Cassava|Dried shredded cassava]] (Abacha) === For the sauce/dressing === * [[Cookbook:Palm Oil|Palm oil]] * [[Cookbook:Potash|Potash (akanwu/kaun)]] – helps thicken and emulsify the sauce * [[Cookbook:Crayfish|Ground crayfish]] * [[Cookbook:Pepper|Pepper]] (fresh or dry, to taste) * Salt * Seasoning cubes (optional) === Traditional add-ins === * Ugba (very important for authentic flavor) * Smoked fish or dried fish * Ponmo (cow skin) === Vegetables & garnishes === * [[Cookbook:Utazi|Utazi leaves]] (adds a slight bitter taste) * [[Cookbook:Garden Egg|Garden eggs (African eggplant)]] * Onions === Optional extras (depending on preference) === * [[wikipedia:Stockfish|Stockfish]] * Kpomo sauce or meat bits * Fresh herbs == PROCEDURE == * Soak the dried Abacha in warm water until soft, then drain. * Mix palm oil with a little dissolved potash until it thickens. * Add crayfish, pepper, salt, and seasoning to the oil. * Combine the softened Abacha with the sauce. * Stir in Ugba and any proteins like fish or ponmo. * Add onions, utazi leaves, and garden eggs. * Mix well and serve. [[Category:Easy recipes]] [[Category:Nigerian recipes]] 40oq9rgsim0brz9p3lrv3f0p6zjcmlu 102 483116 4634102 2026-05-04T15:45:01Z SHE-LOVES-BRIAN 3581157 added categories 4634102 wikitext text/x-wiki Nigerian starch is a traditional cassava-based “swallow” food popular among the Urhobo people and Itsekiri people. It’s cooked into a smooth, stretchy dough and is usually eaten with soups like [[Cookbook:Banga Soup|Banga soup]]. It has a mild taste and soft texture, making it ideal for pairing with rich, flavorful soups. == INGREDIENTS == * Cassava starch * [[Cookbook:Water|water]] == PROCEDURE == Boil water, mix cassava starch with cold water, then pour it into the boiling water while stirring. Cook until it thickens into a smooth, stretchy dough, then serve with soups like [[Cookbook:Banga Soup|Banga soup.]] [[Category:Nigerian recipe]] [[Category:Traditional recipie]] [[Category:Swallow recipie]] e64y80h2r5zys5litbl4f4974ykyein 4634105 4634102 2026-05-04T15:47:36Z SHE-LOVES-BRIAN 3581157 added categories 4634105 wikitext text/x-wiki Nigerian starch is a traditional cassava-based “swallow” food popular among the Urhobo people and Itsekiri people. It’s cooked into a smooth, stretchy dough and is usually eaten with soups like [[Cookbook:Banga Soup|Banga soup]]. It has a mild taste and soft texture, making it ideal for pairing with rich, flavorful soups. == INGREDIENTS == * Cassava starch * [[Cookbook:Water|water]] == PROCEDURE == Boil water, mix cassava starch with cold water, then pour it into the boiling water while stirring. Cook until it thickens into a smooth, stretchy dough, then serve with soups like [[Cookbook:Banga Soup|Banga soup.]] [[Category:Nigerian recipes]] [[Category:Traditional recipes]] [[Category:Recipes by origin]] jzzu6do4i5856ygl1au0au29qcch4ok 4634129 4634105 2026-05-04T17:43:34Z Kittycataclysm 3371989 incomplete 4634129 wikitext text/x-wiki {{Incomplete recipe|reason=excessive capitalization, missing quantities, missing ingredient links, missing categories, missing cookbook templates, stylistic adjustments needed, incorrect formatting, ingredients not in order}} Nigerian starch is a traditional cassava-based “swallow” food popular among the Urhobo people and Itsekiri people. It’s cooked into a smooth, stretchy dough and is usually eaten with soups like [[Cookbook:Banga Soup|Banga soup]]. It has a mild taste and soft texture, making it ideal for pairing with rich, flavorful soups. == INGREDIENTS == * Cassava starch * [[Cookbook:Water|water]] == PROCEDURE == Boil water, mix cassava starch with cold water, then pour it into the boiling water while stirring. Cook until it thickens into a smooth, stretchy dough, then serve with soups like [[Cookbook:Banga Soup|Banga soup.]] [[Category:Nigerian recipes]] [[Category:Traditional recipes]] [[Category:Recipes by origin]] k1qhis0zmjdfism6zlamk9n9k3j7hz8 102 483117 4634109 2026-05-04T16:07:07Z SHE-LOVES-BRIAN 3581157 added a wiki link and categories 4634109 wikitext text/x-wiki Ofada stew, also known as [[Cookbook:Ayamase Jollof Rice|ayamase]], is a rich and spicy Nigerian sauce popular in southwestern Nigeria, especially among the Yoruba people. It is made mainly from green peppers, palm oil, locust beans (iru), and assorted meats. The stew is known for its strong aroma, deep flavor, and slightly smoky taste, which comes from the way the palm oil is prepared. It is traditionally served with [[Cookbook:Ofada rice|Ofada rice]], making it a classic and culturally significant dish enjoyed at homes and local eateries. == INGREDIENTS == * [[Cookbook:Palm Oil|Palm oil]] * Green peppers(Tatashe) * scotch bonnet peppers (Ata rodo} * Onions * Locust beans (Iru) * [[Cookbook:Assorted meat|Assorted meats]] ([[Cookbook:Beef|Beef,]]Tripe,cow skin) * Boiled Eggs (optional) * Seasoning cubes * [[Cookbook:Salt|Salt]] == PROCEDURE == * '''Prepare the peppers''' Blend the green peppers and Scotch bonnet peppers roughly (not too smooth) and set aside. * '''Boil the meat''' Season and boil the assorted meats until tender. Keep the stock. * '''Bleach the palm oil''' Heat the palm oil in a pot until it becomes very hot and slightly darker, then allow it to cool a bit. * '''Fry the onions and iru''' Add chopped onions and locust beans (iru) to the oil and fry briefly to release the aroma. * '''Add blended peppers''' Pour in the blended pepper mixture and cook, stirring occasionally, until the sauce thickens and the oil begins to rise to the top. * '''Add meat and stock''' Add the cooked meats and a little meat stock, then stir well. * '''Season and simmer''' Add seasoning cubes and salt to taste, then let it simmer for several minutes so the flavors combine. * '''Add eggs (optional)''' Add boiled eggs and allow them to absorb the sauce. * '''Serve''' Serve hot with Ofada rice. [[Category:Recipes by origin]] [[Category:Nigerian recipes]] [[Category:Recipes using meat]] jd74xvfnm1luaiaa41js8tf5h19d4pt 4634128 4634109 2026-05-04T17:43:10Z Kittycataclysm 3371989 incomplete 4634128 wikitext text/x-wiki {{Incomplete recipe|reason=excessive capitalization, missing quantities, missing ingredient links, missing categories, missing cookbook templates, stylistic adjustments needed, incorrect formatting, ingredients not in order}} Ofada stew, also known as [[Cookbook:Ayamase Jollof Rice|ayamase]], is a rich and spicy Nigerian sauce popular in southwestern Nigeria, especially among the Yoruba people. It is made mainly from green peppers, palm oil, locust beans (iru), and assorted meats. The stew is known for its strong aroma, deep flavor, and slightly smoky taste, which comes from the way the palm oil is prepared. It is traditionally served with [[Cookbook:Ofada rice|Ofada rice]], making it a classic and culturally significant dish enjoyed at homes and local eateries. == INGREDIENTS == * [[Cookbook:Palm Oil|Palm oil]] * Green peppers(Tatashe) * scotch bonnet peppers (Ata rodo} * Onions * Locust beans (Iru) * [[Cookbook:Assorted meat|Assorted meats]] ([[Cookbook:Beef|Beef,]]Tripe,cow skin) * Boiled Eggs (optional) * Seasoning cubes * [[Cookbook:Salt|Salt]] == PROCEDURE == * '''Prepare the peppers''' Blend the green peppers and Scotch bonnet peppers roughly (not too smooth) and set aside. * '''Boil the meat''' Season and boil the assorted meats until tender. Keep the stock. * '''Bleach the palm oil''' Heat the palm oil in a pot until it becomes very hot and slightly darker, then allow it to cool a bit. * '''Fry the onions and iru''' Add chopped onions and locust beans (iru) to the oil and fry briefly to release the aroma. * '''Add blended peppers''' Pour in the blended pepper mixture and cook, stirring occasionally, until the sauce thickens and the oil begins to rise to the top. * '''Add meat and stock''' Add the cooked meats and a little meat stock, then stir well. * '''Season and simmer''' Add seasoning cubes and salt to taste, then let it simmer for several minutes so the flavors combine. * '''Add eggs (optional)''' Add boiled eggs and allow them to absorb the sauce. * '''Serve''' Serve hot with Ofada rice. [[Category:Recipes by origin]] [[Category:Nigerian recipes]] [[Category:Recipes using meat]] 8jopvkd6xvc5ienx27uo1048pzm5irs 102 483118 4634112 2026-05-04T16:13:48Z SHE-LOVES-BRIAN 3581157 added a wiki link and categories 4634112 wikitext text/x-wiki Ofada rice is a traditional, unpolished Nigerian rice with a distinct aroma and earthy taste, popular among the Yoruba people. It is usually served with a rich, spicy sauce called [[Cookbook:Ofada stew|Ofada stew.]] == INGREDIENTS == * Ofada rice * [[Cookbook:Water|Water]] * [[Cookbook:Salt|Salt]] (optional) == PROCEDURE == Wash and clean Ofada rice, parboil and rinse it, then cook in fresh water until soft. Add a little salt if desired and serve with [[Cookbook:Ofada stew|Ofada stew.]] [[Category:Recipes by origin]] [[Category:Nigerian recipes]] [[Category:Traditional recipes]] fpxcnrcq67v22r3smdly8lawjybqcdq 4634127 4634112 2026-05-04T17:42:56Z Kittycataclysm 3371989 incomplete 4634127 wikitext text/x-wiki {{Incomplete recipe|reason=excessive capitalization, missing quantities, missing ingredient links, missing categories, missing cookbook templates, stylistic adjustments needed, incorrect formatting, ingredients not in order}} Ofada rice is a traditional, unpolished Nigerian rice with a distinct aroma and earthy taste, popular among the Yoruba people. It is usually served with a rich, spicy sauce called [[Cookbook:Ofada stew|Ofada stew.]] == INGREDIENTS == * Ofada rice * [[Cookbook:Water|Water]] * [[Cookbook:Salt|Salt]] (optional) == PROCEDURE == Wash and clean Ofada rice, parboil and rinse it, then cook in fresh water until soft. Add a little salt if desired and serve with [[Cookbook:Ofada stew|Ofada stew.]] [[Category:Recipes by origin]] [[Category:Nigerian recipes]] [[Category:Traditional recipes]] n1mqvucqliqzilex36k0zd1vgm6gz39 102 483120 4634121 2026-05-04T17:21:08Z SHE-LOVES-BRIAN 3581157 added a wiki link and categories 4634121 wikitext text/x-wiki Isi ewu is a traditional dish of the Igbo people made from goat head cooked in a rich, spicy palm oil sauce. It is a flavorful delicacy often enjoyed at gatherings and with [[Drinking Water/Distillation|drinks]]. == INGREDIENTS == * [[Cookbook:Goat head|Goat head]] * Scotch bonnet peppers * Ground crayfish * Utazi leaves * Seasoning cubes * [[Cookbook:Salt|Salt]] * EHURU (Calabash nutmeg) * Potash (akanwu) * Onions * Palm oil == PROCEDURE == * '''Clean and cut the goat head''' Wash thoroughly and cut into smaller pieces. * '''Cook the [[Cookbook:Meat|meat]]''' Season with salt, onions, and seasoning cubes, then boil until very tender. Keep the stock. * '''Prepare the sauce base''' Dissolve a small amount of potash (akanwu) in water and mix with palm oil until it thickens and turns yellow. * '''Add [[Cookbook:Herbs and Spices|spices]] and flavoring''' Stir in ground crayfish, ehuru, and blended peppers. * '''Combine with [[Cookbook:Meat|meat]]''' Add the cooked goat head and a little stock, then mix well. * '''Simmer''' Allow it to cook for a few minutes so the sauce coats the meat properly. * '''Add utazi leaves''' Sprinkle chopped utazi leaves for a slightly bitter taste. * '''Serve hot''' Best enjoyed fresh, often with drinks. [[Category:African cuisines]] [[Category:Traditional recipes]] [[Category:Recipes using meat]] rjyrq88yoalwkcocvrk2j98wxix8ly6 4634125 4634121 2026-05-04T17:41:11Z Kittycataclysm 3371989 incomplete 4634125 wikitext text/x-wiki {{Incomplete recipe|reason=excessive capitalization, missing quantities, missing ingredient links, missing categories, missing cookbook templates, stylistic adjustments needed}} Isi ewu is a traditional dish of the Igbo people made from goat head cooked in a rich, spicy palm oil sauce. It is a flavorful delicacy often enjoyed at gatherings and with [[Drinking Water/Distillation|drinks]]. == INGREDIENTS == * [[Cookbook:Goat head|Goat head]] * Scotch bonnet peppers * Ground crayfish * Utazi leaves * Seasoning cubes * [[Cookbook:Salt|Salt]] * EHURU (Calabash nutmeg) * Potash (akanwu) * Onions * Palm oil == PROCEDURE == * '''Clean and cut the goat head''' Wash thoroughly and cut into smaller pieces. * '''Cook the [[Cookbook:Meat|meat]]''' Season with salt, onions, and seasoning cubes, then boil until very tender. Keep the stock. * '''Prepare the sauce base''' Dissolve a small amount of potash (akanwu) in water and mix with palm oil until it thickens and turns yellow. * '''Add [[Cookbook:Herbs and Spices|spices]] and flavoring''' Stir in ground crayfish, ehuru, and blended peppers. * '''Combine with [[Cookbook:Meat|meat]]''' Add the cooked goat head and a little stock, then mix well. * '''Simmer''' Allow it to cook for a few minutes so the sauce coats the meat properly. * '''Add utazi leaves''' Sprinkle chopped utazi leaves for a slightly bitter taste. * '''Serve hot''' Best enjoyed fresh, often with drinks. [[Category:African cuisines]] [[Category:Traditional recipes]] [[Category:Recipes using meat]] bgr68mxv6w59lfqlvki78galvpk2h6y 4634126 4634125 2026-05-04T17:42:26Z Kittycataclysm 3371989 add 4634126 wikitext text/x-wiki {{Incomplete recipe|reason=excessive capitalization, missing quantities, missing ingredient links, missing categories, missing cookbook templates, stylistic adjustments needed, incorrect formatting, ingredients not in order}} Isi ewu is a traditional dish of the Igbo people made from goat head cooked in a rich, spicy palm oil sauce. It is a flavorful delicacy often enjoyed at gatherings and with [[Drinking Water/Distillation|drinks]]. == INGREDIENTS == * [[Cookbook:Goat head|Goat head]] * Scotch bonnet peppers * Ground crayfish * Utazi leaves * Seasoning cubes * [[Cookbook:Salt|Salt]] * EHURU (Calabash nutmeg) * Potash (akanwu) * Onions * Palm oil == PROCEDURE == * '''Clean and cut the goat head''' Wash thoroughly and cut into smaller pieces. * '''Cook the [[Cookbook:Meat|meat]]''' Season with salt, onions, and seasoning cubes, then boil until very tender. Keep the stock. * '''Prepare the sauce base''' Dissolve a small amount of potash (akanwu) in water and mix with palm oil until it thickens and turns yellow. * '''Add [[Cookbook:Herbs and Spices|spices]] and flavoring''' Stir in ground crayfish, ehuru, and blended peppers. * '''Combine with [[Cookbook:Meat|meat]]''' Add the cooked goat head and a little stock, then mix well. * '''Simmer''' Allow it to cook for a few minutes so the sauce coats the meat properly. * '''Add utazi leaves''' Sprinkle chopped utazi leaves for a slightly bitter taste. * '''Serve hot''' Best enjoyed fresh, often with drinks. [[Category:African cuisines]] [[Category:Traditional recipes]] [[Category:Recipes using meat]] r2m4juwjdpc0f9a24vh04wxnxughgmo 3 483121 4634130 2026-05-04T17:43:59Z Kittycataclysm 3371989 /* Welcome to the Cookbook */ new section 4634130 wikitext text/x-wiki == Welcome to the Cookbook == {{mbox | type = | image = [[File:Foodlogo2.svg|40px]] | imageright = | style = | textstyle = | text = Hello and thank you for your recent contribution to the [[Cookbook:Table of Contents|Wikibooks Cookbook]]! When adding to the Cookbook, please make sure all content conforms to [[Cookbook:Policy|Cookbook policy]], including the [[Cookbook:Manual of Style|manual of style]] and standard page templates. Feel free to let me know if you need any help or have any questions! {{#ifeq: |||<br>'''Additional details:''' }} | small = | smallimage = | smallimageright = | smalltext = }} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:43, 4 May 2026 (UTC) tfrfrx56iub26h9f0btukniiy8kyg03 3 483122 4634132 2026-05-04T17:45:52Z Kittycataclysm 3371989 /* Welcome to the Cookbook */ new section 4634132 wikitext text/x-wiki == Welcome to the Cookbook == {{mbox | type = | image = [[File:Foodlogo2.svg|40px]] | imageright = | style = | textstyle = | text = Hello and thank you for your recent contribution to the [[Cookbook:Table of Contents|Wikibooks Cookbook]]! When adding to the Cookbook, please make sure all content conforms to [[Cookbook:Policy|Cookbook policy]], including the [[Cookbook:Manual of Style|manual of style]] and standard page templates. Feel free to let me know if you need any help or have any questions! {{#ifeq: |||<br>'''Additional details:''' }} | small = | smallimage = | smallimageright = | smalltext = }} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:45, 4 May 2026 (UTC) itgwzf0lvb91yoxdq06w2rhi649aend 10 483123 4634136 2026-05-04T17:55:28Z Kittycataclysm 3371989 Created page with "{{Documentation subpage}} {{possible-risk}} <!-- Please add categories and interwikis to the bottom of this page, and also add interwikis to Wikidata. --> === Usage === This Cookbook template is for in-line insertion when a quantity is missing. === See also === <includeonly> <!-- Categories and interwikis go here, and interwikis also go on Wikidata. --> [[Category:Cookbook templates]] </includeonly>" 4634136 wikitext text/x-wiki {{Documentation subpage}} {{possible-risk}} <!-- Please add categories and interwikis to the bottom of this page, and also add interwikis to Wikidata. --> === Usage === This Cookbook template is for in-line insertion when a quantity is missing. === See also === <includeonly> <!-- Categories and interwikis go here, and interwikis also go on Wikidata. --> [[Category:Cookbook templates]] </includeonly> 2z11wfszvn4bgtgtbkhucgabrg56eip 4634143 4634136 2026-05-04T18:11:53Z Kittycataclysm 3371989 add doc from [[Template:Citation needed]] 4634143 wikitext text/x-wiki {{Documentation subpage}} {{possible-risk}} <!-- Please add categories and interwikis to the bottom of this page, and also add interwikis to Wikidata. --> === Usage === This Cookbook template is for in-line insertion when a quantity is missing. The template produces a superscripted notation like the following: :Add water{{How much}} and stir. You may append a date to the template in the following format: :<code>{{Tlx|How much|date{{=}}{{CURRENTMONTHNAME}} {{CURRENTYEAR}}}}</code> '''Notes''': * Substitution of this template will automatically fill the date parameter. * The date parameter consists of the name of the current month and the year only, not full dates. The names of the months are capitalized in English. ''Any deviation from these two rules will result in an "invalid date parameter" error.'' You can also add the (non-displayed) {{para|reason}} parameter to leave a better record for future editors. === See also === <includeonly> <!-- Categories and interwikis go here, and interwikis also go on Wikidata. --> [[Category:Cookbook templates]] </includeonly> {{Documentation subpage}} 5v9k608x7rlbtftlc1ijpozrvmesox1 4634144 4634143 2026-05-04T18:12:15Z Kittycataclysm 3371989 4634144 wikitext text/x-wiki {{Documentation subpage}} {{possible-risk}} <!-- Please add categories and interwikis to the bottom of this page, and also add interwikis to Wikidata. --> === Usage === This Cookbook template is for in-line insertion when a quantity is missing. The template produces a superscripted notation like the following: Add water{{How much}} and stir. You may append a date to the template in the following format: :<code>{{Tlx|How much|date{{=}}{{CURRENTMONTHNAME}} {{CURRENTYEAR}}}}</code> '''Notes''': * Substitution of this template will automatically fill the date parameter. * The date parameter consists of the name of the current month and the year only, not full dates. The names of the months are capitalized in English. ''Any deviation from these two rules will result in an "invalid date parameter" error.'' You can also add the (non-displayed) {{para|reason}} parameter to leave a better record for future editors. === See also === <includeonly> <!-- Categories and interwikis go here, and interwikis also go on Wikidata. --> [[Category:Cookbook templates]] </includeonly> {{Documentation subpage}} ovd8a2mlqi1t4hjux99s6bovma5qwwj 102 483124 4634142 2026-05-04T18:06:37Z Bamjos 3505411 Created cookbook Afrocuisine 2026 4634142 wikitext text/x-wiki {{Ingredient}} '''Rice''' is the seed of a monocot plant, it's the most important staple food for a large part of the world's human population.<ref>{{Cite web |title=Rice Dishes Archives |url=https://sisijemimah.com/category/rice-dishes-3/ |access-date=2026-05-04 |website=Sisi Jemimah |language=en-GB}}</ref> Cooking a white rice with fish soup is very delicious. {{Ingredient summary | Image = [[File:Rice grains (IRRI).jpg|300px]] | Category = Cereals }} [[File:White rice at a restaurant.jpg|thumb|Image of white rice]] == Ingredients == === Rice === * Raw [[Cookbook:Rice|rice]] * [[Cookbook:Water|water]] * Salt === Fish Soup === * [[Cookbook:Fish|Fish]] * [[Cookbook:Pepper|Pepper]] * [[Cookbook:Onion|Onion]] * Tomatoes * salt * [[Cookbook:Maggi|Maggi]] * Groundnut oil * [[Cookbook:Thyme|Thyme]] == Preparation == === Rice === # Put your raw rice inside a bowl # Raise it well # Put water on the fire till it boil # Pour the washed rice inside the boiled water # Allow it to boil for 15 minutes # Add salt to it and check if it is soft enough before adding water again # Leave it on fire till it get dry === Fishe soup === # Boil the fish with seasoning for 10 minutes and put it in a plate # Heat groundnut oil in a pot; sauté onions for 2–3 minutes. # Add blended tomatoes, pepper, and season with salt, , and thyme. Bring to a simmer. # Add the boiled fish (cut into pieces) and simmer for 3–5 minutes until the fish is opaque and flakes easily. # Serve the soup with the Rice<ref>{{Cite web |last=Rice |first=Jess |date=2025-04-04 |title=This Fish soup is the BEST easy high-protein lunch or dinner! |url=https://www.budgetbytes.com/budget-friendly-fish-soup/ |access-date=2026-05-04 |website=Budget Bytes |language=en-US}}</ref> == References == [[Category:Recipes by diet]] [[Category:Grains]] [[Category:Recipes by ingredient]] l1xo8sxodzbtomkxt6pm4v0vwhjmomd 103 483125 4634159 2026-05-04T18:46:50Z Kittycataclysm 3371989 /* Recipe questions */ new section 4634159 wikitext text/x-wiki == Recipe questions == @[[User:Fatimah Bello|Fatimah Bello]] I have a few clarifying questions for this recipe: * Is ogiri okpei the same as iru? My understanding was that using locust beans makes it iru and not ogiri. * Are you adding water when you cook the meat? If so, how much? Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 4 May 2026 (UTC) 6sef0fncx46bq4vmragqyb6jobs2gc5 0 483126 4634195 2026-05-04T22:35:15Z ~2026-21296-62 3574173 Created page with "==2016 vote== Crooked Hillary<br> Trump<br> ''Art of the Deal''<br> But the emails<br> Pizzagate<br> Qanon<br> Feel the Bern<br> ==Covid19== Corona<br> Lockdown<br> Social distance<br> Tiger King<br>" 4634195 wikitext text/x-wiki ==2016 vote== Crooked Hillary<br> Trump<br> ''Art of the Deal''<br> But the emails<br> Pizzagate<br> Qanon<br> Feel the Bern<br> ==Covid19== Corona<br> Lockdown<br> Social distance<br> Tiger King<br> 2i2qfnbpxbv8md4zb7ll8lkg4d4es1z 4634213 4634195 2026-05-05T02:34:27Z MathXplore 3097823 Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]] 4634213 wikitext text/x-wiki ==2016 vote== Crooked Hillary<br> Trump<br> ''Art of the Deal''<br> But the emails<br> Pizzagate<br> Qanon<br> Feel the Bern<br> ==Covid19== Corona<br> Lockdown<br> Social distance<br> Tiger King<br> {{BookCat}} ensxpok2kiwtb59nwzmob08f93fsw43 4634214 4634213 2026-05-05T02:34:52Z MathXplore 3097823 Adding {{qr-em}} tag 4634214 wikitext text/x-wiki {{qr-em|1=}} ==2016 vote== Crooked Hillary<br> Trump<br> ''Art of the Deal''<br> But the emails<br> Pizzagate<br> Qanon<br> Feel the Bern<br> ==Covid19== Corona<br> Lockdown<br> Social distance<br> Tiger King<br> {{BookCat}} dixi2uegve46esqpwhl0bycs63o9rfw 102 483127 4634196 2026-05-04T22:37:08Z NiferO 3505520 Created article 4634196 wikitext text/x-wiki {{Recipe summary | Category = Zambian recipes | Servings = 4 | Medium = 2 |Cooking time = 20 minutes |Cuisine = Zambian }} [[File:Nshima and Fish traditionally prepared.jpg|thumb|Nshima_and_Fish_traditionally_prepared]] '''Nshima''' is a staple maize dish meal wisely consumed in Zambia and neighboring regions. Nshima is widely eaten in much of Sub-Saharan Africa actually, where it is known by different names in different countries e.g Ugali (Uganda), Sadza (Zimbabwe), Tuwo (Nigeria), Pap (South Africa) etc. == Ingredients == * 3 cups of Mealie Meal/ White [[Cookbook:Cornmeal|Cornmeal]] * 1 Litre Boiling water * 1 1/2 cups Cold Water == Techniques == # Sauce pan # Cooking stick # Cornmeal # Water == Procedure == # Boil 1 Litre of water in advance, in a Kettle or Sauce pan. # Once the water boils, combine 1 cup of Cornmeal or Meal as we call it, with 1 1/2 cups of cold water in a sauce pan, to make a smooth paste. A flat cooking stick is ideal for this. # Transfer the Cornmeal paste to the stove (set at medium high heat), and then slowly pour about 700ml of boiling water into the saucepan, stirring continuously, making sure the mixture is smooth and well combined. # This should lead to a smooth porridge, almost creamy. Allow this to boil for at least 10 minutes, covered. # Remove the cover after 10 minutes and begin to add the remaining Cornmeal to the porridge, a little at a time, making sure it is well combined, before adding some more. # The porridge should stiffen up quickly with each addition of Cornmeal, and you will need to exert a bit of muscle to mix this well, smoothing out any lumps that form in the process # Remove from the stove after the 10 minutes, and using a smooth serving spoon, scoop out the Nshima, one lump at a time and transfer into your serving dish. == Serving == protein (meat, fish, poultry, or beans) and side of green vegetables [[Category:Zambian recipes]] [[Category:Recipes by ingredient]] [[Category:Recipes by diet]] [[Category:Recipes by preparation technique]] [[Category:Recipes by difficulty]] [[Category:Recipes]] 560v8izvfyg8m4imoqva9juwnaae0je 4634197 4634196 2026-05-04T22:57:27Z NiferO 3505520 Added wiki Links 4634197 wikitext text/x-wiki {{Recipe summary | Category = Zambian recipes | Servings = 4 | Medium = 2 |Cooking time = 20 minutes |Cuisine = Zambian }} [[File:Nshima and Fish traditionally prepared.jpg|thumb|Nshima_and_Fish_traditionally_prepared]] '''Nshima''' is a staple maize dish meal wisely consumed in Zambia and neighboring regions. Nshima is widely eaten in much of Sub-Saharan Africa actually, where it is known by different names in different countries e.g Ugali (Uganda), Sadza (Zimbabwe), Tuwo (Nigeria), Pap (South Africa) etc. == Ingredients == * 3 cups of Mealie Meal/ White [[Cookbook:Cornmeal|Cornmeal]] * 1 Litre Boiling water * 1 1/2 cups Cold Water == Techniques == # Sauce pan # Cooking stick # Cornmeal # [[Cookbook:Water|Water]] == Procedure == # Boil 1 Litre of water in advance, in a Kettle or Sauce pan. # Once the water boils, combine 1 cup of Cornmeal or Meal as we call it, with 1 1/2 cups of cold water in a sauce pan, to make a smooth paste. A flat cooking stick is ideal for this. # Transfer the Cornmeal paste to the stove (set at medium high heat), and then slowly pour about 700ml of boiling water into the saucepan, stirring continuously, making sure the mixture is smooth and well combined. # This should lead to a smooth porridge, almost creamy. Allow this to boil for at least 10 minutes, covered. # Remove the cover after 10 minutes and begin to add the remaining Cornmeal to the porridge, a little at a time, making sure it is well combined, before adding some more. # The porridge should stiffen up quickly with each addition of Cornmeal, and you will need to exert a bit of muscle to mix this well, smoothing out any lumps that form in the process # Remove from the stove after the 10 minutes, and using a smooth serving spoon, scoop out the Nshima, one lump at a time and transfer into your serving dish. == Serving == protein (meat, fish, poultry, or [[Cookbook:Beans porridge|beans]]) and side of green [[Cookbook:Vegetable|vegetables]] [[Category:Zambian recipes]] [[Category:Recipes by ingredient]] [[Category:Recipes by diet]] [[Category:Recipes by preparation technique]] [[Category:Recipes by difficulty]] [[Category:Recipes]] 5ccluiw5z97tq72fjq4d05zle14824x 102 483128 4634230 2026-05-05T08:38:05Z Itzv1ktor 3581155 Created Article 4634230 wikitext text/x-wiki '''Black soup (Omoebe)''' is a traditional Nigerian delicacy, especially popular among the Edo people of southern Nigeria. It’s known for its dark color, rich flavor, and strong nutritional value.“Omoebe” refers to the leaves used to make the soup. These leaves naturally darken when cooked, giving the soup its signature black appearance. == INGREDIENTS == * Fresh Omoebe leaves (or substitutes like bitter leaf and scent leaf) * Assorted meats (beef, goat meat, tripe) * Dried or smoked fish * Palm oil * Ground crayfish * Pepper and seasoning * Local spices like [[Cookbook:Uziza|uziza]] and ehuru == PROCEDURE == * '''Prepare the leaves''' Wash and squeeze the omoebe leaves until they release their dark color. Set aside. * '''Cook the meat and fish''' Boil assorted meat and dried fish with pepper, seasoning, and onions until tender. * '''Add palm oil & spices''' Pour in palm oil, then add ground crayfish, pepper, and local spices like ehuru and uziza. * '''Add the leaves''' Put in the prepared omoebe leaves and stir well. * '''Simmer''' Let it cook for a few minutes until it thickens and the flavors combine. * '''Serve hot''' Enjoy with pounded yam, fufu, or garri (eba). htiwle0nacwhx1m7zphc1k6fr2w5det 4634231 4634230 2026-05-05T08:44:26Z Itzv1ktor 3581155 Added categories and wiki links 4634231 wikitext text/x-wiki '''Black soup (Omoebe)''' is a traditional Nigerian delicacy, especially popular among the Edo people of southern Nigeria. It’s known for its dark color, rich flavor, and strong nutritional value.“Omoebe” refers to the leaves used to make the soup. These leaves naturally darken when cooked, giving the soup its signature black appearance. == INGREDIENTS == * Fresh Omoebe leaves (or substitutes like bitter leaf and scent leaf) * Assorted meats (beef, goat meat, tripe) * Dried or smoked fish * Palm oil * Ground crayfish * Pepper and seasoning * Local spices like [[Cookbook:Uziza|uziza]] and ehuru == PROCEDURE == * '''Prepare the leaves''' Wash and squeeze the omoebe leaves until they release their dark color. Set aside. * '''Cook the meat and fish''' Boil assorted meat and dried fish with pepper, seasoning, and onions until tender. * '''Add palm oil & spices''' Pour in palm oil, then add ground crayfish, pepper, and local spices like ehuru and uziza. * '''Add the leaves''' Put in the prepared omoebe leaves and stir well. * '''Simmer''' Let it cook for a few minutes until it thickens and the flavors combine. * '''Serve hot''' Enjoy with pounded yam, fufu, or garri (eba). [[Category:Nigerian recipes]] dvtfji1jzjeq3oj6uk15mrkmup0i3qw 1 483129 4634235 2026-05-05T08:49:31Z ~2026-27092-60 3581372 /* Truck simulator nepal */ new section 4634235 wikitext text/x-wiki == Truck simulator nepal == this game is real stick ane always system is working [[Special:Contributions/&#126;2026-27092-60|&#126;2026-27092-60]] ([[User talk:&#126;2026-27092-60|talk]]) 08:49, 5 May 2026 (UTC) isfcytu8si04k7i3zbe5y54cwrp7raw 4634251 4634235 2026-05-05T10:43:42Z MathXplore 3097823 Marking for speedy deletion: Test page 4634251 wikitext text/x-wiki <noinclude>{{Delete|example=false|Test page}}</noinclude> == Truck simulator nepal == this game is real stick ane always system is working [[Special:Contributions/&#126;2026-27092-60|&#126;2026-27092-60]] ([[User talk:&#126;2026-27092-60|talk]]) 08:49, 5 May 2026 (UTC) ppp8ixdhfhll6huoplxrzcg1awkpvof 0 483130 4634237 2026-05-05T08:55:57Z ~2026-26995-93 3581107 Published page. 4634237 wikitext text/x-wiki {{Chess Opening Theory/Position|Caro-Kann Defence: Edinburgh Variation |eco=[[Chess/ECOB|B12]] |parent=[[../|Caro-Kann Defense: Modern Variation]] }} {{Chess/sideline}} = Caro-Kann Defence: Edinburgh Variation = == 3...Qb6 == The Edinburgh Variation. This is a minor sideline of 3. Nd2, where Black attacks the undefended d4 pawn. '''[[/4. c3/]]''' is the main and best move. White defends their pawn with another pawn, forming a solid b2-c3-d4 pawn chain. '''[[/4. Ngf3/]]''' is another good move. White develops their g-knight to its most active square and defemds the d-pawn. ==Theory table== {{Chess Opening Theory/Table}}. 1.e4 c6 2.d4 d5 3.Nd2 Qb6 <table border="0" cellspacing="0" cellpadding="4"> <tr> <th></th> <th align="left">4</th> </tr> <tr> <th align="right"></th> <td>[[/4. c3|c3]] </td> </tr> <tr> <th align="right"></th> <td>[[/4. Ngf3|Ngf3]] </td> </tr> </table> == References == {{reflist}} {{ChessMid}} {{Chess Opening Theory/Footer}} {{BookCat}} tee9oh1j8wrxfmioym1oyl3od6u0fao 102 483131 4634239 2026-05-05T09:03:35Z Itzv1ktor 3581155 Created Article 4634239 wikitext text/x-wiki '''Native Jollof rice (Iwuk Edesi)''' is a traditional rice dish from the Efik people and Ibibio people of southern Nigeria, especially in Cross River State and Akwa Ibom State. “Iwuk Edesi” simply means '''“native rice”'''. Unlike the popular party-style Jollof rice, this version is more traditional and cooked with local ingredients that give it a distinct, earthy flavor. === What makes it different === * It is '''not tomato-based''' like regular Jollof rice * It uses '''palm oil''' instead of vegetable oil * It has a '''rich, smoky, and slightly spicy taste''' * It often includes seafood like periwinkle and dried fish == INGREDIENTS == * Rice * [[Cookbook:Palm Oil|Palm oil]] * Meat * Fish (often smoked or dried) * [[Cookbook:Crayfish|Crayfish]] * Pepper and seasoning * Local spices and sometimes scent leaves === Optional ingredient === [[Cookbook:Periwinkle (mollusc)|Periwinkle]] ( This is typically optional. But traditionally it is used) == PROCEDURE == * '''Parboil the rice''' Wash and partially cook the rice, then set aside. * '''Prepare the base''' Heat palm oil in a pot, then add chopped onions and pepper. * '''Add protein & flavor''' Add cooked meat, smoked fish, or periwinkle. Stir in ground crayfish and seasoning. * '''Build the native flavor''' Pour in a little stock (from the meat/fish) and allow it to simmer. * '''Add the rice''' Put in the parboiled rice and mix well so it absorbs the palm oil and spices. * '''Cook till done''' Cover and cook on low heat until the rice is soft and flavorful. Add scent leaves if available. * '''Serve hot''' Enjoy on its own or with extra fish or meat. 4g9z3jab849rbjt9kpghie2pfk36rdu 4634241 4634239 2026-05-05T09:07:06Z Itzv1ktor 3581155 Added categories and wiki links 4634241 wikitext text/x-wiki '''Native Jollof rice (Iwuk Edesi)''' is a traditional rice dish from the Efik people and Ibibio people of southern Nigeria, especially in Cross River State and Akwa Ibom State. “Iwuk Edesi” simply means '''“native rice”'''. Unlike the popular party-style Jollof rice, this version is more traditional and cooked with local ingredients that give it a distinct, earthy flavor. === What makes it different === * It is '''not tomato-based''' like regular Jollof rice * It uses '''palm oil''' instead of vegetable oil * It has a '''rich, smoky, and slightly spicy taste''' * It often includes seafood like periwinkle and dried fish == INGREDIENTS == * Rice * [[Cookbook:Palm Oil|Palm oil]] * Meat * Fish (often smoked or dried) * [[Cookbook:Crayfish|Crayfish]] * Pepper and seasoning * Local spices and sometimes scent leaves === Optional ingredient === [[Cookbook:Periwinkle (mollusc)|Periwinkle]] ( This is typically optional. But traditionally it is used) == PROCEDURE == * '''Parboil the rice''' Wash and partially cook the rice, then set aside. * '''Prepare the base''' Heat palm oil in a pot, then add chopped onions and pepper. * '''Add protein & flavor''' Add cooked meat, smoked fish, or periwinkle. Stir in ground crayfish and seasoning. * '''Build the native flavor''' Pour in a little stock (from the meat/fish) and allow it to simmer. * '''Add the rice''' Put in the parboiled rice and mix well so it absorbs the palm oil and spices. * '''Cook till done''' Cover and cook on low heat until the rice is soft and flavorful. Add scent leaves if available. * '''Serve hot''' Enjoy on its own or with extra fish or meat. [[Category:Nigerian recipes]] 5nuhqv1ab0pcz9pz1h4fxgmdmk3o4d5 4634242 4634241 2026-05-05T09:09:32Z Itzv1ktor 3581155 Added categories and wiki links 4634242 wikitext text/x-wiki '''Native Jollof rice (Iwuk Edesi)''' is a traditional rice dish from the Efik people and Ibibio people of southern Nigeria, especially in Cross River State and Akwa Ibom State. “Iwuk Edesi” simply means '''“native rice”'''. Unlike the popular party-style Jollof rice, this version is more traditional and cooked with local ingredients that give it a distinct, earthy flavor. === What makes it different === * It is '''not tomato-based''' like regular Jollof rice * It uses '''palm oil''' instead of vegetable oil * It has a '''rich, smoky, and slightly spicy taste''' * It often includes seafood like periwinkle and dried fish == INGREDIENTS == * Rice * [[Cookbook:Palm Oil|Palm oil]] * Meat * Fish (often smoked or dried) * [[Cookbook:Crayfish|Crayfish]] * Pepper and seasoning * Local spices and sometimes [[Cookbook:Scent Leaf|scent leave]]<nowiki/>s === Optional ingredient === [[Cookbook:Periwinkle (mollusc)|Periwinkle]] ( This is typically optional. But traditionally it is used) == PROCEDURE == * '''Parboil the rice''' Wash and partially cook the rice, then set aside. * '''Prepare the base''' Heat palm oil in a pot, then add chopped onions and pepper. * '''Add protein & flavor''' Add cooked meat, smoked fish, or periwinkle. Stir in ground crayfish and seasoning. * '''Build the native flavor''' Pour in a little stock (from the meat/fish) and allow it to simmer. * '''Add the rice''' Put in the parboiled rice and mix well so it absorbs the palm oil and spices. * '''Cook till done''' Cover and cook on low heat until the rice is soft and flavorful. Add scent leaves if available. * '''Serve hot''' Enjoy on its own or with extra fish or meat. [[Category:Nigerian recipes]] sb2acdq912e4yhfko50dsvsvjpdbed6 102 483132 4634243 2026-05-05T09:25:36Z Itzv1ktor 3581155 Created Article 4634243 wikitext text/x-wiki '''Omi Ukpoka (Corn soup)''' is a traditional Nigerian dish from the Benin people,a traditional, aromatic soup native to the Afemai people of Northern Edo State, Nigeria, particularly Agenebode.“Omi Ukpoka” simply means '''corn soup'''. It is made from blended or pounded fresh corn, giving it a naturally thick, smooth texture and a slightly sweet taste. == INGREDIENTS == * Fresh corn (blended or pounded) * [[Cookbook:Palm Oil|Palm oil]] * Fresh or dried fish * Meat * [[Cookbook:Crayfish|Ground crayfish]] * Pepper * Seasoning cubes * Salt * Onions * [[Cookbook:Scent Leaf|Scent leaves]] ( This is optional) == PROCEDURE == * '''Prepare the corn''' Blend or pound fresh corn into a smooth paste. * '''Cook the fish or meat''' Boil with seasoning, pepper, and onions until tender. * '''Add palm oil & crayfish''' Pour in palm oil and add ground crayfish, then allow it to simmer. * '''Add the corn paste''' Stir in the blended corn gradually to avoid lumps. * '''Cook and stir''' Keep stirring as it thickens into a smooth, creamy texture. * '''Add scent leaves (optional)''' For extra aroma and flavor. * '''Serve hot''' Enjoy as a light, nourishing meal. mbmjpprkljoz9npdrhuqulponiqwr6c 4634244 4634243 2026-05-05T09:29:21Z Itzv1ktor 3581155 Added categories and wiki links 4634244 wikitext text/x-wiki '''Omi Ukpoka (Corn soup)''' is a traditional Nigerian dish from the Benin people,a traditional, aromatic soup native to the Afemai people of Northern Edo State, Nigeria, particularly Agenebode.“Omi Ukpoka” simply means '''corn soup'''. It is made from blended or pounded fresh corn, giving it a naturally thick, smooth texture and a slightly sweet taste. == INGREDIENTS == * Fresh corn (blended or pounded) * [[Cookbook:Palm Oil|Palm oil]] * Fresh or dried fish * Meat * [[Cookbook:Crayfish|Ground crayfish]] * Pepper * Seasoning cubes * Salt * Onions * [[Cookbook:Scent Leaf|Scent leaves]] ( This is optional) == PROCEDURE == * '''Prepare the corn''' Blend or pound fresh corn into a smooth paste. * '''Cook the fish or meat''' Boil with seasoning, pepper, and onions until tender. * '''Add palm oil & crayfish''' Pour in palm oil and add ground crayfish, then allow it to simmer. * '''Add the corn paste''' Stir in the blended corn gradually to avoid lumps. * '''Cook and stir''' Keep stirring as it thickens into a smooth, creamy texture. * '''Add scent leaves (optional)''' For extra aroma and flavor. * '''Serve hot''' Enjoy as a light, nourishing meal. [[Category:Nigerian recipes]] lb3tw7i7rzt56gthtu4yptkea1loufp 102 483133 4634245 2026-05-05T09:56:29Z Itzv1ktor 3581155 Created Article 4634245 wikitext text/x-wiki '''Zobo''' is a popular Nigerian drink brewed ''from dried petals of the Hibiscus sabdariffa.it is a '''non-alcoholic herbal drink''' known for its deep red color, slightly tart taste.It is usually flavoured with ingredients like ginger, cloves, or pineapple and served best served chilled,especially in hot weather.'' == INGREDIENTS == * Dried hibiscus petals [[Cookbook:Hibiscus|(Hibiscus sabdariffa)]] * [[Cookbook:Ginger|Ginger]] * [[Cookbook:Clove|Cloves]] * Pineapple (fruit or peel, optional) * Sugar or sweetener (to taste) * Water * Lemon or lime (optional for extra flavour) == PROCEDURE == == 1. Sort and wash the hibiscus petals == * Pour the dried hibiscus petals into a bowl. * Pick out any dirt, sticks, or impurities. * Rinse thoroughly with clean water 2–3 times. * Drain and set aside. ---- == 2. Prepare the flavour ingredients == * Peel and slice ginger into small pieces (or blend slightly). * Wash cloves lightly. * Peel pineapple and cut into chunks (or use just the peel for stronger flavour). ---- == 3. Boil the base mixture == * Pour about '''4–6 liters of water''' into a large pot. * Add: ** Washed hibiscus petals ** Ginger ** Cloves ** Pineapple (or peel) * Cover and bring to a boil on medium heat. ---- == 4. Simmer for extraction == * Once boiling starts, reduce heat. * Let it simmer for '''20–40 minutes'''. * Stir occasionally with a wooden spoon. * You’ll notice the water turning deep red as the colour and flavour extract. == 5. Turn off heat and steep == * After simmering, turn off the heat. * Allow the mixture to '''steep for another 10–15 minutes''' for stronger taste. ---- == 6. Strain the liquid == * Place a fine sieve over a clean bowl or pot. * Carefully pour the mixture through the sieve. * Press lightly on the solids to extract more juice. * Discard the leftover pulp. ---- == 7. Sweeten and adjust flavour == * Add sugar to taste while the drink is still warm (easier to dissolve). * Stir well until fully dissolved. * Add lemon or lime juice if desired for extra freshness. ---- == 8. Cool and store == * Allow the drink to cool completely. * Pour into bottles or jugs using a funnel if needed. * Refrigerate for at least 2–4 hours before serving. == 9. Serving == * Best served chilled with ice cubes * Can be garnished with fruit slices if desired (optional) [[Category:Nigerian recipes]] [[Category:Nigerian beverages]] 0hb5hhonak9ztod6crierosavxl8l3s 102 483134 4634248 2026-05-05T10:18:12Z Itzv1ktor 3581155 Created Article 4634248 wikitext text/x-wiki '''Nigerian grilled catfish barbecue''' is a popular dish made by seasoning fresh catfish with spices and grilling it over charcoal until smoky and tender inside. It has a spicy, smoky flavor and is commonly sold at outdoor spots and street grills across Nigeria. It is often served with pepper sauce, onions, tomatoes, or sides like plantain or rice. INGREDIENTS * [[Cookbook:Catfish|Fresh catfish]] * Ground pepper (chili or [[Cookbook:Cayenne Pepper|cayenne]]) * Garlic * Ginger * Onions * [[Cookbook:Vegetable Oil|Vegetable oil]] or [[Cookbook:Olive Oil|olive oil]] * Seasoning cubes or powder * Salt * Lemon or lime juice (for cleaning and flavor) === OPTIONAL INGREDIENTS === * Ground crayfish ( This is optional for extra taste) * [[Cookbook:Thyme|Thyme]] or [[Cookbook:Curry Powder|curry powder]] == PROCEDURE == * '''Clean the fish''' Wash the catfish thoroughly with salt and lemon/lime juice to remove slime and odor. * '''Prepare marinade''' Mix pepper, garlic, ginger, onions, seasoning, salt, oil, and spices into a thick paste. * '''Marinate the fish''' Rub the mixture all over the fish and allow it to sit for at least 30 minutes (or longer for deeper flavor). * '''Preheat grill''' Heat charcoal grill until hot and steady. * '''Grill the fish''' Place the catfish on the grill and cook slowly, turning occasionally until it is well cooked, smoky, and slightly crispy outside. == SERVING == * '''Serve hot''' Enjoy with pepper sauce, onions, tomatoes, or sides like plantain or rice. [[Category:Nigerian recipes]] a2xro7q61vn2uviax8z5gqvqzylj6ph 3 483135 4634252 2026-05-05T10:43:43Z MathXplore 3097823 Notifying author of speedy deletion nomination 4634252 wikitext text/x-wiki == I have added a tag to a page you created == Hi! I'm MathXplore, and I recently reviewed your page, [[:Talk:Chemical Sciences: A Manual for CSIR-UGC National Eligibility Test for Lectureship and JRF/Vibrational circular dichroism]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. The reason I provided was: <blockquote><strong>Test page</strong></blockquote> If you believe that your page should not be deleted, please post a message on [[Talk:Chemical Sciences: A Manual for CSIR-UGC National Eligibility Test for Lectureship and JRF/Vibrational circular dichroism|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 10:43, 5 May 2026 (UTC) 2nqrjru754sjhhyfo2y3wx9b2jjqrlv 102 483137 4634255 2026-05-05T11:12:04Z Itzv1ktor 3581155 Created Article 4634255 wikitext text/x-wiki Onunu is a traditional '''Ijaw delicacy''' widely associated with places like Rivers State. It is made by pounding or mashing a combination of '''boiled yam and ripe plantain''' until it becomes smooth, soft, and slightly stretchy. Riverine soup is a traditional style of soup from the coastal and riverine areas of southern Nigeria, especially in the Niger Delta region. It is not a single recipe but a group of soups shaped by access to rivers and creeks. It is mainly made with '''seafood such as fish, crab, prawns, and periwinkles''', often cooked in '''palm oil and local spices'''. Unlike inland Nigerian soups that rely more on meat, riverine soups focus on fresh water and marine ingredients. == INGREDIENTS == * Fresh fish (croaker, catfish, or local river fish) * Crabs * Periwinkles * Prawns or shrimp * Crayfish (ground or whole) * Palm oil * Fresh pepper * Onion * Salt * Seasoning cubes or traditional seasoning * Ground crayfish === Leafy additions (optional depending on style) === * Scent leaf * Bitter leaf * Uziza leaf (gives a peppery aroma) === Thickeners (only in some versions) === * Cocoyam paste or starch (for thicker soups like “owho” style variants) === OPTIONAL: === * Snails or small amounts of meat == PROCEDURE == === FOR ONUNU: === * '''Boil the main ingredients''' Peel and cut '''yam and ripe plantain''', then boil them together in water until they are very soft. * '''Drain and prepare for mashing''' Pour out excess water and allow the boiled yam and plantain to cool slightly so they are easier to handle. * '''Pound or mash together''' Traditionally, the mixture is pounded in a mortar and pestle until smooth and stretchy. (You can also mash with a strong spoon or masher.) * '''Add palm oil and mix''' Gradually add a little '''palm oil''' while mixing to give it a soft texture, rich taste, and light orange colour. * '''Adjust texture''' Continue mixing until it becomes smooth, slightly elastic, and well combined (no lumps). === FOR RIVERINE SOUP: === * '''Clean and prepare seafood''' Wash and season fresh fish, crabs, prawns, and periwinkles with salt, pepper, and a little seasoning. Set aside. * '''Start the base''' Heat palm oil in a pot. Add chopped onions and fry lightly to release aroma. * '''Add pepper and seasoning''' Blend or pound fresh pepper and add it to the oil. Stir in ground crayfish, seasoning cubes, and salt. * '''Cook the seafood''' Add the tougher seafood first (like crab and fish) and allow it to cook and release its flavor. Then add softer seafood like prawns and periwinkles. * '''Simmer and develop flavor''' Add a little water or stock if needed and let everything simmer gently so the flavors combine. * '''Add leaves (optional)''' Stir in scent leaf, bitter leaf, or uziza leaf depending on preference. * '''Final simmer''' Cook for a few more minutes until the soup is well blended and aromatic. * '''Serve hot''' Riverine soup is usually eaten with swallows like yam-based dishes or starch. [[Category:Nigerian recipes]] rwvr77wthcnr1guwa0wvvzaopqht9ue 3 483138 4634257 2026-05-05T11:13:28Z MathXplore 3097823 Notifying author of speedy deletion nomination 4634257 wikitext text/x-wiki == I have added a tag to a page you created == Hi! I'm MathXplore, and I recently reviewed your page, [[:STUN THE WORLD]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. The reason I provided was: <blockquote><strong>Spam</strong></blockquote> If you believe that your page should not be deleted, please post a message on [[Talk:STUN THE WORLD|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathXplore|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 11:13, 5 May 2026 (UTC) olhuft2y05rhde95bguog49oc0utjp0 102 483139 4634258 2026-05-05T11:24:22Z Itzv1ktor 3581155 Created Article 4634258 wikitext text/x-wiki '''Ewa Agoyin''' is a popular Nigerian street food made from '''very soft, mashed beans''' served with a rich, spicy, and deeply caramelized pepper sauce. It is widely enjoyed across Nigeria, especially in cities like Lagos, where it is a common breakfast or lunch meal.It is commonly eaten,especially in urban areas like Lagos, and is often served with bread, plantain, or yam. It is known for being simple, filling, and very flavorful. == INGREDIENTS == * Brown beans (or honey beans) * Water * Salt === For the pepper sauce === * Dried red pepper * Onions * Palm oil * Salt === Optional INGREDIENTS === * Crayfish (for extra flavor in some versions) * A little garlic or ginger (less traditional, but sometimes used) * Seasoning cubes (optional but common) == PROCEDURE == * '''Cook the beans''' Rinse and boil beans (usually brown beans) in plenty of water until they become extremely soft and mushy. * '''Mash the beans''' Stir or lightly mash the cooked beans until you get a smooth, thick, porridge-like texture. Add a little salt to taste. * '''Prepare the pepper sauce''' Blend or grind dried pepper and boil it with chopped onions. Cook in palm oil and allow it to fry slowly until it becomes dark, thick, and smoky. * '''Season the sauce''' Add salt and seasoning cubes if desired, and continue frying until the oil rises and the sauce is well cooked. * '''Combine and serve''' Spoon the hot pepper sauce over the mashed beans and serve. == SERVING == * Often eaten with '''bread, fried plantain, or yam''' [[Category:Nigerian recipes]] [[Category:Bean recipes]] 54hf2oom09uqsmf1zpoyr3ulmhoyjaq